_______________________________________________________________
Document Information
| Document Number: | 502344686 |
| Functional Area: | DB2 for i5/OS |
| Subfunctional Area: | Journal and Commitment Control |
| Sub-Subfunctional Area: | General |
| OS/400 Release: | V5R3M0; V5R3M5; V5R4M0; V5R4M5 |
| Product: | I5/OS (5761SS1DB) OS/400 DATABASE (5722SS1DB) |
| Product Release: | N/A |
_______________________________________________________________
Document Title
Ending A Rollback - V530 and Later Releases
Document Description
There are two important things to understand about ending a rollback before you end it.
First, ending a rollback will "compromise the integrity of your database." But what does this really mean? It will not leave any files "damaged" or unusable; however, you will not know exactly what data is in your file. Some of the transaction may still be in the data, some may not be. If the transaction you want to end is over only one file, then only that one file will be affected. You may want to restore from the latest backup, so you know how current the file is. If this is test data, or if you plan to restore a backup version of the file, it is safe for you to do the rollback. The warning message regarding this is in Step 3 below.
Second, even after the rollback itself has been cancelled, there is still a step of releasing the record locks that can take a considerable amount of time. It may be a few minutes, or a couples hours at most. It will probably not take half a day, or day(s), or anywhere near as long as the rollback would have run. The releasing lock stage is a subset of the rollback process. We can estimate the amount of time to release locks by viewing the commit block in STRSST. If you cannot wait for the locks to release, you may IPL the system to release them. This will be a normal IPL as long as the rollback has been ended. Refer to Step 4 below.
You are now sufficiently informed to End that Rollback.
1. If you have not done this already, issue ENDJOB *IMMED. This will cause the job to go into rollback.
2. Issue the WRKCMTDFN command, and enter the fully qualified job name.
3. Press F23 to see more options. You will see END ROLLBACK option 20.
If you do not see END ROLLBACK, it is because you do not have explicit QSECOFR authority. You will need this authority. It does not count if your group profile has QSECOFR authority.
Take option 20 by the commitment definition to end the rollback. You will receive a warning message asking 'Are you sure?'. Answer 'Yes'. This is asking you to consider the first item in this document, data integrity.
4. This will end the rollback; however, there is also some time to release the locks on the file.
5. After the locks are released, it is your decision as to whether you want to RST this file from backup, or use a program or another SQL to get the data as desired.
Please discuss with your programmer why this commitment control job took so long and why it had to be cancelled. Consider breaking the SQL up into smaller chunks, with more COMMITs in between. For example, use WHERE RRN(MYFILE) BETWEEN N and Z, incrementing the variables.
__________________________________________________________________
PMR Number: |  | |
Related APARs: | | |
Related Public Documents: | | |
- IBM disclaims all warranties, whether express or implied, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. By furnishing this document, IBM grants no licenses to any related patents or copyrights. Copyright © 1996,1997,1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 IBM Corporation. Any trademarks and product or brand names referenced in this document are the property of their respective owners. Consult the Terms of use link for trademark information.