RDF System Management Manual for H-Series RVUs (RDF 1.8)

The STOP UPDATE command is useful when you want to produce reports from the database
on the backup system. For more information, see “Reading the Backup Database” (page 140) and
“Access to Backup Databases in a Consistent State” (page 140). If the STOP UPDATE command
includes the TIMESTAMP parameter, RDFCOM returns a prompt as soon as all processes have
been advised of the stop operation. If the STOP UPDATE command does not include the
TIMESTAMP parameter, however, RDFCOM does not return a prompt until all updater processes
stop on the backup system. When the prompt does appear, start the reporting processes on the
backup system. After reporting has completed, enter this command to resume updating:
]START UPDATE
NOTE: RDF always starts with updating enabled, unless you explicitly specify UPDATE OFF
in the START RDF command. This scenario is true even if updating was disabled when RDF
was last stopped.
Updaters cannot always respond immediately to a STOP UPDATE 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 you erroneously set the timestamp too far into the future (for example, 26NOV2009), the only
way to correct this mistake is to enter a STOP RDF command, restart RDF, and reenter the STOP
UPDATE command with the correct timestamp.
Examples
To suspend updating activities and stop the updater processes, enter this command:
STOP UPDATE
To suspend updating activities and stop the updaters from processing transactions committed
by 2:30 P.M. or later on January 20, 2004, enter this command:
STOP UPDATE, TIMESTAMP 20JAN2004 14:30
TAKEOVER
The TAKEOVER command causes the backup database to become transactionally consistent and
available as the database of record.
TAKEOVER [!]
!
Causes the takeover to be performed immediately, with no attempt to verify that the primary
system is inaccessible.
Be careful. If you include the "!" and the primary system is still accessible, executing the
TAKEOVER command could put your backup database out of synchronization with the
primary database. You should use the "!" only if you are absolutely certain the primary is
down and you want the takeover to proceed immediately.
Where Issued
Backup system only.
Security Restrictions
You can issue the TAKEOVER command if you are the member of the super-user group that
initialized RDF.
RDF State Requirement
Normally you can issue the TAKEOVER command only if the communication lines between the
backup and primary systems are down, or the monitor process is not running on the primary
system. You can, however, override this requirement by including the "!" in the command.
RDFCOM Commands 239