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 : 21-08-2017
ORA-16000

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

  • ora-24389 : Invalid scrollable fetch parameters
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-24026 : operation failed, queue string.string has errors
  • ora-14259 : table is not partitioned by Hash method
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-30205 : invalid Character set
  • ora-15175 : cannot create alias for diskgroup metadata file 'string'
  • ora-38404 : schema extension not allowed for the attribute set name
  • ora-17500 : ODM err:string
  • ora-00822 : MMAN process terminated with error
  • ora-31064 : Cannot instantiate abstract element or property [string]
  • ora-36913 : (XSAGDNGL49) In AGGMAP workspace object, LOAD_STATUS object workspace object must be an undimensioned VALUESET over the relation dimension.
  • ora-02443 : Cannot drop constraint - nonexistent constraint
  • ora-37043 : (XSACQUIRE_DEP_OLDGEN) Composite, concat, dimension map, or internal partition workspace object cannot be locked since another user has committed a new one already.
  • ora-39068 : invalid master table data in row with PROCESS_ORDER=string
  • ora-12441 : policy string already exists
  • ora-23410 : materialized view "string"."string" is already in a refresh group
  • ora-29661 : Unable to find the superclass of the defined in the EXTERNAL NAME
  • ora-13415 : invalid or out of scope point specification
  • ora-16701 : generic resource guard request failed
  • ora-13375 : the layer is of type [string] while geometry inserted has type [string]
  • ora-39128 : unexpected DbmsJava error number from statement string
  • ora-19710 : unsupported character set string
  • ora-30192 : reserved for future use
  • ora-06511 : PL/SQL: cursor already open
  • ora-14319 : DEFAULT cannot be specified with other values
  • ora-01734 : illegal parameters - EXTENT MIN higher than EXTENT MAX
  • ora-12681 : Login failed: the SecurID card does not have a pincode yet
  • ora-30975 : invalid Order Key Index option for XML Index
  • 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.