ORA-12522: TNS:listener could not find available instance with given INSTANCE_ROLE

Cause : There are not any available and appropriate database instances registered with the listener, that are part of the service identified by SERVICE_NAME given in the connect descriptor and that have the specified INSTANCE_ROLE (and INSTANCE_NAME, if specified).

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

Check to make sure that the INSTANCE_ROLE specified is correct. Run "lsnrctl services" to ensure that the instance(s) have registered with the listener and that they are ready to accept connections.

update : 23-06-2017
ORA-12522

ORA-12522 - TNS:listener could not find available instance with given INSTANCE_ROLE
ORA-12522 - TNS:listener could not find available instance with given INSTANCE_ROLE

  • ora-19201 : Datatype not supported
  • ora-07721 : scgcm: not enough OS resource to obtain system enqueue
  • ora-10658 : Lob column to be shrunk is marked unused
  • ora-08464 : input raw decimal data contains more than 42 digits
  • ora-01463 : cannot modify column datatype with current constraint(s)
  • ora-12558 : TNS:protocol adapter not loaded
  • ora-16538 : no match on requested item
  • ora-13619 : The procedure argument string is greater than the maximum allowable length of string characters.
  • ora-37132 : (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.
  • ora-13904 : The file has been dropped and recreated during the procedure call.
  • ora-13801 : invalid value for SQLTUNE_CATEGORY parameter
  • ora-34164 : (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
  • ora-25442 : too many column values for table alias: string
  • ora-16255 : Log Auto Delete conflicts with another LogMiner session
  • ora-02801 : Operations timed out
  • ora-16114 : applying DDL transaction with commit SCN string
  • ora-00604 : error occurred at recursive SQL level string
  • ora-30744 : "string" is not an object table
  • ora-23609 : unable to find directory object for directory string
  • ora-28340 : a different encryption algorithm has been chosen for the table
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-23358 : invalid remote user
  • ora-12719 : operation requires database is in RESTRICTED mode
  • ora-16575 : request terminated at broker discretion
  • ora-01882 : timezone region string not found
  • ora-02792 : Unable to fstat() a file being used for asynchronous I/O.
  • ora-30177 : invalid flag used in a format specification
  • ora-39768 : only one direct path context top level column array is allowed
  • ora-31465 : cannot obtain a lock on the subscription
  • ora-16238 : attempt to use version 9 log
  • 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.