ORA-33445: (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.

Cause : Two variables are "partition-dependent" if they share any external partition target variables, or if one is the target of an external partition of the other. If object names referred to non-partition-dependent variables at compile time but refer to partition-dependent variables in the run-time context, the OLAP DML program, formula, or model will be automatically recompiled.

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

None needed.

update : 29-06-2017
ORA-33445

ORA-33445 - (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.
ORA-33445 - (ESDREAD15) Discarding compiled code for workspace object because workspace object and workspace object, which were not partition-dependent when the code was compiled, are now partition-dependent.

  • ora-07656 : slsprom:$GETDVI failure
  • ora-02376 : invalid or redundant resource
  • ora-32732 : Parallel Oradebug session is aborted
  • ora-27073 : Trying to close a file which has async I/Os pending to be dequeued
  • ora-36962 : (XSRELTBL08) string is not a valid workspace object.
  • ora-13336 : failure in converting standard diminfo/geometry to LRS dim/geom
  • ora-30340 : illegal dimension name
  • ora-28235 : algorithm not available
  • ora-28539 : gateway does not support result sets
  • ora-31609 : error loading file "string" from file system directory "string"
  • ora-01940 : cannot drop a user that is currently connected
  • ora-03213 : Invalid Lob Segment Name for DBMS_SPACE package
  • ora-02180 : invalid option for CREATE TABLESPACE
  • ora-31414 : error(s) occurred during change table advance
  • ora-22851 : invalid CHUNK LOB storage option value
  • ora-12436 : no policy options specified
  • ora-31035 : Could not bind locked resource to path string/string
  • ora-28671 : UPDATE BLOCK REFERENCES may not be used on a partitioned index as a whole
  • ora-01935 : missing user or role name
  • ora-38950 : Source platform string not cross platform compliant
  • ora-32845 : Messaging Gateway agent is already running
  • ora-09882 : sstasfre/sstasdel: shmctl error, unable to remove tas shm page
  • ora-06901 : CMX: no local name assigned to local application
  • ora-07245 : sfccf: unable to lseek and write the last block.
  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-01569 : data file too small for system dictionary tables
  • ora-16823 : redo transport mode is incompatible for current operation
  • ora-25531 : MTTR specified is too small: string
  • ora-31630 : a job name is required to attach a job for user string
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • 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.