For administrators to be most effective, they must be able to identify and clearly organize the complete set of managed systems such as databases, nodes, application servers, and applications. OEM extends the administrator's reach beyond the data server, providing a centralized management foundation for the complete set of Oracle products.
- Oracle Parallel Server,
- Oracle Applications,
- Oracle Forms
and even complex features such as Oracle Replication, all take advantage of OEM as their base management environment. OEM offers a comprehensive set of management services that can be run on hosts, databases, and applications to monitor the health of the operating environment and to check for specific conditions. OEM must be configured to manage the database environment. In this lesson, we will look at the different steps involved within its configuration.
Below are a series of image that contain the code requirements for REPORT commands and illustrates the step-by-step requirements for configuring OEM for Recovery Manager.
RMAN can be used either with or without a recovery catalog. A recovery catalog is a schema stored in a database that tracks backups and stores scripts for use in RMAN backup and recovery situations. An experienced DBA would suggest that
- the Enterprise Manager instance schema and
- RMAN catalog schema
be placed in the same utility database on a server separate from the main servers.
The RMAN schema generally only requires 17 megabyte per year per database backed up.
The RMAN schema owner is created in the RMAN database using the following steps:
- Start SQL*Plus and connect as a user with administrator privileges to the database containing the recovery catalog. For example, enter:
CONNECT SYS/oracle@catdb AS SYSDBA
- Create a user and schema for the recovery catalog. For example, enter:
CREATE USER rman IDENTIFIED BY cat
TEMPORARY TABLESPACE temp
DEFAULT TABLESPACE tools
QUOTA UNLIMITED ON tools;
- Grant the recovery_catalog_owner role to the user. This role provides all of the privileges required to maintain and query the recovery catalog:
SQL> GRANT RECOVERY_CATALOG_OWNER TO rman;
Once the owner user is created, the RMAN recovery catalog schema can be added:
- Connect to the database that contains the catalog owner. For example, using the RMAN user from the above example, enter the following from the operating system command line. The use of the CATALOG keyword tells Oracle this database contains the repository:
% rman CATALOG rman/cat@catdb
- It is also possible to connect from the RMAN utility prompt:
RMAN> CONNECT CATALOG rman/cat@catdb
- Now, the CREATE CATALOG command can be run to create the catalog. The creation of the catalog may take several minutes. If the catalog tablespace is this user's default tablespace, the command would look like the following:
While the RMAN catalog can be created and used from either a 9i or 10g database, the Enterprise Manager Grid Control database must be a 9i database. This is true at least for release 1, although this may change with future releases.
Each database that the catalog will track must be registered.