Hi all,
Platform DB2 V9.1 FP3 on AIX V5.3, HADR is configured and running.
LOGARCHMETH1 is TSM , FAILARCHPATH is set to a local filesystem.
Szenario:
TSM Server is unavailable for some time, DB2 primary archives its logs
to FAILARCHPATH as expected.
Now the HADR Standby goes down. While the standby is unavailable the
primary continues work and archives some log files to FAILARCHPATH
(TSM still not available). The log files were removed /renamed on the
active log path. When the standby comes back later it contacts the
primary to get synched and throws errors about missing log files on
the primary. So it looks like the primary does not "retrieve" log
files from FAILARCHPATH.
If TSM comes up again, the primary will archive the log files from
FAILARCHPATH to TSM. When the standby is activated now, it will
receive log files from the primary(which were retrievd from TSM). So
far so good - but if the primary is stopped while using FAILARCHPATH
and is restarted when TSM is available again it will not archive the
log files from FAILARCHPATH to TSM, thus leaving a gap in the
archived log chain.
Im not able to open up a PMR for this situation at the moment - anyone
else seen this behaviour ?
TIA for any answer
Joachim
Platform DB2 V9.1 FP3 on AIX V5.3, HADR is configured and running.
LOGARCHMETH1 is TSM , FAILARCHPATH is set to a local filesystem.
Szenario:
TSM Server is unavailable for some time, DB2 primary archives its logs
to FAILARCHPATH as expected.
Now the HADR Standby goes down. While the standby is unavailable the
primary continues work and archives some log files to FAILARCHPATH
(TSM still not available). The log files were removed /renamed on the
active log path. When the standby comes back later it contacts the
primary to get synched and throws errors about missing log files on
the primary. So it looks like the primary does not "retrieve" log
files from FAILARCHPATH.
If TSM comes up again, the primary will archive the log files from
FAILARCHPATH to TSM. When the standby is activated now, it will
receive log files from the primary(which were retrievd from TSM). So
far so good - but if the primary is stopped while using FAILARCHPATH
and is restarted when TSM is available again it will not archive the
log files from FAILARCHPATH to TSM, thus leaving a gap in the
archived log chain.
Im not able to open up a PMR for this situation at the moment - anyone
else seen this behaviour ?
TIA for any answer
Joachim