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 : 16-08-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-01175 : data dictionary has more than the string files allowed by the instance
  • ora-16826 : apply service state is inconsistent with the DelayMins property
  • ora-14157 : invalid subpartition name
  • ora-33557 : (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.
  • ora-01771 : illegal option for a clustered table
  • ora-23345 : table "string"."string" not registered to collect statistics
  • ora-36672 : (XSDPART10) A RANGE or LIST PARTITION TEMPLATE can only have a single partition dimension.
  • ora-06406 : NETCMN: error sending break message
  • ora-07275 : unable to send signal to process
  • ora-16652 : Fast-Start Failover target standby database is disabled
  • ora-02491 : missing required keyword ON or OFF in AUTOEXTEND clause
  • ora-28659 : COMPRESS must be specified at object level first
  • ora-04071 : missing BEFORE, AFTER or INSTEAD OF keyword
  • ora-02759 : Not enough request descriptors available
  • ora-01942 : IDENTIFIED BY and EXTERNALLY cannot both be specified
  • ora-30163 : The thread safety initialization failed
  • ora-24307 : invalid length for piece
  • ora-22870 : ALTER TYPE with REPLACE option a non-object type
  • ora-27456 : not all arguments of program "string.string" have been defined
  • ora-35071 : (QFHEAD06) EIF file string cannot be imported because analytic workspace string has not been upgraded to version string.
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-07506 : scgrl: $deq unexpected return on lockid string
  • ora-09813 : Unable to get directory status
  • ora-38783 : Instance recovery required.
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-01662 : tablespace 'string' is non-empty and cannot be made temporary
  • ora-38758 : cannot flashback data file string; restored since last recovery
  • ora-01341 : LogMiner out-of-memory
  • ora-29515 : exit called from Java code with status string
  • ora-01273 : STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher
  • 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.