ORA-12524: TNS:listener could not resolve HANDLER_NAME given in connect descriptor

Cause : The HANDLER_NAME in the CONNECT_DATA was not found in the listener's tables for the specified SERVICE_NAME and INSTANCE_NAME.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Check to make sure that the HANDLER_NAME specified is correct.

update : 28-04-2017

ORA-12524 - TNS:listener could not resolve HANDLER_NAME given in connect descriptor
ORA-12524 - TNS:listener could not resolve HANDLER_NAME given in connect descriptor

  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-22295 : cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
  • ora-22164 : delete element operation is not allowed for variable-length array
  • ora-08000 : maximum number of session sequence lists exceeded
  • ora-29307 : datafile string error, string
  • ora-01411 : cannot store the length of column in the indicator
  • ora-00062 : DML full-table lock cannot be acquired; DML_LOCKS is 0
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-39138 : Insufficient privileges to load data not in your schema
  • ora-13367 : wrong orientation for interior/exterior rings
  • ora-01683 : unable to extend index string.string partition string by string in tablespace string
  • ora-38955 : Source platform string not cross platform compliant
  • ora-13236 : internal error in R-tree processing: [string]
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-19753 : error writing to change tracking file
  • ora-30112 : multiple values not allowed for parameter 'string'
  • ora-31456 : error executing a procedure in the DBMS_CDC_UTILITY package
  • ora-30447 : internal data for run number string is inconsistent
  • ora-06535 : statement string in string is NULL or 0 length
  • ora-39778 : the parallel load option is not allowed when loading lob columns
  • ora-32008 : error while processing parameter update at instance string
  • ora-07759 : slemtr: invalid destination
  • ora-16553 : the Data Guard broker process (DMON) failed to shutdown
  • ora-15049 : diskgroup "string" contains string error(s)
  • ora-14064 : Index with Unusable partition exists on unique/primary constraint key
  • ora-02222 : invalid PCTINCREASE storage option value
  • ora-38426 : attribute set assigned to an expression set may not be dropped
  • ora-12526 : TNS:listener: all appropriate instances are in restricted mode
  • ora-01283 : Options specified is invalid
  • ora-29359 : invalid method name string specified for resource plan string
  • 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.