ORA-16785: the database is not in ARCHIVELOG mode

Cause : The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to be a primary database.

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

Reset the database to ARCHIVELOG mode by issuing ALTER DATABASE ARCHIVELOG command.

update : 26-04-2017

ORA-16785 - the database is not in ARCHIVELOG mode
ORA-16785 - the database is not in ARCHIVELOG mode

  • ora-23466 : flavor requires missing object "string"."string"
  • ora-02071 : error initializing capabilities for remote database string
  • ora-03278 : duplicate ALLOCATE EXTENT option specification
  • ora-37005 : (AWLISTALL03) number readers
  • ora-25229 : error on transformation of message string string
  • ora-23343 : no match for specified conflict resolution information
  • ora-01804 : failure to initialize timezone information
  • ora-01234 : cannot end backup of file string - file is in use or recovery
  • ora-40286 : remote operations not permitted on mining models
  • ora-12630 : Native service operation not supported
  • ora-27064 : cannot perform async I/O to file
  • ora-10284 : simulate zero/infinite asynch I/O buffering
  • ora-21709 : cannot refresh an object that has been modified
  • ora-19804 : cannot reclaim string bytes disk space from string limit
  • ora-13405 : null or invalid dimensionSize parameter
  • ora-24401 : cannot open further connections
  • ora-23477 : unable to alter propagation mode for object group "string"."string"
  • ora-16256 : Failure to complete standby redo logfile archival after failover
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-30736 : objects in a table or view hierarchy have to be in the same schema
  • ora-00021 : session attached to some other process; cannot switch session
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-00408 : parameter string is set to TRUE
  • ora-25100 : TABLESPACE option can only be used with ALTER INDEX REBUILD
  • ora-33094 : (XSAGGMAPLIST01) Your expression uses too much execution space. Eliminate recursion or reduce the levels of nesting.
  • ora-25175 : no PRIMARY KEY constraint found
  • ora-09705 : spcre: cannot initialize latch semaphore
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-16803 : unable to query a database table or fixed view
  • ora-12991 : column is referenced in a multi-column constraint
  • 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.