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.
Implement a password file and to overcome any ORA-01031 errors on the database. (follow metalink note: 358201.1)
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 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:
$ emctl stop dbconsole
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