DB2 FOR LUW / DB2FORLUW / A50 - DB2

While migrating a db2 v9.8 Purescale env. to db2 v10.5 server 
environment, db2start can fail with SQL1698N error as follows 
after successfully installing the db2 v10.5 code and upgrading 
the db2 instance to v10.5.x. 
 
$db2start 
ADM12026W  The DB2 server has detected that a valid license for 
the 
product "DB2 Enterprise Server Edition" has not been registered. 
11/21/2013 08:56:32     1   0   SQL1698N  The START DATABASE 
MANAGER 
command failed on a DB2 pureScale instance where fix pack 
updates are 
being applied or have been applied. Reason code: "7". 
11/21/2013 08:56:32     2   0   SQL1698N  The START DATABASE 
MANAGER 
command failed on a DB2 pureScale instance where fix pack 
updates are 
being applied or have been applied. Reason code: "7". 
<> 
SQL6032W  Start command processing was attempted on "6" node(s). 
"1" 
node(s) were successfully started.  "0" node(s) were already 
started. 
"5" node(s) could not be started. 
 
This will occur in a setup where the same physical server has 
multiple logical members as follows. 
 
$cat db2nodes.cfg 
DB2 pureScale member configuration 
      Number of nodes in db2nodes.cfg is: 6 
      Current node number is: 0 
 
      Node information from the db2nodes.cfg file: 
      0 xxxx.xxxxx.xxxx. 0 xxxx-ib0.xxxx.xxxx-ibo. - MEMBER 
      1 xxxx.xxxxx.xxxx  1 xxxx-ib0.xxxxx.xxxx-ib0. - MEMBER 
      2 xxxx.xxxxx.xxxx  2 xxxx-ib0.xxxxx.xxxx - MEMBER 
 
where all the members shared the same physical host. 
 
db2diag.log will have the following entry: 
2013-09-13-11.26.48.961521-240 I10737A1236          LEVEL: Error 
 
PID     : 27394054             TID : 1              PROC : 
db2star2 
INSTANCE: xxxxx               NODE : 001 
HOSTNAME: xxxxxxxx 
EDUID   : 1 
FUNCTION: DB2 UDB, base sys utilities, sqleRollupCanMemberStart, 
 
probe:339 
MESSAGE : ZRC=0xFFFFF95E=-1698 
          SQL1698N  The START DATABASE MANAGER command failed on 
a DB2 
pureScale instance where fix pack updates are being applied or 
have 
          been applied. Reason code: "". 
 
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes 
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1698   sqlerrml: 1 
 
 sqlerrmc: 7 
 sqlerrp : SQL10051 
 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: 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are 
resolved to the nearest symbol) 
  [0] 0x09000000183870EC sqleRollupCanMemberStart + 0x36E8 
  [1] 0x0900000018364848 sqleRollupCanMemberStart + 0x218 
  [2] 0x000000010000B804 DB2StartMain + 0xADE4 
  [3] 0x00000001000002F8 __start + 0x70

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS of DB2 LUW V10.5                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V10.5 FP3 or Later                        * 
****************************************************************

Obtain the service password from support team and then 
as user root execute the following: 
export DB2SVCPW='service password' 
db2iupdt  -recover_ru_metadata <inst name>

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
 

First Fixed in DB2 LUW V10.5 FP3

not known / see Local fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

25.11.2013
22.12.2014
22.12.2014