• No results found

Convert the Archives

In document PI Server System Management Guide (Page 187-191)

Chapter 12. Finding and Fixing Problems: the pidiag Utility

9.3 Shut Down the Retired System

9.3.3 Convert the Archives

Converting the retired systems archive requires the binary ID conversion file. This is created from the ID conversion text file created on the retired system - retiredidconv.txt:

$ piartool -idci /opt/PI/adm/retiredidconv.txt -idco /opt/PI/adm/retiredidconv.bin

Creating new conversion table: /opt/PI/adm/retiredidconv.bin... 37 input lines processed

37 names in table

The offline archive utility is used to convert the archives from the retired system. For this example, one archive will be converted and registered. Other archives are handled in a similar manner. Here is the dialog from the conversion:

$ ../bin/piarchss -id /opt/PI/adm/retiredidconv.bin -if /opt/PI/dat/piarchretired.002 -of /opt/PI/dat/piarchconv.002 PIarchss offline archive utility

Input file type: PI 3

Archive input file: piarchretired.002

Beginning first pass. Sorting input archive. Archive indicated start time: 2-Mar-98 12:51:41 Archive indicated end time: 3-Mar-98 11:09:30 Archive indicated recordcount: 2048

Processing record 1 ...

Invalid ID Conversion on input Point ID 13 . Record not processed. Primary record load completed.

Records processed: 38 Records with data: 21 Empty records: 17 Records with errors: 0 Records out of time range: 0 Records with duplicate time range: 0 Overflow record load completed.

Records processed: 157 Records with data: 155 Empty records: 0 Records with errors: 0 Records out of time range: 2

Records with duplicate time range: 0

Begining Output pass. Output archive: piarchconv.002 Processing record 1 ...

Invalid ID Conversion on input Point ID 13 . Record not processed. 22722 Loaded in 3( 1 + 2 ) Seconds 7574 Event/Sec.

80269 Archive Total seconds - ratio: 26756 Service Manager requested shutdown of piarchss

Records for points not merged will not be processed. The above dialog shows a message indicating records for PointID 13 are not processed - this is the PI Batch point that was intentionally not merged.

Note the times on the archive converted. The times overlap the primary archive on the destination system. This problem must be addressed before the converted archive can be registered. The solution is to force a shift, and combine the converted archive with the destination archive. After the shift, the destination system's archives are as follows:

$ piartool -al

Archive shift prediction:

Shift Time: 18-Jan-38 19:14:07.7930 Target Archive: /opt/PI/dat/piarch.002 Archive: /opt/PI/dat/piarch.003

PIarcfilehead [$Workfile: piarfile.cxx $ $Revision: 21 $]: Version: 4 Path: /opt/PI/dat/piarch.003

State: 4 Type: 0 Write Flag: 1 Shift Flag: 1 Record Size: 1024 Count: 2048

Offsets: Primary: 98/512 Overflow: 2047/2048 Start Time: 3-Mar-98 16:32:27

End Time: Current Time Backup Time: Never

Archive: /opt/PI/dat/piarch.001

PIarcfilehead [$Workfile: piarfile.cxx $ $Revision: 21 $]: Version: 4 Path: /opt/PI/dat/piarch.001

State: 4 Type: 0 Write Flag: 1 Shift Flag: 1 Record Size: 1024 Count: 2048

Offsets: Primary: 98/512 Overflow: 1948/2048 Start Time: 2-Mar-98 12:21:11

End Time: 3-Mar-98 16:32:27 Backup Time: Never

Archive: /opt/PI/dat/piarch.002

PIarcfilehead [$Workfile: piarfile.cxx $ $Revision: 21 $]: Version: 4 Path: /opt/PI/dat/piarch.002

State: 4 Type: 0 Write Flag: 1 Shift Flag: 1 Record Size: 1024 Count: 2048

Offsets: Primary: 1/512 Overflow: 2047/2048 Start Time: Current Time

End Time: Current Time Backup Time: Never

The converted archive and piarch.001 must be combined. For this example the conversion will be made into a dynamic size. If converting into a fixed size archive, there must be

9.3 - Shut Down the Retired System

enough space for all used records in both archives being combined. If in doubt use dynamic archives--they can always be moved into a fixed size archive later.

In the following dialogs, the ID conversion file is not required:

$ ../bin/piarchss -if /opt/PI/dat/piarch.001 -of /opt/PI/dat/piarchcomb.001

PIarchss offline archive utility Input file type: PI 3

Archive input file: /opt/PI/dat/piarch.001 Beginning first pass. Sorting input archive. Archive indicated start time: 2-Mar-98 12:21:11 Archive indicated end time: 3-Mar-98 16:32:27 Archive indicated recordcount: 2048

Processing record 1 ...

Primary record load completed. Records processed: 97 Records with data: 86 Empty records: 11 Records with errors: 0 Records out of time range: 0 Records with duplicate time range: 0 Overflow record load completed.

Records processed: 101 Records with data: 101 Empty records: 0 Records with errors: 0 Records out of time range: 0 Records with duplicate time range: 0

Begining Output pass. Output archive: /opt/PI/dat/piarchcomb.001 Processing record 1 ...

19260 Loaded in 1( 0 + 1 ) Seconds 19260 Event/Sec. 101476 Archive Total seconds - ratio: 101476

Service Manager requested shutdown of piarchss

Now combine the converted archive.

$ ../bin/piarchss -if /opt/PI/dat/piarchconv.002 -of /opt/PI/dat/piarchcomb.001

PIarchss offline archive utility Input file type: PI 3

Archive input file: /opt/PI/dat/piarchconv.002 Beginning first pass. Sorting input archive. Archive indicated start time: 2-Mar-98 12:51:41 Archive indicated end time: 3-Mar-98 11:09:30 Archive indicated recordcount: 395

Processing record 1 ...

Primary record load completed. Records processed: 97 Records with data: 26 Empty records: 71 Records with errors: 0 Records out of time range: 0

Records with duplicate time range: 0 Processing record 200 ...

Overflow record load completed. Records processed: 139 Records with data: 139 Empty records: 0 Records with errors: 0 Records out of time range: 0 Records with duplicate time range: 0

Begining Output pass. Output archive: /opt/PI/dat/piarchcomb.001 Processing record 1 ...

21870 Loaded in 20( 1 + 19 ) Seconds 1093 Event/Sec. 80269 Archive Total seconds - ratio: 4013

Service Manager requested shutdown of piarchss

The combined archive is now ready for registration. Register it and have a look at some data from a merged point:

$ piartool -ar /opt/PI/dat/piarchcomb.001

Attempting to register archive file: /opt/PI/dat/piarchcomb.001 Successfully registered archive file: /opt/PI/dat/piarchcomb.001 peach piadmin$ piartool -al

Archive shift prediction:

Shift Time: 18-Jan-38 19:14:07.7930 Target Archive: /opt/PI/dat/piarch.002 Archive: /opt/PI/dat/piarch.003

PIarcfilehead [$Workfile: piarfile.cxx $ $Revision: 21 $]: Version: 4 Path: /opt/PI/dat/piarch.003

State: 4 Type: 0 Write Flag: 1 Shift Flag: 1 Record Size: 1024 Count: 2048

Offsets: Primary: 98/512 Overflow: 2047/2048 Start Time: 3-Mar-98 16:32:27

End Time: Current Time Backup Time: Never

Archive: /opt/PI/dat/piarchcomb.001

PIarcfilehead [$Workfile: piarfile.cxx $ $Revision: 21 $]: Version: 4 Path: /opt/PI/dat/piarchcomb.001

State: 4 Type: 1 Write Flag: 1 Shift Flag: 0 Record Size: 1024 Count: 499

Offsets: Primary: 98/256 Overflow: 499/1048576 Start Time: 2-Mar-98 12:21:11

End Time: 3-Mar-98 16:32:27 Backup Time: Never

Archive: /opt/PI/dat/piarch.002

PIarcfilehead [$Workfile: piarfile.cxx $ $Revision: 21 $]: Version: 4 Path: /opt/PI/dat/piarch.002

State: 4 Type: 0 Write Flag: 1 Shift Flag: 1 Record Size: 1024 Count: 2048

Offsets: Primary: 1/512 Overflow: 2047/2048 Start Time: Current Time

End Time: Current Time Backup Time: Never

9.3 - Shut Down the Retired System

$ piconfig

* (Ls - ) PIconfig>

* (Ls - ) PIconfig> @Input piarc.dif

* (Ls - PIARC) PIconfig> sinusoidRetired,2-mar-98,*, *> sinusoidRetired,2-mar-98,*, 87.71619,GOOD,2-Mar-98 13:37:56 99.23527,GOOD,2-Mar-98 14:39:56 96.20524,GOOD,2-Mar-98 15:44:56 75.77717,GOOD,2-Mar-98 16:57:56 14.20552,GOOD,2-Mar-98 19:31:26 1.545739,GOOD,2-Mar-98 20:31:26 1.869217,GOOD,2-Mar-98 21:31:26 18.17325,GOOD,2-Mar-98 22:40:56 86.39859,GOOD,3-Mar-98 01:33:26 99.15742,GOOD,3-Mar-98 02:38:56 96.37012,GOOD,3-Mar-98 03:43:56 75.96362,GOOD,3-Mar-98 04:57:26 14.35799,GOOD,3-Mar-98 07:30:56 0.7647065,GOOD,3-Mar-98 08:39:56 3.794814,GOOD,3-Mar-98 09:44:56 24.22295,GOOD,3-Mar-98 10:57:56 Digital State,Shutdown,3-Mar-98 11:04:09 Digital State,Pt Created,3-Mar-98 14:29:48 98.3448,GOOD,3-Mar-98 14:30:26

98.2471,GOOD,3-Mar-98 15:30:26 82.16194,GOOD,3-Mar-98 16:39:56 79.05913,GOOD,3-Mar-98 16:48:56 End Repeat...

Take a good look at several points before proceeding.

In document PI Server System Management Guide (Page 187-191)