ORA-29549: class string.string has changed, Java session state cleared

Cause : A calss ni us eby hte cruren tsesison aws rdeefiend o rdropped,i nvaildatnig teh currentJ avas essoin satte nad rqeuirnig taht i tbe lcearde.

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

No catio nreqiured.

update : 28-04-2017
ORA-29549

ORA-29549 - class string.string has changed, Java session state cleared
ORA-29549 - class string.string has changed, Java session state cleared

  • ora-38760 : This database instance failed to turn on flashback database
  • ora-19676 : one or more files failed during proxy backup or restore
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-32019 : The parameter SPFILE cannot be updated in the server parameter file.
  • ora-39959 : invalid warning number (string)
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-07324 : smpall: malloc error while allocating pga.
  • ora-19201 : Datatype not supported
  • ora-19268 : XQ0048 - namespace string does not match target namespace string
  • ora-26525 : session connection attempt failed for string (@string)
  • ora-07279 : spcre: semget error, unable to get first semaphore set.
  • ora-10841 : Default un-inintialized charact set form to SQLCS_IMPLICIT
  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-12856 : cannot run parallel query on a loopback connection
  • ora-23618 : Generation of script string is not complete.
  • ora-26740 : cannot downgrade because there are file groups
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-29849 : error occurred in the execution of ODCIINDEXSPLITPARTITION routine
  • ora-24415 : Missing or null username.
  • ora-24395 : cannot reinitialize non-existent pool
  • ora-36831 : (XSLMGEN01) View token cannot be NA
  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • ora-13755 : invalid "SQL Tuning Set" name
  • ora-29911 : null scan context returned by ODCIIndexStart() routine
  • ora-18002 : the specified outline does not exist
  • ora-30683 : failure establishing connection to debugger
  • ora-27001 : unsupported device type
  • ora-01177 : data file does not match dictionary - probably old incarnation
  • ora-00299 : must use file-level media recovery on data file string
  • 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.