Examples of propagating data to the production database

The following examples illustrate how you propagate changed records from production-ready data to a production database.

Example 1

Note: Type the utilities on a single line. The utilities are shown here, on more than one line, for presentation purposes only.
Propagate all changes from the staging server database to the production database.
  1. Set the PATH environment variables.
  2. Configure the database.
  3. Type the following command:
    • DB2
      • LinuxAIXFor IBM i OS operating systemstagingprop.sh -scope _all_ -sourcedb staging_database_name -destdb production_database_name -sourcedb_user user -destdb_user user
      • Windowsstagingprop -scope _all_ -sourcedb staging_database_name -destdb production_database_name -sourcedb_user user -destdb_user user
    • Oracle
      • AIXstagingprop.sh -scope _all_ -sourcedb staging_database_name -destdb production_database_name dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
      • Windowsstagingprop -scope _all_ -sourcedb staging_database_name-destdb production_database_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
  4. Examine the log file to verify that the utility was successful. Check the description of the logs parameters to determine the default location of this log file for your database type and platform.

The stagingprop utility first propagates all site data, and then all merchant data to the production database. If an error occurs, the entire transaction rolls back.

To specify the log file name and path, use the log file parameter:
  • DB2
    • LinuxAIXFor IBM i OS operating systemstagingprop.sh -scope _all_ -sourcedb staging_database_name -destdb production_database_name -log log_file_name -sourcedb_user user -destdb_user user
    • Windowsstagingprop -scope _all_ -sourcedb staging_database_name -destdb production_database_name -log log_file_name -sourcedb_user user -destdb_user user
  • Oracle
    • AIXstagingprop.sh -scope _all_ -sourcedb staging_database_name -destdb production_database_name -log log_file_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
    • Windowsstagingprop -scope _all_ -sourcedb staging_database_name -destdb production_database_name -log log_file_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password

Example 2

Propagate all modified site data from the production-ready data to the production database.
  1. Set the PATH environment variables.
  2. Configure the database.
  3. Type the following command:
    • DB2
      • LinuxAIXFor IBM i OS operating systemstagingprop.sh -scope _site_ -sourcedb staging_database_name -destdb production_database_name -sourcedb_user user -destdb_user user
      • Windowsstagingprop -scope _site_ -sourcedb staging_database_name -destdb production_database_name -sourcedb_user user -destdb_user user
    • Oracle
      • AIXstagingprop.sh -scope _site_ -sourcedb staging_database_name -destdb production_database_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
      • Windowsstagingprop -scope _site_ -sourcedb staging_database_name -destdb production_database_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
  4. Examine the log file to verify that the utility was successful. Check the description of the logs parameters to determine the default location of this log file for your database type and platform.

Example 3

Propagate all modified merchant data from the production-ready data to production database (after propagating the site data).
  1. Set the PATH environment variables.
  2. Configure the database.
  3. Type the following command:
    • DB2
      • LinuxAIXFor IBM i OS operating systemstagingprop.sh -scope _merchant_ -sourcedb staging_database_name -destdb production_database_name -sourcedb_user user -destdb_user user
      • Windowsstagingprop -scope _merchant_ -sourcedb staging_database_name -destdb production_database_name -sourcedb_user user -destdb_user user
    • Oracle
      • AIXstagingprop.sh -scope _merchant_ -sourcedb staging_database_name -destdb production_database_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
      • Windowsstagingprop -scope _merchant_ -sourcedb staging_database_name -destdb production_database_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
  4. Examine the log file to verify that the utility was successful. Check the description of the logs parameters to determine the default location of this log file for your database type and platform.