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 : 19-08-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-19709 : numeric parameter must be non-negative integer
  • ora-01668 : standby database requires DROP option for offline of data file
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-29860 : cannot truncate a table with domain indexes marked LOADING
  • ora-16602 : object must be disabled to perform this operation
  • ora-16778 : redo transport error for one or more databases
  • ora-30378 : MV_CAPABILITIES_TABLE is not compatible with Oracle version
  • ora-06405 : NETCMN: reset protocol error
  • ora-07824 : sspain: $SETIMR failure
  • ora-28575 : unable to open RPC connection to external procedure agent
  • ora-07418 : sfareq: Database writer got error in timing function.
  • ora-24154 : rule string.string already in rule set string.string
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-07409 : slpdtb: invalid packed decimal nibble.
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-01220 : file based sort illegal before database is open
  • ora-13866 : Client identifier must be specified
  • ora-19568 : a device is already allocated to this session
  • ora-19916 : %s
  • ora-13401 : duplicate entry for string in USER_SDO_GEOR_SYSDATA view
  • ora-02362 : error closing file: string
  • ora-00212 : block size string below minimum required size of string bytes
  • ora-36700 : (XSRELTBL04) Dimension workspace object cannot be qualified more than once.
  • ora-08330 : Printing not supported
  • ora-02311 : cannot alter with COMPILE option a valid type with type or table dependents
  • ora-12713 : Character data loss in NCHAR/CHAR conversion
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-09767 : osnmfs: bad return code from msg_send.
  • ora-01576 : The instance string is not enabled
  • ora-32827 : Messaging Gateway agent must be shut down
  • 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.