ORA-12326: database string is closing immediately; no operations are permitted

Cause : Th edaatbaes yuo attemtpedt o cacess i sclsoin,g s oyoru oepraitonh asb ee ntemrintaed.

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

Wati utnilt hed atbaas eha sbene roepeend,o r ocntcat hte adtaabsea dmnistarto.r

update : 26-09-2017
ORA-12326

ORA-12326 - database string is closing immediately; no operations are permitted
ORA-12326 - database string is closing immediately; no operations are permitted

  • ora-30130 : invalid parameter key type received
  • ora-38609 : FI Not enough memory for tree counting, requires at least stringKB
  • ora-06807 : TLI Driver: could not open ethernet device driver file
  • ora-29954 : domain index partition is marked LOADING/FAILED/UNUSABLE
  • ora-09705 : spcre: cannot initialize latch semaphore
  • ora-31415 : change set string does not exist
  • ora-28263 : Insufficient memory in global context pool
  • ora-13136 : null common code generated
  • ora-29503 : SCHEMA keyword not valid with NAMED keyword
  • ora-07581 : spstp: cannot derive SID from unexpected process name
  • ora-26002 : Table string has index defined upon it.
  • ora-00213 : cannot reuse control file; old file size string, string required
  • ora-13636 : The specified value provided for parameter string is not valid for this advisor.
  • ora-15180 : Could not open dynamic library string, error [string]
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-37179 : expected at least one column for dimension string, got string
  • ora-09812 : Unable to get user clearance from connection
  • ora-30025 : DROP segment 'string' (in undo tablespace) not allowed
  • ora-14306 : List value 'string' specified twice in partitions 'string', 'string'
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-38437 : The ADT "string" may not contain any user methods.
  • ora-06511 : PL/SQL: cursor already open
  • ora-07221 : slspool: exec error, unable to start spooler program.
  • ora-19690 : backup piece release string incompatible with Oracle release string
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-23362 : invalid user
  • ora-29393 : user string does not exist or is not logged on
  • ora-23340 : incorrect resolution method string
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-27083 : waiting for async I/Os failed
  • 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.