ORA-29394: session id string and serial# string do not exist

Cause : Invalid session id and serial# were specified as arguments to procedure SWITCH_CONSUMER_GROUP_FOR_SESS of package DBMS_SYSTEM.

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

Specify valid values from the view V$SESSION.

update : 29-06-2017

ORA-29394 - session id string and serial# string do not exist
ORA-29394 - session id string and serial# string do not exist

  • ora-12702 : invalid NLS parameter string used in SQL function
  • ora-30193 : reserved for future use
  • ora-01029 : internal two task error
  • ora-22957 : NULL is an invalid input to powermultiset and COLLECT functions
  • ora-25110 : NOSORT may not be used with a bitmap index
  • ora-29289 : directory access denied
  • ora-00092 : LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
  • ora-31194 : Resource string is already deleted
  • ora-13267 : error reading data from layer table string
  • ora-31040 : Property string: XML type (string) not compatible with internal memory type (string)
  • ora-09293 : sksasmo: unable to send message to console
  • ora-26049 : Unscoped REF column has non-existent table name.
  • ora-36763 : (XSAGGCNTMOVE01) Aggregation variable workspace object cannot have itself as an AGGCOUNT.
  • ora-14268 : subpartition 'string' of the partition resides in offlined tablespace
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-13373 : invalid line segment in geodetic data
  • ora-24032 : object string exists, index could not be created for queue table string
  • ora-39143 : dump file "string" may be an original export dump file
  • ora-30367 : a JOIN KEY clause is required
  • ora-13750 : User "string" has not been granted the "ADMINISTER SQL TUNING SET" privilege.
  • ora-22885 : cannot get REF to a non-persistent object
  • ora-16638 : could not get the instance status
  • ora-36815 : (XSTBLFUNC08) The OLAP_TABLE has attempted to use an AW single row function with the aw_attach parameter set to DURATION QUERY.
  • ora-16956 : Only SELECT or DML statements are supported for test execute.
  • ora-15091 : operation incompatible with open handle in this session
  • ora-29264 : unknown or unsupported URL scheme
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-24803 : illegal parameter value in lob read function
  • ora-16200 : Skip procedure requested to skip statement
  • ora-38731 : Expected version string does not match string in log header.
  • 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.