Kbase P42210: After running aimage new, old ai extent has status of locked
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
14/01/2009 |
|
Status: Verified
SYMPTOM(s):
Error attempting to run rfutil dbname -C extent empty -a dbname.ax
Site Replication processing for area <area number>; is not complete. (10432)
Rfutil dbname -C extent new was run successfully.
Rfutil dbname -C aimage extent list reports ai file is in a locked state
Database are being replicated using Fathom High Availability Replication
No database transactions being run after running rfutil dbname -C aimage new.
FACT(s) (Environment):
Fathom High Availability Replication 1.0A
OpenEdge Replication 10.x
Fathom Replication 2.0A
Fathom Replication 3.0A
UNIX
Windows
CAUSE:
This is expected behavior when no transactions have been run against the source database after the aimage new has been run. The lock will be removed as soon as the first have been flushed out of the new active extent.
FIX:
To work around this issue make sure a transaction has been run after the aimage new has been issued.