RMAN Related

• UDP 9.1 does not support multiple Oracle owner accounts (installation user accounts) for the Linux Oracle server.
• When the databases (instances) that need to be protected are installed with different Oracle owner accounts within the Linux Oracle server, perform manual workaround.
• To perform manual workaround, follow these steps:
• Deploy all the plans that were created for the databases (instances) installed within the concerned Linux Oracle server.
• On the RPS, navigate to the Unified Data Protection\Engine\Configuration\OracleDatabase installation directory to locate the appropriate Backup policy XML file, and correct the Oracle owner account in the following tag:
• <oracleSourceHostItem>
• <userName>OracleOwnerAccount root</userName> [space separated user accounts]
• </oracleSourceHostItem>
• On the RPS, navigate to the Unified Data Protection\Engine\Configuration\AssuredRecovery\Scheduled installation directory to locate the appropriate Assured Recovery policy XML file, and correct the Oracle owner account in the following tag:
• <oracleRMANInfo>
• <NonRootUserName>OracleOwnerAccount</NonRootUserName>
• <oracleRMANInfo>
• Notes:
• For all the databases (instances) that need to be protected from the concerned Linux Oracle server, perform step 2 and step 3.
• After re-deploying any plan or performing node update operation for one of the databases (instances) from the Linux Oracle server, perform manual workaround to make sure correct Oracle owner account is being used for backup and assured recovery policies.
• UDP 9.1 does not support multiple sudo user accounts for protecting the Linux Oracle server.
• The Solaris RMAN support added in UDP 9.1 does not support multiple Oracle owner accounts (installation user accounts) for the Solaris server.
• Granular restore of PDB tablespace is not supported when PDB tablespace is dropped prior to recovery.
• The backup of PDB tablespace in RECOVER state is not supported.
• After restoring the whole CDB, all the PDBs are in a MOUNTED state.
• RMAN does not allow TSPITR for the recreated (cloned) logical entities. Hence, the restore of PDB tablespace created with the clone command fails, and the following error occurs:
• RMAN-03015: error occurred in stored script
• You cannot recover dropped PDBs with a full or granular recovery.
• For a full or PIT recovery of a PDB, CDB must be in a READ WRITE state.
• For a full or PIT recovery of a whole PDB, PDB must be in a READ WRITE or MOUNTED state.
• Solaris 11.x OS provides the SMB client implementation only for SMB 1.0 protocol. If you want to perform the RMAN backup of Oracle® Solaris database, ensure that the SMB version 1.0 is enabled in RPS according to the associated risk policy, and then perform a backup.
• Restore to an alternate node is not supported if the source and destination are on two different oracle versions.
• After upgrading to 8.1, when the Restore to an Alternate Location or Alternate Node job is performed, the archive log recovery points that were created before upgrading to 8.0 become invalid. The recovery points become invalid because they do not contain details of DataFile mapping in Flash DB as needed.
• For archive log restores to an alternate location or alternate node in 8.1, the incremental backup (All data types) must be performed first, and then the subsequent archive log schedules can be used for restores.
• When the Oracle Listener is configured in the non-default location, the Oracle Database does not appear in the node list automatically and must be added manually during the plan creation.
• The Pause/Resume option is not available under the Node menu for Oracle nodes.
• Oracle does not support Tablespace if the Tablespace name contains Dollar Sign ($) in Oracle 19c.
• Granular restore is not supported when the Oracle database is installed using virtual account.
• UDP 8.1 does not support backup of databases from different Oracle versions installed on the same server.
• Table recovery as per Oracle limitations:
• Tables created from SYSTEM and SYSAUX tablespace cannot be recovered.
• Tables created from system or system user cannot be recovered.
• RPS acts as a Backup, Restore and Assured Recovery Agent.
• For Standard Edition, only the Full DB restore with recover all and point-in-time (PIT) is supported from the latest and intermediate recovery points.
• For Standard Edition, Tablespace restore with recover all is supported from the latest recovery point and the UNTIL clause is not supported in the RMAN script.
• For Standard Edition, Oracle does not support table level restores.
• After a Full DB restore, the next incremental backup will be auto converted into a full backup.
• If the WRP size changes, the next backup will be a full backup.
• The maximum number of channels supported are 10.