Browse Prior Art Database

Hetererogenous Database Change Propagation

IP.com Disclosure Number: IPCOM000118161D
Original Publication Date: 1996-Oct-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 2 page(s) / 60K

Publishing Venue

IBM

Related People

Holmes, KT: AUTHOR

Abstract

When a change is made to one copy of a data record in a database, that change must be propagated to other copies.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 53% of the total text.

Hetererogenous Database Change Propagation

      When a change is made to one copy of a data record in a
database, that change must be propagated to other copies.

      Change propagation includes capturing the change to one copy
and forwarding it for application against another copy.  In this way,
a copy can be maintained without the need for a full refresh (new
copy).  Asynchronous propagation means that there is a time lag
between the change to the source copy and the change to the target
copy.

      Most replication and asynchronous propagation solutions use
change record formats and protocols which are specific to the
databases that they support.  The provision of a general propagation
solution that would support a heterogenous environment involves a
number of problems:

      Character sets may be different (e.g., EBCDIC/ASCII) - Data
Types may be different between source and target - Data Types may be
different between multiple targets - No character architecture is
universally supported - There are wide and varied sets of numerical
representations - Database naming conventions are different (e.g.,
Tables/Records/Segments, etc.) - Multiple changes making a
Unit-Of-Work (UOW) may need to be preserved - Database types are
different (e.g., Relational/Hierarchical/Network/Object
based/Inverted list, etc.).

      The solution described defines a change record which can be
independent of the database, network or operating system.  It is
based on...