can you log database activities to a file? it might be
costly to do but logging SQLs to a file might give you
some idea on whats going on and what enteries cause
the sql to fail/miss. Also, are you catching SQL
errors? may be logging those to a file will help too
--- Troy Davis <troy@xxxxxxxxxxxxxxxxxx> wrote:
> Thank you for replying, but there's no evidence of
> any other statements
> failing, just the insertion of the article order
> data. I also turned on
> query logging on the server and inspected the logs
> the last three times
> this happened, there was no insert statements for
> the order data after
> each bug report. However, there were plenty of
> similar transactions
> before and after that happened successfully,
> including the insertion of
> ordering data.
>
> The other thing that confuses me is that it's not
> reproducible. It
> happens much less often than 1 in 10 times, probably
> 1 in 50 or 1 in
> 100.
>
> Thank You,
> Troy
>
> On Dec 29, 2004, at 3:58 PM, Jason Kretzer wrote:
> > Have you tried executing a 'Commit' to the
> database
> > before and after the insert? I know DB2 has this
> > problem even when autocommit is set to true.
> >
> > -Jason
>
>
> ---------
> You may unsubscribe from this mailing list
> by sending a blank email addressed to:
> users-unsubscribe@xxxxxxxxxx
>
> --
> Find additional help by sending a blank email
> addressed to:
> users-help@xxxxxxxxxx
>
>
|