Migration prerequisites

Ensure successful migration by following the listed procedure.

Before you begin

Before you start migration, ensure you complete the following steps:
  • You must have adequate permissions for following actions:
    • To create and modify tables, and indexes in the database,
    • To create and delete files in the sub directories of the $TOP directory.
  • You must verify that you have at least 30% free space in the database.
  • You must delete old Product Master data before you migrate to avoid running out of log space.
  • You must have a $TOP/logs directory before you run any migration scripts.
  • You must use the Db2® or Oracle database version as mentioned in the system requirements. For more information, see Db2 databases and Oracle databases. See the Db2 or Oracle documentation for upgrading your Db2 and Oracle database to the supported version.
  • You must ensure that the Product Master database user has appropriate privileges. Consult with your database Administrator team for any changes in database user privileges because of any security policy.
  • While migrating to a higher release, and not a fix pack of the same release, you must use a new installation directory to avoid JAR file version mismatches.

Procedure

To ensure a successful migration, ensure you complete the following steps:

  1. Manually copy following files and folder since migration method does not support exporting local system files.
    • $TOP/etc/default/docstore_mount.xml
    • $TOP/etc/default/user_jars.list
    • $TOP/public_html/suppliers/<cmp code>/ctg_files folder
    • Required user JAR files
      For more information, see Deploying a custom user .jar file
  2. Do not overwrite the property files from an older version to a new version.
  3. Modify each customized property from a previous release to the corresponding file in the new version.
  4. Manually redo any customization changes that you made to the Default Rich Search Results Report Script because migration overwrites the existing script available in the /scripts/report docstore folder. The Default Rich Search Results Report Script script is used for exporting Product Master object search results to an Excel sheet.
    For more information, see Exporting search results to Excel.
  5. Ensure that there is no verbose compilation option that is set for compiling scripts.
  6. Verify that in the common.properties file you do not use verbose as the value for the script_compiler_options parameter. For more information, see script_compiler_options parameters.
  7. If you are using custom table space names instead of the default USERS, INDX, or BLOB_TBL_DATA, you must manually modify the table space names in the following files:
    • create_pimdb.sh and create_pimdb_for_zLinux.sh script files located at $TOP/bin/db_creation folder
    • IBM® Db2 SQL files located at $TOP/src/db/schema/dbscripts/db2 folder
    • Oracle database SQL files located at $TOP/src/db/schema/dbscripts/oracle folder
      Database Modify for 11.4 and 11.5 release Modify for 11.6 release
      IBM Db2
      addCehEntryId.sql
      		 alter_ers_table_detail_status.sql alter_scu_table_password_date.sql alter_scu_table_email.sql create_conn_workflow_connector.sqlcreate_idx_sch_job_status.sql create_rules_engine.sql ddl_export_item_status_table_connector.sql
      Oracle database addSstShared.sql add_icm_index.sql add_lot_index.sql add_sca_index.sql add_sit_index1.sql modifyIcm1Index.sqlredefine_ctg_indexes.sql
  8. Run the setup.sh script located in the $TOP folder to check whether the version of PERL installed on your computer is compatible with the version of Product Master that you install. If the current version of PERL is not compatible, you must install a new version.
    For more information, see Installing Perl.
  9. If you install the new version of Product Master in a new folder, you must update the value of TOP and PERL5LIB variables in the .bash_profile file. You must set the PERL5LIB variable to $TOP/bin/perllib directory.