Characteristics of a tracker site
A tracker site is a separate Db2 subsystem or data sharing group that exists solely for the purpose of keeping shadow copies of the data at your primary site.
Because the tracker site must use only the primary site logs for recovery, you must not update the catalog and directory or the data at the tracker site. The Db2 subsystem at the tracker site disallows updates.
- The following SQL statements are not allowed at a tracker site:
- GRANT or REVOKE
- DROP, ALTER, or CREATE
- UPDATE, INSERT, or DELETE
Dynamic read-only SELECT statements are allowed, but not recommended. At the end of each tracker site recovery cycle, databases might contain uncommitted data, and indexes might be inconsistent with the data at the tracker site.
- The only online utilities that are allowed are REPORT, DIAGNOSE, RECOVER, REBUILD, and RESTORE SYSTEM LOGONLY. Recovery to a prior point in time is not allowed.
- BIND is not allowed.
- TERM UTIL is not allowed for LOAD, REORG, REPAIR, and COPY.
- The START DATABASE command is not allowed when LPL or GRECP status exists for the object of the command. Use of the START DATABASE command is not necessary to clear LPL or GRECP conditions because you are going to be running RECOVER jobs that clear the conditions.
- The START DATABASE command with ACCESS(FORCE) is not allowed.
- Down-level detection is disabled.
- Log archiving is disabled.
- Real-time statistics are disabled.