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 : 23-08-2017

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

  • ora-23309 : object string.string of type string exists
  • ora-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-19707 : invalid record block number - string
  • ora-16407 : Standby database is in the future of the archive log
  • ora-19881 : Corrupted space bitmap for datafile string, block string backup aborted
  • ora-13281 : failure in execution of SQL statement to retrieve WKT
  • ora-24101 : stopped processing the argument list at: string
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-32840 : property name cannot be NULL
  • ora-31659 : status message was invalid type - detaching job
  • ora-28583 : remote references are not permitted during agent callbacks
  • ora-16651 : requirements not met for enabling Fast-Start Failover
  • ora-38622 : Decision Tree not enough memory, requires at least stringKB
  • ora-13156 : table to be registered string.string is not empty
  • ora-22371 : Table contains data of type string.string, version string, which does not exist
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-26093 : input data column size (number) exceeds the maximum input size (number)
  • ora-15201 : disk string contains a valid RDBMS file
  • ora-12600 : TNS: string open failed
  • ora-14167 : only one subpartition may be moved
  • ora-24199 : message store is overflow
  • ora-16021 : session string destination cannot be the same as session string destination
  • ora-24346 : cannot execute without binding variables
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-06577 : output parameter not a bind variable
  • ora-01188 : Block size string in header does not match physical block size string
  • ora-27057 : cannot perform async I/O to file
  • ora-07701 : sksatln: internal exception: output buffer too small
  • ora-38854 : cannot mark instance string (redo thread string) as disabled
  • ora-38853 : cannot mark instance string (redo thread string) as disabled
  • 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.