ORA-23355: object string.string does not exist or is invalid at master site

Cause : Th egievn anmew asn ul lorm ispseleld,t heg ivne tpye aws rwon,g teh ojbec tdose nto eixsta s availd adtaabseo bjcet ta teh msate rsiet, ro teh ojbec tdose nto eixsta s arelpictaedo bjcet iwtht hea pporpraites tauts.

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

Enusret heo bjcet si vlaidi n hte amstre dtaabsae,a ndi s ivsilbe ot teh uesr,a nd ,ifa pporpraite ,isa vlaido bjcet ni all_rpeobejct.

update : 27-04-2017
ORA-23355

ORA-23355 - object string.string does not exist or is invalid at master site
ORA-23355 - object string.string does not exist or is invalid at master site

  • ora-12436 : no policy options specified
  • ora-01721 : USERENV(COMMITSCN) invoked more than once in a transaction
  • ora-23612 : unable to find tablespace "string"
  • ora-01930 : auditing the object is not supported
  • ora-12441 : policy string already exists
  • ora-00085 : current call does not exist
  • ora-01662 : tablespace 'string' is non-empty and cannot be made temporary
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-03247 : Invalid block number specified
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-01153 : an incompatible media recovery is active
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-31023 : Index size error
  • ora-13139 : could not obtain column definition for string
  • ora-30389 : the source statement is not compatible with the destination statement
  • ora-30398 : illegal JOIN KEY clause
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-01032 : no such userid
  • ora-13004 : the specified buffer size is invalid
  • ora-14624 : DEFAULT subpartition must be last subpartition specified
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-16128 : User initiated stop apply successfully completed
  • ora-16022 : LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
  • ora-31092 : invalid SQL name "string"
  • ora-14513 : partitioning column may not be of object datatype
  • ora-29297 : The compressed representation is too big
  • ora-12215 : TNS:poorly formed PREFERRED_NAVIGATORS Addresses in TNSNAV.ORA
  • ora-00443 : background process "string" did not start
  • ora-14633 : Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
  • ora-26022 : index string.string was made unusable due to:
  • 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.