February 22, 2024\n19:00\tRun pfmdb ckpdb -v #x #m12 pfmdb on ingdb1a\nFebruary 22, 2024\n01:00\tRunning ckpdb -v #x #m12 pfmdb completed\n07:00\tThe server ingdb1a was down because of hardware failure (memory)\n09:30\tRerouted to ingdb2a\n\tThe database was down because DBLOC1 has no data. CKPT2 was mounted instead of DBLOC1\n\tAttempted to run rollforward but failed because of I/O error due to file system incompatibility (DBLOC1 and CKPT2 has different file system type)\n\tAttempted to run the rollforward for the 2nd time but failed\n14:30\tRerouted again to ingdb1a\n14:45\tRun rollforwarddb pfmdb +c +j #x #c2158 #m12 on ingdb1a\n17:00\tFinished running rollforwarddb pfmdb +c +j #x #c2158 #m12 with some inconsistency.\n\n?sql -A10? was run against pfmdb to patch inconsistency\n18:45\tUsermod on affected tables:\n-pf_ledger_21_25\n-pf_ledger_79_00\n-pf_ledger_01_05\n-pf_ledger_06_10\n-pf_ledger_11_15\n- pf_ledger_16_20\nFebruary 23, 2024\n05:45\tHDMF reported to DSI that there?s discrepancy on the data between ingdb1a and data_warehouse.\n12:38\tRun rollforwarddb pfmdb -j -e #x #c2158 #m12 on ingdb1a\n\nAs of writing, there is on-going replaying and/or testing of data.