- 论坛徽章:
- 0
|
使用Toad for Oracle Version 8.5.3 做的database health check,LOG 如下:
********************************************************************
*** CHORA_168.168.1.81 2010-8-24 15:04:01 ***
********************************************************************
~Time to Connect : 0 seconds.
~Database Version : 10.2.0.4.0
~Database Up Since : 12:04:10 ÏÂÎç, 8ÔÂ 18 2010
~Buffer Cache Hit Ratio : 99.8207
~Library Cache Miss Ratio : 0.3843
~Dictionary Cache Miss Ratio : 0.1009
[Shared Pool Usage] Query Failed! ORA-01476: divisor is equal to zero
[Archive Log Mode Info] Exec Time 0 seconds
~ Archiver : STARTED
~ Log Mode : ARCHIVELOG
! log_archive_start (init.ora param) = FALSE
[Archive Log Info] Exec Time 0 seconds
~ Average Log Switches Per Day : 16.78
~ Hard Drive Storage (in Mb) for this many archive logs : 5035.34
! Error using UTL_FILE to examine alert log!
! Error using UTL_FILE
! Possible causes:
! 1) You don't have privileges to execute the UTL_FILE package.
! 2) UTL_FILE_DIR initialization parameter does not include one of these lines:
! utl_file_dir=/oracle/oracle/admin/chora/bdump
! utl_file_dir=*
! 3) alert.log file name is not among the following:
! (if this is the case please inform Quest support)
! alert_chora.log
! choraalrt.log
! 4) No directory has been created for /oracle/oracle/admin/chora/bdump,
! or directory exists but privileges have not been granted for it.
[Redo Log Group Sizes and Quantities] Exec Time 0 seconds
~ Number of Log Groups : 3
! Number of Members per Log Group: 1
~ All redo log members are 300M in size.
[Rollback Segments with wait ratios > 1 %] Exec Time 0 seconds
~ None
[Objects with Mixed-Case Names] Exec Time 0 seconds
! Constraint PM.BIN$i/PSz/NAUU7gRAATIeq5IA==$0
! Constraint PM.BIN$i/PSz/NBUU7gRAATIeq5IA==$0
! Constraint PM.BIN$i/PSz/NCUU7gRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vAXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vBXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vDXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vEXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vFXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vGXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vHXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vIXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vJXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vKXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vLXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vMXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vNXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vOXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vPXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vQXrrgRAATIeq5IA==$0
! Constraint PM.BIN$ihQox7vRXrrgRAATIeq5IA==$0
! Constraint PM.BIN$il5tOzvBKJLgRAATIeq5IA==$0
! Constraint PM.BIN$il5tOzvFKJLgRAATIeq5IA==$0
! Constraint PM.BIN$il5tOzvHKJLgRAATIeq5IA==$0
! Constraint PM.BIN$il5tOzvKKJLgRAATIeq5IA==$0
! Constraint PM.BIN$il5tOzvMKJLgRAATIeq5IA==$0
! Constraint PM.BIN$jjr4P3vATfbgRAATIeq5IA==$0
! Constraint PM.BIN$jjr4P3vBTfbgRAATIeq5IA==$0
! Constraint PM.BIN$jjr4P3vCTfbgRAATIeq5IA==$0
! Constraint PM.BIN$jjr4P3vDTfbgRAATIeq5IA==$0
! Constraint PM.BIN$jnWHxRLAXRngRAATIeq5IA==$0
! Constraint PM.BIN$jnWHxRLBXRngRAATIeq5IA==$0
[Tables with > 5 % chained rows and > 500 total rows] Exec Time 0 seconds
~ None
[Table Partitions with > 5 % chained rows and > 500 total rows] Exec Time 0 seconds
~ None
[Segments with < 10% of extents remaining and (maxextents > 1)] Exec Time 0 seconds
~ None
[Segments with > 100 extents] Exec Time 0 seconds
! TABLE PM.CAPP_DOCHIST: 119 Extents
! TABLE PM.SC_PART_STOR: 122 Extents
! TABLE PM.SC_PART_STOR_BAK: 103 Extents
[Objects which can't extend because there is not
enough room in the tablespace] Exec Time 0 seconds
~ None
[Jobs] Exec Time 0 seconds
~ None
[redundant object privs with conflicting grant option] Exec Time 0 seconds
~ None
[Profiles that are not granted to any user] Exec Time 0 seconds
~ None
[Tablespace Fragmentation] Exec Time 0 seconds
~ A common set of extent sizes is a good way to reduce tablespace fragmentation.
~ Sometimes fragmentation can be improved with 'Alter tablespace <tblspace> coalesce'.
~ Tablespace fragmentation should not be a problem if you use locally managed tablespaces.
~
======================================================================
== TableSpace Name % # of # of ==
== Fragmented Extents Holes ==
======================================================================
! CH_PRODUCE 70 233 537
[Tablespaces with less than 10% free space] Exec Time 0 seconds
~ None
执行如下语句:
select tablespace_name,sqrt(max(blocks)/sum(blocks))*
(100/sqrt(sqrt(count(blocks)))) FSFI
from dba_free_space
group by tablespace_name
TABLESPACE_NAME FSFI
1 SYSTEM 41.29254342
2 CH_CONFIG 83.98414701
3 TOOLS 100
4 USERS 48.48849607
5 CHPM 84.05457089
6 FP 100
7 RTPM 66.86867479
8 CH_ASSIST 83.12858549
9 CH_FINISHED_PRODUCT 84.0035282
10 CH_MANHOUR 83.99584379
11 CH_PROVIDE 100
12 CH_SYS 83.82576125
13 RTINDEX 75.95682556
14 SYSAUX 53.60098083
15 UNDOTBS1 32.76250014
16 CH_FILE 70.42143689
17 CH_PRODUCE 12.58561501
18 SP_TECH 100
执行如下语句:
TABLESPACE_NAME CHUNKS MAX_CHUNK
1 SYSTEM 32 2627.9375
2 CH_CONFIG 2 372.9375
3 TOOLS 1 98.625
4 USERS 5 551.6875
5 CHPM 2 673.9375
6 FP 1 497.9375
7 RTPM 5 1560.625
8 CH_ASSIST 2 34.9375
9 CH_FINISHED_PRODUCT 2 60.9375
10 CH_MANHOUR 2 55.9375
11 CH_PROVIDE 1 445.875
12 CH_SYS 2 118.9375
13 RTINDEX 3 709.9375
14 SYSAUX 12 865.9375
15 UNDOTBS1 16 799.9375
16 CH_FILE 4 1548.9375
17 CH_PRODUCE 537 531.9375
18 SP_TECH 1 299.3125 |
|
免费注册
发表于 2010-08-24 19:03
