Now let's move on to look at some Q replication performance considerations. Our Q replication environment is made up of four components:
The DB2 database layer comprising the source and target databases
WebSphere MQ
Q Capture
Q Apply
Let's look at tuning each of these components.
The DB2 source or target databases: The tuning that should be performed for the DB2 databases is normal tuning that we would do for any database. The only point to bear in mind is that the amount of DB2 log space required may increase due to DATA CAPTURE CHANGES
being set. There are no other special considerations if the databases are involved in Q replication.
We may need to run RUNSTATS
and REORGS
on the replication control tables—these tables should be treated as any other application table.
We have mentioned the MAXDEPTH
parameter for queues (Refer to the MQ Queue management—To define a Local Queue section of Chapter 4), and if we increase...