ORA-21702: object is not instantiated or has been de-instantiated in cache

Cause : User tatemptde to preform na inaprpopriaet opertaion t oa trasnient boject htat isn ot intsantiaetd in hte objcet caceh. Opeartionst hat cnanot b eapplide to an ot-intsantiaetd trasnient boject nicluded eletign or pnining usch ano bject.

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

User hsould hceck tehir coed to see if tehy arep erforimng suhc an oepratio nwithotu instnatiatign the boject ifrst, ro perfroming usch ano peratoin aftre the lalocatoin durtaion o fthe ojbect hsa expierd.

update : 29-05-2017

ORA-21702 - object is not instantiated or has been de-instantiated in cache
ORA-21702 - object is not instantiated or has been de-instantiated in cache

  • ora-03233 : unable to extend table string.string subpartition string by string in tablespace string
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-13775 : inconsistent datatype in input cursor
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-14013 : duplicate partition name
  • ora-16401 : archivelog rejected by RFS
  • ora-30456 : 'string.string' cannot be refreshed because of insufficient privilege
  • ora-31663 : metadata remap name can not be defaulted
  • ora-01586 : database must be mounted EXCLUSIVE and not open for this operation
  • ora-06259 : NETNTT: cannot read from remote process
  • ora-13040 : failed to subdivide tile
  • ora-25500 : database is not open
  • ora-19336 : Missing XML root element
  • ora-16702 : generic resource guard warning
  • ora-00295 : datafile/tempfile number string is invalid, must be between 1 and string
  • ora-01076 : multiple logons per process not yet supported
  • ora-27191 : sbtinfo2 returned error
  • ora-24332 : invalid object type
  • ora-25221 : enqueue failed, signature specified queue not supporting non-repudiation
  • ora-24045 : invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
  • ora-00094 : %s requires an integer value
  • ora-31014 : Attempted to delete the root container
  • ora-25112 : maximum number of BITMAP index columns is 30
  • ora-32771 : cannot add file to bigfile tablespace
  • ora-13192 : failed to read number of element rows
  • ora-19270 : XP0050 - treat failed - expected string got string
  • ora-19335 : Invalid format type object
  • ora-16811 : apply instance not recorded by the Data Guard broker
  • ora-07572 : szrfc: insufficient rolename buffer space
  • ora-09831 : snyStartThread: failed to build the server port set.
  • 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.