Replication Agent crashes applying the last ai extent

Replication Agent crashes when manually applying Locked AI extents to the target database with dsrutil -C applyextent
Manually applying ai extents from a mixture of archived sources with different naming conventions fails with a Memory Violation
After the failed dsrutil applyextent, accessing the database -RO while the target is still in Pre-Transition mode does not include transactional data from this ai extent

For AI Management (AIMGT) enabled databases:

• Applying archived extents and then the current BUSY extent copied directly from the source database fails with a memory violation
• Applying archived extents and then non-archived ai extents from the source database fails with a memory violation
• Applying archived extents from archive directories (-aiarcdir) with different folder depths fails with a memory violation

For AI files managed by scripts, applying renamed os copied extents and the current BUSY extent copied directly from the source database fails with a memory violation

Stack trace from rpagent reads:
rpSET_DBExitCallBack()
dbExit()
dsmFatalMsgnCallBack()
rlaiswitch()
rlaixtn()
rlwrite()
rlputnote()
rlaiApplyNote()
dsaAIApplyNote()
rpNOT_ProcessNoteBlock()
rpAPY_ApplyExtent()
rpAGT_AgentLoop()
Replication_Agent()

Stack trace from rpagent reads:

Applying only extents that were archived to one archive directory(-aiarcdir)  by the AI daemon succeeds.
Applying only ai extents that were copied directly from a source database succeeds.
Applying ai extents with the same naming convention succeeds.

 

The ai extent name is not null terminated. This leads to the extent name containing characters from the previous applyextent operation by the agent.

Example:

$   dsrutil target -C applyextent DR~db~source.20160109.091330.00000091.source.a19

The OpenEdge Replication Agent is being instructed to apply after-image extent /DR/db/DR~db~source.20160109.091330.00000091.source.a19. (13992)
         The Replication Agent has successfully applied the after-image extent /DR/db/DR~db~source.20160109.091330.00000091.source.a19.

$   dsrutil target -C applyextent source.a20

The OpenEdge Replication Agent is being instructed to apply after-image extent /DR/db/source.a20ce.20160109.091330.00000091.source.a19. (13992)
The Replication Agent has successfully processed 0 after-image blocks from the after-image extent /DR/db/ source.a20ce.20160109.091330.00000091.source.a19. (14003)

Upgrade to OpenEdge 11.7.0 where Agent error handling was improved and the AI extent name is null terminated allowing variable length ai extents names to be used when manually applying multiple extents to the target database.

When multiple ai extents need to be manually applied to the target database with DSRUTIL -C applyextent:

1. Modify the ai extent names to be applied so that their names are all equal in length, or
2. The ai filename increases in length when a name-change of the ai file is realised in the order in which they are applied.

Progress Article: 

What is DSRUTIL applyextent?   ​