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 : 24-08-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-02750 : osnfsmmap: cannot open shared memory file ?/dbs/ftt_.dbf
  • ora-23353 : deferred RPC queue has entries for object group "string"."string"
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-30197 : reserved for future use
  • ora-13001 : dimensions mismatch error
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-24432 : The statement that was returned is not tagged.
  • ora-28164 : REVOKE already specified
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-26732 : invalid file group string privilege
  • ora-06140 : NETTCP: no such user
  • ora-13044 : the specified tile size is smaller than the tolerance
  • ora-31117 : Table "string"."string" is not resource metadata enabled
  • ora-27037 : unable to obtain file status
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-30191 : missing argument list
  • ora-13333 : invalid LRS measure
  • ora-13643 : The task can not be interrupted or cancelled.
  • ora-39173 : Encrypted data has been stored unencrypted in dump file set.
  • ora-39304 : conflicting changes to object "string" : string
  • ora-13523 : unable to allocate required space for return type
  • ora-31069 : Cannot apply typed changes to non-schema-based XMLType nodes
  • ora-31637 : cannot create job string for user string
  • ora-13243 : specified operator is not supported for 3- or higher-dimensional R-tree
  • ora-39952 : only numbers can be specified as range values
  • ora-29663 : Unable to find a method that matches one or more of the functions
  • ora-03212 : Temporary Segment cannot be created in locally-managed tablespace
  • ora-29307 : datafile string error, string
  • ora-13510 : invalid RETENTION string, must be in the range (string, string)
  • ora-39097 : Data Pump job encountered unexpected error 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.