23 August,2011 by Tom Collins

Setting HADR_PEER_WINDOW at zero ,  only blocks primary transactions for the time specified in HADR_TIMEOUT.   

If the HADR_PEER_WINDOW is set to greater than zero, then the Primary database waits until the connection is restored  or the HADR_PEER_WINDOW  period finishes.

 Connections between the Primary and Standby databases are temporarily broken .

Possible reasons can be:

a) network 

b) OS issues

c) DB2 problems. How to report a DB2 performance problem

Leaving the HADR_PEER_WINDOW at zero , is beneficial to maintain availability.   At zero, soon as the connection between Primary and Standby  closes , the Primary is no longer in Peer state. 

 Therefore ,

a)  For data consistency , go for a non-zero value

b)  For data availability , consider a zero value

Related Posts

DB2 – Backup history

DB2 – check backup command and contents of a database

DB2 – Restore database from a ONLINE backup

Author: Rambler(http://www.dba-db2.com)


Verify your Comment

Previewing your Comment

This is only a preview. Your comment has not yet been posted.

Your comment could not be posted. Error type:
Your comment has been saved. Comments are moderated and will not appear until approved by the author. Post another comment

The letters and numbers you entered did not match the image. Please try again.

As a final step before posting your comment, enter the letters and numbers you see in the image below. This prevents automated programs from posting comments.

Having trouble reading this image? View an alternate.


Post a comment on DB2 HADR and HADR_PEER_WINDOW settings

Comments are moderated, and will not appear until the author has approved them.

dba-db2.com | DB2 Performance Tuning | DBA DB2:Everything | FAQ | Contact | Copyright