DB2: To bounce reporting server prd603

Turn off mnitoring 

 

To check the HADR status on the reporting server

[prd1ins1@db2prd603  ~]

$ db2pd -db wcprd1 -hadr


Database Member 0 -- Database WCPRD1 -- Active Standby -- Up 90 days 06:49:31 -- Date 2025-02-04-08.08.14.294993


                            HADR_ROLE = STANDBY

                          REPLAY_TYPE = PHYSICAL

                        HADR_SYNCMODE = SUPERASYNC

                           STANDBY_ID = 0

                        LOG_STREAM_ID = 0

                           HADR_STATE = REMOTE_CATCHUP

                           HADR_FLAGS = TCP_PROTOCOL

                  PRIMARY_MEMBER_HOST = db2prd601

                     PRIMARY_INSTANCE = prd1ins1

                       PRIMARY_MEMBER = 0

                  STANDBY_MEMBER_HOST = db2prd603

                     STANDBY_INSTANCE = prd1ins1

                       STANDBY_MEMBER = 0

                  HADR_CONNECT_STATUS = CONNECTED

             HADR_CONNECT_STATUS_TIME = 11/06/2024 03:12:53.427590 (1730884373)

          HEARTBEAT_INTERVAL(seconds) = 5

                     HEARTBEAT_MISSED = 14

                   HEARTBEAT_EXPECTED = 1560054

                HADR_TIMEOUT(seconds) = 20

        TIME_SINCE_LAST_RECV(seconds) = 0

             PEER_WAIT_LIMIT(seconds) = 0

           LOG_HADR_WAIT_CUR(seconds) = 0.000

    LOG_HADR_WAIT_RECENT_AVG(seconds) = 0.000162

   LOG_HADR_WAIT_ACCUMULATED(seconds) = 36357.169

                  LOG_HADR_WAIT_COUNT = 260406689

SOCK_SEND_BUF_REQUESTED,ACTUAL(bytes) = 0, 46080

SOCK_RECV_BUF_REQUESTED,ACTUAL(bytes) = 0, 360960

            PRIMARY_LOG_FILE,PAGE,POS = S0087163.LOG, 54929, 19540474241803

            STANDBY_LOG_FILE,PAGE,POS = S0087163.LOG, 54929, 19540474241803

                  HADR_LOG_GAP(bytes) = 577

     STANDBY_REPLAY_LOG_FILE,PAGE,POS = S0087163.LOG, 54929, 19540474241803

       STANDBY_RECV_REPLAY_GAP(bytes) = 0

                     PRIMARY_LOG_TIME = 02/04/2025 08:08:14.000000 (1738678094)

                     STANDBY_LOG_TIME = 02/04/2025 08:08:14.000000 (1738678094)

              STANDBY_REPLAY_LOG_TIME = 02/04/2025 08:08:14.000000 (1738678094)

         STANDBY_RECV_BUF_SIZE(pages) = 4302

             STANDBY_RECV_BUF_PERCENT = 0

           STANDBY_SPOOL_LIMIT(pages) = 12375000

                STANDBY_SPOOL_PERCENT = 0

                   STANDBY_ERROR_TIME = NULL

                 PEER_WINDOW(seconds) = 0

             READS_ON_STANDBY_ENABLED = Y

    STANDBY_REPLAY_ONLY_WINDOW_ACTIVE = N

              HADR_LAST_TAKEOVER_TIME = NULL


[prd1ins1@db2prd603  ~]







THIS IS HOW HADR LOOKS LIKE ON THE STANDY / TSA SERVER prd602

[prd1ins1@db2prd602  ~]

$ db2pd -db wcprd1 -hadr


Database Member 0 -- Database WCPRD1 -- Standby -- Up 90 days 06:18:12 -- Date 2025-02-04-08.09.46.689735


                            HADR_ROLE = STANDBY

                          REPLAY_TYPE = PHYSICAL

                        HADR_SYNCMODE = NEARSYNC

                           STANDBY_ID = 0

                        LOG_STREAM_ID = 0

                           HADR_STATE = PEER

                           HADR_FLAGS = TCP_PROTOCOL

                  PRIMARY_MEMBER_HOST = db2prd601

                     PRIMARY_INSTANCE = prd1ins1

                       PRIMARY_MEMBER = 0

                  STANDBY_MEMBER_HOST = db2prd602

                     STANDBY_INSTANCE = prd1ins1

                       STANDBY_MEMBER = 0

                  HADR_CONNECT_STATUS = CONNECTED

             HADR_CONNECT_STATUS_TIME = 11/06/2024 03:05:50.475410 (1730883950)

          HEARTBEAT_INTERVAL(seconds) = 5

                     HEARTBEAT_MISSED = 0

                   HEARTBEAT_EXPECTED = 1559223

                HADR_TIMEOUT(seconds) = 20

        TIME_SINCE_LAST_RECV(seconds) = 0

             PEER_WAIT_LIMIT(seconds) = 0

           LOG_HADR_WAIT_CUR(seconds) = 0.000

    LOG_HADR_WAIT_RECENT_AVG(seconds) = 0.000119

   LOG_HADR_WAIT_ACCUMULATED(seconds) = 36357.410

                  LOG_HADR_WAIT_COUNT = 260408203

SOCK_SEND_BUF_REQUESTED,ACTUAL(bytes) = 0, 16384

SOCK_RECV_BUF_REQUESTED,ACTUAL(bytes) = 0, 87380

            PRIMARY_LOG_FILE,PAGE,POS = S0087164.LOG, 1170, 19540479300700

            STANDBY_LOG_FILE,PAGE,POS = S0087164.LOG, 1170, 19540479300700

                  HADR_LOG_GAP(bytes) = 2085

     STANDBY_REPLAY_LOG_FILE,PAGE,POS = S0087164.LOG, 1170, 19540479300700

       STANDBY_RECV_REPLAY_GAP(bytes) = 2442

                     PRIMARY_LOG_TIME = 02/04/2025 08:09:46.000000 (1738678186)

                     STANDBY_LOG_TIME = 02/04/2025 08:09:46.000000 (1738678186)

              STANDBY_REPLAY_LOG_TIME = 02/04/2025 08:09:46.000000 (1738678186)

         STANDBY_RECV_BUF_SIZE(pages) = 4302

             STANDBY_RECV_BUF_PERCENT = 0

           STANDBY_SPOOL_LIMIT(pages) = 12375000

                STANDBY_SPOOL_PERCENT = 0

                   STANDBY_ERROR_TIME = NULL

                 PEER_WINDOW(seconds) = 300

                      PEER_WINDOW_END = 02/04/2025 08:14:46.000000 (1738678486)

             READS_ON_STANDBY_ENABLED = N

              HADR_LAST_TAKEOVER_TIME = NULL


[prd1ins1@db2prd602  ~]

$


$ db2 deactivate db wcprd1


DB20000I  The DEACTIVATE DATABASE command completed successfully.


[tst3ins3@db2tst601  ~]


$ db2 stop hadr on db wcprd1


DB20000I  The STOP HADR ON DATABASE command completed successfully.


[tst3ins3@db2tst601  ~]


$ db2stop


04/04/2024 10:59:45     0   0   SQL1064N  DB2STOP processing was successful.


SQL1064N  DB2STOP processing was successful.


[tst3ins3@db2tst601  ~]


$ db2pd -db wcprd1 -hadr



Bring up the standby


Start Db2


$ db2start


Start HADR


$ db2 start hadr on db wcprd1 as standby


Verify HADR


$ db2pd -db wcprd1 -hadr







Actual steps:

$ db2 deactivate db wcprd1

SQL1493N  The command failed because the application is already connected to

an active database.


[prd1ins1@db2prd603  ~]

$ db2 terminate

DB20000I  The TERMINATE command completed successfully.


[prd1ins1@db2prd603  ~]

$ db2 deactivate db wcprd1

SQL1495W  Deactivate database is successful, however, there is still a

connection to the database.


[prd1ins1@db2prd603  ~]

$ db2 stop hadr on db wcprd1

DB20000I  The STOP HADR ON DATABASE command completed successfully.


[prd1ins1@db2prd603  ~]

$ db2stop

05/02/2025 00:31:26     0   0   SQL1064N  DB2STOP processing was successful.

SQL1064N  DB2STOP processing was successful.


[prd1ins1@db2prd603  ~]

$ db2start

05/02/2025 00:31:32     0   0   SQL1063N  DB2START processing was successful.

SQL1063N  DB2START processing was successful.


[prd1ins1@db2prd603  ~]

$  db2 start hadr on db wcprd1 as standby

DB20000I  The START HADR ON DATABASE command completed successfully.


[prd1ins1@db2prd603  ~]

$  db2pd -db wcprd1 -hadr


Database Member 0 -- Database WCPRD1 -- Active Standby -- Up 0 days 00:00:10 -- Date 2025-05-02-00.31.45.045498


                            HADR_ROLE = STANDBY

                          REPLAY_TYPE = PHYSICAL

                        HADR_SYNCMODE = SUPERASYNC

                           STANDBY_ID = 0

                        LOG_STREAM_ID = 0

                           HADR_STATE = REMOTE_CATCHUP

[...]

Comments

Post a Comment

Popular posts from this blog

Postgres: Clean up stopped replication slot

Image
  When a slot is inactive, that means that Murty and his team have stopped the replication on their side. The SQL below will identify inactive slots. We should schedule this script in a job , running every hour.    (1) SELECT  slot_name,  pg_size_pretty(pg_wal_lsn_diff(pg_current_wal_lsn(),restart_lsn)) AS size,  active,  slot_type  FROM pg_replication_slots;       (2) Once you identify the replication slot, the job should drop it with the following command:     SELECT pg_drop_replication_slot ('pg_replication_slot_name_from_above');         (3) Restart the database instance to clean up unwanted disk space.   Notes from Google:- Thank you for contacting Google Cloud Support. My name is Jagadeesh and I will be assisting you with this issue.   I understand that WAL logs are expanding to over 1.5TB and you want to know what is causing WAL logs to grow and you want to reduce it. Please confirm if ...
Read more