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 : 26-07-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-00329 : archived log begins at change string, need change string
  • ora-01274 : cannot add datafile 'string' - file could not be created
  • ora-15059 : invalid device type for ASM disk
  • ora-29293 : A stream error occurred during compression or uncompression.
  • ora-13369 : invalid value for etype in the 4-digit format
  • ora-06400 : NETCMN: No default host string specified
  • ora-00272 : error writing archive log string
  • ora-02773 : Invalid maximum client wait time
  • ora-01655 : unable to extend cluster string.string by string in tablespace string
  • ora-12724 : regular expression corrupt
  • ora-31620 : file or device "string" cannot be specified for string operation
  • ora-00469 : CKPT process terminated with error
  • ora-29967 : Cannot drop an operator binding with dependent objects
  • ora-06701 : TLI Driver: incorrect number of bytes written
  • ora-04062 : %s of string has been changed
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-30345 : circular dimension hierarchy
  • ora-21702 : object is not instantiated or has been de-instantiated in cache
  • ora-02195 : Attempt to create string object in a string tablespace
  • ora-15017 : diskgroup "string" cannot be mounted
  • ora-01156 : recovery in progress may need access to files
  • ora-19586 : %s k-byte limit is too small to hold piece directory
  • ora-29806 : specified binding does not exist
  • ora-31109 : Action failed as parent resource string is locked
  • ora-36993 : (XSRELGID10) OBJECT workspace object must be a VARIABLE, RELATION, or a numeric SURROGATE DIMENSION based on the level dimension workspace object.
  • ora-38769 : FLASHBACK DATABASE failed after modifying data.
  • ora-07758 : slemcw: invalid handle
  • ora-31507 : %s parameter value longer than maximum length string
  • ora-31482 : invalid option for non-distributed Hotlog change source
  • 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.