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 : 20-09-2017

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-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-07638 : smsget: SGA pad area not large enough for created SGA
  • ora-24014 : invalid value string, RETENTION_TIME should be FOREVER or non-negative
  • ora-13418 : null or invalid parameter(s) for set functions
  • ora-16174 : user requested thread/sequence termination of managed recovery
  • ora-26517 : materialized view control entry for 'string.string' was not found
  • ora-32408 : materialized view log on "string"."string" already has new values
  • ora-28354 : wallet already open
  • ora-07577 : no such user in authorization file
  • ora-32741 : Hang analysis already going on
  • ora-06932 : CMX: error in local name
  • ora-15195 : Internal ASM testing event number 15195
  • ora-29908 : missing primary invocation for ancillary operator
  • ora-27016 : skgfcls: sbtinfo returned error
  • ora-39038 : Object path "string" is not supported for string jobs.
  • ora-14155 : missing PARTITION or SUBPARTITION keyword
  • ora-25020 : renaming system triggers is not allowed
  • ora-39079 : unable to enqueue message string
  • ora-02331 : cannot create constraint on column of datatype string
  • ora-03263 : cannot drop the first file of tablespace string
  • ora-00052 : maximum number of enqueue resources (string) exceeded
  • ora-07759 : slemtr: invalid destination
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-30192 : reserved for future use
  • ora-21708 : inappropriate operation on a transient object
  • ora-32802 : value for string must be string
  • ora-12987 : cannot combine drop column with other operations
  • ora-01223 : RESETLOGS must be specified to set a new database name
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-26664 : cannot create STREAMS process 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.