When connecting to a database on a single member DPF instance,
that is a DPF instance with a single line in the db2nodes.cfg,
the connection is successful but the SQLCA's SQLERRM token
number 8 (member number) and token number 10 (number of members)
are set to zero rather than the correct values.
Similarly, when attaching to a single member DPF instance, the
attach is successful but the SQLCA's SQLERRM token number 8
(member number) and token number 9 (number of members) are set
to zero rather than the correct values.
The result of this is that if db2ckupgrade is run against a
single member DPF instance, the error message below can occur:
Version of DB2CKUPGRADE being run: VERSION "10.5"
Database: "DB1"
DBT5509N The db2ckupgrade utility failed because it could not
connect to the database. Database: "DB1".
DBT5529N The db2ckupgrade utility did not complete
successfully. The database cannot be upgraded. The output log
file is named "/tmp/file0123".
The db2diag.log can show messages like below:
2014-10-10-16.19.34.778853-240 I20122A545 LEVEL: Error
PID : 10420330 TID : 1 PROC :
db2ckupgrade64_exe
INSTANCE: db2inst1 NODE : 433
HOSTNAME: server123
EDUID : 1
FUNCTION: <0>, <0>, <0>, probe:1363
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : sqlcabc: 0 sqlcode: -1032 sqlerrml: 0
sqlerrmc:
sqlerrp :
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1)
...
2014-10-10-16.19.34.780228-240 I21270A297 LEVEL:
Warning
PID : 10420330 TID : 1 PROC :
db2ckupgrade64_exe
INSTANCE: db2inst1 NODE : 433
HOSTNAME: server123
EDUID : 1
DATA #1 : <preformatted>
DB2CKUPGRADE: End: sqlemCkupgSingleDB with rc = 3 |
