Consultor Eletrônico



Kbase P102501: When to use rfutil -C sequence?
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   14/08/2008
Status: Verified

GOAL:

When to use rfutil -C sequence?

GOAL:

Considerations when using proquiet on an after-image enabled database?

GOAL:

How to roll forward AI files onto a backup taken from a mirror?

GOAL:

What is the procedure to backup your database when splitting the mirror?

GOAL:

OpenEdge 10.0B01

FACT(s) (Environment):

Progress 9.1E
OpenEdge 10.1A

FIX:

This solution is applicable for those customers who use proquiet to quiet a database and then use a 3rd party tool (or an operating system tool) to backup the database and after image files.

When doing this, there are special steps that need to be taken to allow those after image files to be applied to the copied database (when it has never had AI files applied to it).

1.) Normally the method that the databases are backed up is similar to the following:
$ proquiet source enable
(once the proquiet command has indicated that the quiet point has been enabled)
$ use operating system commands to split mirrors
$ cp sourceDB* /hotspare
$ proquiet sourceDB disable



2.) The target.st file must be altered to describe the physical location of the fractured copy of the database. Then this .st file is used with the prostrct repair utility to alter the file list of the fractured database and update internal database information to reflect its online status.

$ prostrct repair /hotspare/sourceDB /hotspare/target.st

3.) The target database must have its sequence corrected prior to attempting to apply an AI extent with roll forward. Please note that because "rfutil -C roll forward" disables after imaging, it is impossible to correct the sequence after roll forward has been disabled. (Must be on 9.1E, 10.0B01 or higher for this command to work.)

$ rfutil /hotspare/source -C sequence

You will see the following entry in the log file, for example:
RFUTIL 0: Ai sequence 1 changed to 2
5.) Roll forward the second AI extent from the source database to the standby copy. This will be whichever extent was in a BUSY status at the time + 1 for the proquiet aimage switch that the copy/fracture of the database was made.
$ rfutil /hotspare/source -C roll forward -a source.a2

This solution will only work for those customers running on Progress 9.1E, OpenEdge 10.0B01 and higher.