Recovering from application errors
You can recover from a problem in which an application program placed a logically incorrect value in a table.
Symptoms
Unexpected data is returned from an SQL SELECT statement, even though the SQLCODE that is associated with the statement is 0.Causes
An SQLCODE of 0 indicates that Db2 and SQL did not cause the problem, so the cause of the incorrect data in the table is the application.Resolving the problem
System programmer response: You might be able to use the Db2 RECOVER
utility with the TOLOGPOINT option to restore the database to a point
before the error occurred. However, in many circumstances you must
manually back out the changes that were introduced by the application.
Among those circumstances are:
- Other applications changed the database after the error occurred. If you recover the table spaces that were modified by the bad application, all subsequent changes that were made by the other applications are lost.
- Db2 checkpoints were taken after the error occurred. In this case, you can use RECOVER TOLOGPOINT to restore the data up to the last checkpoint before the error occurred. However, all subsequent changes to the database are lost.