ORA-16002: database already open for read-write access by another instance

Cause : The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.

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

This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access.

update : 23-05-2017

ORA-16002 - database already open for read-write access by another instance
ORA-16002 - database already open for read-write access by another instance

  • ora-01082 : 'row_locking = always' requires the transaction processing option
  • ora-00080 : invalid global area specified by level string
  • ora-19724 : snapshot too old: snapshot time is before file string plug-in time
  • ora-37082 : Invalid percent
  • ora-36832 : (XSLMGEN02) View token cannot be greater than 4000 bytes
  • ora-19016 : attributes cannot occur after element specifications
  • ora-06533 : Subscript beyond count
  • ora-24094 : invalid transformation, target type does not match that of the queue
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-09839 : removeCallback: callback port is not in the callback set.
  • ora-24239 : object could not be invalidated
  • ora-14174 : only a may follow COALESCE PARTITION|SUBPARTITION
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-04043 : object string does not exist
  • ora-12454 : label string does not exist for policy string
  • ora-35076 : (QFHEAD04) CAUTION: The textual data in EIF file string is encoded in a character set that is not recognized by this version of string.
  • ora-27039 : create file failed, file size limit reached
  • ora-16073 : archiving must be enabled
  • ora-31666 : Master process string had an unhandled exception.
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-34719 : (NLSCHARSET03) Character data loss in NTEXT/TEXT conversion
  • ora-30569 : data type of given column is not supported in a log group
  • ora-16703 : cannot set property while the database is enabled
  • ora-31418 : source schema string does not exist
  • ora-31078 : error in SQL mapping information
  • ora-06707 : TLI Driver: connection failed
  • ora-04050 : invalid or missing procedure, function, or package name
  • ora-07224 : sfnfy: failed to obtain file size limit; errno = string.
  • ora-01354 : Supplemental log data must be added to run this command
  • ora-00315 : log string of thread string, wrong thread # string in header
  • 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.