RES: RES: Pin S wit on X
José Pitombeira <[email protected]>
| Newsgroups | gmane.linux.suse.oracle.general |
|---|---|
| Message-ID | <[email protected]> |
The correct link is http://www.dbform.com/wp-content/uploads/2007/09/sr6470259992.htm _____ De: [email protected] [mailto:[email protected]] Em nome de José Pitombeira Enviada em: quinta-feira, 3 de julho de 2008 13:52 Para: [email protected] Assunto: [suse-sles-e] RES: Pin S wit on X Thanks, lots of thanks four yours answers. I found a document that i thik will solve my problem. [email protected] Pitombeira _____ De: Peter Santos [mailto:[email protected]] Enviada em: quinta-feira, 3 de julho de 2008 11:00 Para: José Pitombeira Cc: [email protected] Assunto: Re: [suse-sles-e] Pin S wit on X Pitombeira You really need to provide more information, than just this wait event. What version of 10.2 are you on (10.2.0.1, 10.2.0.2, 10.2.0.3, or 10.2.0.4). Also if you provide an awr report that might help. Additionally, here are some possibly related bugs. 5907779 Self deadlock hang on "cursor: pin S wait on X" (typically from DBMS_STATS) - fixed in 10.2.0.4 Note: 402027.1 - Bug:5653007; 5485914: SELF DEADLOCK PROCESS WAITS ON ''Cursor: Pin S Wait On X'' Bug 6904068 High CPU usage when there are "cursor: pin S" waits - causes high CPU when waiting specifically on "cursor: pin S" Again, if you can provide more information, we might be able to help more. -peter José Pitombeira wrote: Hi, Could somebody help me with deal with PIN S WAIT ON X. This wait event has too high values and is impacting with my normal operation. SLES9 and Oracle 10GR2. Thanks, Pitombeira _______________________________________________ suse-sles-e mailing list [email protected] http://listx.novell.com/mailman/listinfo/suse-sles-e _______________________________________________ suse-sles-e mailing list [email protected] http://listx.novell.com/mailman/listinfo/suse-sles-e