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 : 28-04-2017

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-06960 : Failed to access log file
  • ora-00364 : cannot write header to new log member
  • ora-13439 : GeoRaster metadata pyramid maxLevel error
  • ora-38756 : Flashback is already turned off for this tablespace.
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-01908 : EXISTS keyword expected
  • ora-00319 : log string of thread string has incorrect log reset status
  • ora-02372 : data for row: string
  • ora-08114 : can not alter a fake index
  • ora-15049 : diskgroup "string" contains string error(s)
  • ora-02169 : FREELISTS storage option not allowed
  • ora-06000 : NETASY: port open failure
  • ora-01204 : file number is string rather than string - wrong file
  • ora-37002 : Oracle OLAP failed to initialize. Please contact Oracle OLAP technical support.
  • ora-13502 : Cannot rename SYSAUX tablespace
  • ora-02357 : no valid dump files
  • ora-12439 : invalid combination of policy options
  • ora-30032 : the suspended (resumable) statement has timed out
  • ora-08001 : maximum number of sequences per session exceeded
  • ora-29277 : invalid SMTP operation
  • ora-29926 : association already defined for the object
  • ora-12518 : TNS:listener could not hand off client connection
  • ora-12716 : Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-32505 : too many watchpoints
  • ora-14402 : updating partition key column would cause a partition change
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-26516 : no push transaction acknowledgement
  • ora-26064 : Invalid SCN specified - Wrap: string Base: string.
  • ora-12569 : TNS:packet checksum failure
  • 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.