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 : 27-06-2017
ORA-12521

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-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-39079 : unable to enqueue message string
  • ora-14262 : new subpartition name must differ from the old subpartition name
  • ora-30493 : The percentile value should be a number between 0 and 1.
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-02721 : osnseminit: cannot create semaphore set
  • ora-01479 : last character in the buffer is not Null
  • ora-15043 : ASM disk "string" is not a diskgroup member
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-26667 : invalid STREAMS parameter string
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-16116 : no work available
  • ora-36163 : (XSMXAGGR06) The AGGREGATE function cannot be run on more than one variable at a time.
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-24078 : cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
  • ora-07496 : sppst: lm_post failed.
  • ora-06706 : TLI Driver: service not found
  • ora-01685 : max # extents (string) reached in index string.string partition string
  • ora-39040 : Schema expression "string" must identify exactly one schema.
  • ora-02150 : invalid new tablespace name
  • ora-14155 : missing PARTITION or SUBPARTITION keyword
  • ora-10565 : Another test recovery session is active
  • ora-02229 : invalid SIZE option value
  • ora-01310 : requested return type not supported by the lcr_mine function
  • ora-31005 : Path name length string exceeds maximum length string
  • ora-31224 : DBMS_LDAP: invalid LDAP session
  • ora-09969 : unable to close or remove lock file
  • ora-30197 : reserved for future use
  • ora-22288 : file or LOB operation string failed string
  • ora-00372 : file string cannot be modified at this time
  • 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.