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

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

  • ora-14136 : ALTER TABLE EXCHANGE restricted by fine-grained security
  • ora-16042 : user requested cancel immediate of managed recovery operation
  • ora-17612 : Failed to discover Oracle Disk Manager library, return value string
  • ora-38716 : Must supply an integer for the TYPE option.
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-16000 : database open for read-only access
  • ora-04066 : non-executable object, string
  • ora-01112 : media recovery not started
  • ora-03289 : partition name and segment type do not match
  • ora-14611 : Duplicate subpartition name string in template
  • ora-31454 : invalid value string for operation parameter, expecting: ADD or DROP
  • ora-40217 : priors table mismatched with training data
  • ora-00325 : archived log for thread string, wrong thread # string in header
  • ora-32007 : internal
  • ora-24042 : no propagation schedule exists for QUEUE string and DESTINATION string
  • ora-04085 : cannot change the value of an OLD reference variable
  • ora-00405 : compatibility type "string"
  • ora-12431 : invalid audit action
  • ora-14454 : attempt to reference temporary table in a referential integrity constraint
  • ora-22931 : MOVE of nested table to a different tablespace not supported
  • ora-31101 : Token "string" not given while locking resource "string"
  • ora-16259 : Switchover to logical standby requires a log archive destination
  • ora-27074 : unable to determine limit for open files
  • ora-25147 : UNIFORM SIZE value greater than maximum extent size
  • ora-22153 : source variable-length array is not initialized
  • ora-25265 : specified signature for a queue which does not support reciever non-repudiation
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-29538 : Java not installed
  • ora-26080 : file "string" is not part of table string.string partition string
  • ora-30048 : Internal event for IMU auto-tuning
  • 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.