This firm uses System Level Backup (SLB), but the DBA group, I kid you not, did not know this little factoid (they had alternate facts to works with), and so when the request to restore tables x, y and z to a specific Point in Time (PiT) arrived, they simply created the required RECOVER control cards and, after checking that the tables, indexes and tablespaces were not being used, submitted the RECOVER jobs. This is bad news… Backup system to the Rescue?
Icopy in db2 zos software#
The developers pushed some software to production and then found out, five hours later, that there was a logical error and it was doing really bad updates and deletes in a bunch of tables that it should *not* have done.
This time it was a request to recover some tables to a specific point in time that started the ball rolling… Staged too soon? Bad updates and deletes This month is another war story from the trenches of Production DBAs fighting the fight for 24×7 Shops around the world… Please excuse the heading, I simply could not resist…
War story : Why is Db2 z/OS IMAGE COPY very useful in the current Db2 z/OS world?
0 kommentar(er)
