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 : 18-08-2017
ORA-13869

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-00406 : COMPATIBLE parameter needs to be string or greater
  • ora-22297 : warning: Open LOBs exist at transaction commit time
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-38312 : original name is used by an existing object
  • ora-06404 : NETCMN: invalid login (connect) string
  • ora-12650 : No common encryption or data integrity algorithm
  • ora-19764 : database id string does not match database id string in control file
  • ora-08460 : invalid environment clause in environment parameter
  • ora-16193 : Primary and standby network encryption mismatch
  • ora-13641 : Task cannot be interrupted yet. You may cancel it instead.
  • ora-31617 : unable to open dump file "string" for write
  • ora-23360 : only one materialized view for master table "string" can be created
  • ora-12456 : label security startup in progress
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-22993 : specified input amount is greater than actual source amount
  • ora-30194 : reserved for future use
  • ora-13126 : unable to determine class for spatial table string
  • ora-02828 : Segment free list is empty
  • ora-16135 : Invalid LOG_ARCHIVE_CONFIG modification while in protected mode
  • ora-07427 : spstp: cannot change directory to dbs.
  • ora-38750 : FLASHBACK DATABASE may not be performed using a dispatcher.
  • ora-02799 : Unable to arm signal handler
  • ora-28503 : bind value cannot be translated into SQL text for non-Oracle system
  • ora-30513 : cannot create system triggers of INSTEAD OF type
  • ora-12062 : transaction string received out of sequence from site string
  • ora-30177 : invalid flag used in a format specification
  • ora-02460 : Inappropriate index operation on a hash cluster
  • ora-26754 : cannot specify both one-to-one transformation function string and one-to-many transformation function string
  • ora-12018 : following error encountered during code generation for "string"."string"
  • ora-06925 : CMX: disconnect during connect request
  • 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.