Re: doubt about sga query

From: jchiappa <jchiappaNOjcSPAM_at_bbvabrasil.com.br.invalid>
Date: 2000/08/05
Message-ID: <080d3f23.a234b73c@usw-ex0105-034.remarq.com>#1/1

Nope, the problem is not the query : see the select * next :

SQL*Plus: Release 3.3.4.0.0 - Production on Sat Aug 5 21:10:50 2000

Enter password:

Connected to:
Oracle7 Server Release 7.3.4.5.0 - Production With the distributed and parallel query options PL/SQL Release 2.3.4.5.0 - Production

sys_at_prod::SQL>select * from v$sgastat;

NAME                            BYTES
-------------------------- ----------
free memory                 101929556
miscellaneous                  222228
fixed_sga                       38992
db_block_buffers             90112000
log_buffer                    1048576
LCCMD SGA Table                 13832
VIRTUAL CIRCUITS               590220
PLS non-lib hp                   2096
client/slave fibs               56000
latch nowait fails or sle       10320
db_block_multiple_hashcha      594108
fixed allocation callback         512
node map                        16384
db_block_hash_buckets         4021208
PL/SQL DIANA                   253580
enqueue_resources             3600000
SEQ S.O.                        71040
DML locks                      162000
log_buffer                      16384
gc_*                            90728
transactions                   234240

NAME                            BYTES
-------------------------- ----------
enqueue_hash                    13740
enqueue_locks                  361088
PL/SQL MPCODE                  149140
dictionary cache              5463684
event statistics               699300
table definiti                    600
character set memory            21456
messages                        85952
library cache                15176972
distributed_transactions-       50592
sql area                      6803832
processes                      348000
sessions                       885780
ktlbk state objects            163480
transaction_branches            87552

36 rows selected.

> I think that it is a bug in the sql creating the v$ view
(i.e., the text should be "log buffer memory" or something in this way, and it was truncated in the view v$).

Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free!
http://www.keen.com Received on Sat Aug 05 2000 - 00:00:00 CDT