Professional Documents
Culture Documents
Overview
When you choose to create a preconfigured database during the Oracle 10g
installation, you can select the Oracle Enterprise Manager (OEM) interface that you want
to use to manage the database. The following options are available:
If an Oracle Management Agent is not installed, you must choose to use Database
Control to manage the database. However, if you install Oracle Management Agent after
you install Oracle Database, you can then use Grid Control to manage this database.
o Database Control
Custom installation
If you choose the Custom installation type or the Advanced database configuration option
during the installation, the Installer does not display the OEM setup screens. Instead, it
runs the Database Configuration Assistant (DBCA) in interactive mode, which enables
you to create a custom database.
DBCA also enables you to specify the Oracle Enterprise Manager interface that you want
to use. Furthermore, you can also use DBCA after the installation to configure Database
Control for a database that was not previously configured to use it.
However, if you decide to setup your own Database, you must install the Database
Control manually.
The Database Control relies on various underlying technologies to discover, monitor, and
administer the Oracle Database environment.
From the Database Control, you can monitor and administer a single Oracle Database
instance.
The Database Control Framework consists of the Database Control and its underlying
technologies:
o A local version of the Oracle Management Service designed to work with the local
database or clustered database.
o A local Oracle Management Repository installed in the local database and designed
to store management data for the Database Control.
Create the Database Control Repository and setup the OC4J Application Server
Make sure, that you can connect to the Repository Database (Test it with SQL*Plus).
Examples for Setup Files can be found here:
Windows Linux
LISTENER.ORA listener.ora
SQLNET.ORA sqlnet.ora
TNSNAMES.ORA tnsnames.ora
Now start the Oracle EM dbconsole Build Script ($ORACLE_HOME/bin/emca for Linux
and $ORACLE_HOME\Bin\emca.bat for Windows).
---------------------------------------------------------
You have specified the following settings
M oracle.sysman.emcp.EMConfig createRepository
INFO: Creating repository ...
M oracle.sysman.emcp.EMConfig perform
INFO: Repository was created successfully
M oracle.sysman.emcp.util.PortQuery findUsedPorts
INFO: Searching services file for used port
AM oracle.sysman.emcp.EMConfig getProperties
...........
...........
INFO: Starting the DBConsole ...
AM oracle.sysman.emcp.EMConfig perform
INFO: DBConsole is started successfully
INFO: >>>>>>>>>>> The Enterprise Manager URL
ishttp://akira:5500/em <<<<<<<<<<<
Enterprise Manager configuration is completed successfully
FINISHED EMCA at Fri May 14 10:55:25 MEST 2004
http://akira:5500/em
If you look at the installed schemas, you can now find the SYSMAN schema, which is the
database Control Repository.
Troubleshooting
If you have troubles to connect, check your local configuration which can be found
in $ORACLE_HOME/<hostname>_<SERVICE_NAME>. For Example our DbConsole Setup
Directory looks as follows:
$ pwd
/opt/oracle/product/10.1.0/akira_AKI1/sysman/config
$ ls -l
-rw-r--r-- b64InternetCertificate.txt
-rw-r--r-- emagentlogging.properties
-rw-r--r-- emd.properties
-rw-r--r-- emomsintg.xml
-rw-r--r-- emomslogging.properties
-rw-r--r-- emoms.properties
-rw-r--r-- OUIinventories.add
The most important file is emoms.properties, where you can find all the configuration
parameters.