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 : 21-07-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-06550 : line string, column string: string
  • ora-29377 : consumer group string is not part of top-plan string
  • ora-30463 : 'string' is not a detail table of any summary
  • ora-31223 : DBMS_LDAP: cannot open more than string LDAP server connections
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-34296 : (MXDCL36) A NUMBER dimension must be defined with a fixed precision and scale, using the form NUMBER(precision) or NUMBER(precision, scale).
  • ora-00025 : failed to allocate string
  • ora-25443 : duplicate column value for table alias: string, column number: string
  • ora-09800 : Process sensitivity label retrieval failed.
  • ora-12406 : unauthorized SQL statement for policy string
  • ora-12825 : explicit degree of parallelism must be specified here
  • ora-27194 : skgfdvcmd: sbtcommand returned error
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-31460 : logfile location string is not an existing directory
  • ora-24147 : rule string.string does not exist
  • ora-16137 : No terminal recovery is required
  • ora-13351 : two or more rings of a complex polygon overlap
  • ora-30074 : GLOBAL partitioned index on TIME/TIMESTAMP WITH TIME ZONE not allowed
  • ora-24167 : incompatible rule engine objects, cannot downgrade
  • ora-10584 : Can not invoke parallel recovery for test recovery
  • ora-14308 : partition bound element must be one of: string, datetime or interval literal, number, or NULL
  • ora-29271 : not connected
  • ora-12615 : TNS:preempt error
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-09977 : skxfqhini: Error Connecting
  • ora-06806 : TLI Driver: could not complete protocol initialization for SPX
  • ora-25286 : Invalid number of elements in the message properties array
  • ora-32846 : Messaging Gateway agent cannot be started; status is string
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • 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.