Kbase P155797: Replicated database shutdown after error 3773
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/11/2009 |
|
Status: Unverified
SYMPTOM(s):
Replicated database shutdown after error 3773
Can't switch to after-image extent it is full. (3773)
Database Server shutting down as a result of after-image extent switch failure. (5350)
Backup after-image extent and mark it as empty. (3774)
SYSTEM ERROR: mtlatch <latch-num>, holding <lock>. (3712)
The <source-or-target> database is crashing. Fathom Replication cannot continue. (10672)
The source database is crashing. Fathom Replication cannot continue. (10672)
Begin ABNORMAL shutdown code (2249)
FACT(s) (Environment):
Source database was not started with -aistall
All Supported Operating Systems
Progress 9.1x
OpenEdge 10.x
OpenEdge Replication
CAUSE:
This is expected behavior.
PROGRESS has tried to switch to the next after-image extent, but it is full.
The server shutsdown because the -aistall parameter has not been specified on startup. The -aistall parameter causes the server to hang until the next extent is backed up and marked empty.
FIX:
There is no need to disable replication. Depending on the current status of the ai extents will determine how to recover from this. The steps below details the steps of making existing or new ai extents available depending on the status of them.
1) Check for the status of the after-image files using "RFUTIL source -C aimage list"
2a) IF there are any FULL ai extents, archive (backup the file) them and marked these as empty executing "rfutil source -C aimage empty" for each ai file.
2b) If there were only LOCKED (except of course the current one BUSY) add more ai extents by running: "prostrct add source addai.st" where addai.st defines where the new ai files will be placed. and then run: "prostrct reorder ai source" to ensure that the EMPTY ai extents immediately follow the current BUSY ai extent.
IMPORTANT NOTE: This Option is only available in Progress 9.1E or Open Edge 10.0B and later, (with the exception of OpenEdge 10.1B 10.1B01 and 10.1B02. Please refer Progress Solution: P71887 )
3) restart the target and source databases
Consider start using -aistall startup parameter. This will allow the source database to continue run but no updates allowed until ai extents becomes available.