Oracle errors when not logged in trigger #gciErrBadSessionId

Any GemConnect Oracle errors generated while the session is not yet logged
into GemStone (for example, problems loading liboraapi library using a
topaz loadua commnad) will generate a #gciErrBadSessionId error, rather
than a more helpful Oracle error.

Workaround:

Login to GemStone first, then attempt to load the GemConnect liboraapi
user action library. This should expose the underlying Oracle error
(typically, a problem finding the $ORACLE/lib directory).