V11 SP8
Loading...

Oracle Agent Command Line FAQs

Table of Contents

Can we perform command line backups of Oracle instances with different Oracle SID and database names?

Different SID and database names for Oracle instances are supported for Oracle command line backups. However to get single job id CvOraSID Environmental variable should be used otherwise multiple jobs are generated.

Example for UNIX:

SBT_LIBRARY=<software_install_path>
/Base64/libobk.so,
BLKSIZE=1048576,ENV=(CvClientName=<client_name>,
CvInstanceName=<instance_name>,
CvOraSID=<oracle_sid>

Can we perform command line backups if the Oracle database name and instance name (as defined in the CommCell Console) are different?

No. Prior to running backups from the RMAN command line, ensure that the Oracle database name and the Instance Name as defined in the CommCell Console are the same, otherwise you will need to pass the name of the instance in the RMAN script as follows:

allocate channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=<SBT_LIBRARY_NAME>,ENV=(CvClientName=<client_name>,CvInstanceName=<instance_name>,CvOraSID=<Oracle_SID>)"

where <client_name> and <instance_name> are the names of the Client and Instance (e.g., Instance001) on which the Agent is installed.

Example for Linux:

Consider the Oracle instance name as RMAN and database name as RMANDB.

allocate channel ch1 type 'sbt_tape'
PARMS="SBT_LIBRARY=<software_install_path>/Base/libobk.so>,ENV=(CvClientName=machine1_cn,CvInstanceName=Instance001,CvOraSID=RMAN)"

Can we perform RMAN cross check on On-Demand instances?

No. We cannot perform RMAN Cross check on On-Demand Instances.

Can we run multiple instance scripts using the same input file for an On-Demand instance?

No. We cannot run multiple instance scripts using the same input file for an On-Demand Instance.

Why does the data size increase when you restart an On-Demand backup job?

If you restart an On-Demand backup job with multiple scripts for the same instance, the backup is resumed from the beginning of the script. During this process, the archive files that were backed up before the restart will again be included in the backup after the restart. This increases the data size of the restarted backup job.

You can prevent this behavior by updating the scripts before the restart.

Can we run third-party command line backup operations when a selective online backup job is running?

No. Third-party command line backup operations cannot be run when a selective online full backup job is running.

Can we move Oracle instances using the command line?

Move Oracle instances from one client or cluster node to another client or node within a CommCell using the qoperation move command. However, On-Demand instances cannot be moved using this command.

Can we include multiple run blocks in the same RMAN script for an On-Demand instance?

No. We cannot include multiple Run Blocks in the same RMAN script.

What happens If one of the streams fail when running third-party command line operations with multiple streams?

Oracle third-party command line operations running on multiple streams will share the same Job ID in the Job Manager. If all the streams return failure, then the job is marked as failed. However, if one of the streams fail, it is submitted to the other stream for completion.

How are third party command line jobs handled when Oracle services use a different service account instead of the local system?

When Oracle Services use a different service account other than Local System, third party command line jobs are run with multiple job IDs. In such cases, use the following steps to enable third party command line jobs to run with a single job ID:

  1. From the Start menu, point to Administrative Tools, and then click Local Security Policy.
  2. Double-click Local Policies and then double-click User Rights Assignment.
  3. In the details pane, double-click Adjust memory quotas for a process.
  4. Click Add User or Group.
  5. In the Enter the object names to select box, type the user or group name to which you want to assign the user right and then click OK.
  6. In the details pane, double-click Replace a process level token.
  7. Click Add User or Group.
  8. In the Enter the object names to select box, type the user or group name to which you want to assign the user right and then click OK.

Can we perform a command line duplicate database restore without connecting to the target database from the restore to disk backup pieces?

You can perform a command line duplicate database restore without connecting to the target if you use a catalog server and an RMAN connect statement that uses "catalog user/password@catalog".

Can the time format be changed for RMAN logs for Oracle Backups performed on the Oracle Agent?

Yes, see Changing the Time Format In RMAN Logs for Oracle Backups.

How do I prevent command line data backups from being considered as log backups and using the log storage policy?

When you have a command line script that has a line that includes the archive log ('backup database plus archive log'), the data backup is treated as a log backup and uses the log storage policy. Control file backups always use the data storage policy. You can set the following additional setting to have the data component use the data storage policy.

  1. From the CommCell Browser, right-click the client and then click Properties:
  2. In the Client Properties dialog box, click the Additional Settings tab and then click Add.
    1. In the Name box, type sORASKIPSTREAMOPT.
    2. In the Category box, select OracleAgent.
    3. In the Type box, select String.
    4. In the Value box, type Y.
    5. Click OK to close the Add Additional Settings dialog box.
  3. Click OK to close the Client Properties dialog box.