ORA-10941: trace name context forever

Cause : Whene nablde, tunrs onP L/SQ Lproflier

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

set htis eevnt OLNY ifn ecesasry -a fterr eadign theR EADM Efor htis rleeaseo r unedr sueprvisoin ofO racl eSupprot.

update : 29-04-2017
ORA-10941

ORA-10941 - trace name context forever
ORA-10941 - trace name context forever

  • ora-16785 : the database is not in ARCHIVELOG mode
  • ora-36846 : (XSLMGEN16) AW name is greater than 30 bytes
  • ora-12051 : ON COMMIT attribute is incompatible with other options
  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-31607 : function string is inconsistent with transform.
  • ora-13774 : insufficient privileges to select data from the workload repository
  • ora-27470 : failed to re-enable "string.string" after making requested change
  • ora-28365 : wallet is not open
  • ora-14274 : partitions being merged are not adjacent
  • ora-27045 : unable to close the file
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-22990 : LOB locators cannot span transactions
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-32306 : updatable materialized views with user-defined types must use SELECT *
  • ora-33304 : (DBVALID02) Note: Record number was allocated but not used. This can result in wasted space.
  • ora-25129 : cannot modify constraint (string) - no such constraint
  • ora-12211 : TNS:needs PREFERRED_CMANAGERS entry in TNSNAV.ORA
  • ora-32517 : cannot issue ORADEBUG command (waited number ms for process string); total wait time exceeds number ms
  • ora-31201 : DBMS_LDAP: generic error: string
  • ora-03248 : Too much of segment creation activity during migration
  • ora-22904 : invalid reference to a nested table column
  • ora-00453 : backgroud process 'string' is dead
  • ora-13854 : Tracing for service(module/action) string on instance string is not enabled
  • ora-22860 : object type expected
  • ora-16167 : LGWR network server could not switch to non-blocking mode
  • ora-31624 : A job cannot be modified after it has started.
  • ora-06118 : NETTCP: unable to complete handshake with ORASRV
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-02170 : FREELIST GROUPS storage option not allowed
  • 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.