DB2 - Problem description
Problem IT36207 | Status: Closed |
TARGET DATABASE CAN FAIL STARTUP AFTER RESTORE INTO WHEN ACCESSING SOURCE DATABASE'S LOG FILES/TAG | |
product: | |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 | |
Problem description: | |
After a redirected restore, the target database will fail startup if it tries to locate the database in a different database's path. Example: - restore A into B - update db cfg for B USING NEWLOGPATH - rollforward B In this case, the rollforward fails to connect to database with -1042. The reason is that the SQLLPATH.TAG file in A's log path was removed when the rollforward was attempted. This tag file may or may not be required for a successful restore/rollforward. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.5 Fix Pack 6 * **************************************************************** | |
Local Fix: | |
This problem can be avoided by specifying the NEWLOGPATH option as part of the RESTORE command. For example: - restore A into B NEWLOGPATH - rollforward B | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 11.5 Fix Pack 6 * **************************************************************** | |
Comment | |
First fixed in DB2 11.5 Fix Pack 6 | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 12.03.2021 08.07.2021 08.07.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |