Skip to main content

How to Connect to the RMAN Recovery Catalog with Oracle Autonomous Recovery Service (ARS)

 Connecting to the ARS Recovery Catalog with RMAN


When using Oracle Autonomous Recovery Service (ARS / DBRS) for database backups, the connection to the recovery catalog is secured via an auto-generated Oracle Wallet and configured TNS alias.

To run manual RMAN operations (such as maintenance, reporting, or manual validation), you need to point your environment to the directory containing the ARS wallet/TNS configuration and connect via the catalog alias.

Step 1: Locate and Set the TNS_ADMIN Directory

First, identify the directory where your ARS configuration files (tnsnames.ora, sqlnet.ora, and wallet files like cwallet.sso) reside. On OCI Database environments (such as Base Database Service or Exadata), these are typically stored under the database cluster file system (ACFS) path.

Export the TNS_ADMIN environment variable so RMAN knows where to look for network configuration and credential artifacts:

# Verify the directory path containing your ARS credentials

[oracle@dev-fghd1 TEMP_TNS]$ pwd

/var/opt/oracle/dbaas_acfs/anidev/TEMP_TNS

# Set TNS_ADMIN to the wallet directory

[oracle@dev-fghd1 TEMP_TNS]$ export TNS_ADMIN=/var/opt/oracle/dbaas_acfs/anidev/TEMP_TNS

Step 2: Establish the RMAN Session

Launch RMAN by connecting locally to the target database and using passwordless wallet authentication to connect to the ARS catalog (/@dbrs):

[oracle@dev-fghd1 TEMP_TNS]$ rman target / catalog /@dbrs

target /: Connects to the local target database instance using OS authentication (SYSDBA/SYSBACKUP).

catalog /@dbrs: The slash (/) instructs RMAN to authenticate using the local wallet credentials inside $TNS_ADMIN, while @dbrs references the ARS catalog TNS entry defined in your tnsnames.ora







Key Takeaway: Always ensure that sqlnet.ora inside your $TNS_ADMIN path is configured with WALLET_LOCATION pointing directly to your ARS wallet directory. This eliminates the need to expose or hardcode catalog passwords in backup automation scripts.

Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-65139: Mismatch between XML metadata file and data file

Error: CDB$ROOT@EBTUPRDC> CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse; CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse * ERROR at line 1: ORA-65139: Mismatch between XML metadata file and data file /u05/odb/ORADATA_1/EBTUSPRDC/datafile/system.1531.807800993 for value of fcpsb (2230502002 in the plug XML file, 2230505492 in the data file) Fix: Don't open Non-CDB database until we complete pdb creation other wise we will get above error. Shutdown immediate; startup mount; alter database open read only; create xml file. shutdown immediate; Connect to CDB and Create Pluggable database .
2 comments
Read more

Useful OEM Queries to get Target details from OEM Repository

List Targets with TNS Listener ports configured : SELECT mgmt$target.host_name , mgmt$target.target_name , mgmt$target.target_type , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$target.target_name = mgmt$target_properties.target_name ) AND ( mgmt$target.target_type = mgmt$target_properties.target_type ) and ( mgmt$target.target_type = 'oracle_listener' ) and ( mgmt$target_properties.property_name = 'Port' ); Devora02       LISTENER_ora02                       oracle_listener Port 1529 Devora01       LISTENER_ora01                       oracle_listener Port 1529 Devora04       LISTENE...
1 comment
Read more

TFA-00002 : Oracle Trace File Analyzer (TFA) is not running

TFA Failed to start listening for commands on one of the Rac Node : As a root user /etc/init.d/init.tfa  start Starting TFA.. start: Job is already running: oracle-tfa Waiting up to 100 seconds for TFA to be started.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successfully started TFA Process.. . . . . . TFA-00002 : Oracle Trace File Analyzer (TFA) is not running TFA Failed to start listening for commands Solution : run synctfanodes.sh  if you have root password . if no root password copy below files to TFA Failed node and try to restart TFA .. Please check whether these 4 files exist on all nodes are similar. TFA_HOME/server.jks TFA_HOME/client.jks TFA_HOME/internal/ssl.properties   TFA_HOME/internal/ portmapping.txt If not similar just copy these files to TFA Failing node and try TFA Restart ..It Worked for me .   [root@host01]# ./tfactl  -v "debug" start Starting TFA...
Post a Comment
Read more