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 : 22-07-2017
ORA-16785

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

  • ora-23542 : dependent object "string"."string" already registered
  • ora-26714 : User error encountered while applying
  • ora-01303 : subordinate process error: number. Check alert and trace logs
  • ora-12030 : cannot create a fast refresh materialized view
  • ora-08313 : sllfop: could not allocate buffers
  • ora-19224 : XP0004 - XQuery static type mismatch: expected - string got - string
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-06703 : TLI Driver: send break message failed
  • ora-02157 : no options specified for ALTER USER
  • ora-25019 : too much concurreny
  • ora-12632 : Role fetch failed
  • ora-24371 : data would not fit in current prefetch buffer
  • ora-12551 : TNS:missing keyword
  • ora-13844 : no new SQL profile name or category specified.
  • ora-14290 : PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-30449 : syntax error in parameter string
  • ora-25123 : Too many components specified in the name.
  • ora-23337 : priority or value not in priority group string
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-00104 : deadlock detected; all public servers blocked waiting for resources
  • ora-37032 : (XSMLTMAINT03) You cannot MAINTAIN partition template workspace object in MULTI mode.
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-38951 : Target platform string not cross platform compliant
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • ora-31475 : redo log catalog contains no metadata for the source table
  • ora-16162 : Cannot add new standby databases to protected configuration
  • ora-28276 : Invalid ORACLE password attribute.
  • ora-07592 : sspgprv: Error obtaining required privileges
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-09986 : wrong number of bytes read from SGA definition file
  • 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.