Re: Long Transaction [1879]

#1

Quote:

The procedure is taking rows from a view, inserting them into a table and
then updating them. The table is used for reporting purposes and contains

about 60,000 rows in all, but only about 1000 rows are involved when the
procedure is run. The procedure runs fine for 3 months worth of data but
fails with error 458 (long trans) for longer time spans ie more rows.

Quote:

Have you checked to ensure that you do not have a cartesian product

somewhere in the intermediate results? This could be generating a lot of log
activity without producing a large result set. I have seen this many times
with Peoplesoft queries.

Quote:

3. Logfiles 99, Logsize 80MB

Don't know how big your db is, but this does not seem like a lot of

logspace.

Quote:

7. Other procedures work quite happily with lots of rows. Especially the
week-end routine which inserts data into the table.

This makes me even more suspicious of a problem with the stored procedure.

On the production server it seems that the oninit process is actually
killed when the procedure is run a second time and they have to reboot the

server. They obviously do want to try to reproduce this and so I cannot be
sure of this.

Quote:

Sounds to me like you should report this to tech support.

Mark

sending to informix-list

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Re: Long Transaction [1879]

comp.databases.informix comp.databases.informix

Re: Long Transaction [1879] - 09-16-2003 , 08:00 AM