ORA-12224: TNS:no listener

Cause : The connection request could not be completed because the listener is not running.

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

Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.

update : 21-08-2017

ORA-12224 - TNS:no listener
ORA-12224 - TNS:no listener

  • ora-32107 : internal OCI memory allocation failure
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-28236 : invalid Triple DES mode
  • ora-19241 : XP0021 - cast to type string failed
  • ora-01312 : Specified table/column does not exist
  • ora-14000 : only one LOCAL clause may be specified
  • ora-10639 : Dump library cache during kksfbc-reparse-infinite-loop error
  • ora-15104 : conflicting CONTENTS options
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-19235 : XQ0015 - unsupported must-understand extension
  • ora-16585 : illegal operation on a primary site
  • ora-38735 : Wrong log number string in flashback log file header.
  • ora-00367 : checksum error in log file header
  • ora-22317 : typecode number is not legal as a number type
  • ora-10706 : Print out information about global enqueue manipulation
  • ora-07632 : smsrcx: $DELTVA failure
  • ora-24364 : internal error while padding blanks
  • ora-12665 : NLS string open failed
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • ora-30956 : invalid option for XML Index
  • ora-16524 : unsupported operation
  • ora-24406 : API mode switch is disallowed when a call is in progress.
  • ora-32031 : illegal reference of a query name in WITH clause
  • ora-30122 : value 'string' for 'string' must be between 'number' and 'number'
  • ora-16523 : operation requires the client to connect to instance "string"
  • ora-29963 : missing BINDING keyword
  • ora-10266 : Trace OSD stack usage
  • ora-09772 : osnpmetbrkmsg: message from host had incorrect message type
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-36904 : (XSAGDNGL44) In AGGMAP workspace object, RELATION workspace object occurs after a dynamic model. The dynamic model must be the last calculation within the AGGMAP.
  • 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.