Our online backup failed again and again without any clue.
The error message is:
SQL0911N The current transaction has been rolled back because of a deadlock
or timeout. Reason code "68". SQLSTATE=40001
SQL0843N The server name does not specify an existing connection.
I checked, but there was no deadlock, no lock-wait to force application.
Is there any clues cause online backup corrupted. Disk space is ok for backup.
Could you guide me how to find the timestamp for incremental backup?
If my full ONLINE Backup is failed. How much database I can restore.
There is no base line for incremental backup. How can I still take the backup.
After making sure no utilities are running(you can kill them) run the backup; you have to look in the diaglog as to why db2 backup is failing. If it fails, tell us what command you used and what the diaglog says at that time.
The very first step in the online backup is to take a backup of the catalog tablespace
and this copy of the catalog is required to be a consistent one, For this DB2 takes table level share locks (not sure if it is S locks or some internal lock simialr to S)
When a runstats, load or reorg is running, an update lock is taken the rows of catalog tables that reference the user table on which the utilities are running.
As you can see, the above two are conflicting locks.
Therefore, if a backup starts when utilities are running, the backup waits for locktimeout seconds to obtain locks on the catalog. If it is unable to, then just like any other application, the backup fails.
Remember, that if a backup has finished copying catalog tablespace, then utilites can start on tables and both of them can contine in paralllel. In this case, just like for any other table, chnages to the catalog tables is 'tracked' using the transaction logs.
Hope this answers your question
Visit the new-look IDUG Website , register to gain access to the excellent content.