Third-Party Command Line Operations

Topics| Related Topics

Overview

Important Considerations

• DB2
• DB2 DPF
• Informix
• Oracle
• Oracle RAC

Miscellaneous Issues

Overview

Besides running data protection and data recovery operations from the CommCell Console, you can use the third-party command line to run such operations for the following Agents:

• DB2
• DB2 DPF
• Informix
• Oracle
• Oracle RAC

Moreover, such operations for the SAP for Oracle and SAP for MAXDB iDataAgents can currently be run only from the third-party command line.

Be sure to consult the documentation for your product for information on running third-party command line operations.

Generally, the various CommServe job-reporting windows and job reports (including, e.g., Job Manager, Job Controller, Backup Job History report) provide details for third-party command line operations that are similar to those details provided for such operations run from the CommCell Console. The following section provides some exceptions in this regard.

Important Considerations

Consider the following while executing third party commands:

DB2

You can perform backup and restore jobs from DB2 command line. For detailed information, see:

• Third-Party Command Line Backups
• Third-Party Command Line Restores

DB2 DPF

For DB2 DPF, the following options are available:

• To set a configuration parameter for a specific database simultaneously on all the nodes, run the following command:

  db2_all ";db2 update db cfg for <database name> using <parameter name> recovery"

  where <database name> is the name of the DB2 database (e.g., pubs); <parameter name> is the name of the DB2 configuration parameter (e.g., logretain).

  To set a configuration parameter for a specific database for a series of nodes but one node at a time, run the following series of commands for each node:

  export DB2NODE=<node>

  db2 terminate

  db2 update db cfg for <database name> using <parameter name> recovery

  where <node> is the number of the node. For example:

  export DB2NODE=0

  db2 terminate

  db2 update db cfg for pubs using logretain recovery

  export DB2NODE=1

  db2 terminate

  db2 update db cfg for pubs using logretain recovery

• To perform an action (e.g., backup, update) only on one node (e.g., 0), you can run commands similar to the following:

  db2_all "<<+<node number>< db2 update db cfg for pubs using logretain recovery

  db2_all "<<+<node number>< db2 backup db pubs

  db2_all "<<+<node number>< db2 backup db pubs load <software install path>/Base/libDb2Sbt.so

  where <node number> is the number of the node; <software install path> is the install path for the agent software. For example:

  db2_all "<<+0< db2 backup db pubs load /database/level1/Base/libDb2Sbt.so

  To perform an action (e.g., backup) on all the nodes expect one node (e.g., 0), you can run commands similar to the following:

  db2_all "|<<-0< db2 backup db pubs

  db2_all "|<<-0< db2 backup db pubs load /database/level1/Base/libDb2Sbt.so

• A roll-forward operation can be run only from the catalog node (e.g., 0) of the specified database (e.g., pubs02). First, run a restore for each node (e.g., 0, 1, 2, 3). For example:

  db2_all "<<+0< db2 restore db pubs02 load /database/level1/Base/libDb2Sbt.so taken at 20080408165002 without prompting"

  db2_all "<<+1< db2 restore db pubs02 load /database/level1/Base/libDb2Sbt.so taken at 20080408165107 without prompting"

  db2_all "<<+2< db2 restore db pubs02 load /database/level1/Base/libDb2Sbt.so taken at 20080408164536 without prompting"

  db2_all "<<+3< db2 restore db pubs02 load /database/level1/Base/libDb2Sbt.so taken at 20080408164559 without prompting"

  Then run the following commands:

  export DB2NODE=0

  db2 terminate

  Finally, run the roll-forward operation. For example:

  db2 rollforward db to end of logs and stop pubs02

  The trailing status will display details on the roll-forward operation for the four identified nodes.

• A recover operation can be run only from the catalog node (e.g., 0) of the specified database (e.g., pubs02). The recover operation will recover the database on all the nodes. For example:

  export DB2NODE=0

  db2 recover db pubs 02

  The trailing status in this case will display details on the recover operation for the same four nodes identified in the roll-forward operation.

• Consider the following regarding out-of-place restores.
  • For a cross-database restore involving the same DB2 DPF instance, assume, for example, that the name of the source database is pubs01 and that the name of the target database is pubs02. To complete the restore, you must issue the appropriate commands for each DB2 DPF node (partition). For example, starting with the first node, run the following commands:

    export DB2NODE=0

    db2 terminate

    Then run the restore for the node. For example:

    db2 restore db pubs01 load <software install path>/Base/libDb2Sbt.so taken at 20080701073606 into pubs02 without prompting

    Continuing with the next node, run the following commands:

    export DB2NODE=1

    db2 terminate

    Then run the restore for the node. For example:

    db2 restore db pubs01 load <software install path>/Base/libDb2Sbt.so taken at 2008070107353 into pubs02 without prompting

    Continue this sequence for each node.

    If you need to roll-forward the database, be sure to first set for each node the CvSrcDbName option for the LOGARCHOPT1 parameter to the source database name. For example, starting with the first node, run the following commands:

    export DB2NODE=0

    db2 terminate

    db2 update db cfg for pubs02 using LOGARCHOPT1 "'CvSrcDbName=pubs01,CvClientName=<client name>,CvInstanceName=<CommServe instance name>, CvDpfClientName=<DPF Pseudo-Client Name>"'

    Continuing with the next node, run the following commands:

    export DB2NODE=1

    db2 terminate

    db2 update db cfg for pubs02 using LOGARCHOPT1 "'CvSrcDbName=pubs01,CvClientName=<client name>,CvInstanceName=<instance name>, CvDpfClientName=<DPF Pseudo-Client Name>"'

    Continue this sequence for each node.

    Then run the appropriate roll-forward command. For example:

    db2 rollforward db pubs02 to end of logs and stop

  • For a cross-database restore involving different DB2 instances on different DB2 DPF pseudo-clients, assume, for example, that the name of the source pseudo-client is DPF_INST1, the name of the source DB2 instance is db2inst1, the name of the source database is pubs, the name of the destination pseudo-client isDPF_INST2, the name of the destination instance is db2inst2, and the name of the destination database is emp. Also, assume that the CommServe instance name (in a multi-instance environment) is Instance001.

    Before running a restore to a different DB2 DPF pseudo-client, ensure the following: Catalog partition number for the destination database is the same as that for the source database Destination pseudo-client is configured in the CommCell Console

    For each node, before you run the restore, be sure to first set two options for the VENDOROPT parameter. Specifically, set the CvSrcDB2Instance Name option to the source DB2 instance name, and set the CvSrcClientInstanceName option to the source DB2 DPF pseudo-client  name. For example:

    export DB2NODE=0

    db2 terminate

    db2 update db cfg for emp using VENDOROPT "'CvSrcDB2InstanceName=db2inst1,CvSrcClientName=DPF_INST1,CvClientName=supernova,CvInstanceName=Instance001,CvDpfClientName=DPF_INST2"'

    Continuing with the next node, run the following commands:

    export DB2NODE=1

    db2 terminate

    db2 update db cfg for emp using VENDOROPT "'CvSrcDB2InstanceName=db2inst1,CvSrcClientName=DPF_INST1,CvClientName=supernova,CvInstanceName=Instance001,CvDpfClientName=DPF_INST2"'

    Continue this sequence for each node.

    Then run a restore for each node. For example, starting with the first node:

    export DB2NODE=0

    db2 terminate

    db2 restore db pubs01 load /opt/product/Base/libDb2Sbt.so taken at 20080701073606 on /db2home1/db2inst2 into emp without prompting

    For this command, the destination path option (on /db2home1/db2inst2 in this example) will work only for the catalog node since the restore operation on a non-catalog database partition cannot specify automatic storage paths. Also, ensure that you provide a destination path when you run this command to produce the correct result. In this example, if on /db2home1/db2inst2 is not provided, the data will be restored to /db2home1/db2inst1/db2inst2.

    Continuing with the next node, run the following commands:

    export DB2NODE=1

    db2 terminate

    db2 restore db pubs01 load /opt/product/Base/libDb2Sbt.so taken at 20080701073653 into emp without prompting

    Continue this sequence for each node.

    If you need to roll-forward the database, be sure to first set for each node several options for the LOGARCHOPT1 parameter. Specifically, set the CvSrcClientName option to the source pseudo-client name, the CvSrcDB2InstanceName option to the source instance name, and the CvSrcDbName option to the source database name. For example:

    export DB2NODE=0

    db2 terminate

    db2 update db cfg for emp using LOGARCHOPT1 "'CvSrcDbName=pubs01,CvSrcDB2InstanceName=db2inst1,CvSrcClientName=DPF_INST1,CvClientName=supernova,CvInstanceName=Instance001, CvDpfClientName=DPF_INST2"'

    Continuing with the next node, run the following commands:

    export DB2NODE=1

    db2 terminate

    db2 update db cfg for emp using LOGARCHOPT1 "'CvSrcDbName=pubs01,CvSrcDB2InstanceName=db2inst1,CvSrcClientName=DPF_INST1,CvClientName=supernova,CvInstanceName=Instance001, CvDpfClientName=DPF_INST2"'

    Continue this sequence for each node.

    Then run the appropriate roll-forward command. For example:

    db2 rollforward db emp to end of logs and stop

Restoring Database to Individual Nodes

You can restore DB2 DPF database individually to each node using the corresponding backup images.

Informix

• For Informix, in order to run an Onbar third-party command line backup for a particular instance on a client where multiple instances are installed, you must set and export the CvInstanceName= and CvClientName= environment variables. For example:

  export CvClientName=Client1

  export CvInstanceName=Instance001

  where Client1 is the name of the Informix client and Instance001 is the name of the instance.

Performing a Cross Platform/Cross Server Restore

You can perform a cross platform/ cross server restores using onbar. However, the source and destination Informix servers must have the same db spaces name and paths. Ensure that the source and destination Informix servers are configured within the same CommServe.

Follow the steps given below to perform a cross platform/cross server restore:

Renaming Database Spaces

Perform the following validations to rename the db spaces during a cold restore using ON–Bar command line utility:

• Verify to see that the old db space pathnames and offsets exist in archive reserved pages.
• Verify to see that the new db space pathnames and offsets do not overlap each other or existing db spaces.
• If you rename the primary root or mirror root spaces, ON–Bar updates the ONCONFIG file parameters ROOTPATH and ROOTOFFSET, or MIRRORPATH, and MIRROROFFSET. The old version of the ONCONFIG file is saved as $ONCONFIG.localtime.
• ON–Bar restores the data from the old db spaces to the new db spaces.
• New db spaces must have the proper permissions.

If either of the above steps fail, the renaming process stops and ON–Bar writes an error message to the ON–Bar activity log. Provide the old dbspace location and the new db space location either at the command line or in a file to rename a db space. The following table lists example values for two db spaces:

Renaming Database Spaces with Command Line Options

Renaming Database Spaces with a File

Renaming Chunks While Specifying Other Options

Oracle

You can perform backup and restore operations from RMAN command line.

• Third-Party Command Line Backup

  See Running RMAN Scripts from Third Party Command Line

• Third-Party Command Line Restore

  See Running RMAN Scripts from the RMAN Interface

Oracle RAC

You can also perform backup and restore operations for Oracle RAC iDataAgent from the RMAN command line.

• Third-Party Command Line Backup

  See Running RMAN Scripts from Third Party Command Line

• Third-Party Command Line Restore

  See Running RMAN Scripts from the RMAN Interface

Miscellaneous Issues

Third-party command line operations can produce unique output based on the associated Agent. Relevant issues are summarized in the following table.