Here is an easy way to hang on to an Oracle instance due to an unhandled memory leakage. This problem sometimes
results from giving exessive abilities to common Oracle users in production databases. Keeping this memory leakage (or uncontrolled stack growth) problem in mind, administrators should be cautious about giving CREATE PROCEDURE privileges to users. This privilege is included in the RESOURCE role that also has the potential of uncontrolled access due to automatic UNLIMITED TABLESPACE granting. Another way to diminish the harm of breaking a production database is to use systematic profiles limiting DBMS resources usage by common users.
The following may be easily done in Oracle 9.2 running under Win32:
- Open Windows Task Manager to monitor processor load and memory usage
- Go to SQL*Plus and type the following:
connect sys/*** as sysdba startup nomount force declare function sin(x number) return number is begin return 1*sin(x); end; begin dbms_output.put_line(sin(1)); end; /
- See processor load and memory leakage in Task Manager
- The mount state of the instance was used just to show that the problem is with an Oracle instance, not with a database.
- This will also work with other users besides sys.
For More Information
- Feedback: E-mail the editor with your thoughts about this tip.
- More tips: Hundreds of free Oracle tips and scripts.
- Tip contest: Have an Oracle tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize -- submit your tip today!
- Ask the Experts: Our SQL, database design, Oracle, SQL Server, DB2, metadata, and data warehousing gurus are waiting to answer your toughest questions.
- Forums: Ask your technical Oracle questions--or help out your peers by answering them--in our active forums.
- Best Web Links: Oracle tips, tutorials, and scripts from around the Web.