2022-08 sending issues

outstanding tasks

• check backup logs to see if those files can be sent
• send as possible
• process phi csvs
• set file location back to RS
• roll all newest versions (after I hear from Pagasa that she has copied legacy)

Background

Wednesday 2022-08-10 Tina did some updates to Centralized_data.mdb and rolled them out, but the change was accidentally done on an outdated file. That file was returned to the server and collectors started sending to it. Because Pagasa was on vacation, it wasn't noticed until Monday Aug 15 that there were problems with the data.

We reverted to most recent prior backed up centralized_data file from 2022-8-7-10.57 and re-applied the updates.

To bring the file up to current we then attempted to re-send the data in the same sequence as it was sent, based on the pre-sending backup files. Of 14 sends that happened in this period, 6 didn't have backups with time stamps immediately prior to sending. These may have been backed up immediately prior to sending since those stamps are based on last closing time rather than time copied, so would be stamped like that if ccmdb had not been opened since end of last shift.

ADD TABLE OF RE-SEND RECORDS

ccmdb_data.mdb files that needed re-sending are at \\ad.wrha.mb.ca\wrha\REGION\SHARED\ICU_DATA_COLLECTION\data\2022-08-15 resends but will be deleted when this is settled.

Coincidentally, getting collectors to send to an older version of centralized than expected exposed a bug where records with recordstatus = "deleted" could be sent. This was addressed in CCMDB.accdb Change Log 2022#2022-08-15