Troubleshooting: CMDREG data not properly restored during foundation feature disablement

In WebSphere Commerce Version 7 Feature Packs 1, 2 and 3, when foundation is enabled, component specific rows are extracted from the existing CMDREG table and saved to a file. This occurs during enablement immediately before updates are applied to the CMDREG table. When foundation is disabled, the data is restored from that backup file so that the table is restored to its pre-enablement state.

In some cases, there may be multiple backup files. For example, this can occur in the following circumstances:
  • if you have switched databases
  • If you have enabled foundation multiple times
  • If you have enabled multiple versions of the foundation feature
When there are multiple backup files, the disablement process uses the latest backup file to do the restore. If this happens, you might find that the proper data is not contained in the latest backup. You can examine the other backup files to locate and manually restore the data required.

Backup file locations

The name of the backup file or files depends on which fix pack level (not feature pack level) that you had installed when you enabled the feature.
  • WebSphere Commerce Version 7.0.0.2WebSphere Commerce Version 7.0.0.1The backup file is:
    • WC_installdir/components/foundation/xml/wcs.massload.rollback_foundation.xml
  • WebSphere Commerce Version 7.0.0.3The backup file is:
    • WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.version.foundation.xml
    where
    • DBtype is the database type used at the time of enablement
    • schemaName is the schema name used at the time of enablement
    • version is the version of the feature being enabled
WebSphere Commerce Version 7.0.0.3The enablement tool checks for existing files and renames them so that they are not overwritten. If that happens they are renamed similar to this:
  • WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.versionInstalled.foundation.previous.renamed.timestampWhenRenamed.xml
The possible names of the backup files are:
  • Feature Pack 1Depending on the fix pack level, there will be one of the following backup files
    • WebSphere Commerce Version 7.0.0.2WebSphere Commerce Version 7.0.0.1WC_installdir/components/foundation/xml/wcs.massload.rollback_foundation.xml
    • WebSphere Commerce Version 7.0.0.3WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.7.0.0.1.foundation.xml
  • Feature Pack 2Depending on the fix pack level, there will be one or more of the following backup files:
    • WebSphere Commerce Version 7.0.0.2WebSphere Commerce Version 7.0.0.1WC_installdir/components/foundation/xml/wcs.massload.rollback_foundation.xml
    • WebSphere Commerce Version 7.0.0.3WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.7.0.0.2.foundation.xml
    • WebSphere Commerce Version 7.0.0.3The scripts check for existing files and rename them so that they are not overwritten. If that happens they are renamed similar to this:
      • WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.7.0.0.2.foundation.previous.renamed.timestampWhenRenamed.xml
  • Feature Pack 3There will be the following backup files:
    • WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.7.0.0.3.foundation.previous.renamed.timestampWhenRenamed.xml
    • WebSphere Commerce Version 7.0.0.3The scripts check for existing files and rename them so that they are not overwritten. If that happens they are renamed similar to this:
      • WC_installdir/components/foundation/cmdreg_backups/wcs.massload.rollback.DBtype_schemaName.7.0.0.3.foundation.previous.renamed.timestampWhenRenamed.xml

Command used to back up files

The massextract utility is used to back up the data. The following file specifies what to back up:
  • WC_installdir/components/foundation/xml/wcs.massextract.foundation.filter.xml