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 : 30-04-2017

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-01520 : number of data files to add (string) exceeds limit of string
  • ora-16545 : unable to get response
  • ora-16092 : dependent archive log destination is not active
  • ora-02433 : cannot disable primary key - primary key not defined for table
  • ora-07231 : slemcc: invalid file handle, seals do not match.
  • ora-27089 : unable to release advisory lock
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-01253 : cannot start online backup - file string in recovery manager backup
  • ora-32011 : cannot restore SPFILE to location already being used by the instance
  • ora-28510 : heterogeneous database link initialization failed
  • ora-36886 : (XSSRF05) Error rewritting OLAP DML expression. Rewritten expression is greater than number bytes
  • ora-26520 : internal memory failure
  • ora-19277 : XP0005 - XPath step specifies an item type matching no node: (string)
  • ora-34897 : (PPMONTHS01) Blank lines are not allowed in the MONTHNAMES option.
  • ora-31217 : DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
  • ora-40304 : invalid classname string in prior probability specification
  • ora-23423 : job number string is not positive
  • ora-32127 : REFs do not belong to any connection
  • ora-24387 : Invalid attach driver
  • ora-06110 : NETTCP: message send failure
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-31087 : insufficient privileges to delete schema "string"
  • ora-24903 : invalid namespace attribute passed into OCI call
  • ora-14151 : invalid table partitioning method
  • ora-13004 : the specified buffer size is invalid
  • ora-15196 : invalid ASM block header [string:string] [string] [string] [string] [string != string]
  • ora-26507 : null master connection
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • 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.