Shulou(Shulou.com)06/01 Report--

Today, there is a development of students sent a problem, in the implementation of the program when the ora-01000 error, so the next study.

I found some posts on the Internet and looked at them. The links were:

http://blog.csdn.net/msdnchina/article/details/49755025

To some extent, ora-01000 blocks services. It should be that after the number of cursors opened in a session exceeds open_cursors, the session cannot provide services to the outside world.

From:

IF: How to Find SQLsCausing ORA-1000 (File ID 2014381.1)

1. Check the open cursor status of each session using sql as follows:

SELECT s.sid, s.serial#, s.username, a.value "OPEN CURSOR COUNT"

FROM v$sesstat a, v$statname b, v$session s

WHERE a.statistic# = b.statistic#

AND s.sid=a.sid AND b.name = 'opened cursors current'

AND s.username IS NOT NULL

ORDER BY a.value desc;

2. Check the open cursor of suspicious session, get the sid of open cursor high from the previous step, and bring in sql below.

SELECT sid ,sql_text, user_name, count(*) as "OPEN CURSORS"

FROM v$open_cursor

WHERE sid IN ($SID)

GROUP BY sid ,sql_text, user_name;

Note that the above script can only look at the database of current, and cannot analyze the database of the past time period (such as yesterday morning). Because v$open_cursor has no corresponding dba_hist view.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.