Đang chuẩn bị liên kết để tải về tài liệu:
Oracle Built−in Packages- P116

Oracle Built−in Packages- P116: Ah, for the good old days of Version 1.0 of PL /SQL! Life was so simple then. No stored procedures or functions and certainly no packages. You had your set of built−in functions, like SUBSTR and TO_DATE. You had the IF statement and various kinds of loops. With these tools at hand, you built your batch−processing scripts for execution in SQL*Plus, and you coded your triggers in SQL*Forms 3.0, and you went home at night content with a good day's work done. | Appendix A What s on the Companion Disk Any other character Cursor specified by address and hash value 12.2.2.2.1 Exceptions The UNKEEP procedure does not raise any package exceptions. It can raise the following Oracle exceptions if the name parameter does not resolve to a real object or an object of the proper type ORA-06564 Object object name does not exist. ORA-06502 PL SQL numeric or value error. 12.2.2.2.2 Restrictions Note the following restrictions on calling UNKEEP Oracle warns that the UNKEEP procedure may not be supported in future releases. The program does not assert a purity level with the RESTRICT_REFERENCES pragma. 12.2.2.2.3 Example This example releases the object pinned by the KEEP procedure see the example for KEEP earlier SQL BEGIN 2 3 4 SYS.DBMS_SHARED_POOL.UNKEEP SYS.STANDARD P END PL SQL procedure successfully completed. Usually an object is pinned into the shared pool for a reason so it is not likely that you would need to call UNKEEP regularly. However if large objects that have been pinned into the shared pool are definitely no longer needed then memory can be made available to the shared pool by executing UNKEEP on these objects. 12.2.3 Monitoring and Modifying Shared Pool Behavior You can monitor the behavior of objects in the shared pool with the SIZES procedure. You can modify that behavior with the ABORTED_REQUEST_THRESHOLD procedure. 12.2.3.1 The DBMS_SHARED_POOL.SIZES procedure The SIZES procedure displays objects including cursors and anonymous PL SQL blocks that are currently in the shared pool and that exceed the size in kilobytes specified by the minsize parameter. The program header follows PROCEDURE DBMS SHARED POOL.SIZES minsize IN NUMBER The minsize parameter specifies the minimum size in kilobytes of shared pool objects that are displayed. The program does not raise any package exceptions nor does it assert a purity level with the RESTRICT_REFERENCES pragma. 12.2.2 Pinning and Unpinning Objects 566 Appendix A What s on the