ORA-10940: trace name context forever

Cause : Size fo the LP/SQL rtacingc irculra buffre, in iklobytse.

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

Set tihs evetn in cnocert iwth th e10938e vent nad the_ PLSQLD_UMP_BFUFER_EEVNTS iint.orap arameetr, unedr suprevisio nof Orcale Support.

update : 28-06-2017

ORA-10940 - trace name context forever
ORA-10940 - trace name context forever

  • ora-02899 : smscre: Cannot create SGA with Extended Shared Memory feature
  • ora-28604 : table too fragmented to build bitmap index (string,string,string)
  • ora-25254 : time-out in LISTEN while waiting for a message
  • ora-07568 : slspool: $OPEN failure
  • ora-14640 : add/coalesce index partition operation is valid only for hash partitioned global indexes
  • ora-10364 : Do not clear GIMH_STC_SHUT_BEGIN state during shutdown
  • ora-08449 : invalid numeric symbol found in picture mask
  • ora-07493 : scgrcl: lock manager error.
  • ora-01974 : Illegal archive option
  • ora-10580 : Can not modify datafile header during test recovery
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-14253 : table is not partitioned by Composite Range method
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-25287 : Invalid value string, string should be non-negative
  • ora-07219 : slspool: unable to allocate spooler argument buffer.
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-02274 : duplicate referential constraint specifications
  • ora-14620 : DEFAULT subpartition already exists
  • ora-02205 : only SELECT and ALTER privileges are valid for sequences
  • ora-36380 : (AGGRECURSE) AGGREGATE was called recursively, which is not allowed.
  • ora-01481 : invalid number format model
  • ora-31398 : DBMS_LDAP: Shared servers are not supported.
  • ora-12834 : Instance group name, 'string', too long, must be less than string characters
  • ora-31654 : unable to convert file or volume size as specified to a number
  • ora-25473 : cannot store string in rule action context
  • ora-29541 : class string.string could not be resolved
  • ora-38401 : synonym string not allowed
  • ora-26091 : requested direct path operation not supported
  • ora-09989 : attempt to use invalid skgmsdef struct pointer
  • ora-39777 : data saves are not allowed when loading lob columns
  • 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.