Troubleshooting: stagingprop utility fails

The stagingprop utility can fail due to the presence of old access control policy triggers.

Problem

The stagingprop utility can fail due to the existence of old access control policy (ACP) triggers present in the database. These ACP triggers were created during the initial store creation, and are not required.

This issue is only encountered on versions of HCL Commerce 9.1.0.0 through 9.1.12.0.

Solution

To correct this error, choose from one of the following options:
  • HCL Commerce Version 9.1.13.0 or laterUpgrade your migration to HCL Commerce version 9.1.13.0 or greater. You will no longer encounter this issue.
  • For migrations of WebSphere Commerce to HCL Commerce versions prior to 9.1.13.0, you must manually correct the issue.
    1. Drop all of the unnecessary ACP triggers using the DB2dropTriggersDB2.sql or OracledropTriggersOracle.sql SQL script depending on your database type.
    2. Re-run the stagingprop utility with the actionOnError parameter set to 1.
      stagingprop.bat -actionOnError 1 -sourcedb source_db_name 
      -destdb dest_db_name -dbtype dbtype -sourcedb_user user
      -sourcedb_passwd password -destdb_user user 
      -destdb_passwd password

      For more information on the stagingprop utility, see stagingprop utility.

    3. Observe the stagingprop logs.

      Ensure that only the related ACP tables show failures. These errors can be ignored. Any subsequent runs of the stagingprop on the newly migrated database will not produce these errors again, because any ACP STAGLOG entries will not be present.

Result

The stagingprop utility runs as expected.