I need to see more details from the log. Like LogSQLReceived,
LogSQLTransformed.
Seems like the SQL statement is being truncated.
Current 12.6.1 version is 12.6.1 ESD#3. I don't know if you're using that
or not.
Also the entire log has the config props - you might want to report this to
Tech Support so we can get the details and see
if this is resolved with a patch or if it needs to be reported to
engineering.
-Paul
"S érgio Diogo" <S =?ISO-8859-1?B?6XJnaW8=?= Diogo> wrote in message
news:47fdcaf8.54c...@sybase.com...
Hi Paul,
Thanks Again for the quick answer....
the log has the follow output:
LogTargetActivity Transfer: Bulk Commit at row 248
LogTargetActivity Transfer: Bulk Commit at row 249
LogTargetActivity Transfer: Bulk Commit failed at row 249
LogClientMessages Error: 31063 Severity: 19 Transfer:
Failed: . <DCA>
LogTargetActivity Transfer failed.
LogTransferStatistics 262 0.078 0.188 0.000 0.266 249 0 0.000 Bulk
Transfer
LogTargetActivity 6256 NULL NULL ctlibDataSource::connect,
ct_connect did not succeed, CS_RETCODE = 0
<END>
Another weird thing is that I have my select something like:
transfer to '.....'; with replace into... ; select * from
..where ID=X or ID=Y
this returns 4 rows....
If BulkCommitCount is = 1 then no row is inserted because
of the "Transfer: Bulk Commit failed at row 2"
If BulkCommitCount is = 6 then DC returns a 4 row affected
but only the first two rows (where ID=X) are inserted on
Sybase.
If I change the select statement so I only choose the ID=Y
then the 2 rows that weren't inserted (when where clause had
both ID=X or ID=Y) are now inserted on Sybase.
Hope there is an explanation for this weird behaviour.
Thanks,
Best Regards,
Sérgio Diogo
> Hi Sergio,
>
> Do you have hte log output?
>
> What's the error?
>
> -Paul
>
>
> "S érgio Diogo" <S =?ISO-8859-1?B?6XJnaW8=?=
Diogo> wrote
> in message news:47fce0c0.421...@sybase.com...
> Hi All,
>
> I am using DC12.6.1 ESD#3 to transfer data from AS400 to
> Sybase.
>
> I have a weird situation when retrieving data from AS400.
>
> I select data from one table that fails to make bulk
> commit, but the way it fails is completely strange.
>
> If I put BulkCommitCount to 1, it fails on the second
> commit, but if I change the BulkCommitCount to 8, it will
> be able to insert all the rows.
>
> Any explanation about this?
>
> Thanks in advance.
> Sérgio Diogo
>
>
this was sent to Sybase Support that are now working on
it... so a next ESD will have this problem solved.
Thanks,
Sérgio Diogo