Alway 1 lock held?
Whenever you have a database open (i.e. sysmaster), then you will always
have an 'intent' lock on the database itself. This is to prevent some other
user from dropping the database while you are using it.
Intent lock are sharable, and are used to prevent an item from being removed
while it is in use. I'm guessing that is what you are seeing.
lachlan Dunlop wrote:
> Here we go....
>
> I have an Informix server 9.20 on Linux, SuSE 6.4.
>
> The database is configured with "unbuffered logging".
>
> When I go into dbaccess and execute "select * from customer;" I get a
> display of customers on file.
>
> Then in another shell window I run onmonitor -> status -> user threads.
> I see I have 1 lock held for my session. Why is this??
>
> Is there a way to get rid of this lock?? I don't want it!! I have been
> round and round trying different isolation levels and table locking
> levels.
>
> Thanks
>
> Lach
Here we go....
I have an Informix server 9.20 on Linux, SuSE 6.4.
The database is configured with "unbuffered logging".
When I go into dbaccess and execute "select * from customer;" I get a
display of customers on file.
Then in another shell window I run onmonitor -> status -> user threads.
I see I have 1 lock held for my session. Why is this??
Is there a way to get rid of this lock?? I don't want it!! I have been
round and round trying different isolation levels and table locking
levels.
Thanks
Lach