ORA-12521: TNS:listener does not currently know of instance requested 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 in addition to the service name an instance name 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 - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

- Wait a moment and try to connect a second time. - Check which instances are currently known by the listener by executing: lsnrctl services - Check that the INSTANCE_NAME parameter in the connect descriptor specifies an instance name known by the listener. - Check for an event in the listener.log file.

update : 30-04-2017

ORA-12521 - TNS:listener does not currently know of instance requested in connect descriptor
ORA-12521 - TNS:listener does not currently know of instance requested in connect descriptor

  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-06579 : Bind variable not big enough to hold the output value
  • ora-19251 : XQ0031 - unsupported query version
  • ora-39156 : error parsing dump file name "string"
  • ora-02815 : Unable to attach shared memory
  • ora-37157 : MDX syntax error was found in MDX query string but error text was missing
  • ora-02402 : PLAN_TABLE not found
  • ora-39132 : object type "string"."string" already exists with different hashcode
  • ora-13800 : concurrent DDL failure on SQL repository objects
  • ora-19912 : cannot recover to target incarnation string
  • ora-19854 : error obtaining connect string from target
  • ora-12844 : cluster reconfiguration in progress
  • ora-07565 : sldext: $SEARCH failure
  • ora-13458 : GeoRaster metadata SRS error
  • ora-15008 : cannot drop system template
  • ora-19831 : incompatible string.string.string.string DBMS_BACKUP_RESTORE package: string.string.string.string required
  • ora-16216 : Log stream sequence error
  • ora-02422 : missing or invalid schema element
  • ora-27463 : invalid program type string
  • ora-14128 : FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-04013 : number to CACHE must be less than one cycle
  • ora-01905 : STORAGE keyword expected
  • ora-12666 : Dedicated server: outbound transport protocol different from inbound
  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-02059 : ORA-2PC-CRASH-TEST-string in commit comment
  • ora-25961 : join index prevents dml cascade constraint operation
  • ora-12653 : Authentication control function failed
  • ora-30018 : Create Rollback Segment failed, USN string is out of range
  • ora-10560 : block type 'string'
  • ora-16028 : new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.