Backup with OEM   «Prev  Next»

Lesson 3Run RMAN from Enterprise Manager
ObjectiveLaunch the Enterprise Manager Console and start RMAN

Run RMAN from Enterprise Manager

After you have completed Enterprise Manager initial operations, you are ready to start the Enterprise Manager Console.
To launch the Console on Windows select Enterprise Manager Console from the Oracle Enterprise Management Group on the Start menu.
To launch the Console on UNIX platforms, enter:

oemapp console

The command string is case-sensitive and must be entered with lowercase characters. Then there are two remaining steps:
  1. After the first login dialog appears, type the default credentials for the super administrator account. The administrator ID is sysman and the password is oem_temp.
  2. A security login dialog appears where you can change your password. For security, you should change the default password immediately.

Enterprise Manager passwords are case-sensitive, may not exceed eight characters, and may not end with a space character. Note that you are logging in as an administrator of network resources being serviced by a Management Server, not as a user of a database. The first time you log in to the Console, you are prompted to change the default password. This password should be changed immediately. You can use the Management Server dialog to add, edit, or delete the list of available management servers shown within the Login Information dialog box. You can connect to any Oracle database instance from the Console by selecting it within the Navigator window and clicking on the 
’+’

symbol. You can also select a database within the Navigator window with the right-mouse to access the Connect menu option. If you do not have the preferred credentials set up for that database, the Login Information connect dialog box is displayed. Use it to connect to the database. Once you are connected to the database, right-mouse click it and the link to backup management is displayed. Backup Management has the following five options:
  1. Backup
  2. Recovery
  3. Catalog maintenance
  4. Create backup configuration
  5. Backup configuration library
These 5 options are part of RMAN. The first option helps you backup a database. The second option helps you restore a database. The remaining three options assist in managing RMAN. In the following simulation, we will log into OEM and start RMAN.

Starting RMAN from the OEM

  1. Connect to the OEM console by using sysman as the Administrator, oem_temp as the Password, and localhost as the Management Server. Approve the entries by clicking OK.
  2. Next, you would double-click Databases, and right-click the pets database. We have done that for you here. This displays the option for Backup Management. Click Backup to engage the Backup wizard.
  3. The Backup Wizard is engaged, and the Introduction screen appears. This is the end of the simulation. Click Exit.
Recovery Manager (RMAN) is an Oracle Database client that performs backup and recovery tasks on your databases and automates administration of your backup strategies. It greatly simplifies backing up, restoring, and recovering database files. The RMAN environment consists of the utilities and databases that play a role in backing up your data. At a minimum, the environment for RMAN must include the following components:
  1. A target database: An Oracle database to which RMAN is connected with the TARGET keyword. 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. The RMAN metadata is known as the RMAN repository.
  2. RMAN client: An Oracle Database 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 typically located in the same directory as the other database executables. For example, the RMAN client on Linux is located in $ORACLE_HOME/bin.
Some environments use the following optional components:
  1. flash recovery area: A disk location in which the database can store and manage files related to backup and recovery. You set the flash recovery area location and size with the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE initialization parameters.
  2. media manager: An application required for RMAN to interface with sequential media devices such as tape libraries. A media manager controls these devices during backup and recovery, managing the loading, labeling, and unloading of media. Media management devices are sometimes called SBT (system backup to tape) devices.
  3. recovery catalog: A separate database schema used to record RMAN activity against one or more target databases. A recovery catalog preserves RMAN repository metadata if the control file is lost, making it much easier to restore and recover following the loss of the control file. The database may overwrite older records in the control file, but RMAN maintains records forever in the catalog unless deleted by the user.
The next lesson describes the required preparations for scheduling a backup within OEM.
Oracle Backup Recovery