DB2 - Problem description
Problem IT23106 | Status: Closed |
PURESCALE DATABASE MIGHT BE DEACTIVATED AFTER A BACKUP/RESTORE | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
If a database is implicitly activated by an user connection, then when an online backup or restore is the last application, the database will be deactivated at the end of the backup or restore. This is not expected in a DB2 pureScale environment, because in a DB2 pureScale environment, a database that has been explicitly activated through the ACTIVATE DATABASE command or, implicitly activated by a user connection, can only be deactivated through a DEACTIVATE DATABASE command. After this fix, the pureScale database will remain in active state after the backup or restore even it is last application. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * The customer running pureScale. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * This APAR won't be fixed due to potential impact to * * customers who already depend on the old/incorrect behavior. * **************************************************************** | |
Local Fix: | |
Always activate a database explicitly. | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT23080 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.11.2017 23.02.2020 23.02.2020 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |