DB2 - Problem description
Problem IC70394 | Status: Closed |
restore database command PANICS DB2 if SGF file does not exist or is corrupted in the existing database. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
DB2 panics while restoring the database from a backup image if SQLSGF file was missing or corrupted in the existing database. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * NONE * **************************************************************** * PROBLEM DESCRIPTION: * * DB2 panics while restoring the database from a backup * * imageif SQLSGF file was missing or corrupted in the * * existingdatabase. * **************************************************************** * RECOMMENDATION: * * Workaround for this problem is to either:a) Drop the * * database before restoring it from the backupimage.b) * * Completely wipe out the database from the filesystem. * **************************************************************** | |
Local Fix: | |
Workaround for this problem is to either: a) Drop the database before restoring it from the backup image. b) Completely wipe out the database from the filesystem. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
This defect is fixed in DB2 version db2v97_fp3 DB2 will not panic while restoring the database from a backup image if SQLSGF file was missing or corrupted in the existing database. In this case SQLSGF file will be restored from the backup image. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.08.2010 07.10.2010 07.10.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7._FP3 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.3 | |
9.7.0.3 |