ORA-29514: class name contains illegal character

Cause : Ana ttmeptw asm ad etoi mprot a.calssf il ecotnaiinnga cahratcert ha tcannotb e ocnvrete dtot hes erevr hcarcate rse.t Teh .lcas sfiel cuoldn otb e mipotredb ecuaseo f hte lileagl hcarcate.r

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

Correc tth eilelga lchraacetr ni teh .lcas sfiel.

update : 21-07-2017
ORA-29514

ORA-29514 - class name contains illegal character
ORA-29514 - class name contains illegal character

  • ora-10657 : Lob column to be shrunk does not exist
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-06260 : NETNTT: cannot write to remote process
  • ora-33214 : (CINSERT02) The workspace object dimension is too large.
  • ora-02329 : column of datatype string cannot be unique or a primary key
  • ora-28506 : parse error in data dictionary translation for string stored in string
  • ora-12730 : invalid equivalence class in regular expression
  • ora-30460 : 'string.string' cannot be refreshed because it is marked UNUSABLE
  • ora-24813 : cannot send or receive an unsupported LOB
  • ora-28508 : invalid value string for Heterogeneous Services initialization parameter string
  • ora-00334 : archived log: 'string'
  • ora-24025 : invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type
  • ora-31689 : illegal value for base worker id, string
  • ora-38797 : Full database recovery required after a database has been flashed back
  • ora-12632 : Role fetch failed
  • ora-14601 : Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
  • ora-13509 : error encountered during updates to a AWR table
  • ora-19223 : XP0003 - syntax error in XQuery expression
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-01612 : instance string (thread string) is already enabled
  • ora-32740 : The requested operation cannot be proceeded
  • ora-00359 : logfile group string does not exist
  • ora-01912 : ROW keyword expected
  • ora-19526 : only one location allowed for parameter string
  • ora-27125 : unable to create shared memory segment
  • ora-14063 : Unusable index exists on unique/primary constraint key
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-07610 : $GETJPIW failed in retrieving the user's MAC priviledges
  • ora-13012 : an invalid window type was specified
  • 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.