IBM Support

DB2 pureScale HADR ! OFFLINE fixpack upgrade by rolling method.

Technical Blog Post


Abstract

DB2 pureScale HADR ! OFFLINE fixpack upgrade by rolling method.

Body

As an experienced DB2 DBA, you are familiar with HADR and applying DB2 fixpack by rolling maintenance.
Now pureScale with HADR clusters system. What are you going to do ?
 
From DBA’s perspective, it’s always better to have enough service down maintenance time window.
But if your critical business does not permit this way for 24/7 operation requirement, we will have to implement appropriate steps without service interruption.
So I’m writing this blog assuming you have to complete the mission without taking down the business application.
 
First recommended way is online Fix pack update.
 
 
With this way, you don’t even need to takeover the HADR role.
That is simply doing online fixpack on HADR standby cluster, then on primary side cluster.
( As you know, to maintain HADR status, Standby DB level should be same or higher than Primary always.) 
 
But if you have to use OFFLINE Fix pack update with any reason, we should combine steps using the following two links.
 
 
In overall, the steps are like below.
 
1. Deactivate standby Database.
2. Stop the standby cluster
3. Applying new Fixpack on standby
4. Bring up instance and database.
5. Reconnect to the HADR
6. HADR takeover
7. Stop the original primary(current standby) cluster.
8. Applying new Fixpack on original primary(current standby).
9. Bring up instance and database.
10. HADR Takeover back to original primary.

On this blog, I will share the output from my test systems.
At least, you can have how the steps and outputs look like.
 
My environment outlook is like below.
 
<Environment>
Current level : DB2 version 11.1 Mod 2 Fixpack 2
Target level  : DB2 version 11.1 Mod 2 FixPack 2 iFix001
 
This is not the best example because ONLINE fixpack upgrade is possible in this case.
But to show OFFLINE fixpack upgrade, the steps should be same for both V10.5 and V11.1.
On each command, you can see if that is executed by ‘root’ user or DB2 instance user.
 
HADR Primary pureScale cluster hostnames
lpar102ps1 - member 0 / CF 129
lpar103ps2 - member 1 / CF 128
 
HADR Standby pureScale cluster hostnames
lpar104ps3- member 0 / CF 129  <== Replaying standby member.
lpar105ps4- member 1 / CF 128
 
For ‘db2pd’ outputs on this blog, I grepped only interested parts of ‘db2pd -hadr -db <dbname>’.
<Checking current information before start>
 
db2level : 
 
db2inst1@lpar102ps1:/home/db2inst1/junsulee>db2level
DB21085I  This instance or install (instance name, where applicable:
"db2inst1") uses "64" bits and DB2 code release "SQL11012" with level
identifier "0203010F".
Informational tokens are "DB2 v11.1.2.2", "s1706091900", "DYN1701310100AIX",
and Fix Pack "2".
Product is installed at "/opt/IBM/db2/V11.1".
 
 
Primary :
 
root@lpar102ps1:/junsulee>su - db2inst1
db2inst1@lpar102ps1:/home/db2inst1>db2instance -list
ID        TYPE             STATE                HOME_HOST               CURRENT_HOST            ALERT   PARTITION_NUMBER        LOGICAL_PORT    NETNAME
--        ----             -----                ---------               ------------            -----   ----------------        ------------    -------
0       MEMBER           STARTED                lpar102ps1                lpar102ps1               NO                  0                   0    lpar102ps1-en1-2
1       MEMBER           STARTED                lpar103ps2                lpar103ps2               NO                  0                   0    lpar103ps2-en1-1
128     CF               PRIMARY                lpar103ps2                lpar103ps2               NO                  -                   0    lpar103ps2-en1-2
129     CF                  PEER                lpar102ps1                lpar102ps1               NO                  -                   0    lpar102ps1-en1-2
 
HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT
--------                   -----                ----------------        -----
lpar103ps2                ACTIVE                              NO           NO
lpar102ps1                ACTIVE                              NO           NO
 
db2pd on member 0 :
 
db2inst1@lpar102ps1:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = PRIMARY
                        LOG_STREAM_ID = 0
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar102ps1
                       PRIMARY_MEMBER = 0
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/18/2018 22:38:28.737773 (1516275508)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
 
db2pd on member 1
db2inst1@lpar103ps2:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = PRIMARY
                        LOG_STREAM_ID = 1
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar103ps2
                       PRIMARY_MEMBER = 1
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/18/2018 22:42:20.829331 (1516275740)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0

 
Standby :
 
db2inst1@lpar104ps3:/home/db2inst1>db2instance -list
ID        TYPE             STATE                HOME_HOST               CURRENT_HOST            ALERT   PARTITION_NUMBER        LOGICAL_PORT    NETNAME
--        ----             -----                ---------               ------------            -----   ----------------        ------------    -------
0       MEMBER           STARTED                lpar104ps3                lpar104ps3               NO                  0                   0    lpar104ps3-en2-1
1       MEMBER           STARTED                lpar105ps4                lpar105ps4               NO                  0                   0    lpar105ps4-en2-1
128     CF               PRIMARY                lpar105ps4                lpar105ps4               NO                  -                   0    lpar105ps4-en2-2
129     CF                  PEER                lpar104ps3                lpar104ps3               NO                  -                   0    lpar104ps3-en2-2
 
HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT
--------                   -----                ----------------        -----
lpar105ps4                ACTIVE                              NO           NO
lpar104ps3                ACTIVE                              NO           NO
 
db2pd on replay member 0.
 
db2inst1@lpar104ps3:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = STANDBY
                        LOG_STREAM_ID = 0
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar102ps1
                       PRIMARY_MEMBER = 0
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/18/2018 22:28:30.370872 (1516274910)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
                            HADR_ROLE = STANDBY
                        LOG_STREAM_ID = 1
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar103ps2
                       PRIMARY_MEMBER = 1
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/18/2018 22:32:09.812269 (1516275129)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
 

1.Deactivate standby Database.
 
db2inst1@lpar104ps3:/home/db2inst1/junsulee>db2 deactivate db JSHADRDB
DB20000I  The DEACTIVATE DATABASE command completed successfully.
 
2. Stop the standby cluster
 
( installFixPack command will do this if this is not stopped. 
  But I prefer to stop manually. It’s up to you. )
 
db2inst1@lpar104ps3:/home/db2inst1/junsulee>db2stop
01/19/2018 12:18:33     0   0   SQL1064N  DB2STOP processing was successful.
01/19/2018 12:18:33     1   0   SQL1064N  DB2STOP processing was successful.
SQL1064N  DB2STOP processing was successful.
 
db2inst1@lpar104ps3:/home/db2inst1>db2stop instance on lpar104ps3
SQL1064N  DB2STOP processing was successful.
db2inst1@lpar104ps3:/home/db2inst1>db2stop instance on lpar105ps4
SQL1064N  DB2STOP processing was successful.
 
db2inst1@lpar104ps3:/home/db2inst1>db2instance -list
ID        TYPE             STATE                HOME_HOST               CURRENT_HOST            ALERT   PARTITION_NUMBER        LOGICAL_PORT    NETNAME
--        ----             -----                ---------               ------------            -----   ----------------        ------------    -------
0       MEMBER           STOPPED                lpar104ps3                lpar104ps3               NO                  0                   0    lpar104ps3-en2-1
1       MEMBER           STOPPED                lpar105ps4                lpar105ps4               NO                  0                   0    lpar105ps4-en2-1
128     CF               STOPPED                lpar105ps4                lpar105ps4               NO                  -                   0    lpar105ps4-en2-2
129     CF               STOPPED                lpar104ps3                lpar104ps3               NO                  -                   0    lpar104ps3-en2-2
 
HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT
--------                   -----                ----------------        -----
lpar105ps4                ACTIVE                             YES           NO
lpar104ps3                ACTIVE                             YES           NO
 
3. Applying new Fixpack on standby
 
3-1. Offline fix pack update.
 
Standby member 0/CF 129:
 
root@lpar104ps3:/junsulee/server_t>./installFixPack -p /opt/IBM/db2/V11.1FP2_1 -I db2inst1 -offline -l /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.log -t /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.trc
DB2 installation is being initialized.
 
 
DB2 pureScale offline update evaluation:
=======================================
Hostname:lpar104ps3
Instance name:db2inst1
Target Installation path:/opt/IBM/db2/V11.1FP2_1
Target Code level         =  Version:11 Release:1 Modification:2 Fixpack:2 Interim:a Special Build:0
Target Architecture level =  Version:11 Release:1 Modification:2 Fixpack:2 Interim:a Special Build:0
 
TSA version installed on this host : 4.1.0.3
TSA version present on the media : 4.1.0.3
TSA version after update : 4.1.0.3
 
GPFS version installed on the host: 4.1.1.11
GPFS version present on the media : 4.1.1.11
GPFS version after update : 4.1.1.11
 
Total number of tasks to be performed: 3
Total estimated time for all tasks to be performed: 1924 second(s)
 
Task #1 start
Description: Installing DB2 database product binaries  
Estimated time 1485 second(s)
Task #1 end
 
Task #2 start
Description: Stopping the instance on the local host
Estimated time 10 second(s)
Task #2 end
 
Task #3 start
Description: Updating the DB2 database manager instance configuration
Estimated time 429 second(s)
Task #3 end
 
The execution completed successfully.
 
For more information see the DB2 installation log at
"/tmp/myfixpak_20180119_131933.log”.
 
 
Standby member 1 / CF 128 : Doing the same steps.
 
root@lpar105ps4:/junsulee/server_t>./installFixPack -p /opt/IBM/db2/V11.1FP2_1 -I db2inst1 -offline -l /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.log -t /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.trc

...<snippet>....
 
The execution completed successfully.
 
For more information see the DB2 installation log at
"/tmp/myfixpak_20180119_133139.log".

 
3-2. Run check commit.
 
Standby member 0 / CF 129:
 
root@lpar104ps3:/junsulee/server_t>./installFixPack -check_commit -I db2inst1 -l /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.log -t /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.trc
DBI1446I  The installFixPack command is running.
 
 
The pre-commit verification process for an offline fix pack update has started....
The checks for the pre-commit verification process have been completed successfully.
 
If you perform a commit, the new level will be =
   Version:11 Release:1 Modification:2 Fixpack:2 Interim:a Special Build:0
 
The execution completed successfully.
 
For more information see the DB2 installation log at "/tmp/mychkcommit_20180119_140231.log".
DBI1070I  Program installFixPack completed successfully.
 
Standby member 1 / CF 128 : Doing the same steps.
 
root@lpar105ps4:/junsulee/server_t>./installFixPack -check_commit -I db2inst1 -l /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.log -t /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.trc

 
...<snippet>....
 
The execution completed successfully.
 
For more information see the DB2 installation log at "/tmp/mychkcommit_20180119_140203.log".
DBI1070I  Program installFixPack completed successfully.
 
 
3-3. Commit the DB2 instance to the new level.
 
root@lpar104ps3:/junsulee/server_t>./installFixPack -commit_level -I db2inst1 -l /tmp/mycommitlevel_`date +%Y%m%d_%H%M%S`
DBI1446I  The installFixPack command is running.
 
The execution completed successfully.
 
For more information see the DB2 installation log at "/tmp/mycommitlevel_20180119_140718".
DBI1070I  Program installFixPack completed successfully.
 
 
4. Bring up instance and database.
 
db2inst1@lpar104ps3:/home/db2inst1>db2start instance on lpar104ps3
SQL1063N  DB2START processing was successful.
db2inst1@lpar104ps3:/home/db2inst1>db2start instance on lpar105ps4
SQL1063N  DB2START processing was successful.
db2inst1@lpar104ps3:/home/db2inst1>db2start
01/19/2018 14:14:55     0   0   SQL1063N  DB2START processing was successful.
01/19/2018 14:14:57     1   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.
 
 
5. Reconnect to the HADR
 
db2inst1@lpar104ps3:/home/db2inst1>db2 activate db JSHADRDB
DB20000I  The ACTIVATE DATABASE command completed successfully.
 
db2inst1@lpar104ps3:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = STANDBY
                        LOG_STREAM_ID = 0
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar102ps1
                       PRIMARY_MEMBER = 0
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 14:15:43.679458 (1516331743)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
                            HADR_ROLE = STANDBY
                        LOG_STREAM_ID = 1
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar103ps2
                       PRIMARY_MEMBER = 1
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 14:15:45.238645 (1516331745)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
6. HADR takeover
 
db2inst1@lpar104ps3:/home/db2inst1/junsulee>db2 takeover hadr on db JSHADRDB
DB20000I  The TAKEOVER HADR ON DATABASE command completed successfully.
 
Now new primary(original standby) shows HADR_STATE as DISCONNECTED.
This is expected as current primary has high db2level than the current standby.
 
db2inst1@lpar104ps3:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = PRIMARY
                        LOG_STREAM_ID = 0
                           HADR_STATE = DISCONNECTED
                           HADR_FLAGS =
                  PRIMARY_MEMBER_HOST = lpar104ps3
                       PRIMARY_MEMBER = 0
                  STANDBY_MEMBER_HOST = lpar102ps1
                  HADR_CONNECT_STATUS = DISCONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 14:16:57.818979 (1516331817)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
If other member is not activated, activate to use both members for service.
 
db2inst1@lpar105ps4:/home/db2inst1/junsulee>db2 activate db JSHADRDB
SQL1490W  Activate database is successful, however, the database has already
been activated on one or more nodes.
 
db2inst1@lpar105ps4:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = PRIMARY
                        LOG_STREAM_ID = 1
                           HADR_STATE = DISCONNECTED
                           HADR_FLAGS =
                  PRIMARY_MEMBER_HOST = lpar105ps4
                       PRIMARY_MEMBER = 1
                  STANDBY_MEMBER_HOST = NULL
                  HADR_CONNECT_STATUS = DISCONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 14:17:09.076186 (1516331829)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
 
7. Stop the original primary(current standby) cluster.
 
Original PRIMARY (Current standby)
 
db2inst1@lpar102ps1:/home/db2inst1>db2 deactivate db JSHADRDB
DB20000I  The DEACTIVATE DATABASE command completed successfully.
 
db2inst1@lpar102ps1:/home/db2inst1>db2stop
01/19/2018 14:32:30     0   0   SQL1064N  DB2STOP processing was successful.
01/19/2018 14:32:33     1   0   SQL1064N  DB2STOP processing was successful.
SQL1064N  DB2STOP processing was successful.
 
 
db2inst1@lpar102ps1:/home/db2inst1>db2stop instance on lpar102ps1
SQL1064N  DB2STOP processing was successful.
db2inst1@lpar102ps1:/home/db2inst1>db2stop instance on lpar103ps2
SQL1064N  DB2STOP processing was successful.
 
 
db2inst1@lpar102ps1:/home/db2inst1>db2instance -list
ID        TYPE             STATE                HOME_HOST               CURRENT_HOST            ALERT   PARTITION_NUMBER        LOGICAL_PORT    NETNAME
--        ----             -----                ---------               ------------            -----   ----------------        ------------    -------
0       MEMBER           STOPPED                lpar102ps1                lpar102ps1               NO                  0                   0    lpar102ps1-en1-2
1       MEMBER           STOPPED                lpar103ps2                lpar103ps2               NO                  0                   0    lpar103ps2-en1-1
128     CF               STOPPED                lpar103ps2                lpar103ps2               NO                  -                   0    lpar103ps2-en1-2
129     CF               STOPPED                lpar102ps1                lpar102ps1               NO                  -                   0    lpar102ps1-en1-2
 
HOSTNAME                   STATE                INSTANCE_STOPPED        ALERT
--------                   -----                ----------------        -----
lpar103ps2                ACTIVE                             YES           NO
lpar102ps1                ACTIVE                             YES           NO
 
 
8. Applying new Fixpack on original primary(current standby).
 
8-1. Offline fix pack update.

member 0/CF 129 : 
 
root@lpar102ps1:/junsulee/server_t>./installFixPack -p /opt/IBM/db2/V11.1FP2_1 -I db2inst1 -offline -l /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.log -t /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.trc

 
...<snippet>....
The execution completed successfully.
 
For more information see the DB2 installation log at
"/tmp/myfixpak_20180119_161954.log”.
 
member 1/CF 128 :
 
root@lpar103ps2:/junsulee/server_t>./installFixPack -p /opt/IBM/db2/V11.1FP2_1 -I db2inst1 -offline -l /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.log -t /tmp/myfixpak_`date +%Y%m%d_%H%M%S`.trc
 
...<snippet>....
 
The execution completed successfully.
 
For more information see the DB2 installation log at
"/tmp/myfixpak_20180119_163948.log”.
 
8-2. Run check commit.
 
member 0 / CF 129:
 
root@lpar102ps1:/junsulee/server_t>./installFixPack -check_commit -I db2inst1 -l /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.log -t /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.trc

...<snippet>....
 
The execution completed successfully.
 
For more information see the DB2 installation log at "/tmp/mychkcommit_20180119_165758.log".
DBI1070I  Program installFixPack completed successfully.
 
member 1 / CF 128:
 
root@lpar103ps2:/junsulee/server_t>./installFixPack -check_commit -I db2inst1 -l /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.log -t /tmp/mychkcommit_`date +%Y%m%d_%H%M%S`.trc

...<snippet>....
 
The execution completed successfully.
 
For more information see the DB2 installation log at "/tmp/mychkcommit_20180119_165942.log".
DBI1070I  Program installFixPack completed successfully.
 
 
8-3. Commit the DB2 instance to the new level.
 
root@lpar102ps1:/junsulee/server_t>./installFixPack -commit_level -I db2inst1 -l /tmp/mycommitlevel_`date +%Y%m%d_%H%M%S`
DBI1446I  The installFixPack command is running.
 
 
 
The execution completed successfully.
 
For more information see the DB2 installation log at "/tmp/mycommitlevel_20180119_170105".
DBI1070I  Program installFixPack completed successfully.
 
9. Bring up instance and database.

 

db2inst1@lpar102ps1:/home/db2inst1>db2start instance on lpar102ps1
SQL1063N  DB2START processing was successful.
db2inst1@lpar102ps1:/home/db2inst1>db2start instance on lpar103ps2
SQL1063N  DB2START processing was successful.
 
 
db2inst1@lpar102ps1:/home/db2inst1>db2start
01/19/2018 17:06:25     0   0   SQL1063N  DB2START processing was successful.
01/19/2018 17:06:26     1   0   SQL1063N  DB2START processing was successful.
SQL1063N  DB2START processing was successful.
 
db2inst1@lpar102ps1:/home/db2inst1>db2 activate db JSHADRDB
DB20000I  The ACTIVATE DATABASE command completed successfully.
 
Now we can see HADR_STATE as PEER because the standby db2level became same as primary.
 
db2inst1@lpar102ps1:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = STANDBY
                        LOG_STREAM_ID = 0
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar104ps3
                       PRIMARY_MEMBER = 0
                  STANDBY_MEMBER_HOST = lpar102ps1
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 17:07:00.490778 (1516342020)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
                            HADR_ROLE = STANDBY
                        LOG_STREAM_ID = 1
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar105ps4
                       PRIMARY_MEMBER = 1
                  STANDBY_MEMBER_HOST = lpar102ps1
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 17:07:00.514560 (1516342020)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
 
10. HADR Takeover back to original primary.
 
db2inst1@lpar102ps1:/home/db2inst1/junsulee>db2 takeover hadr on db JSHADRDB
DB20000I  The TAKEOVER HADR ON DATABASE command completed successfully.
 
 
db2inst1@lpar102ps1:/home/db2inst1/junsulee>./db2pd.sh
 
 
                            HADR_ROLE = PRIMARY
                        LOG_STREAM_ID = 0
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar102ps1
                       PRIMARY_MEMBER = 0
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 17:08:13.336294 (1516342093)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0
 
 
If other member is not activated, activate to use both members for service.
 
db2inst1@lpar103ps2:/home/db2inst1/junsulee>db2 activate db JSHADRDB
SQL1490W  Activate database is successful, however, the database has already
been activated on one or more nodes.
 
db2inst1@lpar103ps2:/home/db2inst1/junsulee>./db2pd.sh              
 
 
                            HADR_ROLE = PRIMARY
                        LOG_STREAM_ID = 1
                           HADR_STATE = PEER
                           HADR_FLAGS = TCP_PROTOCOL
                  PRIMARY_MEMBER_HOST = lpar103ps2
                       PRIMARY_MEMBER = 1
                  STANDBY_MEMBER_HOST = lpar104ps3
                  HADR_CONNECT_STATUS = CONNECTED
             HADR_CONNECT_STATUS_TIME = 01/19/2018 17:09:36.567898 (1516342176)
                  HADR_LOG_GAP(bytes) = 0
       STANDBY_RECV_REPLAY_GAP(bytes) = 0


db2inst1@lpar102ps1:/home/db2inst1>db2level
DB21085I  This instance or install (instance name, where applicable:
"db2inst1") uses "64" bits and DB2 code release "SQL11012" with level
identifier "0203010F".
Informational tokens are "DB2 v11.1.2.2", "s1709221349", "DYN1709221349AIX",
and Fix Pack "2a".
Product is installed at "/opt/IBM/db2/V11.1FP2_1".
 
So we are done !!!
Hope this blog helps for your planning on the applying fixpack work that will eventually happen to you if you are using pureScale with HADR.

[{"Business Unit":{"code":"BU029","label":"Data and AI"}, "Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11139974