I have a MASTER table and a COPY table in separate databases (both are Oracle 12c).

I want to sync the MASTER table with the COPY table on a weekly basis. The goal is to keep the two tables exactly in sync.

I can think of a few options for syncing from MASTER to COPY:

• Sync All: Delete all from COPY and insert all from MASTER.
• Period-based: Replace (or add) rows in COPY where sysdate - editdate < 7 in MASTER.
• Period-based with redundancy: Replace (or add) rows in COPY where sysdate - editdate < 31 in MASTER.
  • This applies in situations where rows in previous syncs have failed. The failed rows in MASTER will have been corrected, but we still need to sync them to COPY in future syncs.
• Manual flag: Users manually flag rows in MASTER that need to by synced to COPY. The sync process resets the flag in MASTER once the edits have been synced top COPY.
• Date comparison: If date in MASTER is newer than date in COPY then sync those rows.

Are there any other options or details that I've missed?

I have a MASTER table and a COPY table in separate databases (both are Oracle 12c).

I want to sync the MASTER table with the COPY table on a weekly basis.

I can think of a few options for syncing from MASTER to COPY:

• Sync All: Delete all from COPY and insert all from MASTER.
• Period-based: Replace (or add) rows in COPY where sysdate - editdate < 7 in MASTER.
• Period-based with redundancy: Replace (or add) rows in COPY where sysdate - editdate < 31 in MASTER.
  • This applies in situations where rows in previous syncs have failed. The failed rows in MASTER will have been corrected, but we still need to sync them to COPY in future syncs.
• Manual flag: Users manually flag rows in MASTER that need to by synced to COPY. The sync process resets the flag in MASTER once the edits have been synced to COPY.
• Date comparison: If date in MASTER is newer than date in COPY then sync those rows.

Are there any other options or details that I've missed?

I have a MASTER table and a COPY table in separate databases (both are Oracle 12c).

I want to sync the MASTER table with the COPY table on a weekly basis. The goal is to keep the two tables exactly in sync--with no exceptions.

I can think of a few theoretical options for syncing from MASTER to COPY:

• Sync All: Delete all from COPY and insert all from MASTER.
• Period-based: Replace (or add) rows in COPY where sysdate - editdate < 7 in MASTER.
• Period-based with redundancy: Replace (or add) rows in COPY where sysdate - editdate < 31 in MASTER.
  • This applies in situations where rows in previous syncs have failed. The problem rows in MASTER will have been corrected, but we still need to sync them to COPY in future syncs.
• Manual flag: Users manually flag rows in MASTER that need to by synced to COPY. The sync process resets the flag in MASTER once the edits have been synced top COPY.
• Date comparison: If date in MASTER is newer than date in COPY then sync those rows.

Are there any other theoretical options or details that I've missed?

I have a MASTER table and a COPY table in separate databases (both are Oracle 12c).

I want to sync the MASTER table with the COPY table on a weekly basis. The goal is to keep the two tables exactly in sync.

I can think of a few options for syncing from MASTER to COPY:

• Sync All: Delete all from COPY and insert all from MASTER.
• Period-based: Replace (or add) rows in COPY where sysdate - editdate < 7 in MASTER.
• Period-based with redundancy: Replace (or add) rows in COPY where sysdate - editdate < 31 in MASTER.
  • This applies in situations where rows in previous syncs have failed. The failed rows in MASTER will have been corrected, but we still need to sync them to COPY in future syncs.
• Manual flag: Users manually flag rows in MASTER that need to by synced to COPY. The sync process resets the flag in MASTER once the edits have been synced top COPY.
• Date comparison: If date in MASTER is newer than date in COPY then sync those rows.

Are there any other options or details that I've missed?

I have a MASTER table and a COPY table.

I want to sync the MASTER table with the COPY table on a weekly basis. The goal is to keep the two tables exactly in sync--with no exceptions.

I can think of a few theoretical options for syncing from MASTER to COPY:

• Sync All: Delete all from COPY and insert all from MASTER
• Period-based: Replace (or add) rows in COPY where sysdate - editdate < 7 in MASTER
• Period-based with redundancy: Replace (or add) rows in COPY where sysdate - editdate < 31 in MASTER
  • This applies in situations where rows in previous syncs have failed. The problem rows in MASTER will have been corrected, but we still need to sync them to COPY in future syncs.
• Manual flag: Users manually flag rows in MASTER that need to by synced to COPY. The sync process resets the flag in MASTER once the edits have been synced.
• Date comparison: If date in MASTER is newer than date in COPY then sync those rows

Are there any other theoretical options or details that I've missed?

I have a MASTER table and a COPY table in separate databases (both are Oracle 12c).

I want to sync the MASTER table with the COPY table on a weekly basis. The goal is to keep the two tables exactly in sync--with no exceptions.

I can think of a few theoretical options for syncing from MASTER to COPY:

• Sync All: Delete all from COPY and insert all from MASTER.
• Period-based: Replace (or add) rows in COPY where sysdate - editdate < 7 in MASTER.
• Period-based with redundancy: Replace (or add) rows in COPY where sysdate - editdate < 31 in MASTER.
  • This applies in situations where rows in previous syncs have failed. The problem rows in MASTER will have been corrected, but we still need to sync them to COPY in future syncs.
• Manual flag: Users manually flag rows in MASTER that need to by synced to COPY. The sync process resets the flag in MASTER once the edits have been synced top COPY.
• Date comparison: If date in MASTER is newer than date in COPY then sync those rows.

Are there any other theoretical options or details that I've missed?