TODO.

Preliminary notes:
==================

* Based on Oracle provided mechanism (My Oracle Support note #1299679.1)

All Extract process .prm files should include:
  include HB_Extract.inc

All Extract-Pump process .prm files should include:
  include HB_Pump.inc

All Replicat process .prm files should include:
  include HB_Replicat.inc
OR
  include HB_Replicat.CDC.inc
  - where the source & target databases are the same (eg: CDC processes, MDM 2nd Hop)

Supplemental logging to be added to HEARTBEAT & GGS_HEARTBEAT


TODO:
- explanation on why we map both GGS_HEARTBEAT & HEARTBEAT to target HEARTBEAT
- HEARTBEAT is primarily for 'source' databases
- GGS_HEARTBEAT, GGS_HEARTBEAT_HISTORY - primarily for 'target' databases
- But - might as well deploy entire 'toolkit' as a standard to all DBs?

- Need to decide on schema name... preferably something acceptable to FIL UK, FIL Asia, FMR... not conflicting with existing tables/etc
- Otherwise - minimal changes may be required in incoming feeds from FMR, for example, having a custom HB_Replicat.inc file

- To be developed - the equivalent for other RDBMS...
  - Assuming Oracle will always be target... the only thing to be developed for Sybase/DB2/MS-SQL... would be the equivalent of the HB_job.sql
  - If other systems could be targets... more work necessary
