home Enterprise Manager Documentation

StartStop Enterprise Manager Console

emctl start dbconsole 
emctl stop dbconsole   
emctl status dbconsole

Create/RecreateDBConsole for A Cloned Instance

Versions: 10.2 , 11g
1. Create a password file 
orapwd file=$ORACLE_HOME/dbs/orapwDEVL password=welcome entries=5

The password file is located in the $ORACLE_HOME/dbs directory
2. Add the following line to the initSID.ora
###For sysman  
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
3. Reboot the instance 
connect / as sysdba
shutdown immediate
startup
4. Set ORACLE_HOSTNAME - works without this 
export ORACLE_HOSTNAME=earth.nasa.love.gov
5. Check for the sysman user: 
select username from DBA_USERS where username =   'SYSMAN';
 
6. Create the DB Control Repository Objects and Configuration files
   in one of the following ways:

If there is a sysman user, drop it and recreate the Repository and Config file. See # 5

Recreate the DB Control Repository Objects and Configuration Files 

<ORACLE_HOME>/bin/emca -config dbcontrol db -repos recreate

I tried the following and it still asked for a SID etc...so you only need to use the line above and answer the questions posed.

emca -config dbcontrol db -repos recreate -SID DEVL -port 1524 
-ORACLE_HOME /u01/oracle/DEVL/db/tech_st/11.1.0 -DBCONTROL_HTTP_PORT 1168
 
If the sysman user does not exist, then don't recreate or drop the repository, 
all you need to do is:
Create the DB Control Repository Objects and Configuration Files
<ORACLE_HOME>bin/emca -config dbcontrol db -repos create

Logs are located at $ORACLE_HOME/cfgtoollogs/emca/<SID>/

example:       
emca_2010_02_28_23_34_33.log
emca_repos_drop_2010_02_28_23_35_55.log
emca_repos_create_2010_02_28_23_39_37.log

When it's complete, it will give you the url to connect

Other commands:

Delete DB Control Configuration Files and Repository Objects using EMCA

<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop
To create only the DB Control configuration files: 
<ORACLE_HOME>/bin/emca -config dbcontrol db
When recreating or dropping the repository, the emca command requires the database to be quiesced.
To unquiesce:

Kill the emca command
2. Connect to the database with SYS account through SQL*Plus
SQL > alter system unquiesce;