about "cursor: pin S wait on X" wait event.

hi all:

Recently "cursorin S wait on X" wait event troubles me.
I have two Database Server for a website. Everynight, Server A push
new data to Server B by one way. Because some security reason, Server
B can not "pull" data from Server. So, I using following query to
insert data to Server B:

insert into table_a-at-ServerB
select * from table_on_server_a;

That is: I create a Database link on Server A for Server B .
I running this query on Server A without any problem by means of
sqlplus scribe. But when I put these code on a perl program, system
hunging on this query. I found system issues ""cursor: pin S wait on
X" wait event for this query. Then, I put these code into a
procedure, and running this procedure on sqlplus, system still hunging
there.

Any come cross this problem? Can u help me?

Details:
Server A:Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 -
64bit
OS:windows server 2003 64bit.

Server B:Oracle9i Enterprise Edition Release 9.2.0.1.0
OS:windows server 2000 32bit

thank you!

Havel

Subject: Bug 5907779 - Self deadlock hang on "cursor: pin S wait on
X" (typically from DBMS_STATS)
Note:5907779.8

a bug on 10.2.0.3.

"Helma" schreef in bericht
news:557bdb59-e225-4844-9b5c-96e897673ecb-at-r15g2000prh.googlegroups.com...
> Subject: Bug 5907779 - Self deadlock hang on "cursor: pin S wait on
> X" (typically from DBMS_STATS)
> Note:5907779.8
>
> a bug on 10.2.0.3.

In spite of the docs, we see a lot of "cursor: pin S wait on X" wait events
occurring in a 10.2.0.4 Database as well, causing (according to RDA/AWR reports)
the main portion of out wait events.
We are looking at it right now, will report back!

Shakespeare

On Aug 27, 2:09 pm, "Shakespeare" wrote:
> "Helma" schreef in berichtnews:557bdb59-e225-4844-9b5c-96e897673ecb-at-r15g2000prh.googlegroups.com...
>
> > Subject: Bug 5907779 - Self deadlock hang on "cursor: pin S wait on
> > X" (typically from DBMS_STATS)
> > Note:5907779.8
>
> > a bug on 10.2.0.3.
>
> In spite of the docs, we see a lot of "cursor: pin S wait on X" wait events
> occurring in a 10.2.0.4 Database as well, causing (according to RDA/AWR reports)
> the main portion of out wait events.
> We are looking at it right now, will report back!
>
> Shakespeare

I always see the notes on Mtealink for DBMS_STATS, but on 10.2.0.3 we
see it periodically for no *apparent* reason on a new three node
x86-64 cluster. We have seen up to five wall clock days of wait time
for this even in a half hour AWR period in the last month.

We haven't yet set the "super spy decoder ring" hidden parameter
(_kks_use_mutex_pin), but do have a sev 3 SR open to see if Oracle
recommends it.