Migrate batch data to event frames

Before you migrate your batch data to AF event frames, first you must analyze your batch data to find potential incompatibilities with AF, as shown in Analyze batch data before migration. After fixing essential issues and making any optional changes, you can migrate your data.

During migration, the Module Database is unavailable for updates or modifications. You can update elements in AF, but changes will not be synchronized with the Module Database until after migration completes.

Note: When you start the migration process, the PI Batch Database becomes read-only and the PI Batch Subsystem stops generating batches. Therefore you need to prepare thoroughly before migration. See Prepare batch data sources and consumers for migration.

If you have upgraded to the latest PI batch interface, version 4.0, or later, and it is running when migration starts, it goes into a wait state and before resuming, adds the required AF settings to the initialization (.ini) file. To avoid inadvertently overwriting these settings, close the Event Frame Interface Configuration Manager before starting migration.

After migration, you can review the results. If you chose to utilize PI EFGen in Recovery mode (as explained in Prepare batch data sources and consumers for migration, you might need to delete duplicate batches. You should delete in-progress batches that belong to Category OSIBatchMigration, as long as there are completed and correct batches belonging to the Category OSIBatch. For more information, see Event frame templates for batch data.

Note: You do not have to migrate while the batch is running, but it is perfectly alright to do so. Your batch interface log will record when it detects the start of migration, while it is waiting for migration to complete, and when it starts generating event frame data.

1. Using the PI AF Link tool in PI SMT, after you have obtained an analysis report that contains no must-fix issues, and you have resolved all desired optional issues, click Migrate (available at the end of the Analysis report).

   The Migrate function checks that the user running PI AF Link has appropriate permissions (read-write permissions on the PI SMT AF Link Security database are required).

   Migration progress is shown, and the Batch database status field indicates when migration is complete. Migration can take a while, depending on the amount of PI batch data online. As a guideline, on average, migration can take approximately 1 hour for each year of PI Batch data. To obtain a better estimate, use the information provided when you clicked Analyze about the number of event frames you will be generating. Allow approximately 90 minutes per million event frames, bearing in mind that this time will vary greatly depending on network, hardware and other factors.

2. After migration completes, click View migration report to open the Migration report.

3. Click View errors to see information about any errors that occurred during migration.

   Informational messages are also shown, for example about the following actions:

   • Automatic name modification (truncation of names longer than 259 characters, and replacement of any characters that are invalid in AF).

   • Event frames named with the string <undefined>. You can update this string to give the event frame a meaningful name. This might occur with batch data created by PIBaGen that is migrated to PI Event Frames.

     • The Procedure name of a PI Unit Batch is used as the name of the event frame. If the Procedure name is blank, the Batch ID is used as the event frame name. If both are blank, the event frame is given the name <undefined>.

     • The Batch ID of a PI Batch is used as the event frame name. If the PI Batch has no Batch ID, the event frame is given the name <undefined>.

       Note: The Details tab shows the path to the file containing the migration error report.

       For a list of migration messages, see Migration error report.

4. You now have event frames in AF that represent your batch data. See Verify your event frame data for information about confirming the migration has gone smoothly and has resulted in event frame data in your desired format.

   For example, when you view an event frame's properties, click Extended Properties to see information such as an original object name before truncation or character replacement took place.

   Note: After you have migrated your batch data to event frames, you will no longer be able to re-migrate the Module Database to AF. Remigration used to be a workaround when the Module Database had lost synchronization with the AF database. The recommended workaround is to reset the Module Database from the AF database; in the AF Link tool in PI SMT, on the Details tab, click Reset MDB.