Health Check Report for Oracle 10g Database

dbWatch ASwww.dbwatch.no

November 17, 2010 1:11:35 PM

Health check report for Oracle 10g database

The dbWatch Report displays data collected by the dbWatch tasks installed on the dbWatch Engine. The aim of this report is to

enable a DBA to identify bottlenecks in the database system, and provide the DBA with enough information to trace down the

critical objects. The different sections display tables and charts that visualize the current situation and the trend over time for

the database. There are sections for space usage analysis, memory analysis, growth analysis, configuration and parameter

analysis, activity pattern analysis, error logs etc. As a DBA this report gives you the tool you need to perform long term

configuration and maintenance to secure that your database system runs at an optimal level.

Page 2


Databases The report encompasses information from the following databases:

- oracle 10g

Page 3


1. Status overview

1.1. Status on check informationThe following table lists basic information on the installed checks.

1.2. Last 10 Warnings/AlarmsThe following table lists the 10 last occured warnings and alarms.

Check Status Last run (date)Alert log check 10g OK 17/11/2010 13:10

Archive status Check OK 17/11/2010 13:10

File status check OK 17/11/2010 13:11

Job scheduling check OK 17/11/2010 13:05

Flash Recovery Area Usage OK 17/11/2010 13:10

Free extents check OK 17/11/2010 11:35

Segment size status ("old style" tablespaces) OK 17/11/2010 11:33

Tablespace free space check OK 17/11/2010 11:45

CPU load OK 17/11/2010 13:09

RMAN backup status WARNING 17/11/2010 11:34

Blocking detector OK 17/11/2010 13:09

Check Status Occured (date)RMAN backup status WARNING 17/11/2010 11:34

Alert log check 10g WARNING 17/11/2010 11:10

Page 4


2. System overview The sections shows overall information concerning the database.

2.1. Database informationThe table below lists the identification information for the database.

2.2. Database versionThe table below shows the Oracle version information.

2.3. Database ComponentsThe table below shows information from DBA_REGISTRY dictionary view which displays information about the components loaded into the database.

SID DBMS Type (vendor) Version (#) Database Host OSora10g3 Oracle 10.2.0.1.0 ORA10G3 MAREKSPC 32-bit Windows:

BannerOracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod

PL/SQL Release 10.2.0.1.0 - Production

CORE10.2.0.1.0Production

TNS for 32-bit Windows: Version 10.2.0.1.0 - Production

NLSRTL Version 10.2.0.1.0 - Production

Component ID Status Version Component NameAMD VALID 10.2.0.1.0 OLAP Catalog

APS VALID 10.2.0.1.0 OLAP Analytic Workspace

CATALOG VALID 10.2.0.1.0 Oracle Database Catalog Views

CATJAVA VALID 10.2.0.1.0 Oracle Database Java Packages

CATPROC VALID 10.2.0.1.0 Oracle Database Packages and Types

Page 5


2.4. Availability statisticsThe table below shows availability information about the monitoring session.

2.5. DBMS uptime periodsThe table below shows the periods of time when the database was started/stopped etc. It gives a good indication of the restart frequency of the database.

CONTEXT VALID 10.2.0.1.0 Oracle Text

EM VALID 10.2.0.1.0 Oracle Enterprise Manager

EXF VALID 10.2.0.1.0 Oracle Expression Filter

JAVAVM VALID 10.2.0.1.0 JServer JAVA Virtual Machine

ODM VALID 10.2.0.1.0 Oracle Data Mining

ORDIM VALID 10.2.0.1.0 Oracle interMedia

OWM VALID 10.2.0.1.0 Oracle Workspace Manager

RUL VALID 10.2.0.1.0 Oracle Rules Manager

SDO VALID 10.2.0.1.0 Spatial

XDB VALID 10.2.0.1.0 Oracle XML Database

XML VALID 10.2.0.1.0 Oracle XDK

XOQ VALID 10.2.0.1.0 Oracle OLAP API

DBMS uptime Monitored Down Uptime (%)3 days 16 hours 44 min 0 days 2 hours 9 min 0 days 0 hours 0 min 100.0

Period (#) DBMS startup Last sampled date Period span (in days, hours and minutes)1 13-11-2010 20:27 17-11-2010 13:11 3 days 16 hours 44 min

Page 6


2.6. Database growth rateThe table below shows the total size of the database, space used and growth rate.

2.7. Database growthThe chart below shows the current growth rate of the database.

Total size of DB (GB) Space used (GB) Growth rate (GB/year)1.5 1.1 3.39

Page 7


3. Space usage statistics All database data are organized in units called segments. Segments are grouped by object types such as tables, indexes, clusters etc. Each segment consists ofblocks (the smallest storage unit in Oracle). The blocks are connected to the file system blocks. A database usually consists of thousands of segments, so eachcannot be monitored individually. We therefore retrieve detailed information about the segments that need to be monitored more closely, such as the largestsegments in the database. This section displays information on all segment types and more detailed information on the largest segments.

3.1. SchemasThe following table provides an overview of the object count and size in the monitored database environment. (the 15 largest schemas are shown)

Schema Segment count (#) Segment size (MB)SYS 1,705 707.6

XDB 753 48.1

SYSMAN 760 48.1

MDSYS 125 32.4

SYSTEM 355 22.2

DBW_7434_C 94 16.4

OLAPSYS 249 15.6

DBW_7434_A 99 15.1

DBWATCH 99 14.6

DBW_7520 97 10.6

DBW_7434_B 60 7.0

DBW_ALAN 101 6.9

WMSYS 110 6.9

DBW_7434_D 59 6.8

DBW_7434_E 59 6.8

Page 8


3.2. Segment count and segment sizeThe following chart visualizes the populated table above. (the 15 largest schemas are shown)

Page 9


3.3. Growth rate - schemasThe following chart visualizes the growth rate for the top 5 largest schemas.

Page 10


3.4. Growth rate - segment types per ownerThe following chart visualizes the growth rate for the largest segments types (3 largest schemas).

3.5. Largest segmentsThe table below lists the largest segments in the database. It is important to monitor these according to disk usage.

Owner Segment Segment type Tablespace Extents (#) Total segment size (MB)MDSYS SYS_LOB0000046123C00006$$ LOBSEGMENT SYSAUX 33 18

SYS SOURCE$ TABLE SYSTEM 64 49

SYS TEST_TAB TABLE TEST 56 41

SYS BIN$1J/kbgsxQkiOOxy9JhN5BA==$0 TABLE TEST 55 40

SYS IDL_UB2$ TABLE SYSTEM 35 20

SYS PK_CT INDEX SYSTEM 10 10

SYS C_TOID_VERSION# CLUSTER SYSTEM 31 16

SYS WRI$_OPTSTAT_HISTGRM_HISTORY TABLE SYSAUX 28 13

Page 11


3.6. Growth rate of the largest segmentsThe chart below shows the growth rate of the largest segments. Typically it will be a few segments which make up most of the size development in a schema.The chart contains all elements that have been in the ‘top largest segments’ list

SYS C_OBJ#_INTCOL# CLUSTER SYSTEM 11 11

SYS IDL_UB1$ TABLE SYSTEM 93 175

SYS I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST INDEX SYSAUX 35 20

Page 12


4. Memory usage statistics This chapter shows memory statistics.

4.1. Initialization fileThe following table indicates whether a spfile is used or not. (for oracle 8 the table is empty)

4.2. Memory initialization parametersThe following table shows relevant parameters and their values. Please note that pga_aggregate_target (> 9i) and sga_target (> 10g) settings will cause Oracleto dynamicaly allocate memory resources. Dynamically allocated memory values are not visible to users and will be shown as zero values in the table below.

Parameter Pathspfile E:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEORA10G3.ORA

Parameter Value (MB)sga_max_size 300.0

shared_pool_size 152.0

pga_aggregate_target 50.0

java_pool_size 32.0

db_cache_size 8.0

log_buffer 6.7

sort_area_size 0.1

(db _block_buffers * db_block_size) 0.0

large_pool_size 0.0

sga_target 0.0

Page 13


4.3. User memory statistic historyThe following chart shows the history of user memory allocation during the last 48 hours.

Page 14


4.4. SGA pool size.The following chart shows SGA pool components' sizes in MB.

Page 15


4.5. SGA pools(shared, large, java) statistic historyThe following chart shows the history of buffer size variations for the largest buffers in the system global area during the last 48 hours.

Page 16


4.6. Data cache statistics.The graph below shows the hit ratios for buffer cache versus the number of buffer gets (logical Buffer Gets. The relationship between these statistics is goodindication of the IO efficiency of the database and the applications using the system.

Page 17


5. Session statistics

5.1. Logon historyShows logon history collected from v$session performance view.

5.2. Current connections from hosts.Shows which host have the highest number of sessions. (Top 10)

Hostname Sessionsmarekspc 9

Page 18


5.3. Current connection per username (schema)Shows which users (schemas) have the highest number of sessions. (Top 10)

5.4. Current application types.Shows which programs (applications) have the highest number of connections. (Top 10)

5.5. Current connections.Shows top 50 current sessions. Active and newest first.

Username SessionsDBW_7534 5

DBW_7520 4

Program SessionsdbWatch 9.2 (engine) 8

dbWatch 9.2 (sql worksheet) 1

Username Login time Schema Status Hostname Program nameDBW_7534 2010-11-17 11:01:42.0 DBW_7534 ACTIVE marekspc dbWatch 9.2 (engine)

DBW_7534 2010-11-17 13:10:42.0 DBW_7534 INACTIVE marekspc dbWatch 9.2 (sql worksheet)

DBW_7534 2010-11-17 11:01:40.0 DBW_7534 INACTIVE marekspc dbWatch 9.2 (engine)







Page 19


5.6. Aggregated Logon historyShows aggregated logon history collected from v$session performance view.

Page 20


6. File IO statistics Oracle maintains the information regarding the different types of files (data files, temporary files etc.); each of these statistics requires its own interpretation tounderstand the use of the disk resources on the host machine. This chapter shows information concerning data files. The data files are physically located in thefile system of the Oracle server and they contain all data stored in the database, including metadata. The data files are grouped in the logical storage unittablespace. Looking at the tablespace growth directly gives a more correct insight into how much disk resources particular applications (which typically havetheir own tablespaces) consume.

6.1. Physical reads and writesThe chart below shows physical reads and writes for all data files.

Page 21


6.2. Statistics for data files with the highest average physical readsThe chart below shows data files with the highest average physical reads, i.e. how many times the database has had to read from that particular file in order tosatisfy a request. Disk reads can be alleviated by buffering tables in memory or by reducing transaction loads. If some particular data file needs to be read oftenit may be beneficial to store this file on its own disk.

6.3. Datafiles with the highest average physical reads

File ID (#) Name Tablespace Size (MB)1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\SYSTEM01.DBF SYSTEM 550

5 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBWATCH_01.DBF DBWATCH 120

3 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\SYSAUX01.DBF SYSAUX 360

15 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBW_7534_01.DBF DBW_7534 100

Page 22


6.4. Statistics for data files with the highest average physical writesThe chart below shows data files with the highest average physical writes for each data file. Write operations are caused by transactions that update tables in thedatabase. Depending on the type of database you will see a lot of write activity or very little. If both read and write activity is high and you experience lag yoursafest bet is either to reduce the load on the database (by optimizing SQL statements or rescheduling regular tasks) or moving the data file to another disk.

6.5. Datafiles with the highest average physical writes

File ID (#) Name Tablespace Size (MB)3 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\SYSAUX01.DBF SYSAUX 360

5 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBWATCH_01.DBF DBWATCH 120

2 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\UNDOTBS01.DBF UNDOTBS1 40

6 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\GRIDCONTROL01.DMF GRIDCONTROL 30

Page 23


6.6. Aggregate IO historyShows aggregated reads and writes values per day.

6.7. File statisticsThe table below lists all data files in the database. The column "Auto" refer to AUTOEXTENSIBLE column in DBA_DATA_FILES dictionary view, while"Max" refer to MAXBYTES column.

Tablespace Name Size (MB) Max (GB) AutoDBWATCH E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBWATCH_01.DBF 120.0 0.5 YES

DBWATCH7474 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBWATCH.DBF 50.0 0.5 YES

DBW_7434_D E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBW_7434_D_01.DBF 40.0 0.3 YES

DBW_7534 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\DBW_7534_01.DBF 100.0 0.5 YES

GRIDCONTROL E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\GRIDCONTROL01.DMF 30.0 0.0 NO

JORAPTHNODE1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\JORAPHNODE1.DBF 50.0 0.2 YES

SYSAUX E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\SYSAUX01.DBF 360.0 32.767984375 YES

Page 24


SYSTEM E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\SYSTEM01.DBF 550.0 32.767984375 YES

TEST E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\TEST_01.DBF 2.0 0.0 NO



TEST2 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\TEST2_01.DBF 2.0 0.0 NO

TEST3 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\TEST3_01.DBF 3.0 0.0 NO

UNDOTBS1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\UNDOTBS01.DBF 40.0 32.767984375 YES

USERS E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\USERS01.DBF 5.0 32.767984375 YES

Page 25


7. Redolog analysis Redolog files contain information about transactions in the database. This information is used under 'media recovery' and 'instance recovery' (to rebuildcorrupted/deleted data files or reinstall a terminated instance). This chapter reviews the configuration and efficiency of the redolog files. Archive files arebackups of redolog files. When a redolog file is full or a redolog switch is performed, the content of the redolog files is copied to an archive file (each archiveactivity generates 1 archive file pr. redolog file). A corrupt redolog will lead to loss of data. Switching is an automatic activity which is performed when theredolog file is full. The number of switches is a function of the transaction count and size plus the file size. You can also activate automatic redolog switchingso that switching can be performed regularly independent of the transactions.

7.1. Redolog filesThe table below lists existing redolog files. If several members (physical redolog files) belong to the same group they are mirrored (something which givesbetter protections and is highly recommended). In additon the table lists the redolog files sizes. The following charts shows statistics regarding log swithces.

Thread (ID) Group (ID) Member (path) Size (MB) Status1 1 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\REDO01.LOG 50 CURRENT

1 2 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\REDO02.LOG 50 INACTIVE

1 3 E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\REDO03.LOG 50 INACTIVE

Page 26


7.2. Redolog switch frequency pr. dayThe chart below shows the number of redolog switches pr. day. This chart gives and insigth into the databases transaction rate. Since switching is a resourcedemanding task, it is recommended that switching occurs every 5-20 minutes. However, this should be done according to the specific environment.

Page 27


7.3. Redolog switch frequency per hourThe chart below shows the number of redolog switches per hour. Even if statistics over number of redologs switches pr. day is satisfying you should make surecheck that they are evenly distributed across the day.

Page 28


7.4. Transaction frequencyThe chart below shows the transaction frequency.

Page 29


8. Tablespace statistics

8.1. TablespacesThe following table presents general statistics for the largest tablespaces (maximum 20 tablespaces will be shown). The “Free extents#” column may indicatedefragmentation of the tablespace.

Name Size (MB) Free space (MB) Free extents (#) Percent free (%)SYSTEM 550 28 2 5.1

SYSAUX 360 33 104 9.2

DBWATCH 120 10 9 8.3

DBW_7534 100 95 1 95.0

TEST 84 42 58 50.0

JORAPTHNODE1 50 44 2 88.0

DBWATCH7474 50 44 2 88.0

UNDOTBS1 40 13 11 32.5

DBW_7434_D 40 26 2 65.0

GRIDCONTROL 30 16 3 53.3

TEMP 20 20 1 100.0

USERS 5 5 1 100.0

TEST3 3 1 1 33.3

TEST2 2 2 1 100.0

Page 30


8.2. Tablespace sizeUsed and free space in each of the 10 largest tablespaces.

Page 31


8.3. Tablespace growth rateThe following chart visualizes the growth rate for the 5 largest tablespaces.

Page 32


9. Sorting and temporary space

9.1. Temporary data filesThe following table presents storage configuration for temporary files.

9.2. Sorts statistics for memory and disk.The following chart shows the relationship between sorts in memory vs. sorts to disk for the last 48 hours. .

Tablespace Filename Size (MB) Autoextensible Max size (GB) Inbrement by (bytes)TEMP E:\ORACLE\PRODUCT\10.2.0\ORADATA\ORA10G3\TEMP01.DBF 20.0 YES 33.0 80.0

Page 33


9.3. Sort statistics by rowsThe following chart shows the number of rows sorted over the last 48 hours.

Page 34


9.4. Physical reads/writes for temporary tablespaces.The following chart shows read and write statistics for temporary tablespaces defined with temporary data files (using temp file option in tablespace creation)over the last 48 hours.

Page 35


10. SQL statements analysis The following section lists statistics from V$SQLAREA dynamic performance view. The statistics are divided into four tables sorted by the followingcategorys/values: "rows processed", "buffer gets", "disk reads" and "most executed".

10.1. Statistics for cursors with the highest value of rows processedThe following table lists statistics for cursors with the highest value of records processed.

Rows processed Average rows processed Average buffer gets Hitratio

Average CPU (sec) SQL text

56,920 15 3 93.02 0.45 select /*+ rule */ bucket, endpoint, col#, epvalue from histgrm$ whereobj#=:1 and intcol#=:2 and row#=:3 order by bucket

49,657 1 2 99.99 0.062 SELECT EXECUTION_COUNTER FROM DBW_TASKS WHERETASK_ID=:B1

49,365 98 112 100.0 1.845 DELETE FROM DBW_INSTANCEMEM WHERE H_DATE < :B1

47,766 1 7 100.0 0.094 SELECT NVL(MAX(VALUE),0) FROM DBW_INSTANCEMEMWHERE H_DATE=:B2 AND STATISTIC#=:B1

47,766 1 3 99.44 0.075 INSERT INTO DBW_INSTANCEMEM VALUES ( :B3 , :B2 , :B1 )

47,766 1 3 99.27 0.082 INSERT INTO DBW_INSTANCEMEM_HISTR VALUES (:B2 ,:B6 +1, :B5 , :B4 , :B4 -:B3 , ROUND((:B2 -:B1 )*(24*60*60)) )

38,474 1 1 100.0 0.073 select count(*) from sys.job$ where (next_date > sysdate) and(next_date < (sysdate+5/86400))

33,652 1 0 76.81 0.197 BEGIN dbw_7520.dbw_getEngineTime(:1); END;

26,825 1 1 99.97 0.058 SELECT TASK_ID FROM DBW_TASKS WHERE TASK_ID=:B1

26,601 1 1 100.0 0.044 SELECT TASK_ID FROM DBW_TASKS WHERE TASK_ID =:B1

Page 36


10.2. Statistics for cursors with the highest value of buffer getsThe following table lists statistics for cursors with the highest value of buffer gets.

10.3. Statistics for cursors with the highest value of disk readsThe following table lists statistics for cursors with the highest value of disk reads.

Buffer gets Average buffer gets Hit ratio Average CPU (sec) SQL text6,597,577 391 96.69 26.754 BEGIN dbw_7520.dbw_executeTask(:1,:2); END;

2,757,404 9,608 98.84 284.395 BEGIN dbms_waits(23);END;

1,514,730 81 98.47 3.041 SELECT MAX(NVL(EXECUTION_COUNTER,0)) FROM DBW_WAITS_HISTR

1,433,873 4,961 98.76 167.499 BEGIN latch_stat(26);END;

1,371,824 1,371,824 95.49 43,892.488 call dbms_stats.gather_database_stats_job_proc ( )

1,177,648 130 90.97 20.692 BEGIN dbw_test09.dbw_executeTask(:1,:2); END;

927,346 927,346 69.66 12,187.5 call dbms_space.auto_space_advisor_job_proc ( )

904,500 11,030 69.37 131.539 SELECT OWNER, SEGMENT_NAME, PARTITION_NAME, SEGMENT_TYPE,TABLESPACE_NAME, TABLESPACE_ID FROM SYS_DBA_SEGS WHERESEGMENT_OBJD = :B1

701,280 241 99.98 0.729 SELECT SU.NAME, SO.NAME, A.STATSTYPE#, C.INTCOL# FROMASSOCIATION$ A, OBJ$ O, USER$ U, COL$ C, OBJ$ SO, USER$ SU,COLTYPE$ CT, OBJ$ TY WHERE O.OWNER#=U.USER# ANDA.OBJ#=TY.OBJ# AND O.OBJ#=C.OBJ# AND C.INTCOL#=CT.INTCOL# ANDO.OBJ#=CT.OBJ# AND CT.TOID=TY.OID$ AND A.STATSTYPE#=SO.OBJ#AND SO.OWNER#=SU.USER# AND O.TYPE#=2 AND O.NAME=:B3 ANDU.NAME=:B2 AND C.NAME=:B1

599,781 54 97.65 2.387 SELECT MAX(NVL(EXECUTION_COUNTER,0)) FROMDBW_LATCHSTAT_HISTR

Disk reads Average disk reads Hit ratio Average CPU (sec) SQL text403,911 403,911 69.66 12,187.5 call dbms_space.auto_space_advisor_job_proc ( )

399,338 4,870 69.37 131.539 SELECT OWNER, SEGMENT_NAME, PARTITION_NAME, SEGMENT_TYPE,TABLESPACE_NAME, TABLESPACE_ID FROM SYS_DBA_SEGS WHERESEGMENT_OBJD = :B1

226,015 13 96.69 26.754 BEGIN dbw_7520.dbw_executeTask(:1,:2); END;

Page 37


10.4. Statistics of most executed cursorsThe following table lists statistics for most executed cursors.

117,895 39,298 71.05 1,308.539 BEGIN free_extents(10);END;

116,890 13 90.97 20.692 BEGIN dbw_test09.dbw_executeTask(:1,:2); END;

107,942 750 50.95 36.96 select OBJOID, CLSOID, RUNTIME, PRI, JOBTYPE, SCHLIM, WT, INST,RUNNOW, ENQ_SCHLIM from ( select a.obj# OBJOID, a.class_oid CLSOID,decode(bitand(a.flags, 16384), 0, a.next_run_date, a.last_enabled_time) RUNTIME,(2*a.priority + decode(bitand(a.job_status, 4), 0, 0,decode(a.running_instance, :1, -1, 1))) PRI, 1 JOBTYPE, a.schedule_limit SCHLIM,a.job_weight WT, decode(a.running_instance, NULL, 0, a.running_instance) INST,decode(bitand(a.flags, 16384), 0, 0, 1) RUNNOW, decode(bitand(a.job_status,8388608), 0, 0, 1) ENQ_SCHLIM from sys.scheduler$_job a wherebitand(a.job_status, 515) = 1 and ((bitand(a.flags, 134217728 + 268435456) = 0) or(bitand(a.job_status, 1024) <> 0)) and bitand(a.flags, 4096) = 0 and(a.next_run_date <= :2 or bitand(a.flags, 16384) <> 0) and (a.class_oid is nullor (a.class_oid is not null and a.class_oid in (select b.obj# fromsys.scheduler$_class b where b.affin

86,233 129 80.22 27.422 BEGIN dbw_7534.dbw_executeTask(:1,:2); END;

64,805 64,805 95.49 43,892.488 call dbms_stats.gather_database_stats_job_proc ( )

62,786 31,393 75.1 1,125.028 BEGIN free_extents(13);END;

58,455 1,083 50.12 23.252 select o.obj#, u.name, o.name, t.spare1, DECODE(bitand(t.flags, 268435456),268435456, t.initrans, t.pctfree$) from sys.obj$ o, sys.user$ u, sys.tab$ t where(bitand(t.trigflag, 1048576) = 1048576) and o.obj#=t.obj# and o.owner# =u.user#

Executions Average buffer gets Hit ratio Average CPU (sec) SQL text49,657 2 99.99 0.062 SELECT EXECUTION_COUNTER FROM DBW_TASKS WHERE

TASK_ID=:B1

47,766 3 99.27 0.082 INSERT INTO DBW_INSTANCEMEM_HISTR VALUES (:B2 , :B6 +1, :B5 ,:B4 , :B4 -:B3 , ROUND((:B2 -:B1 )*(24*60*60)) )

47,766 7 100.0 0.094 SELECT NVL(MAX(VALUE),0) FROM DBW_INSTANCEMEM WHEREH_DATE=:B2 AND STATISTIC#=:B1

47,766 3 99.44 0.075 INSERT INTO DBW_INSTANCEMEM VALUES ( :B3 , :B2 , :B1 )

Page 38


10.5. History of resource demanding cursorsThe following table lists statistics for most resource demanding cursors.

38,479 2 100.0 0.125 select job, nvl2(last_date, 1, 0) from sys.job$ where (((:1 <= next_date) and(next_date < :2)) or ((last_date is null) and (next_date < :3))) and (field1 = :4 or(field1 = 0 and 'Y' = :5)) and (this_date is null) order by next_date, job

38,474 1 100.0 0.073 select count(*) from sys.job$ where (next_date > sysdate) and (next_date <(sysdate+5/86400))

33,652 0 76.81 0.197 BEGIN dbw_7520.dbw_getEngineTime(:1); END;

26,828 1 99.97 0.058 SELECT TASK_ID FROM DBW_TASKS WHERE TASK_ID=:B1

26,601 1 100.0 0.044 SELECT TASK_ID FROM DBW_TASKS WHERE TASK_ID =:B1

26,593 7 99.85 0.482 SELECT T.TASK_ID, LAST_RUN, CASE WHEN C.SUSPENDED IS NULLTHEN -1 ELSE C.SUSPENDED END AS SUSPENDED, CASE WHENC.STATUS IS NULL THEN -1 ELSE C.STATUS END AS STATUS,DBW_HASUNACKNOWLEDGED ( :B1 ) AS HAS_UNACKNOWLEDGED,T.EXECUTION_DETAILS FROM DBW_TASKS T LEFT OUTER JOINDBW_CHECKS C ON T.TASK_ID=C.TASK_ID WHERE T.TASK_ID=:B1

Collected Executions Average rows processed Average buffer gets Hit ratio Average CPU (sec) Average elapsed time (sec) SQL text

Page 39


11. Flash recovery area usage

11.1. Flash recovery area usageThe following table lists information from V$FLASH_RECOVERY_AREA_USAGE dictionary view.

11.2. Initialisation parametersThe following table lists Oracle initialisation parameters related to Flash Recovery Area. The db_recovery_file_dest_size parameter value is a user-specifiedlimit on the amount of space that will be used by this database for recovery-related files, and does not reflect the amount of space available in the underlyingfilesystem.

File Type Percent Space Used Reclaimable Number of filesCONTROLFILE 0.0 0.0 0

ONLINELOG 0.0 0.0 0

ARCHIVELOG 27.17 0.0 32

BACKUPPIECE 0.0 0.0 0

IMAGECOPY 0.0 0.0 0

FLASHBACKLOG 0.0 0.0 0

Name Valuedb_recovery_file_dest E:\oracle\product\10.2.0\flash_recovery_area

db_recovery_file_dest_size 5 GB

Page 40


11.3. RMAN CrosscheckYou can free up space from flash recovery area by deleting unnecessary files using RMAN DELETE command. If an operating system command was used todelete files, then use RMAN CROSSCHECK and DELETE EXPIRED commands.

RMAN commandrun

{

DELETE OBSOLETE;

CROSSCHECK ARCHIVELOG ALL;

DELETE EXPIRED ARCHIVELOG ALL;

}

Page 41


12. RMAN backup statistics

12.1. RMAN Backup HistoryThe table below shows history of RMAN backups.

Backup Started Backup ended status Elaps time Output (MB) (MB) Input (MB) (MB)25/10/2010 13:14 25/10/2010 13:21 COMPLETED 00:07:18 3,284 3,714

2/9/2010 14:52 2/9/2010 14:55 COMPLETED 00:02:48 1,099 1,508

30/8/2010 12:33 30/8/2010 12:35 COMPLETED 00:02:39 1,012 1,430

28/8/2010 15:41 28/8/2010 15:44 COMPLETED 00:02:46 992 1,410

27/8/2010 11:23 27/8/2010 11:25 COMPLETED 00:02:23 887 1,307

26/8/2010 05:30 26/8/2010 05:33 COMPLETED 00:02:15 875 1,294

25/8/2010 23:27 25/8/2010 23:29 COMPLETED 00:02:09 858 1,278

25/8/2010 23:12 25/8/2010 23:14 COMPLETED 00:02:18 861 1,280

25/8/2010 23:00 25/8/2010 23:02 COMPLETED 00:01:56 882 1,302

25/8/2010 22:55 25/8/2010 22:55 FAILED 00:00:06 7 7

Page 42


12.2. Backup size historyThe chart below shows history of backup size.

12.3. RMAN Backup piecesThe table below shows history of RMAN backup pieces from V$BACKUP_PIECE dictionary view.

Backup ended Elapsed time (sec.) handle recid Device type tag status25/10/2010 13:21 82 E:\ORACLE\BACKUP\RMAN\ORA10G3\25.10.2010_1314\BK-

S49-P1.ARC48 DISK TAG20101025T131647 A

25/10/2010 13:19 87 E:\ORACLE\BACKUP\RMAN\ORA10G3\25.10.2010_1314\BK-S48-P1.ARC

47 DISK TAG20101025T131647 A


46 DISK TAG20101025T131647 A

25/10/2010 13:16 0 E:\ORACLE\BACKUP\RMAN\ORA10G3\25.10.2010_1314\BK_U1ELRB99N.SPFILE

45 DISK TAG20101025T131639 A

25/10/2010 13:16 0 E:\ORACLE\BACKUP\RMAN\ORA10G3\25.10.2010_1314\BK_U1DLRB99L.CTL

44 DISK TAG20101025T131636 A

Page 43


12.4. RMAN ConfigurationThe table below shows configuration values for RMAN parameters.

25/10/2010 13:16 1 E:\ORACLE\BACKUP\RMAN\ORA10G3\25.10.2010_1314\BK_U1CLRB993_S44_P1_T733324579.DB

43 DISK TAG20101025T131431 A

25/10/2010 13:16 103 E:\ORACLE\BACKUP\RMAN\ORA10G3\25.10.2010_1314\BK_U1BLRB95N_S43_P1_T733324471.DB

42 DISK TAG20101025T131431 A


41 DISK TAG20100902T145510 A

2/9/2010 14:55 1 E:\ORACLE\BACKUP\RMAN\ORA10G3\02.09.2010_1452\BK_U18LMT2Q3.CTL

39 DISK TAG20100902T145459 A

2/9/2010 14:54 104 E:\ORACLE\BACKUP\RMAN\ORA10G3\02.09.2010_1452\BK_U16LMT2MC_S38_P1_T728664780.DB

37 DISK TAG20100902T145259 A

name valueRETENTION POLICY TO RECOVERY WINDOW OF 3 DAYS

Documents

Health Check Report for Oracle 10g Database