Salesforce

When to use rfutil -C sequence with an OS or proquiet database copy?

« Go Back

Information

 
TitleWhen to use rfutil -C sequence with an OS or proquiet database copy?
URL NameP102501
Article Number000126984
EnvironmentProduct: Progress
Version: 9.1E
Product: OpenEdge
Version: 10.0B01, 10.1x, 10.2x, 11.x
OS: All supported platforms
Question/Problem Description
When to use rfutil -C sequence with an OS or proquiet database copy?
Considerations when using proquiet on an after-image enabled database?
How to roll forward AI files onto a backup taken from a mirror?
How to roll forward AI files onto a backup taken during a proquiet?
What is the procedure to backup your database when splitting the mirror?
 
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution

This Article is applicable for customers who use proquiet to first quiet a database in order to use a 3rd party tool (or an operating system tool) to backup the database and after image files, running Progress 9.1E, OpenEdge 10.0B01 or later.

When the purpose of this restored 'snapshot' is to then subsequently roll forward ai files, additional steps need to be taken to allow those after image files to be applied to the copied database.

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 then 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 prior online status.

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

3.)  The target database must then have its AI sequence corrected prior to attempting to apply an AI extent with roll forward. This feature was introduced in Progress 9.1E, OpenEdge 10.0B01 or later.

Please note that because "rfutil -C roll forward" disables after imaging, it is impossible to correct the sequence once after imaging has been disabled. 

$   rfutil /hotspare/sourceOScopy -C sequence

On successful completion the sequence command sets the target database AI sequence number to the last switched AI extent of the source database. The following entry in the log file will confirm this, for example:

(12428) Ai sequence 1 changed to 1229

The differences between the current and expected AI sequence numbers is described in Article

4.)  Roll forward the 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/sourceOScopy -C roll forward -a source.a17

Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:35 AM

Powered by