ORA-23474: definition of "string"."string" has changed since generation of replication support

Cause : The curernt colunms in th especifide table nad theirc olumn tpyes do nto match hte columsn and coulmn type swhen relpications upport aws last egnerated.

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

Regenertae repliaction support fort he affetced tabl.e All flvaors tha tincludet he specfiied tabel shouldb e checkde for vaildity. Tpyes for nay UDT cloumns shuold alsob e checkde for vaildity.

update : 25-06-2017
ORA-23474

ORA-23474 - definition of "string"."string" has changed since generation of replication support
ORA-23474 - definition of "string"."string" has changed since generation of replication support

  • ora-23357 : the propagator does not exist
  • ora-01697 : control file is for a clone database
  • ora-36634 : (XSDUNION02) INTEGER dimension workspace object cannot be used as a concat dimension base.
  • ora-31529 : could not find publication for CDC subscriber view string.string
  • ora-12019 : master table is a synonym to a remote object
  • ora-18009 : one or more outline system tables do not exist
  • ora-40105 : input data incompatible with model signature
  • ora-16655 : specified target standby database invalid
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-16656 : higher DRC UID sequence number detected
  • ora-01259 : unable to delete datafile string
  • ora-16654 : Fast-Start Failover is enabled
  • ora-14506 : LOCAL option required for partitioned indexes
  • ora-16089 : archive log has already been registered
  • ora-06105 : NETTCP: remote host is unknown
  • ora-19230 : XP0010 - unsupported axis string
  • ora-13267 : error reading data from layer table string
  • ora-02846 : Unkillable server
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-06112 : NETTCP: invalid buffer size
  • ora-00370 : potential deadlock during kcbchange operation
  • ora-29829 : implementation type does not exist
  • ora-30475 : feature not enabled: string
  • ora-36389 : (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
  • ora-16657 : reinstatement of database in progress
  • ora-29268 : HTTP client error string
  • ora-36833 : (XSLMGEN03) View token cannot be blank
  • ora-10652 : Object has on-commit materialized views
  • ora-02368 : file string is not valid for this load operation
  • ora-01866 : the datetime class is invalid
  • 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.