Kbase P65712: AI extent remains LOCKED after online backup on source replicated database
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/01/2009 |
|
Status: Unverified
SYMPTOM(s):
AI extent remains LOCKED after online backup on source replicated database
AI extent remains LOCKED after aimage extent switch
FACT(s) (Environment):
Fathom High Availability Replication 2.0A
Fathom Replication 2.0A
Fathom Replication 3.0A
UNIX
Windows
OpenEdge Replication 10.x
CAUSE:
This is an expected behaviour.
An extent remains "locked" until it is replicated by Fathom Replication.
There is an AI Transaction Log Record (AI Note) written to the current AI buffer (in shared memory) whenever an AI extent switch is performed. The buffer isn't being flushed to disk because it's not full. AI buffers are flushed to disk when they become full or when -Mf expires after a transaction end (eg. one transaction after the online backup/ai extent switch).
FIX:
Database activity is one way to cause the buffer to be flushed another way may be to do an explicit AI extent switch. This will cause the first AI buffer to be flushed unlocking the "old" extent, but the AI buffer for the new extent will not be flushed.
In order to "unlock" the extent do a dummy update on the source database.
You can also do manual ai extent switch, but in this case you will waste one ai extent.