Skip to main content

High Availability and Disaster Recovery Options for DB2 on Linux, UNIX, and Windows

Redbooks logo

Readers' comments

Readers' comments (4) 


Posted by Mr. Jan van Reenen on 21 July 2008 at 3:02

In paragraph 6.3.5 you state that the standby server needs to be equal to the primary server. If the primary server takes all SQL and DML and the secondary only the DML via the transaction log, the secondary will need less cpu-capacity. If SQL is about 50% of the workload (in cpu-cycles) and constraint checking again 50% of de cpu load for DML, the secondary server would only require 25% of the cpu capacity as long as it is secondary. During take over the lpar needs to be reconfigured.

Posted by Mr. Jim Jeter on 7 January 2009 at 11:02

Is there any reason why scalability (Part 2) was removed from this draft version of the Redbook?

Posted by W.J. Chen on 8 January 2009 at 8:41

There's "Database Partitioning, Table Partitioning, and MDC for DB2 9", SG24-7467 published after the first version of the HA book. The database and table partitioning book covers more detailed about these scalability features. Therefore, we removed the scalability (Part 2).

Posted by Roberto Lio on 29 April 2009 at 5:58

Why the variable "DB2_FALLBACK" is not mentioned in this redbook?


Add your comments

You must sign in to post comments

Sign in

 

Profile

Publish Date
08 February 2009

Last Update
20 April 2009


Rating:
(based on 2 reviews)


Author(s)

ISBN

0738431389

IBM Form Number
SG24-7363-01