ORA-12334: database (link name string) is still open

Cause : You attempted to dismount a database that is still open.

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

Close the database with the ALTER DATABASE CLOSE command, then re-attempt to dismount the database.

update : 25-06-2017
ORA-12334

ORA-12334 - database (link name string) is still open
ORA-12334 - database (link name string) is still open

  • ora-31483 : cannot have spaces in the parameter string
  • ora-25104 : UNRECOVERABLE option can only be used with ALTER INDEX REBUILD
  • ora-23501 : refresh template cannot be instantiated for database with compatibilty equal to or less than 8.0
  • ora-19698 : %s is from different database: id=string, db_name=string
  • ora-01685 : max # extents (string) reached in index string.string partition string
  • ora-39017 : Worker request not supported when job is in string state.
  • ora-15113 : alias name 'string' refers to a directory
  • ora-08320 : scnget: Call to scnget before scnset or scnfnd.
  • ora-01227 : log string is inconsistent with other logs
  • ora-01205 : not a data file - type number in header is string
  • ora-24265 : Insufficient privileges for SQL profile operation
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-02731 : osnrnf: malloc of buffer failed
  • ora-15127 : ASM file name 'string' cannot use templates
  • ora-04015 : ascending sequences that CYCLE must specify MAXVALUE
  • ora-01981 : CASCADE CONSTRAINTS must be specified to perform this revoke
  • ora-01804 : failure to initialize timezone information
  • ora-16075 : standby database destination mismatch
  • ora-30197 : reserved for future use
  • ora-29665 : Java thread deadlock detected
  • ora-09370 : Windows 3.1 Two-Task driver ORACLE task timed out
  • ora-25307 : Enqueue rate too high, flow control enabled
  • ora-24202 : publisher does not exist for the queue
  • ora-36778 : (XSPGTRLOW) The amount of available temporary storage is still low. Free some temporary storage immediately. You can do so, for example, by UPDATING or DETACHING an analytic workspace.
  • ora-36202 : (XSAGOP01) 'number' is not a valid aggregation operator.
  • ora-38790 : BEFORE must be specified with RESETLOGS
  • ora-01513 : invalid current time returned by operating system
  • ora-08110 : Oracle event to test SMON cleanup for online index build
  • ora-10628 : Turn on sanity check for kdiss index skip scan state
  • ora-23453 : requested operation is not supported on top flavor
  • 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.