One way that you can make the tracker site be the takeover
site is by using the RESTORE SYSTEM utility with the LOGONLY option
in the recovery cycles at the tracker site.
Procedure
To make the tracker site be the takeover site by using
the RESTORE SYSTEM utility with the LOGONLY option:
- If log data for a recovery cycle is en route or is available
but has not yet been used in a recovery cycle, perform the procedure
in Establishing a recovery cycle by using RESTORE SYSTEM LOGONLY.
- Ensure that the TRKSITE NO subsystem parameter is specified.
- For scenarios other than data sharing, continue with step 4.
- Data sharing
- If this is a data sharing system, delete the coupling facility
structures.
- Start Db2 at the
same RBA or ENDLRSN that you used in the most recent tracker site
recovery cycle. Specify FORWARD=YES and BACKOUT=YES in the CRESTART
statement; this takes care of uncommitted work.
- Restart the objects that are in GRECP or LPL status by
issuing the START DATABASE(*) SPACENAM(*) command.
- If you used the DSN1COPY utility to create a copy of SYSUTILX
in the last recovery cycle, use DSN1COPY to restore that copy.
- Terminate any in-progress utilities by using the following
procedure:
- Enter the DISPLAY UTILITY(*) command
.
- Run the DIAGNOSE utility with DISPLAY SYSUTIL to get
the names of objects on which utilities are being run.
- Terminate in-progress utilities in the correct order
by using the TERM UTILITY(*) command.
- Rebuild indexes, including IBM® and
user-defined indexes on the Db2 catalog
and user-defined indexes on table spaces.