Kbase P64230: How to put in place multi After-Image (AI) extents strategy?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Verified
GOAL:
How to put in place multi After-Image (AI) extents strategy?
GOAL:
How to manage the full AI extents?
GOAL:
What has to be done prior to running "aimage empty"
FACT(s) (Environment):
UNIX
Products / Versions
FIX:
When having minimum two After Image (AI) extents, the following strategy can be implemented.
1. Switch AI extent with the command "rfutil <db> -C aimage new"
2. Make a unique copy of the AI extent full
3. Mark the copied AI extent as empty with the command "rfutil <db> -C aimage empty"
Find below a Unix/Linux sample script for a database named "mydb" for which we have minimum three AI extents; "/usr1/mydb" needs to be an existing directory and . The "while loop" is there to take care of any pre-existing full AI extent (the result of an automatic aimage switch on 'probkup' for example); the "sleep 1" is there to assure uniqueness for the copy name. This script should not be run two times in parallel.
rfutil mydb -C aimage new
while test -z `rfutil mydb -C aimage extent full >/dev
ull`
do
last_full='_rfutil mydb -C aimage extent full'
cp $last_full /usr1/mydb/AI`date +"%d%h%H%M%S"`
sleep 1
rfutil mydb -C aimage extent empty $last_full
done