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-08-2017
ORA-16006

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

  • ora-25278 : grantee name cannot be NULL
  • ora-12505 : TNS:listener does not currently know of SID given in connect descriptor
  • ora-29375 : sum of values string for level string, plan string exceeds string
  • ora-21704 : cannot terminate cache or connection without flushing first
  • ora-22324 : altered type has compilation errors
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-01075 : you are currently logged on
  • ora-38410 : schema extension not allowed for the table name
  • ora-26518 : push queue synchronization error detected
  • ora-02717 : osnpfs: incorrect number of bytes written
  • ora-38418 : ADT associated with the attribute set string does not exist
  • ora-33262 : (DBERR01) Analytic workspace string does not exist.
  • ora-32121 : Source FILE is null
  • ora-09741 : spwat: error waiting for a post.
  • ora-29963 : missing BINDING keyword
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-31420 : unable to submit the purge job
  • ora-29660 : Unable to find the class defined in the EXTERNAL NAME clause
  • ora-00257 : archiver error. Connect internal only, until freed.
  • ora-08003 : sequence string.NEXTVAL exceeds internal limits
  • ora-19568 : a device is already allocated to this session
  • ora-00086 : user call does not exist
  • ora-12217 : TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
  • ora-14402 : updating partition key column would cause a partition change
  • ora-16232 : adding Logical Standby skip entry for table string.string
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-01612 : instance string (thread string) is already enabled
  • ora-32055 : invalid file type
  • ora-19257 : XQ0037 - function or variable string in module already defined
  • ora-10631 : SHRINK clause should not be specified for this object
  • 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.