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-09-2017

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

  • ora-25130 : cannot modify primary key - primary key not defined for table
  • ora-29869 : cannot issue ALTER without REBUILD on a domain index marked FAILED
  • ora-01594 : attempt to wrap into rollback segment (string) extent (string) which is being freed
  • ora-10371 : disable TQ hint
  • ora-29841 : invalid option for ALTER INDEXTYPE
  • ora-06705 : TLI Driver: remote node is unknown
  • ora-10915 : TABLESPACE GROUP cannot be specified for this type of tablespace
  • ora-40105 : input data incompatible with model signature
  • ora-25199 : partitioning key of a index-organized table must be a subset of the primary key
  • ora-09803 : Allocation of string buffer failed.
  • ora-19300 : Error occurred in uri processingstring
  • ora-30109 : could not open parameter file 'string'
  • ora-30943 : XML Schema 'string' is dependent on XML schema 'string'
  • ora-14081 : new partition name must differ from the old partition name
  • ora-01640 : cannot make tablespace read only with active transactions
  • ora-08463 : overflow converting decimal number to Oracle number
  • ora-16709 : standby archived log location settings conflict with flash recovery area
  • ora-13002 : specified level is out of range
  • ora-30345 : circular dimension hierarchy
  • ora-38762 : thread string redo log with scn string could not be found
  • ora-12590 : TNS:no I/O buffer
  • ora-19689 : cannot have more than one %F in control file autobackup format(string) for string
  • ora-30963 : The indexed column is not of XMLType.
  • ora-24183 : invalid transformation
  • ora-30130 : invalid parameter key type received
  • ora-00257 : archiver error. Connect internal only, until freed.
  • ora-39136 : cannot specify an SCN on a transportable job
  • ora-02168 : invalid value for FREELISTS
  • ora-31058 : cannot modify read-only XOBs
  • ora-08186 : invalid timestamp 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.