Data Migration Documentation

Issues Resolved in the Migration Scripts

The following migration script issues are resolved in the database migration package.

Issue Migration script Description
26337, 26316;

[INC0014239, INC0012933 ]

DB_update6_2_0_0000_0200.zip, DB_hotfix6_2_0_chf1_0015.zip, DB_hotfix6_2_0_chf2_0062.zip Starting from Calyx RIM 6.1 CHF 4, the migration to Calyx RIM 6.2 and CHFs failed with an ORA error in logs for some customers. This issue is resolved by removing the “select * from dv_user_workflow_secure” query from the migration package.
26281;

[INC0011491]

DB_hotfix6_2_0_chf2_0062.zip The Calyx RIM 6.2 CHF 2 migration script failed to complete after more than 12 hours for some customers. The migrate_asm_update_submit_avbl_flag.sql script was updated to greatly improve the performance of the Calyx RIM 6.2 CHF 2 migration script.
26207 DB_hotfix6_2_0_chf2_0060.zip After migrating from Calyx RIM 6.2 CHF 1 to Calyx RIM 6.2 CHF 2, the association between the Filing Type values and the Filing Type eCTD Codes for legacy specification versions was lost. This issue is resolved.
25986;

[00060676]

DB_update6_2_0_0000_0199.zip The pre_migration_reference_uniqueness.sql report was updated to make names unique within the reference table (within a parent) by suffixing the Name with "-<row_id>" and to add a column for the new unique name.
25971;

[00060660]

DB_update6_2_0_0000_0199.zip The new table product_country_uda was created and populated during the Calyx RIM 6.2 migration, but extra_fields_id was left null. This issue is resolved.
25920;

[00059826]

DB_update6_2_0_0000_0199.zip The pre_migration_reference_uniqueness.sql report was updated to show references that do not have a unique reference name, parent entity ID combination (instead of those not having a unique reference name, parent entity type combination).
25754;

[00058206]

DB_hotfix6_1_0_chf4_0025.zip The originally released Calyx RIM 6.1 CHF 4 migration script had an incorrect RPT_Schema_Diff.lst report. This hotfix contains the corrected RPT_Schema_Diff.lst report.
25750;

[00058083]

DB_hotfix6_1_0_chf4_0025.zip The following error occurred during the Calyx RIM 6.1 CHF 4 migration: ORA-01436: CONNECT BY loop in user data

This issue is resolved.

25745;

[00058838, 00058176]

DB_hotfix6_1_0_chf4_0025.zip This hotfix includes a fix to reduce the execution time of the Calyx RIM 6.1 CHF 4 migration script.
25465 DB_hotfix6_1_0_chf3_0136.zip In Calyx RIM 6.1, an update trigger on the content table was modified to not create entries if the update was due to a renumbering event. This updated trigger was omitted in Calyx RIM 6.1 CHF 1 and CHF 2, but reinstated in CHF 3. The trigger, however, denotes updates to the content table as inserts instead of updates. The trigger was corrected. An optional script to fix existing incorrect data will be provided in a subsequent Calyx RIM 6.1 CHF 3 hotfix.
25414;

[00054605]

DB_hotfix6_1_0_chf3_0136.zip The FLASHBACK_TIME=SYSTIMESTAMP parameter was added to the expdp commands in the dpexportinsight.sql to keep all exported tables synchronized to the same point of time.
25391;

[00054454, 00054327, 00053609]

DB_hotfix6_1_0_chf3_0136.zip ORA-01789 and ORA-00942 errors occurred during the Calyx RIM6.2 CHF 3 migration when the AUD table had an obsolete column that did not exist in the corresponding table in the ODS/MGR/SEC schema. This issue is resolved. Also, the RULE hint is added to improve the migration performance.
25345;

[00053849]

DB_hotfix6_1_0_chf3_0136.zip The odsnew/migrations/migrate_leaf_status.sql script was updated to improve its execution time.
25225;

[00052241]

DB_hotfix6_1_0_chf1_0115.zip There was no password validation for the database user accounts in the migration scripts. This could result in issues with the execution of upgrade scripts. This issue is resolved by adding the password validation to the master.sql script for the following database user accounts:
  • ACTIVITI
  • DM
  • MGR
  • MIGRATION
25209;

[00053438, 00052279, 00052147, 00052137]

DB_hotfix6_1_0_chf1_0115.zip The following error occurred during the LIQUENT InSight 6.1 CHF 1 migration: ORA-01555: snapshot too old. This issue is resolved.
25197;

[00052103]

DB_hotfix6_1_0_chf1_0115.zip Data being copied from a field in the MGR.Application.Term_Withdraw_Reason table to a field in the new MGR.Term_with_reason_type table that was too small resulted in the following errors:
  • ORA-12899: value too large for column
  • ORA-00001: unique constraint

This issue is resolved.

25134;

[00052137, 00051492, 00051212]

DB_hotfix6_1_0_chf1_0115.zip Some customers migrating from Calyx RIM 5.1 to Calyx RIM 6.1 CHF 1 encountered a problem with empty GUID column values for leafs and folders resulting in the following errors:
  • Error adding new not null constraint on FOLDER.GUID

    ORA-02296: cannot enable (ODS.) - null values found

  • Error adding new not null constraint on LEAF.GUID

    ORA-02296: cannot enable (ODS.) - null values found

This issue is resolved.

24594 DB Upgrade 51 CHF2 to 60.zip The Calyx RIM 5.1 to Calyx RIM 6.0 migration did not include MGR in the initial password check. This issue is resolved.
23873 DB Upgrade 50 to 51.zip In the Calyx RIM 5.1 Publishing Settings Library, you must have a Default TOC for Document, Extract, Folder, Leaf, and TOC. This was not mandatory in Calyx RIM 5.0. If you tried to modify and then save a migrated TOC type, but did not have a default TOC type for every aforementioned object type in this Publishing Settings Library, you would get an Invalid Reference java error. This issue is resolved.
23788 DB Upgrade 50 to 51.zip The Calyx RIM 5.1 migration used the ods.SEQ_SETTINGS_ID oracle sequence to populate the ods.overlay_settings table but the ods.SEQ_OVERLAY_ID sequence should be used. This issue is resolved.
23706 DB Upgrade 50 to 51.zip Customers without the R_884 constraint enabled in the Calyx RIM database had duplicate values in the TOC_TYPE table resulting in migration errors. This issue is resolved.
22760 DB Upgrade 50 to 51.zip The “Force New Volume” value defaulted to Yes instead of No for folders that had a null value for this field. This issue is resolved.
24342 51 CHF2 to 60 CHF1.zip The Calyx RIM 6.0 migration can fail if the data was entered into Calyx RIM 5.0 or earlier. The grants required for the migration may not exist, depending on the migration path. This issue is resolved.
24279 51 CHF2 to 60 CHF1.zip The Calyx RIM 6.0 migration generated an error when attempting to copy data with no associated records in the EVMPD_PDS_HISTORY_CHANGE table to the newly created FULL_PRODUCT_PRESENTATION table. This issue is resolved.
22318 DB Upgrade 50 to 51.zip The Calyx RIM Assembly Variables IES (Event Status) and IED (Event Status Date) have been removed from Calyx RIM. If you are upgrading from a previous Calyx RIM version, you must deactivate the IES and IED variables via Calyx RIM Data Administration.
  1. Open the Calyx RIM Go To menu and select Data Administration.
  2. Click InSight Assembly Variables.
  3. Click Event Status, then click Deactivate.
  4. Repeat these steps to deactivate Event Status Date.
22748 DB Upgrade 47 to 50.zip Application products with a product role of comparator will not be migrated to the new standalone comparator entity in Calyx RIM 5.0. The application product associated with a CTA type application (regardless of its role) must retain its hierarchical relationship to maintain the integrity of data associated with the existing products. The reason for this is because previous versions of LIQUENT InSight support the process of tracking PDS details for comparator products. The focus changed with the release of Calyx RIM 5.0. With this release, a comparator is a standalone entity that does not support the tracking of PDS details. 
22361, 22317 DB Upgrade 47 to 50.zip The field size has been increased to 500 characters for Country Trade Name on the Country Details tab, and for Associated Trade Names and Approved Trade Names on the Product Family tabs. This new character limit is now consistent with XEVMPD field sizes.