↪ replying to Wahyu Cahyadi
Hi,
Execute onstat -g ses and you will see the memory consumption per session.
To see the last sql of a session, call onstat -g sql <sessionid>.
To identify which sql in particular leads to the memory usage, is not that
easy. It depends on
Multiple factors, e.g. if large sorts are used, if the application uses many
open cursors etc.
We once had a problem where a connection pool did not close statements and
the memory usage of some sessions
was lead to some 100 MB. It was not a single statement, but the problem that
a statement was not closed correctly.
Marcus
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Wahyu
Cahyadi
Sent: Monday, November 13, 2006 6:35 AM
To: ids@iiug.org
Subject: identify sql process/syntax that consumes bigg.... [7799]
Anyone can help me how to identify sql process/syntax that consumes biggest
resources.
thanks in advance
****************************************************************************
***
Forum Note: Use "Reply" to post a response in the discussion forum.