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 : 25-06-2017
ORA-13867

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

  • ora-01772 : Must specify a value for LEVEL
  • ora-22901 : cannot compare nested table or VARRAY or LOB attributes of an object type
  • ora-32121 : Source FILE is null
  • ora-07210 : slcpu: getrusage error, unable to get cpu time.
  • ora-25009 : Nested table clause allowed only for INSTEAD OF triggers
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-12469 : no user levels found for user string and policy string
  • ora-00274 : illegal recovery option string
  • ora-30110 : syntax error at 'string'
  • ora-28503 : bind value cannot be translated into SQL text for non-Oracle system
  • ora-19116 : too many xmlspace declarations
  • ora-13831 : SQL profile name specified is invalid
  • ora-29281 : invalid mode
  • ora-24431 : Statement does not exist in the cache
  • ora-14036 : partition bound value too large for column
  • ora-13272 : geometric object string in table string is invalid
  • ora-39037 : Object type path not supported for string metadata filter.
  • ora-14288 : index is not partitioned by Composite Range method
  • ora-22627 : tc [string] must be that of object/varray/nested table
  • ora-06924 : CMX: wrong break message length
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • ora-12649 : Unknown encryption or data integrity algorithm
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-01771 : illegal option for a clustered table
  • ora-00113 : protocol name string is too long
  • ora-09751 : pw_attachPorts: server call pws_attach failed.
  • ora-36399 : (XSSPROPDTYPE) The data type of property string must be string.
  • ora-06431 : ssaio: Invalid Block number
  • ora-22813 : operand value exceeds system limits
  • ora-14108 : illegal partition-extended table name syntax
  • 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.