ORA-16000: database open for read-only access

Cause : The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.

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

In order to modify the database, it must first be shut down and re-opened for read-write access.

update : 27-06-2017

ORA-16000 - database open for read-only access
ORA-16000 - database open for read-only access

  • ora-28157 : Proxy user 'string' forbidden to set role 'string' for client 'string'
  • ora-29512 : incorrectly formed name resolver specification
  • ora-30389 : the source statement is not compatible with the destination statement
  • ora-10630 : Illegal syntax specified with SHRINK clause
  • ora-19922 : there is no parent row with id string and level string
  • ora-25453 : invalid iterator: string
  • ora-16125 : large transaction string string string is waiting for more data
  • ora-02759 : Not enough request descriptors available
  • ora-01644 : tablespace 'string' is already read only
  • ora-12416 : policy string not found
  • ora-32342 : The EXPLAIN_MVIEW facility failed to explain the materialized view statement
  • ora-02079 : no new sessions may join a committing distributed transaction
  • ora-27037 : unable to obtain file status
  • ora-14058 : partition number string: INITRANS value must be less than MAXTRANS value
  • ora-31529 : could not find publication for CDC subscriber view string.string
  • ora-13151 : failed to remove exception record
  • ora-09320 : szrfc: unable to obtain the list of valid OS roles
  • ora-19110 : unsupported XQuery expression
  • ora-01570 : MINEXTENTS must be no larger than the string extents currently allocated
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-31009 : Access denied for property string
  • ora-28576 : lost RPC connection to external procedure agent
  • ora-26694 : error while enqueueing into queue string.string
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-29532 : Java call terminated by uncaught Java exception: string
  • ora-02167 : LOGFILE clause specified more than once
  • ora-38415 : invalid name or datatype for the attribute: string
  • ora-21613 : key does not exist
  • ora-01361 : global name mismatch
  • ora-12404 : invalid privilege string: string
  • 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.