Re: [Info-Ingres] unloaddb and E_US1068 Integer overflow detectedin query

Hi Marty,

Yes I've experienced this error too, it seems to be very hit and miss as
to what causes the error. I raised a ticket with Ingres Corp some time
ago and they said it was bug 117982, but they are yet to trace the
source of the error, below is the last correspondence from Ingres Corp
on the issue;

I've looked through the log and the output from inglogs and the short
answer is that it hasn't immediately highlighted where the cause can be
found. The contents of the log suggest that copydb is getting back from
Ingres a row of data referencing uninitialised memory. This could be
caused because at the time the query for all the tables was made,
another transaction was either part way through creating another table,
or deleting another table, or perhaps just modifying it. This would be a
bug of course, but I don't have very many clues as to where this could
be happening in the code. If you have any information about what other
processes may have been running at the same time please do post it in
the isuue. For instance are there any other processes creating or
deleting tables at the same time as the copydb is run? Is it possible to
identify from the list of tables in the log any missing table or tables
- and from this what process may have been deleting, adding or modifying
that table or tables?

One possible lead for me, a long shot though, is that the uninitialised
memory listed in the copydbg log looks like text, so I may be able to
deduce something from that text. Apart from that I'm going to need more
time to comb through the code that retrieves the table information and
check it for timing 'holes' where we could get transient data.

-----------------------------------------------------------------------------------------------------------

What Ingres Corp did do was provide me with a version of copydb that is
able to ignore the Integer Overflow error which seems to do the trick
until a permanent fix can be found.

Thanks

*Damien Owen*
Technical Team
Sandyx Systems
/email:/ damieno-at-sandyxsystems
/
/


Martin Bowes wrote:
>
> Hi All,
>
> I've got a situation where unloaddb will occassionally produce an error:
>
> INGRES UNLOADDB Copyright 2003 Ingres Corporation
>
> Unload directory is '/user/ingres/work.II/sharp_dev'.
>
> Reload directory is '/user/ingres/work.II/sharp_dev'.
>
> E_US1068 Integer overflow detected in query.
>
> The error is not reproducible.
>
> I have tried both binary and ascii unloads. I have tried recovering
> the database to moments just before the error is produced. And on all
> occassions the unload works perfectly well.
>
> There is nothing in the errlog to indicate what the problem might
> be….or that a problem occurred.
>
> I'm running II 2.6/0604 (int.lnx/00) + patch11814.
>
> OS: Red Hat Linux release 7.1 (Seawolf)
>
> I'm recoding some of the scripts where this problem has been observed
> to run 'set trace point sc924 4200' to see if I get lucky and actually
> capture a query at the next occasion.
>
> Has anyone had any experience of this problem and could provide a
> pointer or two? I note that cdi has a mention of a similar problem by
> Eoin in 2005, but I couldn't find a resolution to that issue.
>
> Martin Bowes
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Info-Ingres mailing list
> Info-Ingres-at-kettleriverconsulting.com
> http://www.kettleriverconsulting.com...fo/info-ingres
>


-------------------------------------------------------------------------------------------
This email and the files transmitted with it are meant solely for the use of the individual addressee named above. They may contain confidential and/or legally privileged information. If you are not the addressee or responsible for delivery of the message to the addressee, please delete it from your system and contact the sender right away. Sandyx Systems Ltd has taken steps to ensure that this email and any attachments are virus-free, but it remains your responsibility to confirm and ensure this.