Re: Why event "global cache lock open x " wait forever?

Advice so far doesn't make a lot sense for me.

Version 8.05 isn't supported now for a very long time. Think about upgrading to a supported release.

First thing is to figure out if it is slow or actually hanging. To check that enable event 10046 level 8 and look in the trace file if it is stuck or simply slow.

The wait event global cache open x means that we are trying to open a new lock in exclusive mode. Unfortunately you didn't mention p1 and p2 which is the fileno and the block no.

Next step is to figure out which kind of class the object belongs to and how many locks/resources are configured for that file. This also depends on what kind of locking you are using (hash or dba locking)

You might check the parameter gc_file_to_locks

Regards
Steve

melocy_at_21cn.com (melocy) wrote in message news:<92A2664ABmelocy21cncom_at_130.133.1.4>...
> Evironment:2 * RS6000 AIX4.3.2 Oracle805 OPS(db1,db2)
> on db2,one transaction is that:
>
> set transaction use rollback segment rbig;
> delete from aaa.t1;
> insert into aaa.t1 select * from bbb.t1;
> commit;
>
> WHEN execute statement "Insert into ....",
> process hang.
> query v$session_wait,event is "global cache lock open x "
> query v$session_event,event "global cache lock open x"
> total_waits is adding continually and total_timeouts is adding too.
>
> Help me ,Pls.
> Thx.
Received on Thu Oct 10 2002 - 20:17:49 CDT