[Info-ingres] When is a readonly cursor not a read only cursor?

[Martin Bowes]

Answer: When its attached to a readonly database.

So having turned a database readonly I was somewhat surprised when all my perl DBI code connecting to it suddenly exploded. I have now developed some ESQL-C equivalent and doing a select dbmsinfo('initial_user'),... via a dynamically prepared query will fail at the front end with:
Error Code 33000:
Reason: E_LQ0080 Error in reading query or cursor internal identifier.
E_LC0022 Protocol data read failure.
    Found message GCA_TDESCR while reading message GCA_QC_ID, and read only
    0 bytes.

Exiting session because of communications failure.
E_SC0206 An internal error prevents further processing of this query.
    Associated error messages which provide more detailed information about
    the problem can be found in the error log, II_LOG:errlog.log

And in the errlog we see:
E_SC023B_INCONSISTENT_MSG_QUEUE      The GCA message queue for this session was inconsistent.
All messages for this session will be discarded.
E_QS001E_ORPHANED_OBJ   An orphaned Query Text object was found and destroyed during QSF session exit.
E_QS0014_EXLOCK         QSF Object is already locked exclusively.

I see a bug report in my immediate future.

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