RDF System Management Manual

Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-102
Command Overview
•
All communications lines to the primary system are down.
If the decision has been made to stop RDF on the backup system, issue a STOP
RDF command at the backup system. All processes running on the backup
system write context information to a context file and then stop.
If the communications lines between the primary and backup systems are up, a
STOP RDF command issued at the backup system fails, and RDFCOM displays
an error message.
As it shuts down RDF, the STOP RDF command writes a message to the RDF log file
indicating this action.
Updaters cannot always respond immediately to a STOP RDF command. If an
updater has audit information queued for the disk process, the updater must wait until
all of that information is processed before it can shut down.
If all else fails, you can shut down the individual RDF processes manually. When
doing that, you must first stop the extractor on the primary system, then stop all
updaters on the backup system, stop the purger on the backup system, and finally stop
the receiver on the backup system. The easiest way to do this is to issue a series of
commands of the following form:
STATUS *,PROG RDF-software-loc.procname, STOP
RDF must be in the “started” state with UPDATE ON to issue a STOP RDF, DRAIN or
STOP RDF, REVERSE command. In addition, entering either command as follows
results in an error:
•
on the backup system
•
while RDF is stopping due to a stop TMF
•
while a stop-update-to-timestamp operation is pending
•
while a SQL DDL operation with SHARED ACCESS is being processed
Note. Before you can restart RDF, you must stop RDF on the primary system as well.
Caution. Issuing this command in this situation is only safe, however, if this is the backup
system for a single RDF environment.