Hello,
I'm trying to find out what's causing this problem in one of the databases we have: Oracle 8.05/ Sun Solaris. Customers are using a front-end app where they access database via Forms built modules and run a number of reports. The problem is that occasionally they get errors, each time slightly different ones -- I'm still waiting to hear the exact error message as of this morning, but I'd like to find out whether this may be as simple as rasing the value of OPEN_CURSORS in init.ora. It's currently set to 350 (small size db). I'd raise it to 750 or 1000, but I'd like to see for myself what's causing the errors (may be increased usage, other factors...).
Anyways, part of this select's output is this:
SQLWKS> SELECT s.sid, s.value, t.name
2> FROM v$sesstat s, v$statname t
3> WHERE s.statistic# = t.statistic#
4> AND s.sid = 105;
SID VALUE NAME
---------- ---------- ----------------------------------------------------------------
105 33882 opened cursors cumulative
105 343 opened cursors current
I realize that there may be a number of implicit cursors that are used in the application which increase the likeness of this type of error happening. As you see, for this user "opened current cursors" is 343, but OPEN_CURSORS is set to 350. Besides looking into SQL as possible target for tuning, could it be that OPEN_CUROSRS is set too low for a front-end OLTP small sized DB?
Thank you very much!
Regards,
Viktor
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now
