Understanding errors on LCR

Question

Hello all. Please, bear with me:
I have a doubt about how LCRs are created when an error has occurred. For example, when I see the errors I get through enterprise manager on the apply process, I see an LCR created with a message count of two, caught error 1403. But when I see the content of this LCR, I see 1403 happened on UPDATE (expected) but it DOES ALSO happened on an INSERT statement. Therefore, I wonder, how can a 1403 happened on an insert.
I wonder how can I avoid this? I mean, I cannot apply the insert (in this case) because of the LCR containing an UPDATE statement that is failing. Can I somehow reduce the number for message within an LCR? Or how can I do this to avoid getting into this..
Thanks for everything!
For you to see, this is the content of the transaction (sorry for the long post):
SQL> set serveroutput on
SQL> exec print_transaction( '25.5.10498' );
----- Local Transaction ID: 25.5.10498
----- Source Database: DBSFB
----Error in Message: 1
----Error Number: 1403
----Message Text: ORA-01403: no data found
--message: 1
type name: SYS.LCR$_ROW_RECORD
source database: DBSFB
owner: SFB
object: AHMAH
is tag null: Y
command_type: UPDATE
old(1): CCU_MONED
0
old(2): CCU_OFICI
0
old(3): CCU_PRODU
0
old(4): CCUDIGVER
0
old(5): CCUNUMCUE
0
old(6): DCO_CONTA
0
old(7): DCO_MERCA
0
old(8): ESTADO
A
old(9): HCN_TRANS
0
old(10): HCNLINDSI
0
old(11): HCNLINHOY
13
old(12): HCNSINPOS
0
old(13): HCNTRAMAN
0
old(14): HCO_CAUSA
0
old(15): HCO_FICHA
SIN MICROFICHA
old(16): HCO_PODER
2
old(17): HCO_VINCU
0
old(18): HCOCAMTAR
1
old(19): HCOCIECUE
1
old(20): HCOCIRRET
1
old(21): HCOCKDEPDV
1
old(22): HCOCKGIRDV
1
old(23): HCOCUECAT
34
old(24): HCOCUEINA
1
old(25): HCODEPCHE
0
old(26): HCODEPEFE
0
old(27): HCODEPINC
1
old(28): HCOEJECUE
EJ-1
old(29): HCOENTEST
0
old(30): HCOESTADI
1
old(31): HCOESTCUE
1
old(32): HCOEXOATM
2
old(33): HCOPEREST
3
old(34): HCOREPLIB
1
old(35): HCORESCRE
1
old(36): HCORESCUE
1
old(37): HCORESDEB
1
old(38): HCORESDEP
1
old(39): HCORESRET
1
old(40): HCORETDEP
0
old(41): HCORETIRO
1
old(42): HCOSUCCUE
580
old(43): HCOTIPCUE
2
old(44): HCOTIPINA
0
old(45): HCOTRANFD
1
old(46): HCOUSOATM
0
old(47): HCOUSOFTRA
0
old(48): HCU_MONED
1
old(49): HCU_OFICI
580
old(50): HCU_PRODU
200
old(51): HCUDIGVER
7
old(52): HCUNUMCUE
3426
old(53): HFE_ACTIV8
0
old(54): HFE_INACT8
0
old(55): HFEAPECUE8
3032006
old(56): HFEBLOQUE8
0
old(57): HFECANCUE8
0
old(58): HFEEMBFIA8
0
old(59): HFEEMBNOR8
0
old(60): HFEESTPER8
15082008
old(61): HFEMINPER8
0
old(62): HFEPROMIN
20102008
old(63): HFEREAPER8
0
old(64): HFEULTACT8
0
old(65): HFEULTCAP8
6062008
old(66): HFEULTCIE8
20102008
old(67): HFEULTEST8
16082008
old(68): HFEULTPER8
3102008
old(69): HFEULTPOS8
20102008
old(70): HFEULTRET8
20102008
old(71): HFEULTTRA8
20102008
old(72): HINDEVMES
.14
old(73): HINDEVPAN
0
old(74): HINDEVPER
0
old(75): HINPAGCAP
0
old(76): HINPROPAN
11.73
old(77): HINPROPER
122.47
old(78): HMO_APERT
0
old(79): HMOATMDSI
0
old(80): HMOCOCKDV
0
old(81): HMOCREMES
0
old(82): HMOEFEDSI
0
old(83): HMOTOTDSI
0
old(84): HMOULTDEP
6000
old(85): HNO_CUENT
CORTORREAL PAULINO, RAMON
old(86): HNOSUBTIT
PN
old(87): HNULIBRET
0
old(88): HNULINPOS
0
old(89): HNUULTEST
2
old(90): HSA_AUTOR
0
old(91): HSA_PROTE
0
old(92): HSAATMHOY
0
old(93): HSACHEDSI
0
old(94): HSACHEHOY
0
old(95): HSACIERRE
0
old(96): HSADEPDSI
0
old(97): HSADEPHOY
0
old(98): HSAEFEHOY
1183.73
old(99): HSAEFEPER
104194.26
old(100): HSAEMBFIA
0
old(101): HSAEMBNOR
0
old(102): HSAFLOH1
0
old(103): HSAFLOH2
0
old(104): HSAFLOH3
0
old(105): HSAFLOH4
0
old(106): HSAFLOH5
0
old(107): HSAMINPAN
111.02
old(108): HSAMINPER
7044.2
old(109): HSANUMPER
75440.76
old(110): HSAPROANT
1123.68
old(111): HSAPROM01
3148.98
old(112): HSAPROM02
1332.21
old(113): HSAPROM03
486.42
old(114): HSAPROM04
1067.55
old(115): HSAPROM05
2400.85
old(116): HSAPROM06
892.54
old(117): HSAPROM07
9636.12
old(118): HSAPROM08
2133.02
old(119): HSAPROM09
2493.73
old(120): HSAPROM10
7591.08
old(121): HSAPROM11
1551.62
old(122): HSAPROM12
1072.84
old(123): HSAPROMIN
1183.73
old(124): HSAPROPAN
25147.34
old(125): HSAPROPER
6035.16
old(126): HSAREMCOB
0
old(127): HSARETH1
0
old(128): HSARETH2
0
old(129): HSARETH3
0
old(130): HSARETH4
0
old(131): HSARETH5
0
old(132): HSATOTAAY
0
old(133): HSATOTAYE
1183.73
old(134): HSATOTHOY
1183.73
old(135): HSATOTPAN
7044.2
old(136): HSATOTPER
25838.32
old(137): HSATOTRET
0
old(138): HSAULTEST
173.63
old(139): HSAULTPOS
1183.73
old(140): HSE_CLASE
1
old(141): HSE_IBANK
1
old(142): HSE_LIBTA
2
old(143): HSE_MENOR
0
old(144): HSE_TARJE
1
old(145): HSECERRAR
2
old(146): HSEMOVHOY
0
old(147): HSEPETEST
0
old(148): HSEPLANSO
2
old(149): HSEREPORT
1
old(150): HSETRANTO
2
old(151): HTO_COMIS
0
old(152): HTO_CRE01
24067.45
old(153): HTO_CRE02
23767.45
old(154): HTO_CRE03
22173.82
old(155): HTO_CRE04
24673.82
old(156): HTO_CRE05
22088.32
old(157): HTO_CRE06
22273.82
old(158): HTO_ULT01
0
old(159): HTO_ULT02
0
old(160): HTO_ULT03
0
old(161): HTO_ULT04
0
old(162): HTO_ULT05
0
old(163): HTO_ULT06
0
old(164): HTOPROMES
0
old(165): HVARETCAP
0
old(166): HVARETPAN
0
old(167): HVARETPER
0
old(168): SCO_IDENT
00111881652
old(169): SCOTIPIDE
6
old(170): SNU_DIREC
1
old(171): TSE_CLICO
2
new(1): CCUDIGVER
0
new(2): HCNLINHOY
13
new(3): HCNSINPOS
0
new(4): HCOESTCUE
1
new(5): HCORESCRE
1
new(6): HCORESDEB
1
new(7): HCORESRET
1
new(8): HCU_MONED
1
new(9): HCU_OFICI
580
new(10): HCU_PRODU
200
new(11): HCUDIGVER
7
new(12): HCUNUMCUE
3426
new(13): HFEBLOQUE8
0
new(14): HFEULTACT8
0
new(15): HFEULTPOS8
20102008
new(16): HFEULTTRA8
20102008
new(17): HMOCREMES
0
new(18): HMOEFEDSI
0
new(19): HNO_CUENT
CORTORREAL PAULINO, RAMON
new(20): HSA_AUTOR
0
new(21): HSA_PROTE
0
new(22): HSACHEHOY
0
new(23): HSAEFEHOY
1183.73
new(24): HSAEMBFIA
0
new(25): HSAEMBNOR
0
new(26): HSAFLOH1
0
new(27): HSAFLOH2
0
new(28): HSAFLOH3
0
new(29): HSAFLOH4
0
new(30): HSAFLOH5
0
new(31): HSATOTHOY
1183.73
new(32): HSAULTPOS
1183.73
new(33): HSE_LIBTA
2
new(34): HSE_TARJE
1
new(35): HSECERRAR
2
new(36): HSEMOVHOY
1
new(37): HSEREPORT
1
new(38): SCO_IDENT
00111881652
new(39): SCOTIPIDE
6
--message: 2
type name: SYS.LCR$_ROW_RECORD
source database: DBSFB
owner: SFB
object: AAATR
is tag null: Y
command_type: INSERT
new(1): ACO_CAUSA
167
new(2): ACO_CONCE
2
new(3): ACU_MONED
1
new(4): ACU_OFICI
580
new(5): ACU_PRODU
200
new(6): ACUDIGVER
7
new(7): ACUNUMCUE
3426
new(8): ANU_TARJE
new(9): ANUBONCHE
0
new(10): DCO_OFICI
220
new(11): DCO_TERMI
0
new(12): DCO_TRANS
23
new(13): DCO_USUARI
REPACA0763
new(14): DCODEBCRE
2
new(15): ESTADO
A
new(16): TCO_FLOTA
0
new(17): TDIAPLANT
0
new(18): TFE_REAL8
21102008
new(19): TFE_TRANS8
21102008
new(20): TFETRAREL
18921
new(21): THO_TRANS
18254913
new(22): TNU_REVER
0
new(23): TNU_TRANS
4211
new(24): TNUDOCTRA
4211
new(25): TSE_AUTOR
0
new(26): TSE_REVER
2
new(27): TSE_SUPER
2
new(28): TSEDIAANT
2
new(29): TSEPOSTEO
1
new(30): TVA_MOVIM
10673.82
new(31): TVACHEHOY
0
PL/SQL procedure successfully completed.
SQL>

Answer 1

Hello
Usually when a transaction happens on the source database, all the required LCRs (for tables which has rules configured) will be captured as part of the same transaction. Each LCR has to be executed in the same order within a transaction. Now if an INSERT happens first followed by an UPDATE on the source, when it gets applied on the target, it would be applied only if the INSERT and UPDATE are successful. If INSERT fails with an ORA-00001 eventhough the UPDATE works or if the INSERT works fine and the UPDATE fails with ORA-01403 then the entire transaction would be moved to the apply error queue. None of the LCRs in this transaction will be applied until we correct the problem that happened in one of the LCR.
You can find out which statement has failed in a transaction from the MESSAGE_NUMBER column in DBA_APPLY_ERROR:
SELECT APPLY_NAME,LOCAL_TRANSACTION_ID,SOURCE_DATABASE,MESSAGE_NUMBER,MESSAGE_COUNT,ERROR_NUMBER
FROM DBA_APPLY_ERROR;
How can we apply the non-failing LCRs:
You need to manually execute the LCRs which are not failing. This can be done using a PL/SQL Block which will traverse through the error queue. A sample procedure is below:
declare
     txnid varchar2(80);
     lcr sys.lcr$_row_record;
     msgno number;
begin     
     --for message 2
     msgno:=2;
     txnid:='25.5.10498';
     lcr:=dbms_apply_adm.get_error_message(msgno, txnid);
     --to apply the message 2
     lcr.execute();
     commit;
end;
The script can be modified and customized to get all the non-failing LCRs by combining DBA_APPLY_ERROR view in the above. Once all the non-failing messages are applied, if you want, you can purge the transaction from the error queue using:
EXECUTE DBMS_APPLY_ADM.DELETE_ERROR('25.5.10498');
Hope this helps.
Thanks,
Rijesh