Problem with sent vs complete records: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) mNo edit summary |
TOstryzniuk (talk | contribs) mNo edit summary |
||
| Line 6: | Line 6: | ||
== Log == | == Log == | ||
2018-Aug-01 - GRA_S3-14156, but the Record Status is Complete. Reset Record to Incomplete then Resent and problem fixed. Collector who sent, states no noted problems during sending. | 2018-Aug-01 - GRA_S3-14156, but the Record Status is Complete. Only one file in batch of ? affected. | ||
*Reset Record to Incomplete then Resent and problem fixed. | |||
*Collector who sent, states no noted problems during sending. | |||
2018-Feb-23 - STB_MICU sent, but the Record Status is Complete. | 2018-Feb-23 - STB_MICU sent, but the Record Status is Complete. | ||
2018-Mar-07 - HSC_B3D5 sent, but the Record Status is Complete. | 2018-Mar-07 - HSC_B3D5 sent, but the Record Status is Complete. | ||
Revision as of 17:10, 1 August 2018
Usually a record with the RecordStatus field set to "complete" turns to "sent" in both CCMDB_data.mdb and Centralized_data.mdb when sending is complete. Occasionally, and for unknown reasons, the field remains "complete" in centralized data.mdb.
- When this happens, please find out and document the following:
- ask the collector if there was anything unusual during sending.
- did this happen for some or all records during this send? If some, please include D_IDs in log below, if all, please include sent_dt_tm
Log
2018-Aug-01 - GRA_S3-14156, but the Record Status is Complete. Only one file in batch of ? affected.
- Reset Record to Incomplete then Resent and problem fixed.
- Collector who sent, states no noted problems during sending.
2018-Feb-23 - STB_MICU sent, but the Record Status is Complete.
2018-Mar-07 - HSC_B3D5 sent, but the Record Status is Complete.