Problem Summary: Troubleshoot missing data
There can be multiple reasons why data may be missed. One of the reasons may be a configuration error. One might be by moving the capture position forward to quickly overcome some error but failing to recover the skipped data.
We need the client to help us
- identify a missed change,
- determine when that change took place on the source database
- establish whether that change was recorded in the source database transaction log.
Once we've ascertained those facts, HVR can investigate as to why that change was not captured or integrated.
1. Perform an online refresh of the out-of-sync table to reconcile the source and target to establish a baseline.
2. Add the parameter Integrate/JournalRouterFilesfor the integration location group and regenerate the integrate job.
This will save all processed router files to $HVR_CONFIG/jnl/<hub>/<chn>/YYYYMMDD.
These router files will provide us with a history of what HVR captured and submitted for integration. Additionally, you should do some regular housekeeping on the hub. For example, schedule the hvrmaint utility to manage disk utilization with option '–journal_keep_days=n' to periodically purge the router files after 'n' days, ie 7.
See additional information on the command hvrmaint at https://www.hvr-software.com/docs/commands/hvrmaint
3. It is very important to schedule a frequent row-by-row and verbose HVR Compare so any mismatches are detected as soon as possible.
If you anticipate that the compare will produce more output than the current hub can handle, move the channel to a less busy hub. It is important to note that the compare will almost always report differences, but that is typically due to 'in-flight data' – changes that have been committed at the source but have yet to be replicated to the target. Instead, it is the difference that persists across multiple runs that we need to consider ourselves with.
4. Once you've identified a mismatch, use column 'update_date' or equivalent to determine when the row was last written at the source.
5. Liaise with the source DBA and secure the DBMS transaction log(s) for the transaction that made the missed change. We will then use a transaction log viewer to verify that the change, as well as the entire transaction containing that change is indeed present in the transaction log(s). After all, it is possible that the application (temporarily) disables transaction logging, preventing HVR from capturing the changes.
Once you've identified a mismatch, use column 'update_date' or equivalent to determine when the row was last written at the source.
6. Attach/Upload the transaction logs, router files and .enroll* files to HVR.
In conclusion, please work with your DBA to ensure that the transaction logs remain available for some time. For example, should we identify a missed change that took place a week ago, we will need the transaction log that was active at that time.
Advice will be provided based on the cause of the discrepancy. Once the data has been collected, please upload the data to the ticket. This may be requested multiple times to identify the issue.
Once we have enough information, it may be requested by support to schedule a refresh in the short term but please wait for that action to be specifically requested else valuable information needed to troubleshoot may be lost.