ORA-23356: masterdef recognizes a master which does not recognize the masterdef

Cause : Psosbil ydorpm_atse_rrpegoru pwsa urna ta amsetrs iet ubtr eomv_emsatre_adtbaaessw a snto urna tm atse rdfeiintoins iet ofrt hta amsetr.

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

Rnu ermvoem_atse_rdtaaabsse rfo mmsatre edfniiito nstiet or eomv eteh paporpiraet amsetr( see sascoitae derro rmsesgae)s.

update : 21-08-2017

ORA-23356 - masterdef recognizes a master which does not recognize the masterdef
ORA-23356 - masterdef recognizes a master which does not recognize the masterdef

  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-33002 : (XSAGDNGL00) In AGGMAP workspace object, the FLOOR argument of number must be less than the CEILING argument of number.
  • ora-25218 : enqueue failed, delay must be zero for queue string.string
  • ora-31459 : system triggers for DBMS_CDC_PUBLISH package are not installed
  • ora-03286 : ALLOCATE EXTENT not valid for HASH CLUSTERS
  • ora-06431 : ssaio: Invalid Block number
  • ora-02219 : invalid NEXT storage option value
  • ora-12984 : cannot drop partitioning column
  • ora-10645 : Recursive Extension in SYSTEM tablespace during migration
  • ora-06711 : TLI Driver: error on bind
  • ora-02045 : too many local sessions participating in global transaction
  • ora-00375 : unable to get default db_block_size
  • ora-01191 : file string is already offline - cannot do a normal offline
  • ora-31487 : cannot support begin dates or end dates in this configuration
  • ora-19676 : one or more files failed during proxy backup or restore
  • ora-29702 : error occurred in Cluster Group Service operation
  • ora-33468 : (ESDREAD13) Discarding compiled code for workspace object because number is no longer a surrogate of dimension workspace object.
  • ora-07286 : sksagdi: cannot obtain device information.
  • ora-03243 : destination dba overlaps with existing control information
  • ora-31087 : insufficient privileges to delete schema "string"
  • ora-19115 : too many context items specified
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-29829 : implementation type does not exist
  • ora-09765 : osnmop: fork failed
  • ora-09208 : sftcls: error closing file
  • ora-30109 : could not open parameter file 'string'
  • ora-37005 : (AWLISTALL03) number readers
  • ora-19036 : Invalid query result set in newContextFromHierarchy()
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-32825 : Messaging Gateway agent has not been started
  • 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.