ORA-13869: Instance-wide SQL tracing on instance string is already enabled

Cause : Attempt to enable an instance-level tracing which has been already enabled on a specific instance

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

Disable and re-enable tracing with different bind/wait options

update : 23-06-2017

ORA-13869 - Instance-wide SQL tracing on instance string is already enabled
ORA-13869 - Instance-wide SQL tracing on instance string is already enabled

  • ora-10707 : Simulate process death for instance registration
  • ora-37181 : expected exactly string columns for dimension string, got string
  • ora-16577 : corruption detected in Data Guard configuration file
  • ora-09928 : Unable to restore the label of server
  • ora-14002 : only one GLOBAL clause may be specified
  • ora-13617 : The specified task string already executing
  • ora-19670 : file string already being restored
  • ora-02293 : cannot validate (string.string) - check constraint violated
  • ora-01149 : cannot shutdown - file string has online backup set
  • ora-22897 : no scope clause specified for user-defined REF column "string"
  • ora-01088 : cannot shut down ORACLE while active processes exist
  • ora-27465 : invalid value string for attribute string
  • ora-22993 : specified input amount is greater than actual source amount
  • ora-01236 : Error string occurred during initialization of file header access
  • ora-07427 : spstp: cannot change directory to dbs.
  • ora-29508 : query derived from USING clause did not select a value of type string
  • ora-39064 : unable to write to the log file
  • ora-31484 : source database version must be at least or greater
  • ora-29852 : keyword IS is missing
  • ora-31086 : insufficient privileges to register schema "string"
  • ora-09754 : sppst: invalid process number passed to sppst.
  • ora-02214 : duplicate BACKUP option specification
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-01278 : error creating file 'string'
  • ora-01682 : read-only DB cannot allocate temporary space in tablespace string
  • ora-26519 : no memory available to allocate
  • ora-16235 : DDL skipped because import has occurred
  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • ora-30659 : too many locations specified for external table
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • 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.