Re: A VLDB contest

Our largest database has following:

SQL> select *

     2   from v$sgastat
     3   where name like '%ASM%'
     4   order by bytes;

POOL           NAME                                              Bytes
------------------  ------------------------------------------
--------------------
shared pool   ASM rollback operations                       2592
shared pool   ASM map operations                            3360
shared pool   ASM file                                             19200
large pool      ASM map operations hashta              393216
shared pool   ASM extent pointer array            2.1131E+10

Do not have the ORA-4031 creeping syndrome on this database.

On 8/29/06, Kevin Closson <kevinc_at_polyserve.com> wrote:
>
>
> Does anyone actually have ASM "put to the test" as they say? Anyone
> have huge ASM extent pointer array areas within their shared pool? Anyone
> have "ORA-4031-creeping syndrome" ?
>
> For instance:
> select * from v$sgastat;
> POOL NAME BYTES
> ------------ -------------------------- ----------
> shared pool ASM extent pointer array 287097144
>
> Anyone see 1GB or more?
>
>
> Kevin Closson
> Chief Architect, Oracle Database Solutions
> PolyServe, Inc
> kevinc_at_polyserve.com
> *http://www.polyserve.com/oracle_consolidation.php*<http://www.polyserve.com/oracle_consolidation.php>
> *http://www.polyserve.com/oracle_rac_clusters.php*<http://www.polyserve.com/oracle_rac_clusters.php>
>
>
>

--
http://www.freelists.org/webpage/oracle-l