Stage Check utility

The Stage Check utility determines if there is a unique index key conflict between the staging database and the production database. Run the Stage Check utility before the Stage Propagation utility to ensure successful propagation. The

To run the Stage Check utility, type the following from a command line on staging server or production server. Type the entire script on one line. It is shown here on more than one line for presentation purpose only.

Working with databases other than DB2 for z/OS

This diagram shows the syntax for the stagingcheck utility. Refer to the list entitled Parameter values for the values.

OracleNote: You must include the optional parameters, logon user ID and password in the utility even if you are currently running this utility with the same user ID.

i5/OSiSeries To run shell scripts:

  1. Log on as a user profile that has a CCSID other than 65535.
  2. Open a QSHELL command window by typing the following command: STRQSH.
  3. Run the utility as follows:
    /QIBM/ProdData/CommerceServer56/bin/stagingCheck.sh (parameters . . .)
    Note: The user parameters must always be specified.

Parameter values

scope_unique_index_
The level of scope for the copy to the staging server. Specify _unique_index_.
sourcedb
The name of the database on the staging server.

i5/OSiSeries If the dbtype parameter is DB2/OS400, specify the name of the database on the staging server, as displayed in the relational database directory. If the dbtype parameter is DB2/OS400ToolBox, specify the hostname of the server on which the staging database resides.

destdb
The name of the database on the production server.i5/OSiSeries If the dbtype parameter is DB2/OS400, specify the name of the database on the production server, as displayed in the relational database directory. If the dbtype parameter is DB2/OS400ToolBox, specify the hostname of the server on which the production database resides.
dbtable
(Optional) The name of a specific table to be checked for unique key conflicts.
sourcedb_user
(Optional) The logon ID of the database administrator who has created the schema of the staging database. If not specified, the ID of the user currently invoking the utility is used.

i5/OSiSeries (Required) The user profile associated with the commerce instance. This is the same as the source database schema.

sourcedb_passwd
(Optional) The password of the logon ID that is specified by the sourcedb_user parameter.
destdb_user
(Optional) The logon ID of the database administrator who has created the schema of the production database. If not specified, the ID of the user invoking the utility is used.

i5/OSiSeries (Required) The user profile associated with the commerce instance. This is the same as the destination database schema.

destdb_passwd
(Optional) The password of the logon ID that is specified by the destdb_user parameter. If not specified, the system prompts you to enter the password.
log
(Optional) The path and name of the file in which the Stage Copy utility records its activities and errors. The timestamp is appended to the file name, for example, myLog_yyyy.mm.dd_hh.mm.ss.zzz.log. If this parameter is not specified, a log file called stagingcheck_yyyy.mm.dd_hh.mm.ss.zzz.log is created in the following log directory.
dbtype
(Optional) WindowsAIXSun Solaris Operating EnvironmentLinux The database type (DB2 or Oracle). The default is DB2.i5/OSiSeriesSpecify one of the following:
DB2/OS400
Type DB2/OS400 when using the native JDBC driver. This is the default value if no dbtype is specified.
DB2/OS400ToolBox
Type DB2/OS400ToolBox when using the toolbox JDBC driver.

zSeriesWorking with DB2 for z/OS

This diagram shows the syntax for the stagingcheck utility. Refer to the list entitled Parameter values for the values.

Note: Both users (specified by -sourcedb_user and -destdb_user) need to have the DBADM privilege on the database objects created by each other

Parameter values

scope_unique_index_
(Required) The level of scope for the copy to the staging server. Specify _unique_index_.
sourcedb
(Required) The name of the database on the staging server.
destdb
(Required) The name of the database on the production server.
dbtable
(Optional) The name of a specific table to be checked for unique key conflicts.
sourcedb_user
(Required) The logon ID of the database administrator who has created the schema of the staging database.
sourcedb_passwd
(Required) The password of the logon ID that is specified by the sourcedb_user parameter.
sourcedb_schema
(Required) The schema for the source database.
destdb_user
(Required) The logon ID of the database administrator who has created the schema of the production database.
destdb_passwd
(Required) The password of the logon ID that is specified by the destdb_user parameter.
destdb_schema
(Required) The schema for the destination database
log
(Optional) The path and name of the file in which the Stage Copy utility records its activities and errors. The timestamp is appended to the file name, for example, myLog_yyyy.mm.dd_hh.mm.ss.zzz.log. If this parameter is not specified, a log file called stagingcheck_yyyy.mm.dd_hh.mm.ss.zzz.log is created in the WC_installdir/logs directory.
dbtype
(Required) The database type must be DB2/390.

Feedback