Recovery from OEM startup failure (Patch 8350262 is not patched)

Scenario:

The customer said that the OEM was suddenly unavailable. Because the application is linked to some OEM pages, it must be restored immediately.

Symptom:

Log on to the client server and execute the emctl status dbconsole. An error is reported when an attempt is made.

Solution:

1) Start dbconsole, wait for a long time, and the prompt is not successful. Some logs are as follows:

1. 2011-6-3 18:44:06 Oracle. sysman. emcp. util. DBControlUtil startOMS
2. Information: Starting Database Control (this operation may take some time )...
3. 2011-6-3 18:44:06 oracle. sysman. emcp. util. PlatformInterface serviceCommand
4. Configuration: required type: 0
5. 2011-6-3 18:44:06 oracle. sysman. emcp. util. PlatformInterface serviceCommand
6. Configuration: Starting Windows service... OracleDBConsoleprotect
7. 2011-6-3 18:44:06 oracle. sysman. emcp. util. PlatformInterface serviceCommand
8. Configuration: Waiting for service 'oracledbconsoleprotect 'to fully start
9. 2011-6-3 18:44:16 oracle. sysman. emcp. util. PlatformInterface serviceCommand
10. Configuration: Waiting for service 'oracledbconsoleprotect 'to fully start
11. 2011-6-3 18:44:26 oracle. sysman. emcp. util. PlatformInterface serviceCommand
12. Configuration: Waiting for service 'oracledbconsoleprotect 'to fully start

2) assume that the IP address is modified. After confirming that the network configuration is correct, rebuild the database and Database Control Group.

The above error is still prompted, and the OEM cannot start up.

Later, replace the host name with 127.0.0.1 and recreate the database and Database Control Group. It cannot be started.

Two hours later .......

3) after google review, it is very likely to be a bug. Patch 8350262 must be installed on 10.2.0.4. Download patch --------- Patching

4) when the database is rebuilt, an error is returned:

SYSMAN already exists ........

The database can be deleted, but an error is reported when the database is created.

Delete some objects in the database:

1. SQL> DROP public synonym SETEMVIEWUSERCONTEXT;
3. The synonym has been deleted.
5. SQL> DROP PUBLIC SYNONYM MGMT_TARGET_BLACKOUTS;
7. The synonym has been deleted.
9. SQL> drop role MGMT_USER;
11. The role has been deleted.
13. SQL> DROP USER MGMT_VIEW CASCADE;
15. The user has been deleted.
17. SQL> DROP USER SYSMAN CASCADE;

Try creating a database again.

5) Create a database control group and report an error ......

Follow the prompts to indicate that the database instance cannot be connected.

6) after entering the OEM, the system prompts that the database instance and the listener are not started, but the instance and the listener are well-known.

I suddenly remembered whether the host name in tnsname. ora and listener. ora was changed to 127.0.0.1. Modify it as is. Disable OEM, restart listener, and restart OEM ....

Finally everything is normal.

7) follow the prompts above to change the SYSMAN password and receive the ticket .....

Summary:

Normally, it's okay to look at oracle bugs. It's always good. it's time-saving, worry-free, and worry-free;

Try not to modify the Host IP address when using the OEM;

View More oracle operation logs.