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 : 24-07-2017

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

  • ora-30937 : No schema definition for 'string' (namespace 'string') in parent 'string'
  • ora-07280 : slsget: unable to get process information.
  • ora-23493 : "string" is not a new site for extension request "string"
  • ora-31083 : error while creating SQL type "string"."string"
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-13293 : cannot specify unit for geometry without a georeferenced SRID
  • ora-30676 : socket read or write failed
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-39149 : cannot link privileged user to non-privileged user
  • ora-29374 : resource plan string in top-plan string has no plan directives
  • ora-19590 : conversation already active
  • ora-25332 : Invalid release value string for queue table compatible parameter
  • ora-13762 : The string ranking measure is invalid.
  • ora-02180 : invalid option for CREATE TABLESPACE
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-16176 : background dictionary build cannot be running
  • ora-15071 : ASM disk "string" is already being dropped
  • ora-09716 : kslcll: Unable to fix in-flux lamport latch.
  • ora-04051 : user string cannot use database link string.string
  • ora-32315 : REFRESH FAST of "string"."string" unsupported after mixed DML and Direct Load
  • ora-07417 : sfareq: One or more database writers not active.
  • ora-00266 : name of archived log file needed
  • ora-02360 : fatal error during data export/import initialization
  • ora-00972 : identifier is too long
  • ora-23432 : master site string already exists
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-16548 : object not enabled
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-37101 : (XSVPART01) Partitioning information can only be given for variables dimensioned by a PARTITION TEMPLATE.
  • 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.