ORA-23536: the object "string"."string" is not cached at the middle tier as expected.

Cause : The object may have been dropped or renamed at the back end after dbms_ias_inst.start_ias_inst was executed.

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

Check the validity of the object at the back end and retry the instantiation.

update : 26-06-2017

ORA-23536 - the object "string"."string" is not cached at the middle tier as expected.
ORA-23536 - the object "string"."string" is not cached at the middle tier as expected.

  • ora-19206 : Invalid value for query or REF CURSOR parameter
  • ora-01604 : illegal number range in clause "string" of string
  • ora-13775 : inconsistent datatype in input cursor
  • ora-07203 : sltln: attempt to translate a long environment variable.
  • ora-21522 : attempted to use an invalid connection in OCI (object mode only)
  • ora-29802 : missing CONTEXT keyword
  • ora-22883 : object deletion failed
  • ora-00408 : parameter string is set to TRUE
  • ora-09923 : Can't spawn process - user log directory not created properly
  • ora-18010 : command missing mandatory CATEGORY keyword
  • ora-06752 : TLI: error in signal setup
  • ora-13380 : network not found
  • ora-36960 : (XSFCAST27) The value of the string expression must be an odd number. You specified number.
  • ora-03284 : datafile string is not a member of tablespace string
  • ora-25301 : Cannot enqueue or dequeue user buffered messages to a database with version lower than 10.2
  • ora-30558 : internal error [string] in function based index
  • ora-29346 : invalid tablespace list
  • ora-02179 : valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
  • ora-12626 : TNS:bad event type
  • ora-13518 : Invalid database id (string)
  • ora-14255 : table is not partitioned by Range, Composite Range or List method
  • ora-24803 : illegal parameter value in lob read function
  • ora-38309 : object not purgable
  • ora-12020 : materialized view string is not registered
  • ora-01045 : user string lacks CREATE SESSION privilege; logon denied
  • ora-07219 : slspool: unable to allocate spooler argument buffer.
  • ora-36200 : (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.
  • ora-02776 : Value for request done signal exceeds maximum
  • ora-29256 : Cursor contains both regular and array defines which is illegal
  • ora-14551 : cannot perform a DML operation inside a query
  • 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.