ORA-33456: (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.

Cause : The type of the specified object has changed.

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

None needed.

update : 23-06-2017
ORA-33456

ORA-33456 - (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.
ORA-33456 - (ESDREAD08) Discarding compiled code for workspace object because number is a(n) string, which string did not expect to find in a compiled program.

  • ora-16224 : Database Guard is enabled
  • ora-19281 : XQ0055 - It is a static error if a Prolog contains more than one inherit-namespaces declaration
  • ora-06592 : CASE not found while executing CASE statement
  • ora-31642 : the following SQL statement fails: string
  • ora-19734 : wrong creation SCN - control file expects converted plugged-in datafile
  • ora-08413 : invalid compiler type in FORMAT parameter at string
  • ora-09705 : spcre: cannot initialize latch semaphore
  • ora-36910 : (XSAGDNGL47) In AGGMAP workspace object, DYNAMIC MODEL workspace object can only edit the top level of its matching relation hierarchy.
  • ora-36995 : (XSRELGID12) There are duplicate values in the surrogate dimension gid. Use the levelorder option to resolve the ambiguity.
  • ora-15109 : conflicting protection attributes specified
  • ora-19332 : Invalid column in the CREATE_DBURI operator
  • ora-16207 : Logical standby dictionary build not permitted.
  • ora-00236 : snapshot operation disallowed: mounted control file is a backup
  • ora-25405 : transaction status unknown
  • ora-32125 : Attribute type is not appropriate
  • ora-14518 : partition contains rows corresponding to values being dropped
  • ora-00206 : error in writing (block string, # blocks string) of control file
  • ora-24780 : cannot recover a transaction while in an existing transaction
  • ora-13226 : interface not supported without a spatial index
  • ora-01950 : no privileges on tablespace 'string'
  • ora-02270 : no matching unique or primary key for this column-list
  • ora-01153 : an incompatible media recovery is active
  • ora-36643 : (XSDUNION21) Concat dimension workspace object cannot be changed to NOT UNIQUE because it contains custom member values.
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-28334 : column is already encrypted
  • ora-00278 : log file 'string' no longer needed for this recovery
  • ora-24010 : QUEUE string does not exist
  • ora-00976 : LEVEL, PRIOR, or ROWNUM not allowed here
  • ora-25177 : UNRECOVERABLE option not permitted
  • ora-22978 : only simple attribute name is allowed in the WITH OBJECT OID clause
  • 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.