DB2 - Problem description
Problem IC76561 | Status: Closed |
ON DPF SQL1042C ERROR IS RETURNED FOR ANY TRANSACTION RUNNING AFTER DIAGPATH HAS BEEN RENAMED AND BEFORE IT GETS RE-CREATED. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
All transactions running against a multipartitioned database get SQL1042C error after DIAGPATH is renamed and before it gets re-created. EX: 1. Update DIAGPATH dbm cfg parameter: db2 -v update dbm cfg using diagpath '"/home/db2inst1/current $h$n"' 2. Restart the instance for the changes to be in effect: db2stop force db2start 3. List the paths that were created under /home/db2inst1/current to make sure they were updated: ls /home/anik/current/HOST_p6db2serv NODE0000 NODE0001 NODE0002 4. Ran a simple select to make sure no sql1042c error is returned: db2 "select count(*) from employee" 1 ----------- 42 1 record(s) selected. 5. Then renamed the "current" directory: mv current current_old 6.Right after this, i ran the same select above and got -1042 error: SQL1042C An unexpected system error occurred. With this APAR fix, SQL1042C will not be returned even if the diagpath is not available, thus it will not cause the running transactions to fail. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users on DB2 v97 fp4 * **************************************************************** * PROBLEM DESCRIPTION: * * ON DPF SQL1042C ERROR IS RETURNED FOR ANY TRANSACTION * * RUNNING AFTER DIAGPATH HAS BEEN RENAMED AND BEFORE IT GETS * * RE-CREATED. * **************************************************************** * RECOMMENDATION: * * Apply DB2 v97 FP5 * **************************************************************** | |
Local Fix: | |
No Local Fix | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First Fixed in DB2 v97 fp5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.05.2011 19.12.2011 19.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |