Salesforce

Replicated database shutdown after error 3773

« Go Back

Information

 
TitleReplicated database shutdown after error 3773
URL NameP155797
Article Number000132054
EnvironmentProduct: Fathom Replication
Version: 3.0A
Product: OpenEdge Replication
Version: 10.x, 11.x
OS: All supported platforms
Question/Problem Description
Replicated source database shutdown after error 3773 when -aistall is not in use when the current AI file is filled and there are no EMPTY AI files in sequence
Replication source database activity stalls when -aistall is in use and there are no available AI files to switch to
Steps to Reproduce
Clarifying Information
Error MessageCan'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)
Defect Number
Enhancement Number
Cause
This is expected behavior.

PROGRESS has tried to switch to the next after-image extent, but it is full.

  • The database server shuts down when the -aistall parameter has not been specified on startup.
  • The -aistall parameter causes the database server to hang until the next extent is backed up and marked empty. For further information refer to Article  What does -aistall do?   
Resolution
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 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. 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 to Articles: 3) Restart the target and source databases

If not in use, consider starting the source database with the -aistall startup parameter. This will allow the source database to continue run but no updates allowed until ai extents are made available. For further information refer to the methods outlined in the following Articles:
Workaround
Notes
Progress Articles:



 
Keyword Phrase
Last Modified Date11/20/2020 7:38 AM

Powered by