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 : 19-08-2017
ORA-13867

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

  • ora-38470 : cannot revoke a privilege that was not granted.
  • ora-13616 : The current user string has not been granted the ADVISOR privilege.
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-00100 : no data found
  • ora-00712 : cannot rename system tablespace
  • ora-12539 : TNS:buffer over- or under-flow
  • ora-22804 : remote operations not permitted on object tables or user-defined type columns
  • ora-28154 : Proxy user may not act as client 'string'
  • ora-16554 : translation not valid
  • ora-09958 : IMON: two processes with the same ORACLE pid are active
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-14265 : data type or length of a table subpartitioning column may not be changed
  • ora-32643 : invalid use of window function in MODEL rule
  • ora-00132 : syntax error or unresolved network name 'string'
  • ora-12413 : labels do not belong to the same policy
  • ora-25196 : keyword MOVE in ALTER TABLE MOVE must immediately follow
  • ora-10619 : Avoid assertions when possible
  • ora-19815 : WARNING: string of string bytes is string%% used, and has string remaining bytes available.
  • ora-30187 : reserved for future use
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-36160 : (XSMXAGGR04) You cannot use string on scalar VARIABLE workspace object.
  • ora-31512 : name cannot contain double quotation marks
  • ora-28512 : cannot get data dictionary translations from string
  • ora-02088 : distributed database option not installed
  • ora-30435 : job_queue_processes must be non-zero in order to refresh summaries
  • ora-28513 : internal error in heterogeneous remote agent
  • ora-13124 : unable to determine column id for column string
  • ora-38908 : internal error occurred during DML Error Logging
  • ora-24318 : call not allowed for scalar data types
  • 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.