ORA-26500: error on caching "string"."string"

Cause : Attempt to cache the replication information which is unavailable in the catalog for the object.

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

Use dbms_reputil.sync_up_rep to validate the replication catalog, or use dbms_reputil.make_internal_pkg to validate internal package.

update : 26-04-2017

ORA-26500 - error on caching "string"."string"
ORA-26500 - error on caching "string"."string"

  • ora-29280 : invalid directory path
  • ora-04016 : sequence string no longer exists
  • ora-24069 : cannot downgrade queue table string while it is being upgraded
  • ora-28525 : unable to create Heterogeneous Services error message text
  • ora-27411 : empty string is not a valid repeat interval.
  • ora-28020 : IDENTIFIED GLOBALLY already specified
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-09987 : unable to attach to SGA in READ-ONLY mode
  • ora-32848 : foreign queue DOMAIN required for JMS unified connections
  • ora-00150 : duplicate transaction ID
  • ora-01086 : savepoint 'string' never established
  • ora-25011 : cannot create trigger on internal AQ table
  • ora-13371 : invalid position of measure dimension
  • ora-22628 : OCIAnyData already constructed
  • ora-28164 : REVOKE already specified
  • ora-03204 : the segment type specification should indicate partitioning
  • ora-01868 : the leading precision of the interval is too small
  • ora-26098 : direct path context is not prepared
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-25261 : JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
  • ora-30100 : internal error [number]
  • ora-01534 : rollback segment 'string' doesn't exist
  • ora-01306 : dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents
  • ora-06916 : CMX: error in data read (t_datain)
  • ora-32010 : cannot find entry to delete in SPFILE
  • ora-16783 : instance string not open for read and write access
  • ora-30573 : AUTO segment space management not valid for this type of tablespace
  • ora-13441 : GeoRaster metadata SRS error
  • ora-27504 : IPC error creating OSD context
  • ora-30088 : datetime/interval precision is out of range
  • 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.