DB2 - Problem description
Problem IC85962 | Status: Closed |
BACKUP COMMAND USING DEDUP_DEVICE CAN HANG IF THERE ARE IDLE DB2MED EDUS DURING THE COMPLETION OF THE BACKUP. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Users can use 'db2pd -utilities' output to check if CompletedWork is almost equal to the TotalWork(in bytes). If it is off, then there is a high possibility of hitting the hang situation. Here is a sample scenario where it shows the CompletedWork is off by 12K. Utilities: Address ID Type State Invoker Priority StartTime DBName NumPhases CurPhase Description 0x078000000324EB80 40006 BACKUP 0 0 0 Thu Aug 2 10:51:48 SAMPLE 1 1 online tablespace USERSPACE1... Progress: Address ID PhaseNum CompletedWork TotalWork StartTime Description 0x078000000324F508 40006 1 47957591 bytes 47970415 bytes Thu Aug 2 10:51:48 n/a Note: If the CompletedWork is almost equal to TotalWork and remains that way for an extended time, then this APAR has been encountered. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users running backup with dedup_device option. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 7. * **************************************************************** | |
Local Fix: | |
Remove 'dedup_device' option from the Backup command. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 9.7 Fix Pack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.08.2012 20.10.2012 20.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP7 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.7 |