HP IAP Version 2.0 Administrator Guide (July 2008)

Database Replic
ation
IMPORTANT:
When installing a replica IAP, nish db2 replication before starting JBoss on all other servers. If you
do not some IAP applications will not be able to access db2 because db2 tables are locked by the
db2 replicatio
nprocess.
The top part of the Replication view describes the database replication.
Table 35 D atabase Replication features
Feature
Description
Local Server/Source
Server
The replication and primar y systems i f you are l ogged into the replicated
system.
Local Server/T arget
Server
The primary and replication systems if you are logged into the primary
system.
Replication Set
A set is made of one or more db2 tables that replicated.
Inbound Sync
Time/Outbound Sync
Time
The time at which the database tables in the replication set got last
syn chronized. The synchronization time is displayed in two c olors: green
and red. Green means that the da tabase tables on the primary and
replica DB2 have been synchronized successfully within the last 30
minutes. Red means tha t the synchronization has not happened for 30
minutes or m ore; this could indicate a db2 replication issue and you
should contact HP technical support for advice.
Inbound Status/
Outbound Status
The replication status on the replicated and primary systems.
(Re-)Initializing db2 replication
Follow the steps below to initialize or re-initialize db2 replication:
1. Stop the IAP applications on the primary and replica:
PCC on primary: /opt/bin/stop
PCC on replica: /opt/bin/stop
2. Uncongure db2 replication on p rimary/replica:
DB2 on replica: /opt/bin/repl/dbRepl rm
DB2 on primary: /opt/bin/repl/dbRepl rm
3. Restart db2 on p rimary/replica:
DB2 on primary: /etc/init.d/db2_app start
DB2 on replica: /etc/init.d/db2_app start
4. Re-initialize db2 replication on primary/replica:
DB2 on primary: /opt/bin/repl/dbRepl init
DB2 on replica: /opt/bin/repl/dbRepl init
5. Wait for the replication p rocess to complete (this can take anywhere between a few minutes to
an hour or more depending on the size of the d b2 database and the bandwith of the network
between the two IAPs) :
DB2 on replica: /opt/bin/repl/dbRepl status -brief -force
Look for the message "Replication is active." Re-issue the command every few minutes until this
message is returned, or while you see the message Refresh is in-progress.
6. Once replication is successfully initialized, restart the applications on primary/replica:
PCC on primary: /opt/bin/start
PCC on replica: /opt/bin/start
62
Data management