From: "Chris Leonard" Newsgroups: comp.databases.oracle References: <39f5fc53.0302271648.4c12c84a@posting.google.com> Subject: Re: Question about DBMS_SHARED_POOL package Lines: 41 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: Date: Mon, 3 Mar 2003 10:08:10 -0600 NNTP-Posting-Host: 128.255.4.141 X-Trace: news.uswest.net 1046707691 128.255.4.141 (Mon, 03 Mar 2003 10:08:11 CST) NNTP-Posting-Date: Mon, 03 Mar 2003 10:08:11 CST DBMS_SHARED_POOL only operates on the following object types: packages, procedures, functions, types, triggers, sequences, and SQL cursors. I believe that, in spite of the name DBMS_SHARED_POOL, it only works with objects in the library cache (shared SQL and PL/SQL areas). Hope this helps! -- Cheers, Chris ___________________________________ Chris Leonard, The Database Guy http://www.databaseguy.com Brainbench MVP for Oracle Admin http://www.brainbench.com MCSE, MCDBA, OCP, CIW ___________________________________ "Mike" wrote in message news:39f5fc53.0302271648.4c12c84a@posting.google.com... > According to the Oracle docs purpose of the DBMS_SHARED_POOL package > is to allow access to the shared pool to display sizes of objects and > to "KEEP" objects to avoid shared pool fragmentation. > > From what I can determine this package primarily manipulates the > "Library Cache" for listing, pinning (KEEPING) objects. How are the > other components of the shared pool effected? I assume it must effect > the Dictionary cache also (or some other shared pool components) > otherwise the package would be called "DBMS_LIBRARY_CACHE.(KEEP|SIZE, > etc..) > > Just courious if anyone knows the details on this. > > Thanks!!! > Mike >