Skip to main content

Getting Started with RMAN

 

<<Back to Oracle Backup & Recovery Main Page

Introduction to RMAN

RMAN (Recovery Manager) is a backup and restore utility provided by oracle. 

To start rman you need to set the environment and type rman and press enter as shown below

export ORACLE_HOME=<ORACLE_INSTALLATION_DIR_LOC>
export PATH=$ORACLE_HOME/bin:$PATH


RMAN related terminologies 

Lets understand some components in reference with RMAN utility

• A target database

A target database is a database on which RMAN is performing backup and recovery operations. RMAN always maintains metadata about its operations on a database in the control file of the database known as RMAN repository.

• The RMAN client

Its the executable that interprets commands, directs server sessions to execute those commands, and records its activity in the target database control file. The RMAN executable is automatically installed with the database and is located in $ORACLE_HOME/bin directory

• A fast recovery area (FRA)

A disk location on server in which the database can store and manage files related to backup and recovery.

DB_RECOVERY_FILE_DEST <= Parameter points to the FRA location

DB_RECOVERY_FILE_DEST_SIZE <= defines FRA size

• A media management software

If you want to backup database on tape, you require an application that facilitates the interaction with RMAN and tape device such as tape libraries. A media manager is responsible for loading, labeling, and unloading tapes during backup or recovery operations.

NOTE: installation and configuration instruction of media management software can be found in vendor specific installation/configuration documents 

• A recovery catalog

As you already know RMAN maintains metadata about its operations in control file. If you want to retain this information for rally longer period of time you can configure recovery catalog and instruct rman to write RMAN repository in recovery catalog.

A recovery catalog can store RMAN repository for multiple databases at the same time.


Comments

  1. Great job for publishing such a nice article. Your article isn’t only useful but it is additionally really informative.
    if you are required any TAX and GSTR related information to visit our website click on :Top 10 audit fims in bangalore

    ReplyDelete

Post a Comment

Popular posts from this blog

ORA-28374: typed master key not found in wallet

<<Back to Oracle DB Security Main Page ORA-46665: master keys not activated for all PDBs during REKEY SQL> ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL ; ADMINISTER KEY MANAGEMENT SET KEY FORCE KEYSTORE IDENTIFIED BY xxxx WITH BACKUP CONTAINER = ALL * ERROR at line 1: ORA-46665: master keys not activated for all PDBs during REKEY I found following in the trace file REKEY: Create Key in PDB 3 resulted in error 46658 *** 2019-02-06T15:27:04.667485+01:00 (CDB$ROOT(1)) REKEY: Activation of Key AdnU5OzNP08Qv1mIyXhP/64AAAAAAAAAAAAAAAAAAAAAAAAAAAAA in PDB 3 resulted in error 28374 REKEY: Keystore needs to be restored from the REKEY backup.Aborting REKEY! Cause: All this hassle started because I accidently deleted the wallet and all wallet backup files too and also forgot the keystore password. There was no way to restore the wallet back. Fortunately in my case the PDB which had encrypted data was supposed to be deco...

Understanding the Oracle Database Technical Architecture in Detail continued...

<<Back to DB Administration Main Page Database Redo Logs and Redo Log Buffer Pool In Detail This post is simply the continuation of  Oracle Database Architecture. In this post I will try to explore about Redo Logs. What are Redo Logs? Why are Redo Logs so Important? What Purpose they full fill? How oracle manages them etc etc.... If you have already gone through my previous Posts related to oracle database architecture you are good to proceed. It would be worth to review these posts in case you missed them. The link are here Oracle Database Architecture Overview Explain a  high level Architecture  Database Buffer Cache in Details Explains  how Buffer Cache works and how it is implemented Database Shared Pool in Detail Explains all you want to know about Shared Pool So let's get started before wasting any time What is Redo logs? Oracle Database records all the changes to the database in the form of Redo logs. Redo Logs resides in a memory...

How to Find VIP of an Oracle RAC Cluster

<<Back to Oracle RAC Main Page How to Find Out VIP of an Oracle RAC Cluster Login clusterware owner (oracle) and execute the below command to find out the VIP hostname used in Oracle RAC $ olsnodes -i node1     node1-vip node2     node2-vip OR $ srvctl config nodeapps -viponly Network 1 exists Subnet IPv4: 10.0.0.0/255.255.0.0/bondeth0, static Subnet IPv6: Ping Targets: Network is enabled Network is individually enabled on nodes: Network is individually disabled on nodes: VIP exists: network number 1, hosting node node1 VIP Name: node1-vip VIP IPv4 Address: 10.0.0.1 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes: VIP exists: network number 1, hosting node node2 VIP Name: node2-vip VIP IPv4 Address: 10.0.0.2 VIP IPv6 Address: VIP is enabled. VIP is individually enabled on nodes: VIP is individually disabled on nodes:

How to Install JAVA JVM Component into an Existing Oracle Database

<<Back to DB Administration Main Page How to Add the JVM Component to an Existing Oracle Database Followed oracle Doc ID 1461562.1 and installed oracle JVM component in multitenant database, the script installed JVM component in CDB$ROOT container only and the component was still missing in PDB$SEED and all pluggable database. Since the script and steps mentioned in Doc ID 1461562.1 did not install the component in PDB$SEED , all future PDBs create in the container also inherited the issue and eventually JVM  component was not installed in any of the PDBs. Scroll down to see how to install JVM component in a Multitenant Database environment using catcon.pl How to Verify if JVM component is installed or not select comp_name, version, status from dba_registry where comp_name like '%JAVA%' ; COMP_NAME                           ...

How to Export and Import TDE Master Encryption Key

<<Back to Oracle DB Security Main Page In many cases you need to export the TDE Master Encryption Key and Import it in same or different database. For Example: If you want to migrate a PDB (Using Encryption) from one CDB to another, you must export the TDE Keys from source CDB and import it in Target CDB. How To Export TDE Master Encryption Key SQL> ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS WITH SECRET "any password to protect export file" TO 'file_path' IDENTIFIED BY keystore_password If you run the above statement in PDB it will export the keys for that PDB only SQL> alter session set container=PDB01 ; Session altered. SQL> ADMINISTER KEY MANAGEMENT EXPORT ENCRYPTION KEYS WITH SECRET "mysecret" TO '/home/dbatst1/Wallet/PDB01_TDE.KEY' IDENTIFIED BY keystore_password; keystore altered. NOTE : You can only export the keys if the password based wallet is open in case AUTOLOGIN wallet is open you can export the keys eit...

ORA-46630: keystore cannot be created at the specified location

<<Back to DB Administration Main Page ORA-46630: keystore cannot be created at the specified location CDB011> ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "xxxxxxx"; ADMINISTER KEY MANAGEMENT CREATE KEYSTORE '+DATAC4/CDB01/wallet/' IDENTIFIED BY "EncTest123" * ERROR at line 1: ORA-46630: keystore cannot be created at the specified location Cause  Creating a keystore at a location where there is already a keystore exists Solution To solve the problem, use a different location to create a keystore (use ENCRYPTION_WALLET_LOCATION in sqlnet.ora file to specify the keystore location), or move this ewallet.p12 file to some other location. Note: Oracle does not recommend deleting keystore file (ewallet.p12) that belongs to a database. If you have multiple keystores, you can choose to merge them rather than deleting either of them.

ORA-65104: operation not allowed on an inactive pluggable database alter pluggable database open

<<Back to DB Administration Main Page ORA-65104: operation not allowed on an inactive pluggable database SQL> alter pluggable database TEST_CLON open; alter pluggable database TEST_CLON open * ERROR at line 1: ORA-65104: operation not allowed on an inactive pluggable database Cause The pluggable database status was UNUSABLE. It was still being created or there was an error during the create operation. A PDB can only be opened if it is successfully created and its status is marked as NEW in cdb_pdbs.status column SQL> select PDB_NAME,STATUS from cdb_pdbs; PDB_NAME             STATUS -------------------- --------------------------- PDB$SEED             NORMAL TEST_CLON            UNUSABLE Solution:  Drop the PDB and create it again. Related Posts How to Clone Oracle PDB (Pluggable Database) with in the Same Container

WARNING - My Oracle Support Username/Email Address Not Specified

<<Back to DB Administration Main Page [WARNING] - My Oracle Support Username/Email Address Not Specified ./runInstaller -silent -ignoreSysPrereqs -showProgress -skipPrereqs -responseFile /u01/app/stage/database/response/db_install.rsp Starting Oracle Universal Installer... Checking Temp space: must be greater than 500 MB.   Actual 1204 MB    Passed Checking swap space: must be greater than 150 MB.   Actual 4095 MB    Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2019-01-23_02-41-56PM. Please wait ... [WARNING] - My Oracle Support Username/Email Address Not Specified Solution: Set the following parameter in response file as shown below SECURITY_UPDATES_VIA_MYORACLESUPPORT=false DECLINE_SECURITY_UPDATES=true

ORA-46697: Keystore password required

<<Back to DB Administration Main Page ORA-46697: Keystore password required SQL> CREATE PLUGGABLE DATABASE PDB03 FROM PDB01 USING MIRROR COPY PDB01_CLONE; CREATE PLUGGABLE DATABASE PDB03 FROM PDB01 USING MIRROR COPY PDB01_CLONE * ERROR at line 1: ORA-46697: Keystore password required. Cause:  TDE is configured and Keystore password is supplied. Solution: If you have TDE configured, you must supply the keystore password for such tasks using keystore identified by password clause eg. SQL> CREATE PLUGGABLE DATABASE PDB03 FROM PDB01 USING MIRROR COPY PDB01_CLONE KEYSTORE IDENTIFIED BY keystore_password; Pluggable database created.

ORA-46655: no valid keys in the file from which keys are to be imported

<<Back to DB Administration Main Page SQL> administer key management import encryption keys with secret "xxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxx" with backup; administer key management import encryption keys with secret "xxxxxx" from '/tmp/pdb02_tde_key.exp' force keystore identified by "xxxxxx" with backup * ERROR at line 1: ORA-46655: no valid keys in the file from which keys are to be imported Cause: Either the keys to be imported already present in the target database or correct container (PDB) is not set. Solution: In my case I got the error because I attempted to import the keys for newly plugged database PDB02 from CDB$ROOT container. To Solve the issue just switched to the correct container and re run the import. SQL> show con_name CON_NAME ------------------------------ CDB$ROOT <===Wrong Container selected  SQL> alter session set container=PDB02; Session alt...