ORACLE Management Server configuration

Hi,
To use the Backup Management Wizard, you must be connected to the Oracle Management Server because the wizard uses the EM Job system to execute the backup scripts
EM Backup Management Wizard is just a GUI that creates scripts that are executed by RMAN. It means you have to test the RMAN first to ensure it works before using the Backup Management

Hope this helps

And this is how to configure Backup Manager for Enterprise Manager 2 using a recovery catalog

A. Introduction
Beginning with Oracle Server 8.0.x, Oracle created a command line backup and recovery utility called Oracle Recovery Manager (RMAN). This utility is used for backing up and restoring Oracle 8.x databases. The OEM 2.x Console is integrated with this utility and it allows DBAs to perform backups and recover databases through a GUI interface. The GUI interface is simply a set of wizards that can be activated by right clicking the database in the OEM Console navigator. The wizards will create RMAN scripts that can then be stored or run through the OEM job system.

RMAN stores metadata about the backup configuration in either a Control File or a Recovery Catalog. The Recovery Catalog is a set of tables in an Oracle8 or 8i database and allows for greater flexibility and easier recovery than using a Control File. Oracle recommends using the Recovery Catalog method.

NOTE: Brackets < > and the information contained within the brackets are variables that should be replaced with your information.

For example: connect internal/<oracle>@<tns alias>
might be
connect internal/oracle@oracle.world

B. Creating the Recovery Catalog
The Recovery Catalog method requires at least two databases. One database will be the target (or the one that gets backed up by RMAN). The other database will store the recovery catalog. This database CANNOT be the same database that is being backed up. There are several steps that must complete before RMAN and OEM will perform backups of the database.

1. If the target database is not in archivelog mode, set it to ARCHIVELOG mode.
a) To do this, the database must be mounted exclusive and not open. Next, verify the init.ora for the target database has the following parameters:
##### For archiving if archiving is enabled #####
log_archive_start = true
log_archive_dest_1 = "location=D:\Oracle\oradata\oem1\archive"
log_archive_format = arc%S.%T

b) Use the GUI tool INSTANCE MANAGER or the command line tool Server Manager to set the database in archivelog mode. Note: You must be logged on as SYSDBA to make this change.

If using Server Manager type:
svrmgrl
svrmgrl> connect internal/<password>@<tns alias for target database>
svrmgrl> shutdown immediate
svrmgrl> startup mount
svrmgrl> alter database archivelog
svrmgrl> alter database open

2. If a password file does not exist, you will need to create on. To create the password file, go to the $ORACLE_HOME/bin directory and issue the following command: orapwd file=<name of file> password=<password> entries=5

NOTES:

a. Some versions of Oracle on NT use orapwd80 instead of orapwd.
b. There are no spaces around any of the equal signs.
c. On Unix: The filename MUST be located in the $ORACLE_HOME/dbs directory and MUST be called orapw<SID>. For example:
orapwd file=$ORACLE_HOME/dbs/orapwORCL password=oracle
e. On Windows NT/2000: The filename can be any normal filename, and may be located in %ORACLE_HOME%\database. You can name it what you want. The default is pwd<SID>.ora
orapwd80 file=c:\orant\database\orapwORCL password=oracle


3. Verify the $ORACLE_HOME\dbs\init<sid>.ora has the following parameter: remote_login_passwordfile=exclusive

If the parameter is not set to exclusive, edit the file, change the parameter to exclusive and bounce the instance.

4. Verify both databases (the target database and the one holding the recovery catalog) have been discovered in the OEM Console and Preferred Credentials have been set.

NOTE: Set the Preferred Credentials to a user that has been granted SYSDBA privileges and then verify the &#65533;connect as SYSDBA&#65533; option is also selected.


5. If the user specified in the EM Preferred Credentials does not have SYSDBA privileges, grant this privilege by logging onto SECURITY MANAGER as internal/<password> or SYS/<password> and assign the SYSDBA role to the users
 

6. Connect to the recovery catalog database with the OEM Console or STORAGE MANAGER and create a tablespace called RCAT.
Hint: This can also be done by using SQL*PLUS Worksheet by issuing the following commands:

create tablespace RCAT
datafile ·<fullpath name/rcat01.dbf>· size 20M autoextend on
next 5M maxsize 50M;

NOTE: The RCAT tablespace will be used to store the Recovery Manager catalog (repository).

7. Connect to the Recovery Catalog database through the OEM 2.x Console or SECURITY MANAGER and create a Recovery user account called RMAN.

Hint: This can also be done by using SQL*PLUS Worksheet by issuing the following commands:

create user rman identified by rman
temporary tablespace <temp tablespace>
default tablespace rcat
quota unlimited on rcat;
grant recovery_catalog_owner, connect, resource to rman;

NOTE: The user RMAN will be the account that owns the RECOVERY CATALOG and should be used when logging into the RMAN utility. The role recovery_catalog_owner is a database role that gives the RMAN user all the System Privileges needed to store backup information.

It is very important that the quota to rcat to be set to unlimited. Without this, an error will occur: · unable to create file.

8. For an Oracle 8.1.5 database, perform the following steps:

a. From the command prompt, go to the $ORACLE_HOME\bin directory and issue the following command: rman catalog rman/rman@<recovery catalog database>


b. When the "RMAN>" prompt appears, enter the following: create catalog tablespace "rcat";


NOTE: For Oracle 8.0.x databases, perform the following:
Connect rman/rman@<recovery catalog database>@<$ORACLE_HOME/rdbms/admin>/catrman.sql

NOTE: The catalog and/or catrman.sql script creates procedures and packages used by RMAN:


DBMS_RCVCAT PACKAGE (maintains the recovery catalog)
DBMS_RCVMAN PACKAGE (queries the recovery catalog)
DBMS_BACKUP_RESTORE PACKAGE (performs backup/restore operations for target database)


9. Register the target database in the RMAN recovery catalog database using either the OEM console/job system or command line.

a. To use OEM, right click on the target database found in the navigator window pane. Select Backup Management => Create Backup Configuration. Under the Recovery Catalog tab, enter the logon credentials for the recovery catalog database.

b. To use the command line RMAN interface, go to a command prompt and enter the following command:

For ORACLE 8.1.5:
rman target internal/oracle@<target database> catalog rman/rman@<recovery catalog database>

For ORACLE 8.x:
rman target internal/oracle@<target database> rcvcat rman/rman@<recovery catalog database>

When the RMAN> prompt appears, enter the following: register database

NOTE: The register database command identifies the database to the RECOVERY CATALOG. All information about the target database's structure is propagated to the Recovery Catalog from the target database's control file. The database must be mounted and open to perform this operation.


C. Using the Backup Management Wizard
After the Recovery Catalog has been created, the target databases have been registered in the Recovery Catalog, the OEM job system is completely functional, then the Backup Management Wizard can be used. To get the wizard, highlight the database in the OEM console and right click.

First step is to 'Create a Backup Configuration'. A window with several tabs will appear. Fill in the information as requested in each tab.

1. General Tab is used to give the backup set a name.
2. Channel Tab is used to establish the backup method and assign names and locations for the physical backup files that will be created during the backup process. The 'File Name' parameter uses substitution values that are used when creating the name of the physical files that compose the entire backup set. If specifying disk channels, set the path as a full directory name. Be sure to include a trailing backslashes at the end of the directory 'ie. \ '; otherwise the channel will not be created.

3. Recovery Catalog Tab is used to specify the type of catalog to be used. It can be either a Control File or a Recovery Catalog in an Oracle 8 database.

4. Backup Parameters Tab is used to override defaults on maximum datafiles and maximum backup set sizes.

E. Preferred Credentials Tab is used to override the OEM Console Preferred Credentials. This allows flexibility to enter an account that has SYSDBA privileges if the OEM Console Preferred Credentials are not set to SYSDBA.

 

NOTE: Oracle provides a basic backup strategy to be used if one does not already exist. The predefined backup will do a full database backup and follow up with incremental backups.

The Oracle Enterprise Manager Administrators Guide and On-line help are excellent sources of information on how to use the Backup Management / Recovery Management Wizards.
 

How to resolve "EMSDK-1100 unable to make a secure communication channel" error in OMS.

So, try installing the latest patch for both: Database and OEM