Since 2010, OraERP is a Oracle Forums, Community of Oracle Professionals including Fusion/Cloud Application Consultants, Enterprise Architects, ERP Cloud, HCM Cloud, CX Cloud and OCI Experts, ERP Experts, Oracle Apps Functional Consultants, Apps DBAs, DBAs, Cloud DBAs, Digital Architect, PaaS Experts, IaaS, OCI Architects, Technical Consultants, Fusion Middleware Experts, SQL, PL/SQL Developers and Project Managers. Welcome to OraERP.com Social Community, a friendly and active community of Oracle Technology Professionals who believe that technology can ‘make the world a better place’. By joining Oracle ERP Community you will have the ability to Post Topics, Receive our Newsletter, subscribe to threads and access many other special features. Registration is Quick and Simple. Get unlimited access to Oracle Tutorials, Articles, eBooks, Tools and Tips .
Oracle Forum - The Knowledge Center for Oracle Professionals - Looking Beyond the Possibilities › Oracle Applications › Oracle E-Business Suite (EBS) › Oracle EBS R11i, R12.1, R12.2 Installation, Administration v
ORA-12505: TNS:listener does not currently know of SID given in connect

Thread Rating:
  • 28 Vote(s) - 3.64 Average
  • 1
  • 2
  • 3
  • 4
  • 5
ORA-12505: TNS:listener does not currently know of SID given in connect
07-17-2014, 07:09 AM,
#1
Anumeha Manish Offline
Junior Member
**
 		Posts: 13
Joined: Nov 2013
Reputation: 0
ORA-12505: TNS:listener does not currently know of SID given in connect
Dear All, I am doing application cloning and facing error with the code "ORA-12505: TNS:listener does not currently know of SID given in connect"
Environment is on Oracle RAC.
Thanks
Find
Reply
02-09-2015, 03:55 AM,
#2
Kashif Manzoor Offline
Super Moderator
******
 		Posts: 185
Joined: Oct 2010
Reputation: 0
RE: ORA-12505: TNS:listener does not currently know of SID given in connect
as per ora code description
ORA-12505:
TNS:listener does not currently know of SID given in connect descriptor
Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID for an instance (usually a database instance) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.

Action:
- Wait a moment and try to connect a second time.

- Check which instances are currently known by the listener by executing: lsnrctl services <listener name>

- Check that the SID parameter in the connect descriptor specifies an instance known by the listener.

- Check for an event in the listener.log file.
Website Find
Reply




Users browsing this thread: 2 Guest(s)