OMS Startup Fails during Repository Connection Attempt due to_310772.1

rongshiyuan發表於2014-05-12

OMS Startup Fails during Repository Connection Attempt due to Database Connectivity Problems and Console Access Fails with '503 Service Unavailable' (Doc ID 310772.1)

In this Document

Symptoms

Cause

Solution

References

Applies to:

Enterprise Manager Base Platform - Version 10.1.0.4 to 10.2.0.5 [Release 10.1 to 10.2]
Information in this document applies to any platform.
***Checked for relevance on 05-Oct-2011***
Checked for relevance on 16-Jul-2013

Symptoms

Starting the OMS using 'opmnctl startall' completes successfully and the output of 'opmnctl status' shows:

But trying to access the Grid Console URL from the browser fails with the error:

503 Service Unavailable
Servlet error: Service is not initialized correctly. Verify that the repository
connection information provided is correct.

The 'emctl status oms' command returns:

Oracle Enterprise Manager 10g Release 5 Grid Control
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Oracle Management Server is not functioning because of the following reason:
Connection to the repository failed. Verify that the repository connection information provided is correct.

The /sysman/log/emoms.trc can have one of the following errors:

java.sql.SQLException: Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
The Connection descriptor used by the client was:
(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)(PORT=1521)))(CONNECT_DATA=(SID=emrep)))

jdbc.ConnectionCache _getConnection.352 - Io exception: The Network Adapter could not establish the connection

java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:174)

Cause

This issue could be caused by the following :

- The value of oracle.sysman.eml.mntr.emdRepConnectDescriptor in /sysman/config/emoms.properties has incorrect details for the Repository database connection details.

- The value of oracle.sysman.eml.mntr.emdRepConnectDescriptor in /sysman/config/emoms.properties has incorrect syntax, due to which the repository database connection attempt fails.
Without a correct descriptor in this file, the OMS cannot find a repository and will fail to start.

- The value of oracle.sysman.eml.mntr.emdRepConnectDescriptor in /sysman/config/emoms.properties has correct etails, but the listener servicing the repository database is not UP.

Solution

To implement the solution, please execute the following steps:

1. Stop the opmn components:

cd /opmn/bin
opmnctl stopall

2. Take a backup of the the existing /sysman/config/emoms.properties file to emoms.properties_.

3. Edit the following line in the emoms.properties file:

oracle.sysman.eml.mntr.emdRepConnectDescriptor=(DESCRIPTION\=(ADDRESS_LIST\=(ADDRESS\=(PROTOCOL\=TCP)(HOST\=hostname)(PORT\=1521)))(CONNECT_DATA\=(SID\=EMREP)))

4. Review the syntax above carefully. Each paranthesis and value is required.

5. Test to see if the above connect descriptor works:

a) Edit the connect descriptor and remove the escape characters '\':

(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)PORT=1521)))(CONNECT_DATA=(SID=EMREP)))

b) Test the connection string as follows:

cd /bin
./sqlplus sysman/@'(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)PORT=1521)))(CONNECT_DATA=(SID=EMREP)))'

If the connection is successful then move to step 6 else re-check:
- hostname, port, SID/Service_name is correct
- there is a listener running on hostname/port specificed in the connect descriptor
- the listener on the specified port has a valid service for this repository database and the connections are not 'blocked'.
- the database is actually in status Open

6. Save the changes to the emoms.properties file.

7. Stop and re-start the OMS:

cd /opmn/bin
opmnctl startall

Try connecting to the Grid Console URL from the browser