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-05-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-02854 : Invalid number of request buffers
  • ora-06751 : TLI Driver: bound addresses unequal
  • ora-19254 : XQ0034 - too many declarations for function string
  • ora-33074 : (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.
  • ora-28663 : Logging/Nologging attribute can not be specified in the statement ALTER TABLE ADD OVERFLOW
  • ora-30130 : invalid parameter key type received
  • ora-16245 : paging in transaction string, string, string
  • ora-28331 : encrypted column size too long for its data type
  • ora-19637 : backupPieceCreate requires file name when using DISK device
  • ora-32602 : FREEPOOLS and FREELIST GROUPS cannot be used together
  • ora-31433 : subscriber view does not exist
  • ora-16518 : unable to allocate virtual instance id
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-14177 : STORE-IN (Tablespace list) can only be specified for a LOCAL index on a Hash or Composite Range Hash table
  • ora-30025 : DROP segment 'string' (in undo tablespace) not allowed
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-26021 : index string.string partition string loaded successfully with string keys
  • ora-12084 : must use ALTER MATERIALIZED VIEW to alter "string"."string"
  • ora-12984 : cannot drop partitioning column
  • ora-07244 : ssfccf: create file failed, file size limit reached.
  • ora-16793 : logical standby database guard is unexpectedly off
  • ora-07605 : szprv: $ASCTOID failure
  • ora-12592 : TNS:bad packet
  • ora-16221 : history table synchronization error
  • ora-07452 : specified resource manager plan does not exist in the data dictionary
  • ora-29842 : option not supported with the version string of the indextype interface
  • ora-12987 : cannot combine drop column with other operations
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-19005 : Duplicate XMLType LOB storage option
  • 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.