IBM MAINFRAME HELP & SUPPORT FORUMS

picus_mf · Joined: 09 Jun 2006 Posts: 18

Hi,
One of the tables in our database has been effected with wrong updation. Our intention was to update some 5 records at once, but 24000 records out of 1 million records are updated due to lack of specific condition.

Is there any way other approaching DBA where we can roll back the update and bring back the records to its previous status?

Thanks in Advance.
Praveen.

enrico-sorichetti · Joined: 14 Mar 2007 Posts: 3032 Location: italy

Quote: Is there any way other approaching DBA where we can roll back the update and bring back the records to its previous status?

once a program has properly terminated, the changes have been committed and no roll backs are possible

You just incurred in a programming/analysis error and as such must be fixed by other means than standared Data Base utilities

... if there is an image copy available of the table before the_wrong_program_execution
You might ask support to reload it and operations to rerun all the jobs affecting the table in question
but You need to carefully coordinate everything

dick scherrer · Joined: 23 Nov 2006 Posts: 8589 Location: 221 B Baker St

Hello,

Problems with databases should be brought to the attention of the database support people - immediately.

The longer the delay the more invalid "answers" the system can provide.

It is one thing to make a mistake. It is a far worse thing to try to hide it.

picus_mf · Joined: 09 Jun 2006 Posts: 18

Thanks for the replies.

The updation happened was on test data base. We wanted to know if there is any process that can be done to roll back the updations.
Any way...next course of action is taken.

Thanks once again.

dick scherrer · Joined: 23 Nov 2006 Posts: 8589 Location: 221 B Baker St

Hello,

Quote: We wanted to know if there is any process that can be done to roll back the updations. There should be, but they will be controlled by the dba(s).

Craq Giegerich · Joined: 19 May 2007 Posts: 989 Location: Virginia, USA

You can do a recover to a point in time if there have been no updates since your mass updates but if there are foreign keys you will have to check these and if your mass update caused any cascading changes you would have to fix those also. It is best to ask the DBA for help.