Manually Configuring Oracle Enterprise Manager for a Sentinel Instance
Novell Cool Solutions: Feature
By Tom Burt
Digg This -
Posted: 28 Nov 2007
Installing Sentinel creates a database instance on Oracle 10g but does not configure the Enterprise Manager dbconsole.
Customers who administer the Sentinel systems in their environment are, most often, not database administrators. A prerequisite for Sentinel is a database for storing events but Novell does not include the Database in the Sentinel install suite of components. The assumption is that customers will have the necessary database experience to administer their database. This solution is intended to help guide customers through the manual configuration of an Enterprise Manager dbconsole for their installed Sentinel instance.
Currently the supported databases for Sentinel 6.0 are Oracle, (9i or 10g), and MSSQL 2005. MSSQL2005 installs the MSSQL Management Studio and does not require any additional configuration for access to additional instances.
Note: This article will focus primarily on Oracle 10g, as it is the latest release for Oracle that is supported with Sentinel 6.0. Oracle installs Oracle Enterprise Manager, OEM, as well - but it does not configure each instance for access to OEM. In order to manually configure your Enterprise Manager to connect to your Sentinel database instance, you must complete these tasks:
- Verify that the user you are authenticating to the Solaris or Linux system has the Oracle Environment variables set correctly.
- Manually create and configure your Database Control Repository.
- Set up the OC4J Application Server and start the dbconsole.
Verifying the Oracle Environment Variables
1. Enter the following commands at the console prompt:
esecadm@TBurt01:~>env | grep ORACLE*
You should see the following with the file Path pointing to your Oracle install.
esecadm@TBurt01:~>env | grep ORACLE* ORACLE_SID=ESEC ORACLE_BASE=/opt/oracle ORACLE_HOME/opt/oracle/product/10.2/db_1/
esecadm@TBurt01:~>echo $PATH /opt/novell/sentinel6/bin:/\ /sbin:/usr/sbin:/usr/local/sbin:/\ /opt/gnome/sbin:/root/bin:/\ /usr/local/bin:/usr/bin:/usr/X11R6/bin:/\ /bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/\ /usr/lib/mit/bin:/usr/lib/mit/sbin:/\ /opt/novell/sentinel6/3rdparty/SonicMQ/MQ7.0/bin/\ /opt/oracle/product/10.2/db_1/bin:
The above variables are described as follows:
ORACLE_SID: This is the instance name. Check your init.ora for the instance_name parameter. The Sentinel install creates an instance with instance_name as ESEC by default. This may be different on your server depending on the options you chose during install. Either way, the ORACLE_SID should be set to your instance name for the Sentinel database instance. You can check your oratab file, (usually located in the /etc/ directory), for a list of all database instances installed on your server.
ORACLE_BASE: Refers to the environment variable that points to the base directory where the Oracle software was installed. This will be the same for all instances. On Unix systems this will typically be /opt/oracle or /app/oracle
ORACLE_HOME: Refers to the environment variable pointing to the directory where your Oracle software is installed. On Unix systems this will typically be /opt/oracle/product/10.2/db_1/ for Oracle 10g.
PATH:Refers to the directories that are in your System Path. The imporant one for the Oracle configuration is the /opt/oracle/product/10.2/db_1/bin: variable as this directory includes many of the tools we will be using to configure your dbconsole.
2. If the above environment variables are set correctly, you are ready to continue. If the variables are not set correctly, you should modify your users profile to include them before continuing. If you prefer to continue without modifying your profile, you will need to export the variable for this Terminal Session as well as any future sessions.
After verifying that your environment variables are set correctly, you have one more step to verify before configuring the database control repository: make sure that your netservices files are configured correctly. Sentinel installs the instance database objects and schema as well as configures the Net Services components, so unless you have modified any of this it should already be configured.
To verify, you need to check your tnsnames.ora, listener.ora, and sqlnet.ora files to verify that ESEC is listed.
3. You can verify this by using sqlPlus on the machine and connecting to the Sentinel (ESEC) instance.
4. To do so, initiate the following command:
You should see the following response:
SQL*Plus: Release 10.2.0.3.0 - Production on <Date you initiated this command> Copyright (c) 1982, 2006, Oracle All Rights Reserved. Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production with Partitioning, OLAP, and Data Mining options SQL>
This indicates that you have connected to the Oracle instance created by the Sentinel install.
5. You can further verify by initiating the following command:
SQL>select db_version from esec_db_version;
This should return something similar to the following for Sentinel 6.0Sp1:
SQL> select db_version from esec_db_version; DB_VERSION -------------------------------------------------- 22.214.171.124_SP1
Creating and Configuring the Database Control Repository
1. To create and configure your database control repository, run the following commands in your terminal session:
emca -repos create
This command will prompt you for your Database SID, LIstener port number, Password for your SYS user, and the Password for your SYSMAN user. All of this information should be known prior to running the command. The password for the SYS and SYSMAN users were configured during the Sentinel install.
esecadm@TBurt01:~> emca -repos create STARTED EMCA at Nov 16, 2007 2:08:00 PM EM Configuration Assistant, Version 10.2.0.1.0 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID: ESEC Listener port number: 1521 Password for SYS user: xxxxxxxx Password for SYSMAN user: xxxxxxxx Do you wish to continue? [yes(Y)/no(N)]: y Nov 16, 2007 2:08:24 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /opt/oracle/product/10.2/db_1/cfgtoollogs/emca/ESEC/emca_2007-11-16_02-08-00-PM.log. Nov 16, 2007 2:08:24 PM oracle.sysman.emcp.EMReposConfig createRepository INFO: Creating the EM repository (this may take a while) ...
2. Once your repository is created, you must configure your database control as follows:
emca -config dbcontrol db
This command will again prompt you for your Database SID, Listener port number, Password for SYS, DBSNMP, and SYSMAN users. It will also ask you for data to configure email for notifications from the EM.
esecadm@TBurt01:~>emca -config dbcontrol db STARTED EMCA at <current date> EM Configuration Assistant, Version 10.2.0.1.0 Production Copyright (c) 2003, 2005, Oracle. All rights reserved. Enter the following information: Database SID:ESEC Listener port number: 1521 Password for Sys user: xxxxxxxx Password for DBSNMP user: xxxxxxxx Password for SYSMAN user: xxxxxxxx Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional): ------------------------------------------------- You have specified the following settings Database ORACLE_HOME................./opt/oracle/product/10.2/db_1/ Database hostname.................TBurt01 Listener port number.................1521 Database SID.................ESEC Email address for notifications................ Outgoing Mail (SMTP) server for notifications................ -------------------------------------------------- Do you wish to continue? [yes(Y)/no(N)]:
3. Select Yes (press Y) to continue, and you should see something similar to the following:
Do you wish to continue? [yes(Y)/no(N)]: Y Nov 16, 2007 1:54:27 PM oracle.sysman.emcp.EMConfig perform INFO: This operation is being logged at /opt/oracle/product/10.2/db_1/cfgtoollogs/emca/ESEC/emca_2007-11-16_01-47-22-PM.log. Nov 16, 2007 1:54:30 PM oracle.sysman.emcp.util.DBControlUtil stopOMS INFO: Stopping Database Control (this may take a while) ... Nov 16, 2007 1:55:39 PM oracle.sysman.emcp.ParamsManager getLocalListener Nov 16, 2007 1:55:46 PM oracle.sysman.emcp.util.DBControlUtil startOMS INFO: Starting Database Control (this may take a while) ... Nov 16, 2007 1:57:45 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration INFO: Database Control started successfully Nov 16, 2007 1:57:45 PM oracle.sysman.emcp.EMDBPostConfig performConfiguration INFO: >>>>>>>>>>> The Database Control URL is http://TBurt01:1158/em <<<<<<<<<<< Enterprise Manager configuration completed successfully FINISHED EMCA at Nov 16, 2007 1:57:45 PM
Note: You may see a warning about retrieving the listener for your hostname. This may be normal, but you should verify your host settings.
When the process is completed, you can check for the control file by looking in the $ORACLE_HOME/
Starting the Console
Now that you have created your repository and database control, you are ready to start the console. To start the console, initiate the following command at your terminal console:
esecadm@TBurt01:~>emctl start dbconsole
You will see the status of the console starting up; it will actually list the URL to connect to OEM. For example, I will see the following on my machine:
By lauching a browser and going to this page, I will now be prompted to login to OEM with the Oracle database instance of ESEC.
You now have a working repository and database control to access OEM for your ESEC/Sentinel instance. Have fun, and be careful.
- SuSE Linux Enterprise Server 10 SP1
- Oracle 10g
- Sentinel 6.0 SP1
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com