Consultor Eletrônico



Kbase P131890: Fathom replication agent is dying with error 1028 and 10428 indsaAIApplyNote
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   5/29/2008
Status: Unverified

FACT(s) (Environment):

All Supported Operating Systems
OpenEdge 10.1x
OpenEdge Replication 10.x
OpenEdge Fathom Category: Replication

SYMPTOM(s):

Fathom replication agent is dying with error 1028 and 10428 indsaAIApplyNote

Database <database name> is being replicated from database <database name> on host <host name>. (10392)

The Fathom Replication Agent <agent-name> is beginning Recovery Synchronization at block <block-number>. (10671)

The Fathom Replication Agent agent2 is beginning Recovery Synchronization at block 0. (10671)


Retry transaction point located at dbkey note type updctr . (6806)

Retry transaction point located at dbkey 0 note type 47 updctr 0. (6806)


Retry point located at dbkey note type updctr . (6807)

Retry point located at dbkey 0 note type 14 updctr 0. (6807)


SYSTEM ERROR: Rollforward Apply AI note, BKUPDCTR=<number>, note updctr=<number>. (1028)

SYSTEM ERROR: Rollforward Apply AI note, BKUPDCTR=14633, note updctr=14666. (1028)


area , dbkey , record type (8999)

Function <functionname> failed in <functionname> with error <error>. (10428)

Function dsaAIApplyNote failed in rpNOT_ProcessNoteBlock with error -30000. (10428)


Block processing ended in error at block <block-number> in area <area-number>. Fathom Replication cannot continue. (10495)

Block processing ended in error at block 1 in area 13. Fathom Replication cannot continue. (10495)

Unexpected error <error-code> returned to function <function-name>. (10504)

Unexpected error -30000 returned to function rpAGT_AgentLoop. (10504)


The Fathom Replication Agent <agent-name> is ending. (10506)

happens immediately after restoring the backup

CAUSE:

Performed an online backup after the backup used as the "source" for the target database is not allowed

FIX:

Do not perform additional online backups until the target database is up and running.