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 : 27-06-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-38309 : object not purgable
  • ora-19260 : XQ0040 - invalid namespace node in element constructor
  • ora-28545 : error diagnosed by Net8 when connecting to an agent
  • ora-39783 : Invalid direct path transaction active
  • ora-22605 : FDO handle [string] is not initialized
  • ora-07392 : sftcls: fclose error, unable to close text file.
  • ora-12633 : No shared authentication services
  • ora-07589 : spdde: system ID not set
  • ora-00490 : PSP process terminated with error
  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-19106 : invalid XQueryX: expected string - got string
  • ora-24273 : translation text is required if translation type is T or S
  • ora-12353 : secondary stored object cannot reference remote object
  • ora-22976 : incorrect number of arguments to MAKE_REF
  • ora-01634 : rollback segment number 'string' is about to go offline
  • ora-08260 : ora_addr: cannot open nameserver
  • ora-13210 : error inserting data into the index table
  • ora-09344 : spsig: error signalling thread
  • ora-06442 : ssvwatev: Failed with unexpected error number.
  • ora-19930 : file string has invalid checkpoint SCN string
  • ora-00034 : cannot string in current PL/SQL session
  • ora-01227 : log string is inconsistent with other logs
  • ora-09218 : sfrfs: failed to refresh file size
  • ora-33413 : (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.
  • ora-29528 : invalid Java call in trigger string
  • ora-13149 : failed to generate next sequence number for spatial table string
  • ora-02248 : invalid option for ALTER SESSION
  • ora-31038 : Invalid string value: "string"
  • ora-02174 : Missing required thread number
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • 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.