How Do I Recover from a Replicat Failure with Guardian Error 35?
Last updated on JANUARY 12, 2017
Applies to:Oracle GoldenGate - Version: 4.0.0
HP NonStop Itanium (Guardian)
HP NonStop S-series (Guardian)
When the Replicat fails because of an error 35, for a SQL target, the error message is displayed in this format:
2010-04-13 08:49:08 GGS ERROR 109 Error 0,35 (key 1) mapping \K2.$DATA19.TKAD
BPRD.TGL010T to \DV1.$DATA19.TKADBPRD.TGL010T in seqno 1311 at rba 946741027.
For an Enscribe target, the error message is displayed in the following format:
2007-01-25 11:37:30 GGS ERROR 103 Error 35 (key 'IC') mapping
\DEVEL.$DATA10.VRDATA.MERCFILE to \IDEVEL.$DATA10.VRDATA.MERCFILE at rba
53470100 in seqno 0.
In both cases, the underlying error being reported by Replicat is a Guardian error 35. This article discusses the causes for this error when reported by Replicat, and how to recover from it.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms