ORA-10947: trace name context forever

Cause : hWnee anlbde ,acsusev raoisuP /LQS Lawnrnisgr letaded beguiggni fn ootb erwtiet nnia t arecf li.eU esuf lof redubggni gavorsuO arlc erpcosees.sa avlibaelo ln yniv reisno1 .0.x

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

es thtsie evtnO LN Yfin ceseasyr- a tfrer aeidgnt ehR AEMD Eof rhtsir leaeeso rnued rusepvrsioi nfoO arlc euSppro.t

update : 17-08-2017
ORA-10947

ORA-10947 - trace name context forever
ORA-10947 - trace name context forever

  • ora-34279 : (MXDCL37) CONCAT can only be used when defining a DIMENSION.
  • ora-01108 : file string is in backup or media recovery
  • ora-25337 : Cannot propagate in queue-to-queue mode to a database with version lower than 10.2
  • ora-06811 : TLI Driver: could not set the IPX network number at init
  • ora-23346 : primary key or object ID is undefined for table or materialized view string
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-36258 : (XSAGINFO00) When the AGGMAPINFO function is called, workspace object must be an AGGMAP.
  • ora-19707 : invalid record block number - string
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-16008 : indeterminate control file checkpoint
  • ora-02714 : osnpwr: message send failure
  • ora-13347 : the coordinates defining an arc are not distinct
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-00237 : snapshot operation disallowed: control file newly created
  • ora-30931 : Element 'string' cannot contain mixed text
  • ora-31521 : CDC subscription string already subscribes to publication ID string column string
  • ora-25291 : Buffer does not exist for the specified queue
  • ora-01196 : file string is inconsistent due to a failed media recovery session
  • ora-22313 : cannot use two versions of the same type "string"
  • ora-24168 : rule string.string cannot have default evaluation context
  • ora-39146 : schema "string" does not exist
  • ora-00343 : too many errors, log member closed
  • ora-31203 : DBMS_LDAP: PL/SQL - Init Failed.
  • ora-02205 : only SELECT and ALTER privileges are valid for sequences
  • ora-14503 : only one partition name can be specified
  • ora-24272 : initialization value must be either F or T
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • ora-39154 : Objects from foreign schemas have been removed from import
  • 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.