Book Image

IBM InfoSphere Replication Server and Data Event Publisher

By : Pav Kumar-Chatterjee, Pav Kumar Chatterjee
Book Image

IBM InfoSphere Replication Server and Data Event Publisher

By: Pav Kumar-Chatterjee, Pav Kumar Chatterjee

Overview of this book

Business planning is no longer just about defining goals, analyzing critical issues, and then creating strategies. You must aid business integration by linking changed-data events in DB2 databases on Linux, UNIX, and Windows with EAI solutions , message brokers, data transformation tools, and more. Investing in this book will save you many hours of work (and heartache) as it guides you around the many potential pitfalls to a successful conclusion. This book will accompany you throughout your Q replication journey. Compiled from many of author's successful projects, the book will bring you some of the best practices to implement your project smoothly and within time scales. The book has in-depth coverage of Event Publisher, which publishes changed-data events that can run updated data into crucial applications, assisting your business integration processes. Event Publisher also eliminates the hand coding typically required to detect DB2 data changes that are made by operational applications. We start with a brief discussion on what replication is and the Q replication release currently available in the market. We then go on to explore the world of Q replication in more depth. The latter chapters cover all the Q replication components and then talk about the different layers that need to be implemented—the DB2 database layer, the WebSphere MQ layer, and the Q replication layer. We conclude with a chapter on how to troubleshoot a problem. The Appendix (available online) demonstrates the implementation of 13 Q replication scenarios with step-by-step instructions.
Table of Contents (12 chapters)
IBM InfoSphere Replication Server and Data Event Publisher
Credits
About the Author
About the Reviewer
Preface

Pruning of the control tables


In the previous section, it was discussed how the control tables were populated. This section discusses how they are pruned. The control tables can be pruned automatically by Q Capture and Q Apply (and the Replication Alert Monitor) or can be pruned manually.

Let's first look at the tables that need to be pruned:

  • Q Capture: IBMQREP_CAPMON, IBMQREP_CAPQMON, IBMQREP_CAPTRACE, and IBMQREP_SIGNAL.

  • Q Apply: IBMQREP_APPLYMON and IBMQREP_APPLYTRACE.

  • The Replication Alert Monitor: IBMSNAP_ALERTS and IBMSNAP_MONTRACE.

When it comes to dealing with data in these control tables, we have two questions:

  • How long should the data stay in the tables?

  • Once we have decided that data should be deleted, when is this done?

There are two parameters which manage the answer to both of these questions:

  1. 1. For the xxxMON and CAPQMON tables the answer to the first question is provided by the MONITOR_LIMIT parameter, which determines how long data should be kept in the tables.

  2. 2. The second...