|
Problem IC97122
|
Status: Closed |
DB2 CLIENT PRINTS -1013 IN DB2DIAG.LOG WHEN USING DB2DSDRIVER.CFG AND DB NOT EXIST IN DB CATALOG. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
DB2 Client prints -1013 in the db2diag.log like as below if the
specified database cannot be found in the database catalog
(sqldbdir) even though applications can connect to the database
by using db2dsdriver.cfg.
2013-10-17-09.36.24.431000+540 I2512H721 LEVEL:
Warning
PID : 892360 TID : 1 PROC : db2bp
INSTANCE: db2inst1 NODE : 000
HOSTNAME: db2debug
FUNCTION: DB2 UDB, Connection Manager, sqleUCgetDirInfo,
probe:1012
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -1013 sqlerrml: 6
sqlerrmc: SAMPLE
sqlerrp : SQLEUCCM
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
This APAR will remove the warning after directory lookup check
in client layer. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users who use db2dsdriver.cfg. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V10.5 FixPack 4 or later. *
**************************************************************** |
| Local Fix: |
This error message can eliminate by ether of the following ways.
a) Catalog the database in the system database directory.
b) Remove database catalog file (sqldbdir). |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
This problem was first fixed in DB2 V10.5 FixPack 4. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 23.10.2013
22.09.2014
22.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
