Configuration deployment tool messages

While using the Configuration Deployment Tool, you may encounter either informational messages or warning messages. These message types are described.

Informational messages

Informational messages represent the status of the operation being performed. These messages are displayed in the default color (typically black) in the Status panel. Examples of informational messages include:

  • Refreshing database cache
  • Deployment operation started
  • Reading table YFS_ORGANIZATION

Warning messages

Warning messages typically require corrective action. They are displayed in red on the Status panel. CDT may produce the warning messages described in this section.

WARNING - FK check failed for table <name> to <name2>

This warning message typically indicates that the configuration data that you are trying to deploy causes inconsistent data in the target database.

To analyze and correct this problem:

  1. Determine the size of the data set you are deploying. This error typically occurs when trying to deploy a very small set of data, such as only a driver entity or a configuration group. For example, when deploying a pipeline, this error results if the document type to which the pipeline belongs has not been picked for deployment.

    Try resolving this error by selecting a larger set to deploy. For example, instead of deploying a record, deploy the entire group, if possible.

  2. If you still encounter this error for a group or you must only deploy a particular record, try synchronizing the foreign table before deploying the data.
  3. Occasionally, inconsistent data in the source database causes this error. If this is the case, you must correct the source of the inconsistency before you proceed.

WARNING - cache refresh failed

This error indicates that CDT was unable to inform the application server cluster on the target environment about the newly deployed configuration changes. The reason the cache refresh failed is displayed on the Status panel.

To analyze and correct this problem:

  1. Verify the URL specified in the httpurl field for the target database. The httpurl is accessible from the Logon dialog box. Ensure that the httpurl points to a running instance of the application server and has the following format:

    http://<hostname/ip-address>:<port-number>/smcfs/interop/InteropHttpServlet where hostname, ip-address and port-number are the parameters used to connect to the application server.

  2. If your target environment is not running, no action is required. Sterling Order Management System Software automatically reads the latest configuration data when it is started.
  3. If the target environment is running, you must manually drop the stale database cache using the Sterling Order Management System Software System Administration Console. Not performing this step may result in Sterling Order Management System Software not recognizing the changed configuration.

WARNING - the program detected a few abandoned records in the target database.

In most cases, the abandoned records are harmless and do not lead to incorrect operation of Sterling Order Management System Software. By default, the CDT leaves them untouched.

This warning typically occurs as a result of the following circumstances which are described in detail in Importing externally maintained configuration data.

  • When the CDT determines that records do not belong to a valid driver entity (for example, a pipeline for a process type that no longer exists).
  • When the CDT has been configured to ignore certain tables without ignoring all dependent tables.

To analyze and correct this problem:

  1. Add the -DShowAbandoned=Y Java™ parameter to the ydk.cmd script.
  2. Run the ydk.cmd script. If the CDT finds abandoned records, it dynamically creates a group called "Abandoned Records" and displays them in the Comparison Results window.
  3. Examine these records, and then either ignore them or delete them from the target.