[Info-ingres] E_LQ005D/E_LC0029 what the hell?

Martin Bowes martin.bowes at ctsu.ox.ac.uk
Fri Nov 13 09:42:21 UTC 2015


Hi All,

I have a perl DBI program accessing some databases which has been working perfectly well for some time. Today it started throwing errors E_LQ005D and E_LC0029. There is nothing of any consequence in the errlog. Has anyone got any ideas what it might be bitching about?

I've read the knowledge base on these errors and the one entry mentions problems with a table generated via a copy out/in. This is possibly relevant as the program prepares a GTT in one database and  transfers it to another GTT in another database. The copy is done using an ASCII copy out and copy in.

On the source database we execute:
declare global temporary table record_items as
select field_id from field where item_type = 30
on commit preserve rows with norecovery;

copy record_items(field_id = c0nl) into '/dbwork/II/record_fields.dat';

On the target database we then execute:
declare global temporary table record_items(field_id integer4 not null not default
) on commit preserve rows with norecovery;

copy record_items(field_id = c0nl) from '/dbwork/II/record_fields.dat';

This all proceeds without error.

The error is generated later when we use this gtt in a join as part of a select. This has been working perfectly well for a while. I can emulate the entire thing interactively using a sequence of terminal monitor connections.

Martin Bowes
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.planetingres.org/pipermail/info-ingres/attachments/20151113/ffb83e0d/attachment.html>


More information about the Info-ingres mailing list