ORA-12528: TNS:listener: all appropriate instances are blocking new connections

Cause : All nisatnecss uppotrign htes evriec erqeusetdb yt h eciletn erprotde hta ttehyw eer lbokcign hten e wcnoncetoin.s hTi scnodtiino amyb et epmoarr,y usc ha sa tisntnac esatrutp.

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

Attepmtt h ecnoncetoina gian .I ferro rpressit,s hte ncnotcatt h eamdiinsrtaotrt oc hcekt h esattsu fo htei ntsacne.s

update : 22-08-2017

ORA-12528 - TNS:listener: all appropriate instances are blocking new connections
ORA-12528 - TNS:listener: all appropriate instances are blocking new connections

  • ora-22920 : row containing the LOB value is not locked
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-12345 : user string lacks CREATE SESSION privilege in database link (linkname string)
  • ora-40102 : invalid input string for data mining operation string
  • ora-13368 : simple polygon type has more than one exterior ring
  • ora-23290 : This operation may not be combined with any other operation
  • ora-16216 : Log stream sequence error
  • ora-24100 : error in ktz testing layer
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-16738 : redo tranport service for standby database "string" unexpectedly offline
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-13754 : "SQL Tuning Set" "string" does not exist for user "string".
  • ora-00340 : IO error processing online log string of thread string
  • ora-19506 : failed to create sequential file, name="string", parms="string"
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-38761 : redo log sequence string in thread string, incarnation string could not be accessed
  • ora-13390 : error in spatial analysis and mining function: [string]
  • ora-26730 : %s 'string' already exists
  • ora-13000 : dimension number is out of range
  • ora-39171 : Job is experiencing a resumable wait. string
  • ora-22161 : type code [string] is not valid
  • ora-12902 : default temporary tablespace must be SYSTEM or of TEMPORARY type
  • ora-26521 : rpc initialization error
  • ora-30156 : Out of disk space
  • ora-02797 : No requests available
  • ora-07236 : slemop: open error.
  • ora-16623 : stale DRC UID sequence number detected
  • ora-24318 : call not allowed for scalar data types
  • ora-30181 : integer in argument index is not immediately followed by )
  • ora-10647 : Tablespace other than SYSTEM, string, string not found in read only mode
  • 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.