ORA-13868: Instance-wide SQL tracing on instance string is not enabled

Cause : Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance

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

No action required

update : 23-04-2017

ORA-13868 - Instance-wide SQL tracing on instance string is not enabled
ORA-13868 - Instance-wide SQL tracing on instance string is not enabled

  • ora-30339 : illegal dimension attribute name
  • ora-24950 : unregister failed, registeration not found
  • ora-30115 : error when processing an environment variable
  • ora-39781 : Direct path stream loads are not allowed after another context loading the same table has ended
  • ora-12822 : duplicate option in PARALLEL clause
  • ora-12539 : TNS:buffer over- or under-flow
  • ora-16600 : failover operation can only be submitted at target database
  • ora-14070 : option may be specified only for partitioned indices or with REBUILD
  • ora-39179 : unable to load table "string"."string" because of OID transform
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-12706 : this CREATE DATABASE character set is not allowed
  • ora-16819 : Fast-Start Failover observer not started
  • ora-25401 : can not continue fetches
  • ora-15104 : conflicting CONTENTS options
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-31509 : publication does not exist
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-39213 : Metadata processing is not available
  • ora-01755 : Must specify an extent number or block number
  • ora-39140 : dump file "string" belongs to job string
  • ora-30340 : illegal dimension name
  • ora-16171 : RECOVER...FINISH not allowed due to gap for thr string, seq string-string
  • ora-24182 : attribute number specified does not exist
  • ora-01370 : Specified restart SCN is too old
  • ora-15090 : handle string is not a valid descriptor
  • ora-00078 : cannot dump variables by name
  • ora-24122 : invalid block range specification
  • ora-07506 : scgrl: $deq unexpected return on lockid string
  • ora-39059 : dump file set is incomplete
  • ora-16598 : Data Guard broker detected a mismatch in configuration
  • 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.