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

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

  • ora-31229 : DBMS_LDAP: invalid input parameter
  • ora-02280 : duplicate or conflicting CYCLE/NOCYCLE specifications
  • ora-28530 : Heterogeneous Services initialization error in NLS language ID
  • ora-22620 : buffer size too small to hold the value
  • ora-00227 : corrupt block detected in control file: (block string, # blocks string)
  • ora-14012 : resulting partition name conflicts with that of an existing partition
  • ora-30685 : package version is not compatible with Oracle version
  • ora-00340 : IO error processing online log string of thread string
  • ora-02785 : Invalid shared memory buffer size
  • ora-00250 : archiver not started
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-13233 : failed to create sequence number [string] for R-tree
  • ora-06300 : IPA: Disconnect failure
  • ora-32101 : cannot create OCI Environment
  • ora-36174 : (XSMXAGGR23) workspace object must be either a VARIABLE, a RELATION or a FORMULA.
  • ora-12981 : cannot drop column from an object type table
  • ora-02273 : this unique/primary key is referenced by some foreign keys
  • ora-33217 : (CINSERT20) Custom member values cannot be added to concat dimension workspace object, or to any of its bases, because it is not defined as UNIQUE.
  • ora-32763 : Turn off N-Pass Temp LOB cleanup
  • ora-02720 : osnfop: shmat failed
  • ora-16408 : Incompatible archival Redo Branch lineage
  • ora-30679 : JDWP-based debugging not supported in this configuration
  • ora-25965 : fact table must be included in the from clause
  • ora-36673 : (XSDPART11) Use simple leaf values to identify concat dimension values in a VALUES LESS THAN clause, rather than the format.
  • ora-16799 : Redo Apply is offline
  • ora-02768 : Maximum number of files is invalid
  • ora-23458 : inappropriate flavor string at string
  • ora-32332 : cannot refresh materialized view "string"."string" as type evolution has occured
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-30765 : cannot modify scope for an unscoped REF column
  • 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.