| May you explain to me those error events? [message #409762] |
Tue, 23 June 2009 22:45  |
trantuananh24hg
Messages: 744
Registered: January 2007
Location: Ha Noi, Viet Nam
|
Senior Member |
|
|
Hi all!
Just a few minutes, I've got a trace file in udump, it contents information that I've never seen. Then, I post it at here, hope you help to explain to me.
$ cat vnp_ora_25085.trc
/u02/app/oracle/admin/VNP/udump/vnp_ora_25085.trc
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
ORACLE_HOME = /u02/app/oracle/oracle/product/10.2.0/NEO
System name: SunOS
Node name: database
Release: 5.10
Version: Generic_118833-33
Machine: sun4u
Instance name: VNP
Redo thread mounted by this instance: 1
Oracle process number: 125
Unix process pid: 25085, image: oracleVNP@database
*** 2009-06-24 08:42:34.504
*** SERVICE NAME:(VNP) 2009-06-24 08:42:34.504
*** SESSION ID:(353.8804) 2009-06-24 08:42:34.504
kksfbc: entering diagnosis mode for xsc:ffffffff7a46a800
CUR#188 XSC ffffffff7a46a800 CHILD#58 CI 0 CTX 0
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
Failed sharing : Privilage
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
Compilation environment difference Failed sharing : 0
Change in cursor environment
SQL pgadep:2 pgapls:1 user
*** 2009-06-24 08:46:18.543
CUR#188 XSC ffffffff7a46a800 CHILD#62 CI 59a2f75a8 CTX 0
$
Thank you very much!
|
|
|
|
| Re: May you explain to me those error events? [message #464082 is a reply to message #409762] |
Tue, 06 July 2010 03:52  |
suntrupth
Messages: 13
Registered: July 2010
|
Junior Member |
|
|
This is most likely an indication of increase in child cursors for the sampling SQLs
This will happen only if application SQLs are repeatedly hard parsed(either due to undersized shared pool or usage of literals) and the way to avoid it is by sizing shared pool correctly/using bind variables/using cursor_sharing.
Check the value of cursor_sharing
SQL> show parameter cursor_sharing
Check the sqls that were being executed when you observe the errors in the alert log.
SQL> SELECT * FROM V$SQL_SHARED_CURSOR WHERE address = '<parent cursor address>';
SQL> Select * from v$sql_bind_metadata where address = '<child cursor address>';
Thanks,
Suntrupth
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
