Optimizedb errors E_LQ0040 & E_LC002B

Optimizedb errors E_LQ0040 & E_LC002B

Post by Richard Davi » Fri, 26 Nov 1999 04:00:00



Has anyone ever encountered the following errors during an Optimizedb?

E_LQ0040 Protocol read-failure on internal data.
    Execution of this query is stopped.
E_LC002B Read failure against pre-fetched data.
    The system encountered the end of the pre-fetched message stream.
    Expected to read XX bytes but read only YYY bytes from a GCA_TUPLES
    message.
(Where XX and YYY vary according to which table is being optimized)

I am working with CA Tech Support on this problem, but they are having
difficulty getting it to reproduce. (Even after I managed to produce a
test case which guarantees seeing it!)

Platform: SunOS spock 5.6 Generic_105181-15 sun4u sparc
SUNW,Ultra-Enterprise-10000
Ingres:     Ingres SPARC SOLARIS Version II 2.0/9808 (su4.us5/00) +
Patch 6183
Verifydb: Checks fine out on problem tables and system catalogs

[BTW I can reproduce this problem on Ingres II 2.0/9808 (base level +
all patches) and 2.5/00 (su4.us5/60) Beta]

Anyone??