DB2 FOR LUW / DB2FORLUW / 970 - DB2

When you run the db2support command on Windows, the 
db2support.log file in the zip file that the db2support command 
generates might incorrectly include a sequence of messages which 
includes "RC=-2029060087" as if an error had occurred getting 
the db2dasdiag.log file. 
 
The sequence of messages is like this, where "C:\Program 
Files\IBM\DB2\DB2COPY1\DB2DAS00\dump"' is the location of the 
db2dasdiag.log file: 
 
        XXXX-XX-XX-XX.XX.XX.XXXXXX [db2supdbinfo.C:XXXX] 
RC=-2029060087 Attempting to collect files from '"C:\Program 
Files\IBM\DB2\DB2COPY1\DB2DAS00\dump"' 
 
        XXXX-XX-XX-XX.XX.XX.XXXXXX [db2supdbinfo.C:XXXX] -> 
db2dasdiag.log 
 
Such a sequence of messages might appear even though no error 
has occurred and the db2dasdiag.log has really been correctly 
included in the zip file that the db2support command has 
generated.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users of DB2 for Linux, UNIX and Windows                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* .                                                            * 
****************************************************************

Check that the zip file that the db2support command has 
generated really does contain a db2dasdiag.log file. If it does 
then you can ignore those messages in db2support.log.

Problem was first fixed in Version 9.7 Fix Pack 4. 
At a minimum, this fix should be applied on the machine on 
 
which you run the db2support command.

Check that the zip file that the db2support command has 
generated really does contain a db2dasdiag.log file. If it does 
then you can ignore those messages in db2support.log.

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

31.08.2010
25.05.2011
25.05.2011

9.7.FP4