afcnoc
asked on
EM-dbconsole service will not start after hostname and ip change.
I have an Oracle 10g server. The hostname and IP address of the server were changed and now the dbconsole service will not start. I know this problem is related to the name/ip change but not sure how to fix it.
I have seen articles that say to run emca -x to drop and recreate the "repository" but I am not sure if this will effect the running database/schema. This is an online production server and can't be brought down at this time.
I have seen articles that say to run emca -x to drop and recreate the "repository" but I am not sure if this will effect the running database/schema. This is an online production server and can't be brought down at this time.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'll give it a try and let you know. May not get to it until tomorrow though.
ASKER
Sorry it took so long to get back to this...I got pulled for another project.
The drop/create worked perfectly!!
To anyone else using this solution here are a couple of pointers.
Make sure you enter the SID correctly, it has to match the SID on the server including the case of the letters ( MySid is not the same as mysid).
Make sure you have the passwords for the following user accounts before starting;
SYS
SYSMAN
DBSNMP
The drop/create worked perfectly!!
To anyone else using this solution here are a couple of pointers.
Make sure you enter the SID correctly, it has to match the SID on the server including the case of the letters ( MySid is not the same as mysid).
Make sure you have the passwords for the following user accounts before starting;
SYS
SYSMAN
DBSNMP
Currently after the IP change - I updated the TNSNames.ora and Listener.ora. The console doesnot work. When I try the follwoing
1) conn sys@VRD as SYSDBA
I get connected to idle instance
2) Now when I run startup - the instance is getinng terminated forcefully.
Any solutions to this problem.
1) conn sys@VRD as SYSDBA
I get connected to idle instance
2) Now when I run startup - the instance is getinng terminated forcefully.
Any solutions to this problem.
PS: It will not affect any application schema.