Examples of propagating data to the production database

The following examples illustrate how you propagate changed records from a staging database to a production database.

Note that you should type the utilities in a single line. The utilities are shown here on more than one line for presentation purposes only.

Example 1

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:
    • DB2
      • AIXi5/OSiSeriesSun Solaris Operating EnvironmentLinuxstagingprop.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
    • Oracle
      • AIXSun Solaris Operating Environmentstagingprop.sh -scope _all_ -sourcedbstaging_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 Stage Propagate utility will first propagate all site data, and then all merchant data to the production database. If an error occurs, the entire transaction will rollback.

To specify the log file name and path, use the log file parameter:

Feedback