Enterprise Manager Configuration Guide
This chapter discusses getting started with Oracle Enterprise Manager and configuring the Console when it is running under Microsoft Windows NT or Windows 95.
Please check the Oracle Enterprise Manager Readme for the compatibility matrix. The readme is located in the ORACLE_HOME/SYSMAN/ADMIN directory.
Before you start the Enterprise Manager, you must set up
the repository user account. A repository is a set of tables in
an Oracle database which stores data and information required by the Oracle
Enterprise Manager Console. The tables are owned by the account that creates
You need to have an Oracle user account with DBA (Database
Administrator) privileges set up on the database where the repository will
be created. Each DBA must have their own repository for the nodes they
are responsible for. The repository account can be located in any Oracle
database that is accessible on the network.
Please check the Oracle Enterprise Manager Readme
for the compatibility matrix. The readme is located in the $ORACLE_HOME\SYSMAN\ADMIN
Oracle recommends that you create a separate tablespace for the Oracle Enterprise Manager repository.
For example, assuming a 2K database block size, the file
size should be 20482K.
For the calculation, convert values to bytes; then, convert
bytes to kbytes:
((20 * 1048576) + (2048)) / 1024 = 20482
1048576 is the number of bytes in a Megabyte
|DB_BLOCK_SIZE||Enforced Maximum||Recommended Value|
To set up a user account with DBA privileges, follow the procedure below:
In the Name field, enter a name for the new user.
In the Password and Confirm Password fields, enter a password.
Choose OEMREP as the default tablespace.
Choose a tablespace that is dedicated to temporary segments as the user's temporary tablespace. In order to optimize sort performance, when running Oracle 7.3 or later, ensure this tablespace has been defined with the TEMPORARY keyword. For example, temporary_data.
Choose Role as the Privilege Type.
Grant the DBA role to the user.
When you start Oracle Enterprise Manager, connect to the repository database with this user account. The repository will automatically be generated.
Beginning with Oracle Enterprise Manager version 1.3.5, a new repository will be created for every new user login. One user can use one repository at one time.
The Repository Manager Wizard is started when you select
Repository Manager in the Oracle Enterprise Manager program group.
You need to have an Oracle user account with DBA (Database Administrator) privileges in order to use the Oracle Repository Manager.
The Repository Manager allows you to choose from the following operations:
Create/validate Enterprise Manager repositories
During the create/validate process, Repository Manager upgrades an existing repository or creates a new one if one does not already exist. If you drop a repository, the information contained in the repository is lost.
Drop Enterprise Manager repositories
If the database objects for the repository component exist, they will be deleted.
Save a list of the discovered nodes
You can choose to save a list of the discovered nodes in an existing repository to a text file. Specify the name, such as discnode.txt, and location of the file where you want to save the list of discovered node names. The default location is the ORACLE_HOME\BIN directory.
The text file can be loaded into the Add Nodes page of the Discover New Services wizard.
You can choose the repository components that you want to
create, validate, or drop. The Oracle Diagnostics Pack, Oracle Tuning Pack,
and the Oracle Change Management Pack are dependent on the Oracle Enterprise
Manager repository. Because of this dependency, a selection may be automatically
checked and grayed out when another option is selected. For example, if
you choose to create a Tuning Pack repository, the Oracle Enterprise Manager
option is automatically selected because it is required.
When you choose Drop, Oracle Enterprise Manager is selected
by default. The Oracle Diagnostics Pack, Oracle Tuning Pack, and the Oracle
Change Management Pack are also selected because that repository cannot
exist without the Oracle Enterprise Manager repository. If you want to
drop only a specific pack's repository, remove the check on the Oracle
Enterprise Manager repository; then, check the option for the pack you
would like to remove.
The last page of the wizard allows you to enter the login
information for the repository where the operation you have requested will
be performed. The process takes a few minutes to complete.
All repository objects which are required by a particular
tool will be created the first time the tool is started. Alternatively,
the user can go into the repository and create all the repository objects
If you have an existing repository from a previous release of Oracle Enterprise Manager, check for compatibility:
If there is an unexpected failure during a repository upgrade,
the repository will need to be recreated. To prevent having to recreate
repositories at a future date, Oracle recommends that you save your repository.
Saving the repository protects the user's manually entered information,
such as events, jobs, and preferred credentials, as well as collected information
for products such as Oracle Expert and Trace.
Repositories can be saved by doing a full cold backup (take
the database off-line and copy datafiles to storage) or by exporting the
To start the Enterprise Manager Console, select Oracle Enterprise Manager from the Oracle Enterprise Manager folder on the Start Menu.
Only one instance of the Oracle Enterprise Manager Console can be run on a machine. However, you can run multiple instances of the DBA tools. Oracle Enterprise Manager is not supported to be run from a remote machine. It is only supported if run locally. Shared installs of the console are not supported.
Oracle Enterprise Manager requires unique usernames across all repositories whether or not the repositories are in different databases, because:
The process for connecting to a repository is outlined below.
If the repository does not exist, it is automatically created and a dialog box informs you of the operation.
You should not log on to the Console repository multiple times with the same username. A warning displays if you attempt this. You should only ignore the warning if the previous Console session was aborted or a machine was disconnected. When a username is logged in multiple times, agent notifications are sent to the most recent login.
The Oracle Enterprise Manager Console must discover network
services, such as databases, listeners, and nodes, to populate the Navigator
tree, in order to manage these services for the Job Scheduling and Event
The Navigator's Service Discovery feature provides wizards
for identifying network services and populating the Navigator tree.
To begin discovering services, your Oracle networking system must be properly installed. Methods of discovering services are listed below:
|Method||Function||For Agent Version|
Discover New Services Wizard
Discovers new nodes and the services on the nodes.
Intelligent Agent release 7.3.3 or higher using the TCP/IP protocol
Refresh Services Wizard
Refreshes and retries discovery on nodes
Intelligent Agent release 7.3.3 or higher using the TCP/IP protocol
Manually Define Services Wizard
Enables you to manually enter information about services on nodes
Does not have an Oracle Intelligent Agent or has a pre-7.3.3 Oracle Intelligent Agent
Discovery with topo_ops.ora file
Manual addition of Oracle Parallel Servers that cannot be added with the Navigator Service Discovery
Has a pre-7.3.3 Oracle Intelligent Agent
The intelligent agent must be up at discovery time.
If you have upgraded from a pre-220.127.116.11 Oracle Intelligent Agent, you must delete services already discovered and rediscovered them. The 18.104.22.168 and later agents support global database names.
To discover services:
If this in a new install, the discovery wizard will appear.
If this is not a new install, start the wizard. From the Main menu, select Navigator->Service Discovery->Discover New Services, and click the Next button.
To enter nodes in the wizard, type the node name into the
"New Node" field and click the Add button. Repeat for each node.
If you have many nodes, you may want to construct two text files containing their names. The file should contain each node name on its own line. Name the text file *.text so that Oracle Enterprise Manager may find it.
When requested through the Navigator Discovery menu option,
the agent passes information from the services.ora file to the Enterprise
Manager Console to populate the Navigator tree.
If you could not discover the database(s) in question, please
refer to your platform-specific agent. For NT users, please refer to Troubleshooting
the NT Agent If It Did Not Start Up on page 1-8. For UNIX users,
please refer to Troubleshooting the UNIX
Agent If It Did Not Start Up on page 1-16.
Oracle Enterprise Manager no longer uses topology.ora. We recommend that you remove all of the services in the Navigator tree and delete the topology.ora file that was used by the previous release.
Since Oracle Enterprise Manager (beginning with version 1.4.0) no longer uses a topology.ora file for Pre-7.3.3 agents, the databases which do not have a 7.3.3 or higher agent running must be manually added to the navigator.
Oracle Enterprise Manager Console and database applications can resolve service names via Oracle Names like any other Oracle Console application.
For more information on how to configure a client with Oracle
Names, see the Oracle Names Administrator's Guide.
Before attempting to discover these services or to run jobs, please test the Net8 connectivity. Please refer to Testing the Connectivity to Any SID on page C-4.
You can start an Enterprise Manager database administration application using one of the following methods:
|If you are using...||Then...|
You can choose from the following three methods:
Click on the tool's icon in the toolbar. The tool connects to the default database for the toolbar, if one has been specified.
For information on connecting to other databases, see the online help for the Administration Toolbar.
You can start the database administration applications without running the console. The only exceptions are Backup Manager and Data Manager which use the job system.
When a tool executes, it attempts to connect to an Oracle
database. For information on connecting to an Oracle database, see the
Before starting an application, when you select a database
in the Console, you are connected to the database according to the preferred
credentials that have been set up for the database or the credentials you
used to log on to the Console. If connection to the database fails for
any reason, the Login Information dialog box displays.
In order for the agent to execute jobs on a managed node,
you must specify valid credentials in the Console.
Jobs will be submitted using the repository owner login account unless the user sets the preferred credentials for the specific service (database, node, listener).
To set the preferred credentials, perform the following steps:
For NT users, you must set the preferred credentials for
the node (where the NT Agent resides) to be the same as the user that is
set up to "Logon as a batch job." The Agent authenticates the user name
and password for all owners of jobs that it runs. If you have not set the
preferences correctly, the "Failed to authenticate user" error occurs when
you submit a job.
For UNIX users, you must specify a valid UNIX operating system
user for the node (not db user for database). The user must have operating
system privileges to run programs like sqlplus, import/export on the UNIX
server. The privilege can be assigned to an existing local or domain user.
The "Failed to authenticate user" error will occur if the preferred credentials
do not match the account which started the agent.
Before running the backup subsystem or submitting an administration
task, such as database shutdown or startup, through the Oracle Enterprise
Manager Job system, you need to set up your database for remote operation.
The following procedure outlines the operations you need
to perform on both the server and client. The examples used in the following
procedure are for a UNIX environment. Windows NT directories, system variables,
and conventions will differ.
Refer to the operating system-specific documentation for
your Oracle database for the exact name of the password file creation utility
for your system.
setenv ORACLE_HOME your_oracle_home setenv ORACLE_SID your_oracle_sid
This example assumes that you have set up your database as ORACLE.
$ORACLE_HOME/bin/orapwd file=orapw<SID> password=your_password entries=10
The file name has to be orapw<SID>. Entries =
10 is the maximum number of distinct DBAs and OPERs.
There should be an orapw<SID> created in $ORACLE_HOME/dbs
create user remote identified by remote;
grant connect, resource to remote; grant sysdba to remote;
If you want to be able to start up and shut down your target database remotely, follow the steps below:
If you want to be able to perform on-line backups (hot backups),
you must put the database in ARCHIVELOG mode. Otherwise, you must shut
down your database; then, perform the backup. By default, the database
is in NOARCHIVELOG mode.
To put the database in ARCHIVELOG mode:
# Uncommenting the line below will cause automatic archiving if archiving has # been enabled using ALTER DATABASE ARCHIVELOG. # log_archive_start = true # log_archive_dest = %ORACLE_HOME%\database\archive # log_archive_format = "%%ORACLE_SID%%T%TS%S.ARC"
For more information on backup and recover strategies, see
the Oracle8 Backup and Recovery Guide.
The recovery catalog is a repository of information
that is used and maintained by Recovery Manager. Recovery Manager uses
the information in the recovery catalog to determine how to execute requested
backup and restore actions.
To use Oracle8 Recovery Manager with a recovery catalog,
you must first install the recovery catalog and then register your database.
No setup is required if you are using the control file. It is recommended
that you install the recovery catalog on a different location than the
For more information on recovery catalog maintenance, Recovery
Manager, and backup and recover strategies, see the Oracle8 Backup and
Your Oracle Enterprise Manager Job system must be functioning
properly before attempting to install the recovery catalog. You will need
the Job system to register the target database in the recovery catalog.
To set up a recovery catalog, you must complete the following procedures:
You can also use the Navigator menu from the Oracle Enterprise Manager console to bring up the Create Tablespace property sheet.
You can also use the Navigator menu from the Oracle Enterprise Manager console to bring up the Create User property sheet.
In the Name field, enter the name of the new user. For example,
In the Password and Confirm Password fields, enter a password.
For example, rman.
Choose the default tablespace. For example, RCVCAT.
Choose the temporary tablespace. For example, TEMPORARY_DATA.
Choose Role as the Privilege Type.
Grant the RECOVERY_CATALOG_OWNER role to the user.
When the job completes successfully, your backup and recovery
environment is configured. For more information on recovery catalog maintenance,
Recovery Manager, and backup and recover strategies, see the Oracle8
Backup and Recovery Guide.
A registry key is available for enabling the encoding of
Japanese characters when you are sending email.
To set the registry key
Please refer to the troubleshooting section below if you
should experience any problems during the setup of Oracle Enterprise Manager.
"Failed to authenticate user" error occurs when the user
submits a job. Use the following hints listed below:
If the agent is on a UNIX platform, check $ORACLE_HOME/bin/dbsnmp
and make sure that the dbsnmp executable is owned by root. Refer to Verifying
that root.sh Had Been Run Successfully on page 1-11.
For an NT node, make sure the preferred credentials for the
node is set to be the same as the user that is set up to "Logon as a batch
job." Refer to Setting Preferences on
If an NT agent is started with account other than system,
all jobs fail with the message "Failed to authenticate user." This occurs,
regardless of whether the job credential account has the "Logon as a batch
Using NT's User Manager from the Administrative Tools program group, you must assign the following privileges (User rights) to the account used to start the agent:
These privileges are required since the NT agent uses CreateProcessAsUser()
Win32 API to run jobs. Either create a new account with these privileges
or add these privileges to an existing account.
For an example of how to create a new Windows NT user account
on the local NT machine and grant privileges to the user, refer to Creating
a New NT User Account on page 1-4.
For an example of how to assign privileges to an existing
local user account, refer to Assigning
Privileges to an Existing NT User Account on page 1-5.
To start the agent on Windows NT as a non-system account, perform the following steps:
Job fails and the job output window shows:
output from job # lost
Use the following hints listed below:
On NT, the account must have "Logon as a batch job."
If the Oracle partition is formatted as NTFS (NT File System
which allows for local security of files and directories) then you should
also grant locally the permission set "Full Control" to the user assigned
"Logon as a batch job."
To grant the local file permissions:
Check to see if the agent can access the Console.
Try pinging the Console from the server machine. If you are
not sure about your IP address, please check by running the start button->
settings-> control panel-> network-> protocol-> TCP/IP and clicking the
If you cannot ping the Console, configure the Daemon Manager
host address to the TCP/IP address.
Ensure that the DNS Host entry is set to the node name in the listener.ora and tnsnames.ora files.
The user running jobs must have read/write permissions to
the $ORACLE_HOME\net80 directory (not just $ORACLE_HOME\net80\agent
directory) in order to write *.log files as well as write permissions
to the $TEMP directory or the $ORACLE_HOME directory.