Yes. 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 will be generated.
Example for Unix:
SBT_LIBRARY=<software_install_path>
/Base64/libobk.so,
BLKSIZE=262144,ENV=(CvClientName=<client_name>,
CvInstanceName=<instance_name>,
CvOraSID=<oracle_sid>
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 iDataAgent is installed.
Example for Linux:
Consider 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)"
No. You should always limit the RMAN jobs for the same instance to run one at a time in the CommCell Console and Scheduler.
No. We cannot perform RMAN Cross check on On Demand Instances.
No. We cannot run multiple instance scripts using the same input file for an On Demand Instance.
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.
No. Third-party command line backup operations cannot be run when a selective online full backup job is running.
Yes. We can 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. See qoperation move for more information on usage.
No. We cannot perform On Demand Instance backups (ODI) backups if the channel name contains all zeroes.
Example:
allocate channel ch00 type sbt;
Selective Online Full backup is a full backup performed when an Oracle
database is online and is copied to a selective copy (during an auxiliary copy
operation) from which it can be restored.
The advantage of this type of backup is that both the data and logs use the same
storage policy, which means that they reside together on the same media. They
are completely self-contained for restore and long term archiving purposes. This
is especially useful in disaster recovery situations by alleviating the need to
locate different offsite media from various jobs to gather the necessary data
and logs to recover the database. Also, the data aging rules for selective
online full backups are different from regular full backups, as both data and
logs are aged together under the same storage policy.
Only Oracle Selective Online Full and Offline jobs will be copied to a selective copy. All other jobs including regular online full jobs will not be copied.
Oracle regular Online FULL jobs are not considered for selective copy. Hence, they do not honor the extended retention rules. Extended retention is supported only for Oracle Selective Online Full and Offline FULL jobs.
Oracle Data is retained using the retention settings in RMAN. From the RMAN prompt, run the following command to verify the retention rules:
show RETENTION POLICY;
Run the following command from RMAN to receive obsolete pieces:
report obsolete;
Run the following command from RMAN if you want to delete them:
delete obsolete;
Oracle sends prune request to Media manager to prune data when delete obsolete command is run from RMAN session.
| We do not recommend running these commands as it interferes with Calypso retention rules and auxiliary copies. |
See Oracle RMAN Retention Policy for more information.
In the RMAN output, the date timestamp parameter is set to Mon DD YYYY HH24:MI:SS format, by default.
Use the following steps to set the date timestamp in a specified format:
|
|
No. We cannot include multiple Run Blocks in the same RMAN script.
You must select all the tablespaces on which this table resides to successfully restore a table.
You can restore tables under non-system tablespaces in Oracle 11g2.
When you include the indexes during a table restore, note that only the index definition is restored and not the indexed data.
Once the tables are restored to the auxiliary instance, you can either use the CommCell Console to export the data from the auxiliary instance and import it to a destination that you choose, or you can leave the data in the staging path and import the data manually by using Oracle import utilities.
Stored procedures are restored from the Schema level. Schema is the collection of data objects created by the user to contain or reference their data. Hence, if one of the table within the schema is selected for restore, all the stored procedures for that schema will also get restored.
No. Table restores are not supported when there are schema changes in the database.
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.
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:
When the Oracle database is configured to save archive logs in the Flash recovery area, backup jobs will fail if the Oracle subclients have both the Protect backup recovery area and the Archive Delete options enabled at the same time.
To avoid such backup failures you need to configure two different subclients, one for Protect backup recovery area and the other for enabling Archive Deletion option for deleting Archive logs.
By default, the offline full backup jobs restart from the beginning. The archive files that are created in the earlier attempt are still marked valid. The size of the application in the restarted job will increase from the earlier attempt of this backup job.
If we submit restore from the latest offline restarted jobs, the data from the archive files that are created after the job is restarted will also be restored.
In order to backup Oracle Exadata Database Machines, do the following:
|
|
It happened as you have not removed the data files which are restored to staged path and auxiliary instance when a table level restore failed in export or import phase. You can run the export and import jobs manually without restoring the database again.
Yes. You can assign deduplicated storage policy for log backups. However, the iDataAgent will consider the storage policy as a non-deduplicated storage policy and does not Deduplicate the logs.
If the Oracle connect string uses a dynamic listener, you must configure a static listener to perform:
Yes.