Hi all,
Our business is in manufacturing, and we are running SAP on DB2 8.1,
planning on upgrading to 8.2.2 within a couple of months. We are
running operations 24/7, so are looking for ways to reduce our
maintenance impact to our users. Our users hit some specific SAP tables
very heavily, and concurrently, so even doing an online REORG causes
some system slowdown. We are looking for ways to reduce these slowdown
times, because even though we have an outage once per month to catch up
REORGs, we would like to be able to do them during normal business
hours, without impacting system performance.
The idea of using HADR came to mind, along with the Q Replication, as
mentioned in this article, where businesses were using Q Replication to
minimize downtime:
http://www.db2mag.com/story/showArti...cleID=23903558
Basically, what we would do is, run our maintenance, such as table
REORGs, on the secondary/standby machine, and once the maintenance has
finished, we would then make the machine available to the end users. In
turn, we would then do the same maintenance on the other machine.
Therefore all performance intensive maintenance activities would take
place on a machine that users would not be hitting.
I initially spoke with our sales rep and his engineer about using Q
Replicator, but they thought HADR has a better choice for what we
wanted.
Has anyone had any experience so far with this scenario? Or is there a
better way to approach this?
Also, if anyone from IBM reads these groups, are there any plans to
make HADR load balance?
