Book Image

IBM DB2 9.7 Advanced Administration Cookbook

Book Image

IBM DB2 9.7 Advanced Administration Cookbook

Overview of this book

IBM DB2 LUW is a leading relational database system developed by IBM. DB2 LUW database software offers industry leading performance, scale, and reliability on your choice of platform on various Linux distributions, leading Unix Systems like AIX, HP-UX and Solaris and MS Windows platforms. With lots of new features, DB2 9.7 delivers one the best relational database systems in the market. IBM DB2 9.7 Advanced Administration Cookbook covers all the latest features with instance creation, setup, and administration of multi-partitioned database. This practical cookbook provides step-by-step instructions to build and configure powerful databases, with scalability, safety and reliability features, using industry standard best practices. This book will walk you through all the important aspects of administration. You will learn to set up production capable environments with multi-partitioned databases and make the best use of hardware resources for maximum performance. With this guide you can master the different ways to implement strong databases with a High Availability architecture.
Table of Contents (21 chapters)
IBM DB2 9.7 Advanced Administration Cookbook
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Changing HADR synchronization modes


Synchronization modes determine how primary logs are propagated and synchronized with the standby database when the systems are in peer state. The stricter the synchronization mode, the more influenced the performance on the primary database. There are three synchronization modes: SYNC, NEARSYNC, and ASYNC.

Getting ready

In this recipe, we will switch first to NEARSYNC mode, then to SYNC synchronization mode, and then back to ASYNC mode.

The HADR_SYNCMODE parameter mentioned previously controls the synchronization mode of HADR. Since this parameter is not dynamic after any modification, a HADR and database restart is needed.

How to do it...

The parameter HADR_SYNCMODE is not dynamic, so every change to the synchronization mode requires a database restart for both the primary database and standby database.

Changing to NEARSYNC synchronization mode

  1. Change the value of HADR_SYNCMODE, on both the databases, to NEARSYNC synchronization mode:

    [db2inst1@nodedb22 ~]...