Em does not start after servername has changed

Question

Is there a possibility to get the datanbase running in an ordinary way after the servername has changed after the installation of the database?
System:
Windows Server 2003R2
Oracle 10g R2
I have changed tnsnames.ora and listener.ora, so the client connection runs well.
But enterprise manager does not start:
If I want to start "Database control" there is the old servername in the http-Link:
http://oldservername:1158/em
If I replace the old name with "localhost" or the new name I get also an errormessage that the site cant be found.
In services the OracleDBConsole cant be started.
with ">emctl start dbconsole" I get the error message ORACLE_SID is not defined.
Defining it does not change the behaviour.
Do I have to reinstall the database?
Thanks
Roswitha

Answer 1

Subject: How To Drop, Create And Recreate DB Control In A 10g Database
Doc ID: Note:278100.1 Type: BULLETIN
Last Revision Date: 05-JUN-2007 Status: PUBLISHED
In this Document
Purpose
Scope and Application
How To Drop, Create And Recreate DB Control In A 10g Database
DB Control options:
A. Delete DB Control Objects:
B. Create DB Control Objects
C. Recreate/ReConfig DB Control
Applies to:
Enterprise Manager Grid Control - Version: 10.1 to 10.2
Information in this document applies to any platform.
DBConsole
Purpose
This article provides detailed instructions on how to 1) create, 2) drop and 3)recreate the repository and configuration files for the DB Control application used to manage a single 10g Database.
Scope and Application
The steps in this article are written for a DBA or System Administrator who needs to create, drop or reconfigure the DB Control Application.
The format of the document will include steps for both 10.1 and 10.2 EMCA because the commands changed between the two releases.
How To Drop, Create And Recreate DB Control In A 10g Database
DB Control options:
A. Delete DB Control Objects:
Option 1. Delete DB Control Configuration Files using EMCA scripts
Option 2. Delete DB Control Configuration Files Manually:
Option 3. Delete DB Control Repository Objects using RepManager
Option 4. Delete DB Control Repository Objects Manually
Option 5. Delete DB Control Configuration Files and Repository Objects using EMCA
Option 1. Delete DB Control Configuration Files using EMCA scripts:
For DB Control 10.1.x, run the command: <ORACLE_HOME>/bin/emca -x <sid>For DB Control 10.2.x, run the command: <ORACLE_HOME>bin/emca -deconfig dbcontrol db
Option 2. Delete DB Control Configuration Files Manually:
Remove the following directories from your filesystem:
<ORACLE_HOME>/<hostname_sid>
<ORACLE_HOME>/oc4j/j2ee/OC4J_DBConsole_<hostname>_<sid>
NOTE:
On Windows you also need to delete the DB Console service:
- run regedit
- navigate to HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
- locate the OracleDBConsole<sid> entry and delete it
Alternatively on Windows XP and Windows Server 2003 you can run the following from the command line:
'sc delete <service_name>'
- where <service_name> is the DB Control service name (typically: OracleDBConsole<sid>)
Also available from Microsoft is the delsrv.exe command. (Free download from Microsoft)
Option 3. Delete DB Control Repository using RepManager:
This option is not as complete as the other options. You may find that dropping the repository using the commandline options is a better solution. Also note, RepManager is not used to create a DB Control Repository.
In both 10g R1 and R2 run: <ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager <hostname> <listener_port> <sid> -action drop
Option 4. Delete DB Control Repository Objects Manually
Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:SQL> SHUTDOWN
IMMEDIATE;SQL> STARTUP RESTRICT;SQL> EXEC sysman.emd_maintenance.remove_em_dbms_jobs;SQL> EXEC sysman.setEMUserContext('',5);SQL>
REVOKE dba FROM sysman;SQL> DECLARECURSOR c1 ISSELECT owner, synonym_name nameFROM dba_synonymsWHERE table_owner
= 'SYSMAN';BEGINFOR r1 IN c1 LOOPIF r1.owner = 'PUBLIC' THENEXECUTE IMMEDIATE 'DROP PUBLIC SYNONYM '||r1.name;ELSEEXECUTE
IMMEDIATE 'DROP SYNONYM '||r1.owner||'.'||r1.name;END IF;END LOOP;END;/SQL> DROP USER mgmt_view CASCADE;SQL> DROP ROLE mgmt_user;SQL> DROP USER sysman CASCADE;SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION;
Note: The above will completely delete the DB Control repository from the database; under certain circumstances (e.g. you want to recreate the repository later on) the following statements may be sufficient to remove the repository:
Logon SQLPLUS as user SYS or SYSTEM, and drop the sysman account and management objects:SQL> drop user
sysman cascade;SQL> drop role MGMT_USER;SQL> drop user MGMT_VIEW cascade;SQL> drop public synonym MGMT_TARGET_BLACKOUTS;SQL> drop public synonym SETEMVIEWUSERCONTEXT;
Option 5. Delete DB Control Configuration Files and Repository Objects using EMCA
For DB Control 10.1.x, dropping both the configuration files and the repository objects is a two step process. Run the following two commands:
<ORACLE_HOME>/bin/emca -x <sid><ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager <hostname> <listener_port> <sid> -action drop
For DB Control 10.2.x, both configuration files and repository objects can be deleted with a single command. Run the command:
<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop
B. Create DB Control Objects
Option 1. Create the DB Control Configuration Files
Option 2. Create the DB Control Repository Objects and Configuration Files
Option 1. Create the DB Control Configuration Files
To create only the DB Control configuration files, skipping the repository creation (this would be done for instance if you dropped only the files and left the repository in place):
For DB Control 10.1.x, run the command: <ORACLE_HOME>/bin/emca -rFor DB Control 10.2.x, run the command: <ORACLE_HOME>/bin/emca -config dbcontrol db
Option 2. Create the DB Control Repository Objects and Configuration Files
For DB Control 10.1.x, run the command: <ORACLE_HOME>/bin/emcaFor DB Control 10.2.x, run the command: <ORACLE_HOME>bin/emca -config dbcontrol db -repos create
C. Recreate/ReConfig DB Control
Option 1. Recreate the DB Control Configuration Files only (leave Repository intact)
Option 2. Recreate the DB Control Configuration Files and Repository
In 10.2, the EMCA commands can be used to reconfigure the existing installs without removing them first.
Option 1. Recreate the DB Control Configuration Files only (leave Repository intact):
For DB Control 10.2.x, run the command:
<ORACLE_HOME>/bin/emca -config dbcontrol db
Option 2. Recreate the DB Control Configuration Files and Repository
For DB Control 10.2.x, run the command:
<ORACLE_HOME>/bin/emca -config dbcontrol db -repos recreate
For additional information on EMCA commandline options, please see the Oracle Enterprise Manager 10g Advanced Configuration Guide or see Note 330130.1 Overview Of The EMCA Commands Available for DB Control 10.2