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-06-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-02405 : invalid sql plan object provided
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-31686 : error creating worker processes
  • ora-06907 : CMX: error during connect confirmation
  • ora-07260 : spdcr: wait error.
  • ora-39504 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-13618 : The specified value is not a valid value for procedure argument string.
  • ora-01804 : failure to initialize timezone information
  • ora-32108 : max column or parameter size not specified
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-10644 : SYSTEM tablespace cannot be default temporary tablespace
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-37041 : (XSACQUIRE_DEP_TIMEOUT) Composite, concat, dimension map, or internal partition workspace object is locked by another user and the WAIT timed out.
  • ora-13917 : Posting system alert with reason_id string failed with code [string] [string]
  • ora-12653 : Authentication control function failed
  • ora-28267 : Invalid NameSpace Value
  • ora-26065 : check constraint cannot reference column, string, in direct path load
  • ora-30176 : invalid format code used in the format string
  • ora-31623 : a job is not attached to this session via the specified handle
  • ora-00080 : invalid global area specified by level string
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-16646 : Fast-Start Failover is disabled
  • ora-12714 : invalid national character set specified
  • ora-28177 : incorrect Kerberos ticket version
  • ora-14296 : Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-07514 : scgcan: $deq unexpected return while canceling lock
  • ora-13193 : failed to allocate space for geometry
  • ora-25144 : invalid option for CREATE TABLESPACE with TEMPORARY contents
  • ora-25462 : evaluation context not specified
  • 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.