DB2 - Problem description
| Problem IT08604 | Status: Closed |
DB2SUPPORT WITH DB OPTION PRODUCES SQL1587N, SQL1469N IN LOG, AND PRINTS ERROR IN DB2DIAG.LOG IF IT RUNS AGAINST CF ONLY HOST. | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
The db2support.log prints many SQL1587N, SQL1469N errors, and
db2diag.log shows an error produced by clpbp_exe_sqluhops,
probe:26248 after running db2support tool with database option
against CF only hosts like as below:
db2support <path> -runonhost=<CF only host> -alldbs -purescale
-s -f
db2support.log:
START: START: Database configuration for SAMPLE [Get db cfg
for SAMPLE ]
RC=-1587 Get db cfg for SAMPLE
STOP: Database configuration for SAMPLE
START: START: Database configuration for TESTDB [Get db cfg
for TESTDB ]
RC=-1469 Get db cfg for TESTDB
STOP: Database configuration for TESTDB
db2diag.log: (this error is produced by failure on LIST HISTORY
command.)
2015-04-12-10.37.56.612459+540 E14983A691 LEVEL: Error
PID : 20840450 TID : 1 PROC : db2bp
INSTANCE: db2inst1 NODE : 128
HOSTNAME: host01cfpri
EDUID : 1
FUNCTION: DB2 UDB, command line process, clpbp_exe_sqluhops,
probe:26248
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: 0 sqlerrml: 0
sqlerrmc:
sqlerrp : SQL10053
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000080
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: 00000 | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who run db2support in a CF only host. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V10.1 FixPack 5 or later. * **************************************************************** | |
| Local Fix: | |
Please ignore the error messages because those are harmless. | |
| Solution | |
This problem was first fixed in DB2 V10.1 FixPack 5. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.04.2015 16.07.2015 16.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|