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 : 24-04-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-19380 : invalid plan filter
  • ora-03128 : connection is in blocking mode
  • ora-19915 : unable to encrypt pre-10.2 files
  • ora-01949 : ROLE keyword expected
  • ora-40282 : invalid cost matrix
  • ora-00080 : invalid global area specified by level string
  • ora-39022 : Database version string is not supported.
  • ora-16154 : suspect attribute: string
  • ora-16136 : Managed Standby Recovery not active
  • ora-14625 : subpartition contains rows corresponding to values being dropped
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-02756 : osnfsmnam: name translation failure
  • ora-33883 : (MAKEDCL36) You cannot use the string attribute when you define an EXTERNAL partition with an existing target.
  • ora-00446 : background process started when not expected
  • ora-32165 : Cannot get XA environment
  • ora-16630 : that database property was deprecated
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-12662 : proxy ticket retrieval failed
  • ora-14402 : updating partition key column would cause a partition change
  • ora-13836 : invalid attribute value specified
  • ora-14297 : Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
  • ora-16234 : restarting to reset Logical Standby apply
  • ora-01250 : Error string occurred during termination of file header access
  • ora-12654 : Authentication conversion failed
  • ora-16736 : unable to find the destination entry of standby database "string" in V$ARCHIVE_DEST
  • ora-21602 : operation does not support the specified typecode
  • ora-00477 : SNP* process terminated with error
  • ora-16181 : SGA specified for Logical Standby is too large
  • ora-28576 : lost RPC connection to external procedure agent
  • ora-19044 : character length specified for XMLSerialize is too small.
  • 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.