some problems with the replication

[Andy K]

Hi ,

Finally i was able to setup my replication process between two
databases .

For those who were not following my story , i was trying to setup a
replication between two databases on different linux server (RH 7.3)
for UDB 7.x .

I did the capture with a : asnccp mong warm

and I did an apply with a : asnapply QUAL1 mongtest

the db2instDBNAMESRC.CCP for the source went well . Here is the log :

2005-06-27-13:28:22 ASN0000S: INTERNAL ERROR OCCURRED FOR MESSAGE
NUMBER ASN0105I. ITS SUBSTITUTION FIELDS ARE Pruning Routine Entered .
Looking for Eligible Data to Prune from CD tables . THE RETURN CODE IS
0.

2005-06-27-13:28:24 ASN0000S: INTERNAL ERROR OCCURRED FOR MESSAGE
NUMBER ASN0100I. ITS SUBSTITUTION FIELDS ARE . THE RETURN CODE IS 0.

2005-06-27-13:28:24 ASN0000S: INTERNAL ERROR OCCURRED FOR MESSAGE
NUMBER ASN0103I. ITS SUBSTITUTION FIELDS ARE DBNAMESRC, WARM
STARTSEQ=000000000002E458ECB0, , PRUNE. THE RETURN CODE IS 0.

then i did an apply : asnapply QUAL1 mongtest

005-06-27-13:28:31 ASN1000S: INTERNAL ERROR OCCURRED FOR MESSAGE NUMBER
ASN1045I. ITS SUBSTITUTION FIELDS ARE MONG. THE ERROR CODE IS 034907.2.

It seems that my replication was finally done .

I setup the scheduler for continuous replication (sorry the interface
is not in english and i have a hard time trying to translate some
terms) which means the replication would take place on the target
database as soon as it is written in the source database .

I just mention that the src database is full of data .

So after I start the replication , instead of doing a full refresh on
the target database , db2 began to write plenty of logs on my target
server (in the directory where I launch the apply program) .

The logs began to fill all the space from that folder until it is full
..

I think that those logs are full of data but why that much logs and
more important why the data are not written in the target database ?

Yes my target database is empty (arf!)

Does anyone has an answer .

TIA ,

Andy the beginner in DB2 .

ps1 : here is a sample of my logs name (QUAL is my subscription name ):

QUAL1.000 QUAL100231.LOB QUAL100463.LOB QUAL100695.LOB
QUAL100926.LOB QUAL101158.LOB
QUAL100000.LOB QUAL100232.LOB QUAL100464.LOB QUAL100696.LOB
QUAL100927.LOB QUAL101159.LOB

ps2 : what is inside is binary stuff ( i think it is irrelevant) ...

ps3 : The log is activated on the source database with logretain =
recovery
and not on the target . It is weird because the log are not written and
the path to log files .

[Andy K]

Hi ,

Btw here is my trace file for the apply part :

It is odd because my transaction log are quite big 8mo each with 5 plus
3 secondary .

So what do you think ?

Or another kind of error ?

regards ,

Apply program compiled at 05:22:18 on Apr 16 2001 (Level 70109z)
MSGF: Did not get NLS message
SQLCA is
00000000 53514C43 41202020 FFFFFF88000000
3CFFFFFFFCFFFFFFFFFFFFFFFF SQLCA .....ü..
00000010 00002020 20202020 20202020 20202020 ..
00000020 20202020 20202020 20202020 20202020
00000030 20202020 20202020 20202020 20202020
00000040 20202020 20202020 20202020 20202020
00000050 20202020 20202020 53514C52 49495352 SQLRIISR
00000060 09FFFFFFD5FFFFFFFFFFFFFFFF 09000000 00000000 00000000
..Õ..............
00000070 00000000 00000000 20202020 20202020 ........
00000080 20202035 37303131 57011
*** SQL ERROR ***: SQL0964C The transaction log for the database is
full. SQLSTATE=57011

AINS: sqlda for UILINSRTSTMT SLCTTGTCOLS
sqldaid:
00000000 00000000 00000000 ........
sqldabc: 1952
sqln: 44
sqld: 14
SQLVAR[0].sqltype: 484
SQLVAR[0].sqlind: 0,
SQLVAR[0].sqllen: 10,
sqlvar[0].sqldata:
00000000 00000074 00FFFFFF8C ...t..
SQLVAR[0].sqlname.length: 2
sqlvar[0].sqlname.data:
00000000 4944 ID
SQLVAR[1].sqltype: 449
SQLVAR[1].sqlind: 0,
SQLVAR[1].sqllen: 100,
sqlvar[1].sqldata:
00000000 02003230 00000000 00000000 00000000 ..20............
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 00000000 00000000 ................
00000040 00000000 00000000 00000000 00000000 ................
00000050 20FFFFFFD51242 FFFFFF99060000 00000000 00000000
Õ.B............
00000060 00000000 ....
SQLVAR[1].sqlname.length: 14
sqlvar[1].sqlname.data:
00000000 54595045 5F455645 4E454D45 4E54 TYPE.EVENEMENT
SQLVAR[2].sqltype: 453
SQLVAR[2].sqlind: -1,
SQLVAR[2].sqllen: 10,
SQLVAR[2].sqlname.length: 7
sqlvar[2].sqlname.data:
00000000 434F554C 455552 COULEUR
SQLVAR[3].sqltype: 449
SQLVAR[3].sqlind: 0,
SQLVAR[3].sqllen: 100,
sqlvar[3].sqldata:
00000000 0C007472 616E736D 69737369 6F6E5F70 ..transmission.p
00000010 6C616E6E 696E675F 74726176 61696C00 lanning.travail.
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 00000000 00000000 ................
00000040 00000000 00000000 00000000 00000000 ................
00000050 00000000 00000000 00000000 00000000 ................
00000060 00000000 ....
SQLVAR[3].sqlname.length: 14
sqlvar[3].sqlname.data:
00000000 41435449 4F4E5F52 45414C49 5345 ACTION.REALISE
SQLVAR[4].sqltype: 449
SQLVAR[4].sqlind: 0,
SQLVAR[4].sqllen: 500,
sqlvar[4].sqldata:
00000000 5D004465 6D616E64 65206465 20646576 ..Demande de dev
00000010 69732066 6F75726E 69737365 75722028 is fournisseur .
00000020 36323039 3730202D 20763129 20706F75 620970 . v1. pou
00000030 72206C65 20747261 7661696C 20313030 r le travail 100
00000040 78313730 20206475 2070726F 6A657420 x170 du projet
00000050 72656170 70726F20 66657672 69657254 reappro fevrierT
00000060 20455420 4C454146 4C45544C 45544553 ET LEAFLETLETES
00000070 2031352F 30344520 4D415253 2056454C 15.04E MARS VEL
00000080 4F4C414E 444E5452 45452032 20203235 OLANDNTREE 2 25
00000090 2F303820 76697369 74652D20 3245203A .08 visite. 2E .
000000A0 20303938 37203033 30656E74 696F6E30 0987 030ention0
000000B0 37000000 00000000 00000000 00000000 7...............
000000C0 00000000 00000000 00000000 00000000 ................
000000D0 00000000 00000000 00000000 00000000 ................
000000E0 00000000 00000000 00000000 00000000 ................
000000F0 00000000 00000000 00000000 00000000 ................
00000100 00000000 00000000 00000000 00000000 ................
00000110 00000000 00000000 00000000 00000000 ................
00000120 00000000 00000000 00000000 00000000 ................
00000130 00000000 00000000 00000000 00000000 ................
00000140 00000000 00000000 00000000 00000000 ................
00000150 00000000 00000000 00000000 00000000 ................
00000160 00000000 00000000 00000000 00000000 ................
00000170 00000000 00000000 00000000 00000000 ................
00000180 00000000 00000000 00000000 00000000 ................
00000190 00000000 00000000 00000000 00000000 ................
000001A0 00000000 00000000 00000000 00000000 ................
000001B0 00000000 00000000 00000000 00000000 ................
000001C0 00000000 00000000 00000000 00000000 ................
000001D0 00000000 00000000 00000000 00000000 ................
000001E0 00000000 00000000 00000000 00000000 ................
000001F0 00000000 ....
SQLVAR[4].sqlname.length: 12
sqlvar[4].sqlname.data:
00000000 4F424A45 545F4143 54494F4E OBJET.ACTION
SQLVAR[5].sqltype: 449
SQLVAR[5].sqlind: 0,
SQLVAR[5].sqllen: 100,
sqlvar[5].sqldata:
00000000 04003139 35393000 00000000 00000000 ..19590.........
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 00000000 00000000 ................
00000040 00000000 00000000 00000000 00000000 ................
00000050 00000000 00000000 00000000 00000000 ................
00000060 00000000 ....
SQLVAR[5].sqlname.length: 11
sqlvar[5].sqlname.data:
00000000 52455350 4F4E5341 424C45 RESPONSABLE
SQLVAR[6].sqltype: 393
SQLVAR[6].sqlind: 0,
SQLVAR[6].sqllen: 26,
sqlvar[6].sqldata:
00000000 32303034 2D30322D 31382D31 352E3334 2004.02.18.15.34
00000010 2E33352E 32313130 3030 .35.211000
SQLVAR[6].sqlname.length: 4
sqlvar[6].sqlname.data:
00000000 44415445 DATE
SQLVAR[7].sqltype: 449
SQLVAR[7].sqlind: 0,
SQLVAR[7].sqllen: 100,
sqlvar[7].sqldata:
00000000 04003432 38313000 00000000 00000000 ..42810.........
00000010 00000000 00000000 00000000 00000000 ................
00000020 00000000 00000000 00000000 00000000 ................
00000030 00000000 00000000 00000000 00000000 ................
00000040 00000000 00000000 00000000 00000000 ................
00000050 00000000 00000000 00000000 00000000 ................
00000060 00000000 ....
SQLVAR[7].sqlname.length: 18
sqlvar[7].sqlname.data:
00000000 50524F46 494C5F44 45535449 4E415441 PROFIL.DESTINATA
00000010 4952 IR
SQLVAR[8].sqltype: 485
SQLVAR[8].sqlind: -1,
SQLVAR[8].sqllen: 1,
sqlvar[8].sqldata:
00000000 00 .
SQLVAR[8].sqlname.length: 18
sqlvar[8].sqlname.data:
00000000 414C4552 54455F4D 41494C5F 454E564F ALERTE.MAIL.ENVO
00000010 5945 YE
SQLVAR[9].sqltype: 485
SQLVAR[9].sqlind: 0,
SQLVAR[9].sqllen: 1,
sqlvar[9].sqldata:
00000000 1C .
SQLVAR[9].sqlname.length: 6
sqlvar[9].sqlname.data:
00000000 50555247 4545 PURGEE
SQLVAR[10].sqltype: 485
SQLVAR[10].sqlind: 0,
SQLVAR[10].sqllen: 10,
sqlvar[10].sqldata:
00000000 00000040 063C ......
SQLVAR[10].sqlname.length: 12
sqlvar[10].sqlname.data:
00000000 49445F4F 50455241 54494F4E ID.OPERATION
SQLVAR[11].sqltype: 485
SQLVAR[11].sqlind: 0,
SQLVAR[11].sqllen: 10,
sqlvar[11].sqldata:
00000000 00000620 FFFFFF970C ... ..
SQLVAR[11].sqlname.length: 6
sqlvar[11].sqlname.data:
00000000 49445F44 4F43 ID.DOC
SQLVAR[12].sqltype: 453
SQLVAR[12].sqlind: 0,
SQLVAR[12].sqllen: 26,
sqlvar[12].sqldata:
00000000 31303737 31313438 37353233 33202020 1077114875233
00000010 20202020 20202020 2020
SQLVAR[12].sqlname.length: 9
sqlvar[12].sqlname.data:
00000000 54494D45 5354414D 50 TIMESTAMP
SQLVAR[13].sqltype: 449
SQLVAR[13].sqlind: -1,
SQLVAR[13].sqllen: 100,
SQLVAR[13].sqlname.length: 14
sqlvar[13].sqlname.data:
00000000 4E4F4D5F 52454D50 4C414341 4E54 NOM.REMPLACANT
AINS: Insert failed. errcode is 7E0107. sqlstate is 57011. sqlcode is
-964