Stagingprop exit codes
Consolidating and propagating large amounts of data from a staging to a production environment is a complex process. The stagingprop utility returns exit codes when errors are encountered. Exit code descriptions and resolution actions can help you identify and correct your stagingprop errors.
Exit codes 0 - 18
| Exit code number | Description | Resolution action |
|---|---|---|
| 0 | Normal exit. | None. |
| 15 | Indicates stagingprop caught an instance of java.lang.OutOfMemoryError. The maximum amount of runtime heap that is allowed to be allocated by the invoking Java virtual machine (JVM) might not be sufficient. More diagnostic information can be output on the invoking terminal. | See Improving stagingprop performance for details on how to resolve this error and increase the size of runtime heap that is allocated by the JVM. |
| 16 | Indicates stagingprop encountered an unexpected instance of java.lang.Exception that was not handled, indicating a program error. More diagnostic information can be output on the invoking terminal. | Contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 17 | Indicates stagingprop encountered an unexpected instance of java.lang.Throwable that was not handled, indicating a program error. More diagnostic information can be output on the invoking terminal. | Contact HCL Commerce support and provide any collected terminal output and generated log files |
| 18 | Indicates stagingprop encountered and caught an instance of java.lang.StackOverflowError. The size of the runtime stack that is reserved by the invoking JVM might not be enough. More diagnostic information can be output on the invoking terminal. | See Improving stagingprop performance for details on how to resolve this error and increase the size of runtime stack that is reserved by the JVM. |
Exit codes 21 - 36
Exit code values in this inclusive range indicate that pre-consolidation errors were found in the staging or authoring environment during command-line argument processing.
| Exit code number | Description | Resolution action |
|---|---|---|
| 21 | Indicates that an unexpected error was encountered during the command-line argument processing phase. More diagnostic information can be output on the invoking terminal or in the log file, if one was created. | Check diagnostic information for hints on what the error is. If there is no clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 22 | Indicates that an invalid value was specified for the -dbtype parameter. | Correct the invalid value specification. |
| 23 | Indicates that an invalid value was specified for the -batchsize parameter. | Correct the invalid value specification. |
| 24 | Indicates that an invalid value was specified for the -sourcedb parameter. | Correct the invalid value specification. |
| 25 | Indicates that an invalid value was specified for the -transaction parameter. | Correct the invalid value specification. |
| 26 | Indicates that an invalid value was specified for the -configfile parameter. | Correct the invalid value specification. |
| 27 | Indicates malformed or unexpected content in the XML found in the file that is specified for the -configfile parameter. | Correct the content of the specified file. |
| 28 | Indicates that empty content was found in the XML file that is specified for the -configfile parameter. | Add content to the specified file. |
| 29 | Indicates a contradiction with specification of -configfile parameter, but no corresponding -list value specification to the -transactionparameter. | Either remove the -configfile parameter and its corresponding value, or adjust the value of the -transaction parameter to list. |
| 30 | Indicates an error during the retrieval of staged table names from the staging database. | Ensure that the correct connection information is specified for a staging/authoring database where all of the STGSITETAB, STGMERTAB, and STGMRSTTAB tables are present and can be read from. |
| 31 | Indicates that an invalid value was specified for the -dbtable parameter. | Correct the invalid value specification. |
| 32 | Indicates that an invalid value was specified for the -filter parameter. | Correct the invalid value specification. |
| 33 | Indicates that an invalid value was specified for the -retry parameter. | Correct the invalid value specification. |
| 34 | Indicates that an invalid value was specified for the -retry parameter. | Correct the invalid value specification. |
| 35 | Indicates that an invalid value was specified for the -cutofftime parameter. | Correct the invalid value specification. |
| 36 | Indicates the presence of unexpected parameters, unexpected values on the command line, or both. | Remove any extra parameters, values that are specified on the command line, or both. |
Exit codes 46 - 108
| Exit code number | Description | Resolution action |
|---|---|---|
| 46 - 49 | Values in this inclusive range indicate pre-consolidation errors were found in the staging/authoring environment during the initialization of information that pertains to staged tables. These errors are unexpected. | Ensure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 61 and 62 | Values in this inclusive range indicate that pre-consolidation errors were found in the staging/authoring environment during compilation, during execution, or both of JDBC objects that pertain to acquiring an exclusive lock on the STAGLOG table in the staging database. These errors are unexpected. | Ensure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 71 | Indicates that a pre-consolidation error was found in the production environment because of an invalid value was specified for the -destdb parameter. | Correct the invalid value specification. For more information, see: . |
| 89 - 108 | Values in this inclusive range indicate that consolidation errors were found in the staging/authoring environment. Errors occurred during the compilation or execution of JDBC objects during the consolidation phase of stagingprop. These errors are unexpected. | Ensure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
Exit codes 114 - 121
| Exit code number | Description | Resolution action |
|---|---|---|
| 114 | Indicates that a tolerable error was found during the consolidation process and was resolved successfully. This exit code can only manifest if -actionOnError was specified with a value of 2 and no other subsequent errors were encountered. | This code is an informational exit code. Stagingprop can still successfully complete the consolidation and propagation phases. If there was expectation of error, for example, -actionOnError parameter was set to 2 for a reason, this opportunity can be used to determine the types of errors that are found in the STAGLOG table. |
| 115 | Indicates that an internal error was encountered during the attempted resolution of a consolidation error. This error is unexpected. | Make sure that your staging and authoring environments are in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide them with the collected terminal output and generated log files. |
| 116 | Indicates that an intolerable data error was found during consolidation and
caused stagingprop to abend. This error can occur only if:
|
Drop and re-create any database triggers on custom staged tables. Make sure that the values the triggers insert into the STAGLOG table accurately reflect the scope of the data. |
| 117 | Indicates the discovery of an unexpected sequence of database operations
during the consolidation process. This code can occur when the following sequence of operations is
encountered during examination of the same staged table record: a. – A manifestation of symptoms that is described in exit code 116 but with no specification of the -actionOnError parameter b. – UPDATE of a record followed by an INSERT of the same record c. – DELETE of a record followed by an UPDATE of the same record d. – DELETE of a record followed by another DELETE of the same record e. – INSERT of a record followed by another INSERT of the same record |
The symptoms that are described might occur due to various reasons. Following
is an attempt to address some of the symptoms: a. – see resolution for exit code 116 b, c, d. – These errors might occur if the primary-key column values of a specified record are modified or updated. Stagingprop does not support propagation of records that had one or more of their primary-key columns values modified. To resolve this error invoke stagingprop with the -actionOnError parameter set to 2, then invoking the action that led to the errors, using delete followed by insert actions rather than update actions. e. – This error is unexpected. If this error or any of the other errors occur in absence of the explanations that are provided, it might be an indication of incorrect database triggers. In rare cases, it might be an indication of an issue with a trigger misfiring in the underlying database. |
| 118 | Similar to exit code 116, except that this error can occur only when -consolidationSize is specified. | See resolution for exit code 116 |
| 119 | Similar to exit code 117, except that this error can occur only when -consolidationSize is specified. | See resolution for exit code 117 |
| 120 | Indicates that an intolerable data error was found during consolidation that caused the stagingprop utility to abend. This error can occur if custom staged tables are in use and database triggers used to insert data into the STAGLOG table inserted a value other than 'U', 'D' or 'I' in the STGOP column. | Drop and re-create any database triggers on custom staged tables. Ensure that the values they insert into the STGOP column of STAGLOG table are one of 'U', 'D' or 'I'. |
| 121 | Indicates that records were found for a table in the STAGLOG table during the consolidation process, but no staging configuration entry was found for the table in any of the STGSITETAB, STGMERTAB, and STGMRSTTAB tables. This error can occur only if custom staged tables are in use and no other subsequent errors were encountered. Stagingprop tolerates this error by continuing the consolidation process with a skeletal staging configuration. | This code is an informational exit code. Stagingprop can still successfully complete the consolidation and propagation phases. Ensure that appropriate staging configuration record entries exist for all custom staged tables in the STGSITETAB or STGMERTAB table, and in the STGMRSTTAB table if necessary. See Enabling custom tables for staging for details. |
Exit codes 139 - 145
| Exit code number | Description | Resolution action |
|---|---|---|
| 139 | Indicates that propagation errors were found in the staging/authoring environment during the execution of JDBC objects that pertain to acquiring an exclusive lock on the STAGLOG table in the staging database. This error is unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 140 | Indicates a propagation error in the staging/authoring environment during invocation of a commit on the staging database. This error is unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 141 | Indicates a propagation error in the staging/authoring environment during invocation of a rollback on the staging database. This error is unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 142 | indicates a propagation error in the staging/authoring environment. This error is caused by an interrupt signal that is sent to stagingprop while a wait was pending before a retry. This error is unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 143 | Indicates a propagation error in the staging/authoring environment during the retrieval of column metadata from the staging database for a table on which propagation is to be attempted. This error is unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 144 | Indicates a propagation error in the staging/authoring environment during attempted instantiation of a post-row-propagation Java class for a table after successful propagation of a set of records for that table. This error is unexpected. | Make sure that any configuration values specified for post-row-propagation for any tables are correct. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 145 | Indicates a propagation error in the staging/authoring environment during execution of an instantiated post-row-propagation Java class for a table after successful propagation of a set of records for that table. This error is unexpected. | Make sure that all post-row-propagation implementation classes for any tables are error-free. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
Exit codes 146 - 158
| Exit code number | Description | Resolution action |
|---|---|---|
| 146 - 149 | Indicates that propagation errors were found in the staging/authoring environment. The errors were found during compilation or execution of JDBC objects that pertain to fetching metadata from the STAGLOG table as well as actual data tables before propagation of a set of records for a specified table. These errors are unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 150 | Indicates a propagation error in the staging/authoring environment during retrieval of data from the KEYS table for a specified table. This error is unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 151 - 154 | Indicates that propagation errors were found in the staging/authoring environment. The errors were found during compilation or execution of JDBC objects that pertain to updating metadata in the STAGLOG table after successful propagation of a set of records. These errors are unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 155 - 158 | Indicates that propagation errors were found in the staging/authoring environment. The errors were found during compilation or execution of JDBC objects that pertain to resolving cyclic reuse of unique key values for a propagated table. These errors are unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
Exit codes 159 - 202
| Exit code number | Description | Resolution action |
|---|---|---|
| 159 | Similar to exit code 120, except that this code can occur only in the staging/authoring environment during the propagation phase of stagingprop | See resolution for exit code 120 |
| 160 - 161 | Indicates that propagation errors were found in the staging/authoring environment. The errors were found during compilation or execution of JDBC objects that pertain to fetching metadata from the STAGLOG table before propagation of a set of records for a table that is described in the metadata. These errors are unexpected. | Make sure that your staging/authoring environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 162 | Similar to exit code 121, except that this code can occur only in the staging/authoring environment during the propagation phase of stagingprop | See resolution action for exit code 121 |
| 163 | Indicates that data pointed to by one or more records in the STAGLOG table was not found in the table that is identified by the STAGLOG table record's STGTABLE column. | This error might manifest if primary-key column values of a specified record are modified or updated. Refer to the resolution action specified for exit code 117 b, c, d. |
| 189 | Indicates a propagation error in the production environment during invocation of a commit on the production database. This error is unexpected. | Make sure that your production environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 190 | Indicates a propagation error in the production environment during invocation of a rollback on the production database. This error is unexpected. | Make sure that your production environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 191 - 194 | Indicates that propagation errors were found in the production environment during compilation or execution of JDBC objects that pertain to propagation of data for a specified table. These errors are unexpected. | Ensure that your production environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 195 | Indicates a propagation error in the production environment after execution of an instantiated post-row-propagation Java class for a table after successful propagation of a set of records for said table. This error indicates that an unexpected code was returned by the instantiated object of the class. | Make sure that all post-row-propagation implementation classes for any tables are error-free and return appropriate return codes. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 196 - 200 | Indicates that propagation errors were found in the production environment. The errors were found during compilation or execution of JDBC objects that pertain to resolving cyclic reuse of unique key values for a table that is being propagated. These errors are unexpected. | Make sure that your production environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 201 - 202 | Indicates a propagation error in the production environment during the retrieving or updating of data to or from the KEYS table for a specified table. This error is unexpected. | Make sure that your production environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
Exit codes 203 - 206
| Exit code number | Description | Resolution action |
|---|---|---|
| 203 - 204 | These errors occur during an attempt to either add information to, or clear information from a batched JDBC PreparedStatement object. These errors are unexpected. | Make sure that your production environment is in a stable state. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 205 | This error occurs when one or more of the records that are being propagated in the batch caused a primary-key collision, a unique-index violation, or a foreign key constraint violation. | Depending on the JDBC driver in use, detailed information might be available about the exact record that caused the execution of the batch to fail. If detailed information is not available, invoke stagingprop with the -batchsize parameter set to a value of 0. This parameter provides diagnostic information about the exact failing record. If time constraints do not permit the opportunity for investigation and best-effort propagation is required, consider using the -actionOnError parameter with a value of 1. stagingprop utility for more information. |
| 206 | This error can occur only when the -actionOnError parameter is set to a value of 1 or 2 and an attempt was made to bypass an error in an element of the JDBC batch that did not correspond to a primary-key collision, a unique-index violation, or a foreign key constraint violation. | Depending on the JDBC driver in use, detailed information might be available about the exact record that caused the execution of the batch to fail. If detailed information is not available, invoke stagingprop with the -batchsize parameter set to a value of 0, as this parameter can provide diagnostic information about the exact failing record. |
Exit codes 207 - 238
| Exit code number | Description | Resolution action |
|---|---|---|
| 207 | Indicates a propagation error in the production environment during propagation of a record without a JDBC batch in use; -batchsize parameter is set with a value of 0 or 1. | Detailed information is available about the exact failing record. If the failure information indicates a primary-key collision, a unique-index violation or a foreign key constraint violation, and time constraints do not permit opportunity for investigation and best-effort propagation is required, consider using the -actionOnError parameter with a value of 1. For more information, see stagingprop utility. If there is no other clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 208 - 209 | Indicates a propagation error in the production environment during an attempt to bind data to JDBC PreparedStatement objects before propagation of the data to the production database. | These errors are unexpected. The errors might indicate issues specific to either data fetched from the staging database or with the expected format of said data on the production database. If there is no clear indication of error, contact HCL Commerce support and provide any collected terminal output and generated log files. |
| 210-211 | Indicates a propagation error during a delete operation on a table within the
production environment. The error occurs when the operation causes an ON DELETE RESTRICT violation
or an ON DELETE NO ACTION violation. An attempt to delete a row from a parent table was restricted
since a row within a child table references the row in the parent table. The delete-restrict or
delete-no-action relationship prevents the deletion of rows on tables when an unintentional cascade
delete can occur. As an example, the relationship between the OFFER and ORDERITEMS can result in cascade deletions. Normally a cascade-delete relationship amongst the tables occur when a record in the OFFER table is deleted in the staging environment and the changes propagated to the production environment. When the change is propagated the OFFER record is deleted and any ORDERITEMS record that references the deleted OFFER record is also deleted. |
To avoid cascade deletion, use a delete-restrict relationship or
delete-no-action relationship instead of a delete-cascade relationship. For more information see,
Removing cascade deletion in the production environment to prevent data loss. Avoid issuing deletes on parent tables that contain delete-restrict relationships to child tables that contain data that must be preserved. |
| 238 | Indicates a propagation error in the production environment that was resolved successfully. This exit code can occur only if the -actionOnError parameter was specified with a value greater than 0 and the types of errors that were resolved are either primary-key collisions, unique-index violations, or foreign key constraint violations, and no other types of errors were encountered. | This code is an informational exit code as stagingprop is still able to complete both the consolidation and propagation phases successfully. If there was expectation of error, for example, an -actionOnError parameter was set to a value greater than 0 for a reason, this opportunity can be used to determine the types of errors that are found in the STAGLOG table. For more information, see -actionOnError in stagingprop utility. |