Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT03803 Status: Closed

ADDING DATABASE MOUNTS WITH DB2CLUSTER COMMAND(db2cluster -cm -add
-database_mounts) FAILS WITH SQL0969N ERROR

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
This only occurs if the path is greater than 99 characters long. 
The database path is associated with a database and should be 
present in the sysibmadm.DBPATHS. 
 
Following error will be reported in the db2diag.log when the 
db2cluster command fails: 
 
    2014-08-15-02.13.32.585149+060 E21937E458            LEVEL: 
Error 
    PID     : 7309                 TID : 140331088971552 PROC : 
db2cluster 
    INSTANCE: pdiaq401             NODE : 000            DB   : 
DQ401A01 
    APPID   : *N0.pdiaq401.140815011333 
    HOSTNAME: anhbxpdt401-03.landg.net 
    FUNCTION: DB2 UDB, high avail services, 
SqlhaUIAppContext::sqlhaUIGetDBMountPaths, probe:1000 
    RETCODE : ECF=0x9000052F=-1879046865=ECF_SQLHA_INTERNAL 
              Internal SQLHA Error 
 
From the trace, following information can be seen: 
 
593973 exit DB2 UDB call level interface CLI_sqlFetch fnc 
(2.3.42.56.0) 
pid 7309 tid 140331088971552 cpid 308 node 0 
rc = 1 
 
594374    data DB2 UDB high avail services 
SqlhaUIAppContext::sqlhaUIGetDBMountPaths fnc 
(3.3.115.521.0.1000) 
    pid 7309 tid 140331088971552 cpid 308 node 0 probe 1000 
    bytes 467 
    Data1    (PD_TYPE_DIAG_LOG_REC,459) Diagnostic log record:
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5 or higher.            * 
****************************************************************
Local Fix:
Solution
First fixed in DB2 Version 10.5 Fix Pack 5.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
15.08.2014
13.03.2015
13.03.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.5 FixList