RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

trigger-type
is REVERSE or TAKEOVER. This command parameter alters a trigger that has already been
added to the RDF configuration.
Where Issued
These commands can be issued only at the primary system, except altering the TAKEOVER trigger,
which can also be issued on the backup system if and only if the primary system is not available.
NOTE: You should only alter the TAKEOVER trigger on the backup system if you are about to
issue the TAKEOVER command. If you alter this trigger on the backup system at any other time,
you must remember to issue the same alter command on the primary system when it is available
again. If you fail to do this, then the next time you start RDF, the trigger information on the primary
system is copied to the backup system, and the changes you had made to the trigger on the backup
system are then lost.
Security Restrictions
You can issue the ALTER command if you are a member of the super ID group.
RDF State Requirement
While RDF is running, the only configuration parameters you can alter are the log file, the purge
time, the RDF updater delay, the RDF UPDATEROPEN, and the priority of each RDF process. To
change the setting of any other parameter, you must first stop RDF.
Usage Guidelines
Before entering the ALTER command, you can display the current configuration parameters with
the INFO RDF command. After entering ALTER, you can confirm your changes by again entering
INFO RDF.
For using ALTER RDF UPDATEROPEN to coordinate the taking of online dumps or reloads on the
backup system, see the discussion in Chapter 5 (page 113).
If you use an ALTER RECEIVER command to change the EXTENTS parameter, the change will occur
on the next RDF image file rollover, unless RDF has never been started since its last reinitialization.
Although you can use the SET RECEIVER RDFVOLUME command to specify the disk volume used
for the master image trail, you cannot re-specify this volume by entering an ALTER RECEIVER
RDFVOLUME command. To change this volume, you must reinitialize RDF and use another SET
RECEIVER RDFVOLUME command followed by an ADD RECEIVER command.
If you need to change an updater’s image trail volume, it is recommended that you stop TMF; wait
for RDF to stop; delete the volume; re-add the volume back into the configuration, associating it to
a different image trail volume; and then restart the TMF and RDF subsystems. This is the only way
to ensure that the backup database will remain synchronized with the primary database.
NOTE: Altering the RDF UPDATERDELAY value is not recommended unless you have a very
specific reason for doing so; any value less than the default (10 seconds) can affect updater
performance.
Examples
To change the priority at which an extractor process is currently running, issue an ALTER EXTRACTOR
PRIORITY command. For example, the following command changes the execution priority of the
master extractor process to 170:
]ALTER EXTRACTOR PRIORITY 170
The following command changes the execution priority of the auxiliary extractor process associated
with the auxiliary audit trail AUX02 to 170:
]ALTER EXTRACTOR ATINDEX 2 PRIORITY 170
RDFCOM Commands 185