Page 1 of 4

How to Enable Enterprise Manager on the Oracle E-Business Suite Release

12 [ID 458533.1]

Modified 29-APR-2010 Type HOWTO Status PUBLISHED

In this Document
Goal
Solution
Environment
Instructions
Known Issues
References

Applies to:

Oracle Applications Manager - Version: 12.0 to 12.0.6 - Release: 12 to 12

Goal

This note describes how to enable the Oracle Enterprise Manager DB Control component to use it in
conjunction with a single Oracle E-Business Suite Release 12 database.

This is outside the context of Grid Control or the Oracle Applications Management Pack. This is discussed
separately in Note 394448.1.

The process described specifically applies to the hardware and operating system described below. It would be
expected that implementation of this functionality on other platforms would be mostly similar to the process
described below.

Solution

Environment

The environment used is a single node 12.0.0 fresh installation of the E-Business Suite with the VISION
demonstration database selected. The system was then upgraded to 12.0.2 by applying patch 6014659 (AD
A Delta 2) and patch 5484000 (12.0.2 Release Update Pack - RUP2). The system was then further upgraded
by applying patch 6272715 (AD A Delta 3) and patch 6141000 (12.0.3 Release Update Pack - RUP3). The
system is installed on a Dell Optiplex 745 running Red Hat Enterprise Linux AS release 4 (October Update 5)
running the 2.6.9-55.0.0.0.2.ELhugemem #1 SMP kernel.

This note only considers the enabling of the DB Control application used to manage a single 10g database.
Please refer to Note 394448.1 for managing multiple environments.

Instructions

For the process to complete successfully, the database and database listener must be started. It is not
neccessary that any other E-Business Suite services are running for this process to complete.

Source the environment for the 10g ORACLE_HOME. With a Release 12 environment this would mean
running the <SID>_<NODE>.env script as generated by AutoConfig in the 10gR2 ORACLE_HOME.

Follow Note 358201.1 to implement a password file and to overcome any ORA-01031 errors on the
database.

It is also worth considering converting your Applications database to work with an SPFile instead of an
init.ora. An SPFile is approximately analogous to being a binary equivalent of the init.ora and allows for

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWT... 5/28/2010
 Page 2 of 4

dynamic changes to many database parameters that previously would have required a database restart.
Refer to Note 166601.1 for details on how to convert to using an SPFile.

Next, as the owner of the 10gR2 ORACLE_HOME, run the following command to create the Enterprise
Manager repository:-

$ emca -config dbcontrol db -repos create

When the above create command is run you will be prompted for the following:

STARTED EMCA at Oct 15, 2007 12:26:22 PM

EM Configuration Assistant, Version 10.2.0.1.0 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.

Enter the values appropriate to your environment:-

Database SID: VIS12

Listener port number: 1533
Password for SYS user: change_on_install
Password for DBSNMP user: dbsnmp
Password for SYSMAN user: sysman
Email address for notifications (optional):
Outgoing Mail (SMTP) server for notifications (optional):
-----------------------------------------------------------------
You have specified the following settings

Database ORACLE_HOME ................ /oracle/VIS12/db/tech_st/10.2.0

Database hostname ................ xxxxxxx.xx.oracle.com

Listener port number ................ 1533
Database SID ................ VIS12
Email address for notifications ...............
Outgoing Mail (SMTP) server for notifications ...............
-----------------------------------------------------------------
Do you wish to continue? [yes(Y)/no(N)]: Y

The repository should then start to be created. Typically this can take anywhere between 10 and 60 minutes
depending on hardware and database configuration and size.

INFO: Creating the EM repository (this may take a while) ...

When the repository is created the following message should appear....

INFO: >>>>>>>>>>> The Database Control URL is http://xxxxxxxxxx.xx.oracle.com:1158/em

<<<<<<<<<<<
Enterprise Manager configuration completed successfully
FINISHED EMCA at Sep 13, 2007 2:13:48 PM

Use the above Database Control URL to access the Enterprise Manager console through a browser interface.

Us the following command to drop an EM repository that has already been created:

$ emca -deconfig dbcontrol db -repos drop

Refer to Metalink Note 278100.1 for more detailed instructions on how to drop the DB Control repository in a
10g database.

To enable or disable browser access to dbconsole use the following command after sourcing the
environment for the 10g ORACLE_HOME. With a Release 12 environment this would mean running the
<SID>_<NODE>.env script as generated by AutoConfig in the 10gR2 ORACLE_HOME.

$ emctl start dbconsole

To disable browser access use the following command:

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWT... 5/28/2010
 Page 3 of 4

$ emctl stop dbconsole

Known Issues

Pay particular attention to TZ (timezone) issues as these may become significant during EM setup. If the
repository fails to create, try setting the TZ value in the
<node>.<domain>_<ORACLE_SID>/sysman/config/emd.properties file to match the TZ environment variable.

The following error may occur when dropping the repository

Oct 29, 2007 1:05:25 PM oracle.sysman.emcp.EMReposConfig invoke

SEVERE: Error dropping the repository

For the above error, follow the workaround in Note 358201.1 to enable a password file. The password
specified on the orapwd command line must be the same as the SYS password used when running emca.

The following error may occur when creating the repository

Oct 29, 2007 2:31:31 PM oracle.sysman.emcp.EMReposConfig createRepository

CONFIG: ORA-01920: user name 'MGMT_VIEW' conflicts with another user or role name
ORA-06512: at line 40

For the above error, follow the workaround in Note 358627.1 and drop the SYSMAN and MGMT_VIEW users.

SQL> drop user SYSMAN cascade;

SQL> drop user MGMT_VIEW cascade;

If the above errors are encountered, repeat the following command to create the repository:-

$ emca -config dbcontrol db -repos create

When creating a fresh repository on a cloned database, there may be a problem where the password for the
DBSNMP user is rejected. Refer to Note 337260.1 which describes how to include several parameters on the
initial command line to overcome the problem. The emca log file will probably contain ORA-01034 and/or
ORA-27101 errors. A typical command line to create a fresh repository is as follows

$ emca -config dbcontrol db -repos recreate -SID PROD -PORT 1533 -ORACLE_HOME
/oracle/PROD/db/tech_st/10.2.0 -DBCONTROL_HTTP_PORT 1158

The emca utility will continue to prompt for the dbsnmp password however with the above command line, the
password will not be rejected as invalid. This issue seems limited specifically to PROD but not VISION
databases.

The following error may appear when trying to build the repository if using a fresh 12.0.4 install:-

$ORACLE_HOME/bin/emca: line 44: /nfs/bld/d29/VRIV204/db/tech_st/10.2.0/jdk/bin/java: No such file or

directory

To resolve the above error edit the $ORACLE_HOME/bin/emca script and correct the $ORACLE_HOME
location

References

NOTE:166601.1 - How to Migrate from a Pfile to an Spfile

NOTE:278100.1 - How To Drop, Create And Recreate DB Control In A 10g Database
NOTE:337260.1 - Dbsnmp Password Not Accepted
NOTE:358201.1 - Problem: Running EMCA Fails With 'ORA-01031: insufficient privileges' When Database
Password File Is Not Configured

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWT... 5/28/2010
 Page 4 of 4

NOTE:358627.1 - Problem - RepManager Create Repository Error = 14 during install of Grid Control 10.2 into
an existing database

Related

Products

z Oracle E-Business Suite > Applications Technology > Lifecycle Management > Oracle Applications
Manager

Keywords

ENTERPRISE~MANAGER; ENTERPRISE; E-BUSINESS

Errors

ORA-1034; ORA-6512; ORA-27101; ORA-1031; ORA-1920; 01031 ERROR; 27101 ERROR

Back to top

Rate this document

https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&doctype=HOWT... 5/28/2010