Kbase P124750: LOCKED ai extents are not archived
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/12/2008 |
|
Status: Verified
SYMPTOM(s):
ai extents with LOCKED status are not archived
When ai extents are LOCKED, the aiarchiver doesn't archive these
aiarchiver continues to switch ai extents as per the setinterval n
AIMGT 6: Switched to ai extent . (3777)
source database eventually runs out of available ai extents to switch to
AIMGT 6: (3775) Can't switch to after-image extent D:\101B\WRK\repl\source\source.a1 it is full.
AIMGT 6: (3776) Backup ai extent and mark it as empty.
FACT(s) (Environment):
OpenEdge 10.1x
OpenEdge 10.2x
All Supported Operating Systems
CAUSE:
Bug# OE00154775
CAUSE:
LOCKED ai extents are not considered FULL in OpenEdge 10.1B and 10.1A.
FIX:
Upgrade to OpenEdge 10.1C where the aiarchiver will archive LOCKED extents.
NOTE: although the extents are archived, they are not marked as EMPTY until replication resumes and they have been fully processed against the target database. At this stage they will be marked EMPTY for re-use but not backed-up as they were backed up previously at the time they were first switched. Should replication not resume before all ai files in the sequence chain have been exhausted, the database with either shutdown or stall depending on if the -aistall parameter was set when the database was initially started.
In versions prior to OpenEdge 10.1C, when replication resumes and these LOCKED extents are processed to the target database and marked FULL, the aiarchiver daemon will archive these in sequence then mark them as empty.
RPLS 5: Unlocking after-image file <num> and locking ALL FULL after-image files beginning with file <num>. (11805)
AIMGT 6: After-image extent <name> has been copied to <name>. (13199)
AIMGT 6: Marked after-image extent EMPTY. (3789)
Until replication resumes in any OpenEdge 10.x version:
Change the aiarchiver interval or unset it with the value 0, to preserve ai extents until replication resumes:
$ rfutil source -C aiarchiver setinterval
or stop the aiarchiver deamon: rfutil source -C aiarchiver end
It may be necessary to add more ai extents to record the database activity.
If there is concern that the primary server will fail, these LOCKED ai extents can be manually archived with OS utilities in the meantime.
Once repilcation resumes, the aiarchiver deamon can be restared with the following command line:
$ _mprshut source -C aimgt -aiarcdir xxxx -aiarcinterval n [-aiarcdircreate]