Administer > Stage server > Staging server utilities > stagingprop
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
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.
- Set the PATH environment variables.
- Configure the database.
- Type the following command:
- stagingprop.sh -scope _all_ -sourcedb dbstage-destdb dbprod -sourcedb_user user -destdb_user user
- stagingprop -scope _all_ -sourcedb dbstage -destdb dbprod
- stagingprop.sh -scope _all_ -sourcedb dbstage -destdb dbprod dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- stagingprop -scope _all_ -sourcedb dbstage-destdb dbprod -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- 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 the database type and platform.
The stagingprop utility will first propagate all site data, and then all merchant data to the production database. If an error occurs, the entire transaction will roll back.
To specify the log file name and path, use the log file parameter:
- stagingprop.sh -scope _all_ -sourcedb dbstage -destdb dbprod -loglog_file_name -sourcedb_user user -destdb_user user
- stagingprop -scope _all_ -sourcedb dbstage -destdb dbprod -log log_file_name
- stagingprop.sh -scope _all_ -sourcedb dbstage-destdb dbprod -loglog_file_name-dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- stagingprop -scope _all_ -sourcedb dbstage -destdb dbprod -log log_file_name -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
If you are using DB2 and are not logged on as the Database Administrator, provide values for the -sourcedb_user, -sourcedb_passwd, -destdb_user, and -destdb_passwd options.
Example 2
Propagate all modified site data from the production-ready data to the production database.
- Set the PATH environment variables.
- Configure the database.
- Type the following command:
- stagingprop.sh -scope _site_ -sourcedb dbstage -destdb dbprod -sourcedb_user user -destdb_user user
- stagingprop -scope _site_ -sourcedb dbstage -destdb dbprod
- stagingprop.sh -scope _site_ -sourcedb dbstage-destdb dbprod dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- stagingprop -scope _site_ -sourcedb dbstage -destdb dbprod -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- 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 the database type and platform.
Example 3
Propagate all modified merchant data from the production-ready data to production database (after propagating the site data).
- Set the PATH environment variables.
- Configure the database.
- Type the following command:
- stagingprop.sh -scope _merchant_ -sourcedb dbstage -destdb dbprod -sourcedb_user user -destdb_user user
- stagingprop -scope _merchant_ -sourcedb dbstage -destdb dbprod
- stagingprop.sh -scope _merchant_ -sourcedb dbstage -destdb dbprod dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- stagingprop -scope _merchant_ -sourcedb dbstage -destdb dbprod -dbtype oracle -sourcedb_user user -sourcedb_passwd password -destdb_user user -destdb_passwd password
- 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 the database type and platform.