EM 12c, EM 13c: Enterprise Manager Cloud Control Start [emctl start OMS] Fails With Error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

(Doc ID 2160864.1)

Last updated on DECEMBER 21, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.2.0 and later
Information in this document applies to any platform.

Symptoms

Starting the Enterprise Manager 12.1.0.4 Cloud Control OMS with this command fails: emctl start oms

The output of a repository connection detail query provides this information:

$ emctl config oms -list_repos_details
Oracle Enterprise Manager Cloud Control 12c Release 4  
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Repository Connect Descriptor : (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<repository database host name>)(PORT=15021)))(CONNECT_DATA=(SID=<repository SID name>)))
Repository User : SYSMAN



The <OMS instance base>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out shows:

Error Code: 0
INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
INFO: Found persistence provider "org.eclipse.persistence.jpa.PersistenceProvider". OpenJPA will not be used.
<Jul 13, 2016 10:05:44 PM PDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "sysman-opss-ds":
Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
.>
[EL Severe]: 2016-07-13 22:05:45.401--ServerSession(47281744)--Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.3.1.v20111018-r10243):
org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException:
Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor

 

 

Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms