Data Migration Documentation

Pre-Migration Scripts for Calyx RIM 6.2

It is recommended that you run the following scripts before starting your database migration to conform to new requirements. Running these scripts will not affect the database. See the LIQUENT InSight 6.2 Data Migration Document (PDF) for more information.

The scripts should be run by an ISM user.

Pre-Migration Script Name Pre-Migration Script Description Pre-Migration Script Output
rpt_pre_migration_mpid.sql
  • The script is used to identify data that may have been captured for MPID in Calyx RIM so you can take appropriate steps to move data elsewhere.
  • This script is optional.
The pre-migration script output is a report in a txt file format that identifies the MPID data with Full Product Presentation that have values that cannot be migrated because they do not meet the business rules for the MPID values.
rpt_pre_migration_procidentif.sql
  • The script is used to identify data that may have been captured for Application Identifier in Calyx RIM so you are notified that this data will not be overridden within the migration script.
  • This script is optional.
The pre-migration script output is a report in a txt file format that identifies the Procedure Identifier data with Application that have values that cannot be overridden because they do not meet the business rules for the Application Code migration.
pre_migration_previousevcodes_authorisedprod.sql The pre-migration script is used o identify previous EV Code values that are not assigned to any of the Full Product Presentation entity. The pre-migration script output is a report in a report in a txt file format that identifies the Previous EV Code values that are not assigned to any of the Full Product Presentation and which will be hidden during a migration to Calyx RIM 6.2.
pre_migration_event_uniqueness.sql The pre-migration script is used to identify events that do not have a unique Event Name, Event Code combination within an Application. The pre-migration script output is a report in a txt file format that identifies the Events that are not uniquely identified within an Application and which will be change during a migration to Calyx RIM 6.2.
pre_migration_lic_atc.sql The pre-migration script is used to identify ATC values that are not assigned to the Product Family but remained in the related Registration. The pre-migration script output is a report in a txt file format that identifies Product Families with no ATC values but with ATC values under related Registration that will be changed during migration to Calyx RIM 6.2.
pre_migration_task_uniqueness.sql The pre-migration script is used to identify Tasks and Sub-Tasks that are not uniquely identified within its parent entity. The pre-migration script output is a report in a txt file format that identifies Tasks and Sub-Tasks that are not uniquely identified within the parent entity and which will be changed during a migration to Calyx RIM 6.2.
pre_migration_reference_uniqueness.sql The pre-migration script is used to identify References that are not uniquely identified within a parent entity. The pre-migration script output is a report in a txt file format that identifies References that are not uniquely identified within the parent entity and which will be changed during a migration to Calyx RIM 6.2.
pre_migration_pds_uniqueness.sql The pre-migration script is used to identify PDS (Product Detail Set) that are not uniquely identified within an Application. The pre-migration script output is a report in a txt file format that identifies PDSs that are not uniquely identified within the Application and which will be changed during a migration to Calyx RIM 6.2.
pre_migration_pds_template_uniqueness.sql The pre-migration script is used to identify PDS Templates that are not uniquely identified within a Product. The pre-migration script output is a report in a txt file format that identifies PDS Templates that are not uniquely identified within the Product and which will be changed during a migration to Calyx RIM 6.2.