ORA-16006: audit_trail destination incompatible with database open mode

Cause : Thea udi_ttrali intiialziatino paarmetre wa ssett o "BD" (ro TREU), hwichi s icnomptaibl ewit ha dtaabaes opneed ofr raed-olny access.

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

Whe nthed ataabse si opneed ofr raed-olny access ,thea udi_ttrali intiialziatino paarmetre ca nonl ybe est t o"OS "or N"ONE "(FASLE).

update : 23-05-2017

ORA-16006 - audit_trail destination incompatible with database open mode
ORA-16006 - audit_trail destination incompatible with database open mode

  • ora-24375 : Cannot use V6 syntax when talking to a V8 server
  • ora-24035 : AQ agent string is not a subscriber for queue string
  • ora-12679 : Native services disabled by other process but required
  • ora-01661 : tablespace 'string' is already temporary
  • ora-30115 : error when processing an environment variable
  • ora-29257 : host string unknown
  • ora-29831 : operator binding not found
  • ora-28343 : fails to encrypt data
  • ora-02791 : Unable to open file for use with asynchronous I/O
  • ora-01478 : array bind may not include any LONG columns
  • ora-30195 : reserved for future use
  • ora-30649 : missing DIRECTORY keyword
  • ora-40304 : invalid classname string in prior probability specification
  • ora-39053 : parameter or attribute string must be defined for a string job
  • ora-29390 : some resource plans are not part of any top-plan
  • ora-32839 : property string is reserved, names with MGWPROP$_ prefix are not valid
  • ora-22801 : invalid object row variable
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-04009 : MAXVALUE cannot be made to be less than the current value
  • ora-01117 : adding file 'string' with illegal block size: string; limit is string
  • ora-00710 : new tablespace name is the same as the old tablespace name
  • ora-30387 : invalid rewrite mode for REWRITE_EQUIVALENCE API
  • ora-06912 : CMX: write error in datarq
  • ora-16403 : shutdown in progress - remote connection is not permitted
  • ora-31700 : Very long string supplied for AUDIT_SYSLOG_LEVEL parameter
  • ora-16205 : DDL skipped due to skip setting
  • ora-07846 : sllfop: string byte record too big for string byte user buffer
  • ora-38707 : Media recovery is not enabled.
  • ora-06978 : X.25 Driver: Too many callback tries
  • ora-14157 : invalid subpartition name
  • 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.