ORA-13867: Database-wide SQL tracing is already enabled

Cause : Attempt to enable a database-level tracing which has been already enabled

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

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

update : 28-04-2017
ORA-13867

ORA-13867 - Database-wide SQL tracing is already enabled
ORA-13867 - Database-wide SQL tracing is already enabled

  • ora-10616 : Operation not allowed on this tablespace
  • ora-22818 : subquery expressions not allowed here
  • ora-13710 : Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
  • ora-30188 : reserved for future use
  • ora-38739 : Flashback log file is more recent than control file.
  • ora-01628 : max # extents (string) reached for rollback segment string
  • ora-26103 : V6 or V7 data file used to create control file
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-31491 : could not add logfile to LogMiner session
  • ora-00956 : missing or invalid auditing option
  • ora-36166 : (XSMXAGGR08) workspace object is not a VARIABLE.
  • ora-16789 : missing standby redo logs
  • ora-30369 : maximum number of columns is 32
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-14065 : ALLOCATE STORAGE may not be specified for a partitioned table
  • ora-07200 : slsid: oracle_sid not set.
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-00269 : specified log file is part of thread string not string
  • ora-02484 : Invalid _trace_buffers parameter specification (string)
  • ora-19932 : control file is not clone or standby
  • ora-30025 : DROP segment 'string' (in undo tablespace) not allowed
  • ora-02783 : Both post and wait functions were not specified
  • ora-00334 : archived log: 'string'
  • ora-12633 : No shared authentication services
  • ora-38454 : attribute set not defined for the column being indexed
  • ora-16151 : Managed Standby Recovery not available
  • ora-10916 : TABLESPACE GROUP already specified
  • ora-12229 : TNS:Interchange has no more free connections
  • 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.