Re: [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- From: "Roy Hann" <specially@xxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Nov 2005 20:08:23 -0000
<martin.bowes@xxxxxxxxxxxxx> wrote in message
news:mailman.1132666381.7510.info-ingres@xxxxxxxxxxxxxxxxxx
> Hi Dudes,
>
> I'm connecting to a STAR server ifrom an installation which has an
> ING_SYSTEM_SET specifying a:
> set lockmode session where maxlocks=100;
[snip]
> Anyone got any ideas? I cant see why the STAR server would give a
> monkeys about the lockmode statement, and why does it think its in a
> transaction already?
Maybe there is another day file, that starts a transaction?
Anyway, try changing ING_SYSTEM_SET to "commit; set lockmode session where
maxlocks=100". It is documented as only taking SET statements but in fact
it will take pretty much anything and the COMMIT will ensure you are not
mid-transaction.
Star cares about the lockmode when you have real tables in the star
database. Maybe it propagates the lockmode to the remote database sessions
too, but I've no idea.
Roy
.
- Follow-Ups:
- Re: [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- From: martin . bowes
- Re: [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- References:
- [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- From: martin . bowes
- [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- Prev by Date: Re: Recovery Server Stopped
- Next by Date: RE: [Info-ingres] abf 3gl function
- Previous by thread: [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- Next by thread: Re: [Info-ingres] Ingres/STAR, ING_SYSTEM_SET and set lockmode
- Index(es):