DB2 FOR LUW / DB2FORLUW / 950 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using DB2 v95 fp8 and earlier                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ON DPF SQL1042C ERROR IS RETURNED FOR ANY TRANSACTION        * 
* RUNNING AFTER DIAGPATH HAS BEEN RENAMED AND BEFORE IT GETS   * 
* RE-CREATED.                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v95 FP9                                       * 
****************************************************************

No Local Fix

DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
 

First Fixed in DB2 v95 FP9

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC76561 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

02.05.2011
13.03.2012
13.03.2012

9.5.FP9