health check report for oracle 10g database

dbWatch Software ASwww.dbwatchsoftware.com

September 15, 2009 5:32:42 PM

Health check report for Oracle

10g database

The dbWatch Report displays data collected by the dbWatch Standard and Advanced

tasks/checks 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.

Health check report for Oracle 10g database

Databases The report encompasses information from the following databases:

- ora10g1 ole


1. Status overview

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

1.2. Historical status - last 10 weeksThe following table displays a list of Warnings/Alarms from the last 10 weeks. This gives a generalindication on how the monitored system is responding with the current configuration.

1.3. Warnings/Alarms per checkThe following table lists details of when the different W/A happened and which checks that actuallygenerated them.

Check Status Last run (date)AGRESSO DWS shadow tables OK 11/9/2009 07:13

AGRESSO Application Server OK 15/9/2009 14:30

Data Guard Archive Status Check OK 2/4/2009 15:40

Listener log check 10g WARNING 10/8/2009 12:13

Top user memory usage OK 15/9/2009 17:35

File status check OK 15/9/2009 17:35

Backup log Check 10g ("old style" backups) WARNING 9/8/2009 05:15

Archive status Check OK 15/9/2009 17:35

Free extents check OK 14/9/2009 11:51

Free space Check OK 14/9/2009 11:45

Segment size status ("old style" tablespaces) OK 11/9/2009 06:43

Blocking detector OK 15/9/2009 17:35

Week (#) Warnings Alarms23 3 0

24 2 0

25 1 0

26 4 0

27 4 0

28 1 0

29 71 0

30 2 0

31 71 0

32 79 2

Check Warnings Last occured warning (date) Alarms Last occured alarm (date)Free space Check 3 2009-08-10 16:21:03.0 0

Listener log check 10g 200 2009-08-10 12:13:07.0 0

Backup log Check 10g("old style" backups)

101 2009-08-09 05:15:18.0 0


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

Check Status Occured (date)Free space Check WARNING 10/8/2009 16:21

Top user memory usage ALARM 10/8/2009 16:18

Top user memory usage ALARM 10/8/2009 16:17

Free space Check WARNING 10/8/2009 16:14

Free space Check WARNING 10/8/2009 16:09







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 informationabout the components loaded into the database.

SID DBMS Type (vendor) Version (#) Database Host OSora10g1 Oracle 10.1.0.2.0 ORA10G1 OLE 32-bit Windows:

BannerOracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Prod

PL/SQL Release 10.1.0.2.0 - Production

CORE10.1.0.2.0Production

TNS for 32-bit Windows: Version 10.1.0.2.0 - Production

NLSRTL Version 10.1.0.2.0 - Production

Component ID Status Version Component NameAMD VALID 10.1.0.2.0 OLAP Catalog

APS VALID 10.1.0.2.0 OLAP Analytic Workspace

CATALOG VALID 10.1.0.2.0 Oracle Database Catalog Views

CATJAVA VALID 10.1.0.2.0 Oracle Database Java Packages

CATPROC VALID 10.1.0.2.0 Oracle Database Packages and Types

CONTEXT VALID 10.1.0.2.0 Oracle Text

EM VALID 10.1.0.2.0 Oracle Enterprise Manager

EXF VALID 10.1.0.2.0 Oracle Expression Filter

JAVAVM VALID 10.1.0.2.0 JServer JAVA Virtual Machine

ODM VALID 10.1.0.2.0 Oracle Data Mining

ORDIM VALID 10.1.0.2.0 Oracle interMedia

OWM VALID 10.1.0.2.0 Oracle Workspace Manager

SDO VALID 10.1.0.2.0 Spatial

XDB VALID 10.1.0.2.0 Oracle XML Database

XML VALID 10.1.0.2.0 Oracle XDK

XOQ VALID 10.1.0.2.0 Oracle OLAP API


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 goodindication of the restart frequency of the database.

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.

DBMS uptime Monitored Down Uptime (%)131 days 16 hours 3 min 119 days 3 hours 16 min 9 days 22 hours 29 min 92.98

Period (#) DBMS startup Last sampled date Period span (in days, hours and minutes)8 10-09-2009 03:08 15-09-2009 17:35 5 days 14 hours 27 min

7 16-08-2009 03:10 09-09-2009 15:49 24 days 12 hours 38 min

6 13-08-2009 13:49 16-08-2009 03:08 2 days 13 hours 19 min

5 12-08-2009 03:06 13-08-2009 11:26 1 days 8 hours 20 min

4 11-08-2009 10:04 11-08-2009 20:16 0 days 10 hours 11 min

3 30-07-2009 03:08 11-08-2009 08:31 12 days 5 hours 23 min

2 11-06-2009 03:09 21-07-2009 14:01 40 days 10 hours 51 min

1 27-04-2009 03:02 10-06-2009 15:53 44 days 12 hours 51 min

Total size of DB (GB) Space used (GB) Growth rate (GB/year)7.6 1.1 0.09


3. Space usage statistics All database data are organized in units called segments. Segments are grouped by object types such astables, indexes, clusters etc. Each segment consists of blocks (the smallest storage unit in Oracle). Theblocks are connected to the file system blocks. A database usually consists of thousands of segments, soeach cannot be monitored individually. We therefore retrieve detailed information about the segments thatneed to be monitored more closely, such as the largest segments in the database. This section displaysinformation 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 databaseenvironment. (the 15 largest schemas are shown)

Schema Segment count (#) Segment size (MB)SYS 1866 7166.4

SYSMAN 735 56.4

XDB 733 46.3

DB_WATCH 107 27.3

SYSTEM 345 21.6

OLAPSYS 243 15.2

WK_TEST 34 12.0

TOM_DBWATCH 108 10.6

DBW_1702_1 75 10.3

DBW_T4 75 9.1

DBW_OLE01 65 7.6

WKSYS 114 7.1

TOM_FAT11 108 7.0

TOM_FAT16 108 7.0

TOM_FAT4 108 7.0


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

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


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 diskusage.

Owner Segment Segment type Tablespace Extents (#) Total segment size (MB)SYS IDL_UB1$ TABLE SYSTEM 91 160

SYS SOURCE$ TABLE SYSTEM 66 51

SYS IDL_UB2$ TABLE SYSTEM 38 23

SYS C_OBJ#_INTCOL# CLUSTER SYSTEM 22 22

SYS C_TOID_VERSION# CLUSTER SYSTEM 29 14

SYS I_WRI$_OPTSTAT_H_OBJ#_ICOL#_ST

INDEX SYSAUX 30 15

SYS PK_C0 INDEX SYSTEM 10 10

SYS PK_CS INDEX SYSTEM 10 10

SYS PK_CT INDEX SYSTEM 10 10

SYS PK_O INDEX SYSTEM 10 10

SYS C_OBJ# CLUSTER SYSTEM 25 10

SYS WRI$_OPTSTAT_HISTGRM_HISTORY

TABLE SYSAUX 25 10

SYS I_SOURCE1 INDEX SYSTEM 25 10


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 whichmake up most of the size development in a schema. The chart contains all elements that have been in the‘top largest segments’ list


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 Oracle to dynamicaly allocate memory resources. Dynamicallyallocated memory values are not visible to users and will be shown as zero values in the table below.

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

Parameter Pathspfile C:\ORACLE\PRODUCT\10.1.0\DB_4\DATABASE\SPFILEORA10G1.ORA

Parameter Value (MB)sga_max_size 128.0

shared_pool_size 80.0

java_pool_size 24.0

pga_aggregate_target 24.0

db_cache_size 12.0

large_pool_size 8.0

log_buffer 0.5

sort_area_size 0.1

(db _block_buffers * db_block_size) 0.0

sga_target 0.0


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

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


4.6. Logons historyThe following chart shows the history of the number of users connected to the system during the last 48hours.

4.7. 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 good indication of the IO efficiency of the database and theapplications using the system.


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)

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)

Hostname SessionsOlePC 24

Username SessionsDBW 4

DBW_1702_1 4

DBW_DEMO 4

DBW_T4 4

DBW_T6 4

DB_WATCH 4

Program SessionsdbWatch 9 (engine) 24


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

Username Login time Schema Status Hostname Program nameDB_WATCH 2009-09-15 17:32:19.0 DB_WATCH ACTIVE OlePC dbWatch 9 (engine)

DBW_1702_1 2009-09-15 17:27:13.0 DBW_1702_1 INACTIVE OlePC dbWatch 9 (engine)

DBW 2009-09-15 17:26:11.0 DBW INACTIVE OlePC dbWatch 9 (engine)



DBW_DEMO 2009-09-15 17:26:08.0 DBW_DEMO INACTIVE OlePC dbWatch 9 (engine)

DBW_T4 2009-09-15 17:26:08.0 DBW_T4 INACTIVE OlePC dbWatch 9 (engine)




DB_WATCH 2009-09-15 17:26:07.0 DB_WATCH INACTIVE OlePC dbWatch 9 (engine)















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


6. File IO statistics Oracle maintains the information regarding the different types of files (data files, temporary files etc.); eachof these statistics requires its own interpretation to understand the use of the disk resources on the hostmachine. 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 datafiles are grouped in the logical storage unit tablespace. Looking at the tablespace growth directly gives amore correct insight into how much disk resources particular applications (which typically have their owntablespaces) consume.

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

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 databasehas had to read from that particular file in order to satisfy a request. Disk reads can be alleviated bybuffering tables in memory or by reducing transaction loads. If some particular data file needs to be readoften it may be beneficial to store this file on its own disk.


6.3. Datafiles with the highest average physical reads

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. Writeoperations are caused by transactions that update tables in the database. Depending on the type of databaseyou will see a lot of write activity or very little. If both read and write activity is high and you experience lagyour safest bet is either to reduce the load on the database (by optimizing SQL statements or reschedulingregular 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\ORADATA\ORA10G1\SYSAUX01.DBF SYSAUX 529

1 E:\ORACLE\ORADATA\ORA10G1\SYSTEM01.DBF SYSTEM 530

12 E:\ORACLE\ORADATA\ORA10G1\DBWATCH_T4_01.DBF DBWATCH_T4 100

9 E:\ORACLE\ORADATA\ORA10G1\DBWATCH_01.DBF DBWATCH 100

File ID (#) Name Tablespace Size (MB)3 E:\ORACLE\ORADATA\ORA10G1\SYSAUX01.DBF SYSAUX 529

1 E:\ORACLE\ORADATA\ORA10G1\SYSTEM01.DBF SYSTEM 530

12 E:\ORACLE\ORADATA\ORA10G1\DBWATCH_T4_01.DBF DBWATCH_T4 100

9 E:\ORACLE\ORADATA\ORA10G1\DBWATCH_01.DBF DBWATCH 100


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

6.7. File statisticsThe table below lists all data and temporary files in the database.

File ID Size (MB) Status Type Name AUTOEXTENSIBLE

Max Size (GB) Tablespacename (GB)

1 530 SYSTEM DATA E:\ORACLE\ORADATA\ORA10G1\SYSTEM01.DBF

YES 32 SYSTEM

2 90 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\UNDOTBS01.DBF

YES 32 UNDOTBS1

3 529 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\SYSAUX01.DBF

YES 32 SYSAUX

4 5 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\USERS01.DBF

YES 32 USERS

5 100 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\KHUDIJA01.DBF

YES 0 KHUDIJA

6 100 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\MALABALA01.DBF

YES 0 MALABALA

7 30 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\TOOLS01.DBF

NO 0 TOOLS

8 100 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DB_WATCH01.DBF

YES 0 DB_WATCH

9 100 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DBWATCH_01.DBF

YES 0 DBWATCH

10 100 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DBWATCH_NO_DUMMY_01.DBF

YES 0 DBWATCH_NO_DUMMY


11 10 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DBWATCH_OLE_01.DBF

YES 1 DBWATCH_OLE

12 100 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DBWATCH_T4_01.DBF

YES 0 DBWATCH_T4


YES 0 DBWATCH_T5


YES 0 DBWATCH_T6


YES 0 DBWATCH_T7


NO 0 DBWATCH


NO 0 DBWATCH


NO 0 DBWATCH


NO 0 DBWATCH


NO 0 DBWATCH


NO 0 DBWATCH

22 20 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DBWATCH.DBF

YES 0 DBWATCH_TS_OLE

23 10 ONLINE DATA E:\ORACLE\ORADATA\ORA10G1\DBWATCH_TS_TEST.DBF

YES 0 DBWATCH_TS_TEST

1 5420 ONLINE TEMP E:\ORACLE\ORADATA\ORA10G1\TEMP01.DBF

YES 32 TEMP


7. Redolog analysis Redolog files contain information about transactions in the database. This information is used under 'mediarecovery' and 'instance recovery' (to rebuild corrupted/deleted data files or reinstall a terminated instance).This chapter reviews the configuration and efficiency of the redolog files. Archive files are backups ofredolog files. When a redolog file is full or a redolog switch is performed, the content of the redolog files iscopied to an archive file (each archive activity generates 1 archive file pr. redolog file). A corrupt redologwill lead to loss of data. Switching is an automatic activity which is performed when the redolog file is full.The number of switches is a function of the transaction count and size plus the file size. You can alsoactivate automatic redolog switching so that switching can be performed regularly independent of thetransactions.

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

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

Thread (ID) Group (ID) Member (path) Size (MB) Status1 1 E:\ORACLE\ORADATA\ORA10G1\REDO01.LOG 10 INACTIVE

1 2 E:\ORACLE\ORADATA\ORA10G1\REDO02.LOG 10 ACTIVE

1 3 E:\ORACLE\ORADATA\ORA10G1\REDO03.LOG 10 CURRENT


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

7.4. Transaction frequencyThe chart below shows the transaction frequency.


8. SQL*Net statistics

8.1. Logons statisticsThe following chart shows the history of the number of users connected to the system during the last 48hours.

8.2. SQL*Net transfer statisticsThe following chart shows the amount the data transferred through SQL*Net over the last 48 hours.


8.3. SQL*Net roundtrips statisticsThe following chart shows the client/server traffic over the SQL*Net during the last 48 hours.


9. Tablespace statistics

9.1. TablespacesThe following table presents general statistics for the largest tablespaces (maximum 20 tablespaces will beshown). The “Free extents#” column may indicate defragmentation of the tablespace.

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

Name Size (MB) Free space (MB) Free extents (#) Percent free (%)TEMP 5420 5420 1 100.0

SYSTEM 530 7 2 1.3

SYSAUX 529 8 20 1.5

DBWATCH 142 109 58 76.8

DB_WATCH 100 100 1 100.0

KHUDIJA 100 100 1 100.0

MALABALA 100 98 1 98.0

DBWATCH_NO_DUMMY 100 96 1 96.0

DBWATCH_T5 100 98 1 98.0

DBWATCH_T7 100 96 1 96.0

DBWATCH_T6 100 94 1 94.0

DBWATCH_T4 100 91 1 91.0

UNDOTBS1 90 51 20 56.7

TOOLS 30 30 1 100.0

DBWATCH_TS_OLE 20 20 1 100.0

DBWATCH_TS_TEST 10 8 1 80.0

DBWATCH_OLE 10 10 1 100.0

USERS 5 4 1 80.0


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


10. Sorting and temporary space

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

10.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. .

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

Tablespace Filename Autoextensible (Y/N) Max size (GB) Increment by (KB)TEMP E:\ORACLE\ORADATA\OR

A10G1\TEMP01.DBFYES 33 80


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


11. Undo/Rollback analysis Undo/Rollback segments are Oracle's mechanism to maintain transactions. The undo or rollback segmentsneed to be configured according to the expected number of transactions. Version 9i introduced automaticmanagement of rollback segments, called undo. This chapter shows the statistics of the undo/rollbacksegments and their efficiency. In most cases you will not need to make any changes to the undo setupcreated by Oracle. If you get the “ORA-01555 snapshot too old” message under 9i or higher using automaticmanagement (undo), you will need to increase the value of the UNDO_RETENTION parameter. If you getthe very same message using rollback segments, increasing the size of the rollback segments will be calledfor. Please consult the Oracle documentation for the appropriate commands.

11.1. Rollback segment overviewThe following table shows in which tablespaces the rollback/undo segments are defined.

11.2. Undo/Rollback segments statisticsThe table below lists statistics for the undo/rollback segments and their efficiency. The statistics to focus onare values in the columns "shrinks", "wraps" and "extends" of the first table. If the rollback segments arecorrectly defined, the "extends" values should be close to 0, and the values of "wraps" should be very lowcompared to values in the "writes" column. All rollback segments should also have "optimal size" valuedefined. For the segments that are not automatically managed the optimal size will tell how big the rollbacksegment is trying to be. In case it is set too low according to the amount of transactions you will se a highlevel of extends/shrinks in the following charts. If the segments are automatically managed the optimal sizewill be -1. For these segments you can configure the UNDO_RETENTION parameter in Oracle.

Tablespace Segment (type) Segmentsize (MB) Segments (#)SYSTEM ROLLBACK 0.38 1

UNDOTBS1 TYPE2 UNDO 38.81 34

ID Name Extents (#) Size (MB) Writes (#) Gets (#) Waits (#) Optimalsize(MB)

Shrinks (#)

Wraps(#)

Extends(#)

0 SYSTEM

6 0.37 28956 10185 8 -1 0 1 0

1 _SYSSMU1$

3 1.12 57488474 57262 4 -1 15 115 30

2 _SYSSMU2$

3 1.12 50638652 61235 10 -1 16 103 29

3 _SYSSMU3$

3 1.12 45823014 54535 15 -1 17 116 39

4 _SYSSMU4$

3 1.12 62239812 126754 11 -1 16 120 36

5 _SYSSMU5$

3 1.12 26967046 96550 12 -1 13 86 42

6 _SYSSMU6$

3 0.18 14298230 79994 19 -1 11 86 24

7 _SYSSMU7$

3 0.18 5699136 56773 25 -1 10 75 16


11.3. Total size and count of all rollback/undo segments.The following chart shows the statistics for total size and count of all rollback/undo segments for the last 48hours.

11.4. Total writes and gets for all rollback/undo segments.The following chart shows the statistics of total writes and gets of all rollback/undo segments over the last48 hours.

8 _SYSSMU8$

3 0.18 12426092 64214 15 -1 5 27 8

9 _SYSSMU9$

2 0.12 10477346 52472 17 -1 17 103 50

10 _SYSSMU10$

2 0.12 7496808 39316 8 -1 5 23 6

11 _SYSSMU11$

2 0.12 4113888 37493 15 -1 4 20 5


11.5. History of total waits, extends, wraps and shrinks for all rollback/undo segments.The following chart shows the history of total waits, extends, wraps and shrinks for all rollback/undosegments over the last 48 hours.

11.6. Writes per rollback/undo segment.The following chart shows the number of writes per rollback/undo segment over the last 48 hours.


11.7. Wraps per rollback/undo segment.The following chart shows the number of wraps per rollback/undo segment over the last 48 hours.


12. SQL statements analysis The following section lists statistics from V$SQLAREA dynamic performance view. The statistics aredivided into four tables sorted by the following categorys/values: "rows processed", "buffer gets", "diskreads" and "most executed".

12.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 Averagerowsprocessed

Average buffer gets Hitratio

Average CPU (sec) SQL text

203181 10 12 99.98 0.216 select privilege#,levelfrom sysauth$ connectby grantee#=priorprivilege# andprivilege#>0 start withgrantee#=:1 andprivilege#>0

162380 10 4 97.84 0.381 selectname,intcol#,segcol#,type#,length,nvl(precision#,0),decode(type#,2,nvl(scale,-127/*MAXSB1MINAL*/),178,scale,179,scale,180,scale,181,scale,182,scale,183,scale,231,scale,0),null$,fixedstorage,nvl(deflength,0),default$,rowid,col#,property,nvl(charsetid,0),nvl(charsetform,0),spare1,spare2,nvl(spare3,0) fromcol$ where obj#=:1order by intcol#

87128 13 3 89.24 0.875 select /*+ rule */bucket, endpoint, col#,epvalue from histgrm$where obj#=:1 andintcol#=:2 and row#=:3order by bucket

35956 1 5 99.12 0.191 selectintcol#,nvl(pos#,0),col#,nvl(spare1,0) fromccol$ where con#=:1

34620 2 7 99.45 0.185 selectpos#,intcol#,col#,spare1,bo#,spare2 from icol$where obj#=:1

29209 3 9 99.46 0.224 selectcon#,type#,condlength,intcols,robj#,rcon#,match#,refact,nvl(enabled,0),rowid,cols,nvl(defer,0),mtime,nvl(spare1,0)from cdef$ whereobj#=:1


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

21692 10846 85 53.29 31.168 SELECTswitch_count as"Switch count (hour)",histr_date AS "Historydate" FROMdb_watch.dbw_switch_count_hourORDER BY "Historydate"

21197 3 7 99.95 0.142 select privilege# fromsysauth$ where(grantee#=:1 orgrantee#=1) andprivilege#>0

18938 2 3 94.62 0.291 selectgrantee#,privilege#,nvl(col#,0),max(mod(nvl(option$,0),2))fromobjauth$ where obj#=:1group bygrantee#,privilege#,nvl(col#,0) order bygrantee#

15066 7533 362 37.01 380.793 SELECTa.owner_stype AS"Owner",a.total_count AS "Totalcount", a.total_sizeAS "Total Size",a.h_date AS "Historydate", b.counterAS "Position"FROMdb_watch.dbv_all_owner_stype_histr a,db_watch.dbv_largest_schemas b WHEREa.owner = b.schemaAND b.counter <3ORDER BY "Historydate"

Buffer gets Average buffer gets Hitratio


1958353 249 91.36 12.47 DECLARE job BINARY_INTEGER := :job;next_date DATE := :mydate; brokenBOOLEAN := FALSE; BEGINEMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS(); :mydate := next_date; IFbroken THEN :b := 1; ELSE :b := 0; END IF;END;

276982 1458 98.38 120.28 BEGIN db_watch.dbw_executeTask(:1,:2);END;

250258 12 99.98 0.216 select privilege#,level from sysauth$ connect bygrantee#=prior privilege# and privilege#>0 startwith grantee#=:1 and privilege#>0

225059 1 100.0 0.077 COMMIT

207854 1267 99.23 181.729 BEGIN dbw_t4.dbw_executeTask(:1,:2); END;


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

165511 72 97.86 1.897 SELECT DBW_RUNSELECT (:B1 ) FROMDUAL

127266 5 99.12 0.191 select intcol#,nvl(pos#,0),col#,nvl(spare1,0)from ccol$ where con#=:1

99337 7 99.45 0.185 select pos#,intcol#,col#,spare1,bo#,spare2 fromicol$ where obj#=:1

86848 11 99.9 0.152 SELECT /*+ RULE */ STEP_ID FROMMGMT_JOB_EXECUTION E, MGMT_JOB JWHERE E.JOB_ID=J.JOB_ID ANDSTEP_STATUS IN (:B6 , :B5 , :B4 , :B3 , :B2 )AND STEP_TYPE=:B1 ANDJ.EXECUTION_TIMEOUT > 0 AND(CAST(SYS_EXTRACT_UTC(SYSTIMESTAMP) AS DATE)-E.START_TIME) >(J.EXECUTION_TIMEOUT/24)

74724 9 99.46 0.224 selectcon#,type#,condlength,intcols,robj#,rcon#,match#,refact,nvl(enabled,0),rowid,cols,nvl(defer,0),mtime,nvl(spare1,0) from cdef$ where obj#=:1

Disk reads Average disk reads Hit ratio Average CPU (sec) SQL text185178 24 91.36 12.47 DECLARE job BINARY_INTEGER

:= :job; next_date DATE := :mydate;broken BOOLEAN := FALSE; BEGINEMD_MAINTENANCE.EXECUTE_EM_DBMS_JOB_PROCS(); :mydate:= next_date; IF broken THEN :b := 1;ELSE :b := 0; END IF; END;

5148 0 87.22 1.014 selectobj#,type#,ctime,mtime,stime,status,dataobj#,flags,oid$, spare1, spare2 fromobj$ where owner#=:1 and name=:2and namespace=:3 and remoteowner isnull and linkname is null and subnameis null

4550 24 98.38 120.28 BEGINdb_watch.dbw_executeTask(:1,:2);END;

3619 2 97.86 1.897 SELECT DBW_RUNSELECT (:B1 )FROM DUAL

3287 1 92.64 0.956 selectowner#,name,namespace,remoteowner,linkname,p_timestamp,p_obj#,nvl(property,0),subname,d_attrs fromdependency$ d, obj$ o whered_obj#=:1 and p_obj#=obj#(+) orderby order#

2517 0 89.24 0.875 select /*+ rule */ bucket, endpoint,col#, epvalue from histgrm$ whereobj#=:1 and intcol#=:2 and row#=:3order by bucket

1728 0 94.62 0.291 selectgrantee#,privilege#,nvl(col#,0),max(mod(nvl(option$,0),2))from objauth$where obj#=:1 group bygrantee#,privilege#,nvl(col#,0) orderby grantee#


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

1726 1 83.25 1.284 select /*+ index(idl_ub1$ i_idl_ub11)+*/ piece#,length,piece from idl_ub1$where obj#=:1 and part=:2 andversion=:3 order by piece#

1604 10 99.23 181.729 BEGINdbw_t4.dbw_executeTask(:1,:2); END;

1591 18 97.2 41.279 BEGINdbw_1702_1.dbw_executeTask(:1,:2);END;

Executions Average buffer gets Hitratio


284029 1 100.0 0.077 COMMIT

27695 5 99.12 0.191 select intcol#,nvl(pos#,0),col#,nvl(spare1,0)from ccol$ where con#=:1

21199 12 99.98 0.216 select privilege#,level from sysauth$ connectby grantee#=prior privilege# and privilege#>0start with grantee#=:1 and privilege#>0

15545 4 97.84 0.381 selectname,intcol#,segcol#,type#,length,nvl(precision#,0),decode(type#,2,nvl(scale,-127/*MAXSB1MINAL*/),178,scale,179,scale,180,scale,181,scale,182,scale,183,scale,231,scale,0),null$,fixedstorage,nvl(deflength,0),default$,rowid,col#,property,nvl(charsetid,0),nvl(charsetform,0),spare1,spare2,nvl(spare3,0) from col$ where obj#=:1order by intcol#

15042 7 99.45 0.185 select pos#,intcol#,col#,spare1,bo#,spare2from icol$ where obj#=:1

11959 3 87.22 1.014 selectobj#,type#,ctime,mtime,stime,status,dataobj#,flags,oid$, spare1, spare2 from obj$ whereowner#=:1 and name=:2 and namespace=:3and remoteowner is null and linkname is nulland subname is null

10569 3 97.54 0.168 select /*+ rule */ bucket_cnt, row_cnt,cache_cnt, null_cnt, timestamp#, sample_size,minimum, maximum, distcnt, lowval, hival,density, col#, spare1, spare2, avgcln fromhist_head$ where obj#=:1 and intcol#=:2

9290 3 94.62 0.291 selectgrantee#,privilege#,nvl(col#,0),max(mod(nvl(option$,0),2))from objauth$ where obj#=:1group by grantee#,privilege#,nvl(col#,0) orderby grantee#

9181 2 94.9 0.478 select col#, grantee#,privilege#,max(mod(nvl(option$,0),2)) fromobjauth$ where obj#=:1 and col# is not nullgroup by privilege#, col#, grantee# order bycol#, grantee#

8442 9 99.46 0.224 selectcon#,type#,condlength,intcols,robj#,rcon#,match#,refact,nvl(enabled,0),rowid,cols,nvl(defer,0),mtime,nvl(spare1,0) from cdef$ whereobj#=:1


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

Collected Executions Averagerowsprocessed

Averagebuffergets

Hitratio

Average CPU (sec) Averageelapsed time(sec)

SQL text


13. Alert log

13.1. Status on check informationThe following list shows configuration and status of the Alert log file.Presentation generation failed during retrieval of values from database. Techical error: No task [name =Alert log check 10g, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]

13.2. Alert log WARNING historyThe table shows Alert-log checks history. Each row represents a warning result created by the Alert-logcheck.

Status Occured (date) Execution Details


14. Flash recovery area usage

14.1. Flash recovery area usageThe following table lists information from V$FLASH_RECOVERY_AREA_USAGE dictionary view.Presentation generation failed during retrieval of values from database. Techical error: No task [name =Flash Recovery Area Usage, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]

14.2. Initialisation parametersThe following table lists Oracle initialisation parameters related to Flash Recovery Area. Thedb_recovery_file_dest_size parameter value is a user-specified limit on the amount of space that will beused by this database for recovery-related files, and does not reflect the amount of space available in theunderlying filesystem.Presentation generation failed during retrieval of values from database. Techical error: No task [name =Flash Recovery Area Usage, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]

14.3. RMAN CrosscheckYou can free up space from flash recovery area by deleting unnecessary files using RMAN DELETEcommand. If an operating system command was used to delete files, then use RMAN CROSSCHECK andDELETE EXPIRED commands.Presentation generation failed during retrieval of values from database. Techical error: No task [name =Flash Recovery Area Usage, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]


15. RMAN backup statistics

15.1. RMAN Backup HistoryThe table below shows history of RMAN backups.Presentation generation failed during retrieval of values from database. Techical error: No task [name =RMAN backup status, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]

15.2. Backup size historyThe chart below shows history of backup size.Presentation generation failed during retrieval of values from database. Technical error: Exception occuredduring contact with engine: Failed to execute for query [select start_time "Backup date",round(output_bytes/1048576) "Output (MB)" from V$RMAN_BACKUP_JOB_DETAILS order by 1 asc],SQL exception: ORA-00942: table or view does not exist Presentation generation failed during visualization. No DataSets found

15.3. RMAN Backup piecesThe table below shows history of RMAN backup pieces from V$BACKUP_PIECE dictionary view.Presentation generation failed during retrieval of values from database. Techical error: No task [name =RMAN backup status, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]

15.4. RMAN ConfigurationThe table below shows configuration values for RMAN parameters.Presentation generation failed during retrieval of values from database. Techical error: No task [name =RMAN backup status, company=dbwatch.no] found in dbWatch Engine [ora10g1 ole]


16. dbWatch engine This chapter shows system overview statistics.

16.1. dbWatch error logThe dbWatch error log shown below is a meta-data table, it contains all errors produced by the dbWatchEngine.

16.2. Installed enabled tasksThe table below shows installed enabled tasks. A task is an identifiable unit which can be scheduled forexecution and performs some action when executed. Last run and next run indicates the date when the taskwas last run and when the task will next be run. The schedule computes the next run. It consists of fourpositions. The first position (from left) indicates minute(s) an hour. The second position indicates hour(s) aday. The third position indicates week day(s). The fourth indicates day(s) a month. The * indicates everyminute, hour, day and month. A task is executable when it is enabled (1), or not executable when it isdisabled (0).

Information Occured (date) Code MessageEXCEPTION IN Free_Extentsprocedure

8/3/2007 10:44 -1013 ORA-01013: user requested cancel of current operation

EXCEPTION IN dbms_waits 12/4/2007 09:02 100 ORA-01403: no data found

dbw_registerDependency:Exception: 0

24/4/2007 09:34 -1 ORA-00001: unique constraint(DB_WATCH.PK_DBW_DEPENDENCIES) violated

dbw_registerDependency:Exception: 2

24/4/2007 09:34 -1 ORA-00001: unique constraint(DB_WATCH.PK_DBW_DEPENDENCIES) violated

EXCEPTION IN check_filelogprocedure ... 0. block check path -DBW_DUMP_DIR and filename -alert_ora10g1.log (utl_file_dir=*)

1/5/2007 22:03 -29283 ORA-29283: invalid file operationORA-06512: at "SYS.UTL_FILE", line 475ORA-29283: invalid file operation











TaskID Task Last run (date) Next run (date) Schedule Company Version115 File IO statistics 15/9/2009 17:35 15/9/2009 00:00 4,14,24,34,44,

54 * * *dbwatch.no 1.2


16.3. Task descriptionThe table below contains a description of the installed tasks.

114 Session load 15/9/2009 17:35 15/9/2009 00:00 10,30,50 * * * dbwatch.no 1.1

113 AGRESSO ApplicationServer

15/9/2009 14:30 15/9/2009 00:00 0,10,20,30,40,50 8-18 * *

dbwatch.no 1.2

112 AGRESSO DWS shadowtables

11/9/2009 07:13 12/9/2009 00:00 10 7 * * dbwatch.no 1.1

111 Blocking detector 15/9/2009 17:37 15/9/2009 00:00 * * * * dbwatch.no 1.2

110 Free extents check 14/9/2009 11:51 14/9/2009 00:00 50 6,11,18 * * dbwatch.no 1.1

109 Archive status Check 15/9/2009 17:37 15/9/2009 00:00 * * * * dbwatch.no 1.3

108 Free space Check 14/9/2009 11:45 14/9/2009 00:00 45 6,11,18 * * dbwatch.no 1.5

107 File status check 15/9/2009 17:37 15/9/2009 00:00 * * * * dbwatch.no 1.4

106 Buffer cache statistics 15/9/2009 14:31 15/9/2009 00:00 1,11,21,31,41,51 * * *

dbwatch.no 1.3

105 Database memory statistics 15/9/2009 17:33 15/9/2009 00:00 3,13,23,33,43,53 * * *

dbwatch.no 1.3

103 dbwatch system data 11/9/2009 07:03 12/9/2009 00:00 0 7 * * dbwatch.no 1.1

98 framework 7/9/2009 05:50 14/9/2009 00:00 50 5 1 * dbwatch.no 1.3

97 DBMS uptime 15/9/2009 17:37 15/9/2009 00:00 * * * * dbwatch.no 1.3

95 Segment size collector(large segments -- detail)

11/9/2009 06:58 11/9/2009 00:00 55 6,17 * * dbwatch.no 1.4

93 Segment size status ("oldstyle" tablespaces)

11/9/2009 06:43 11/9/2009 00:00 40 6,17 * * dbwatch.no 1.1

81 User memory statistics 15/9/2009 17:37 15/9/2009 00:00 7,17,27,37,47,57 * * *

dbwatch.no 1.5

80 SQL statement statistics 10g 14/9/2009 11:30 14/9/2009 00:00 30 6,11,18 * * dbwatch.no 1.4

79 Undo statistics 15/9/2009 17:28 15/9/2009 00:00 8,18,28,38,48,58 * * *

dbwatch.no 1.1

77 Database network statistics(SQL*NET)

15/9/2009 17:37 15/9/2009 00:00 7,17,27,37,47,57 * * *

dbwatch.no 1.3

72 Disk read statistics 15/9/2009 17:36 15/9/2009 00:00 * * * * dbwatch.no 1

70 Oracle EnvironmentInformation Collector

15/9/2009 17:37 15/9/2009 00:00 * * * * dbwatch.no 1.3

55 Redo statistics 15/9/2009 17:36 15/9/2009 00:00 6,16,26,36,46,56 * * *

dbwatch.no 1.2

53 Top user memory usage 15/9/2009 17:37 15/9/2009 00:00 * * * * dbwatch.no 1.1

51 Latch statistics 15/9/2009 17:35 15/9/2009 00:00 5,15,25,35,45,55 * * *

dbwatch.no 1.1

49 DBMS waits 15/9/2009 17:32 15/9/2009 00:00 2,12,22,32,42,52 * * *

dbwatch.no 1.2

6 Segment size collector (allsegments -- aggregate)

11/9/2009 06:53 11/9/2009 00:00 50 6,17 * * dbwatch.no 1.8

TaskID Description115 Collects io statistics for all data files.

114 Recordes the number of active sessions over time.

113 Checks if the AGRESSO Application Server is connected to the databasen, and with how many sessions.

112 Check the total size of all shadow tables used by the Agresso DWS (Data Warehouse Server) process.


16.4. Check descriptionThe table lists all checks that are currently installed on the dbWatch Engine. The status indicates the mostrecent status of that check. It is represented by a number where 0 indicates OK,1 indicates WARNING and 2indicates ALARM. The acknowledgement is a an optional mechanism indicating that a certainwarning/alarm has been "recieved". 1 indicates that the check is registered with the akcnowledmentmechanism. The suspended column indicates the number of minutes a check is suspended, i.e. not executed.

111 Checks if a session is waiting on a TX (transaction) lock.

110 Checks free extents in all tablespaces.

109 Checks how many redolog files are not archived.

108 Checks the level of free space for all tablespaces.

107 Reacts on changed status of data files and/or temporary files .

106 Gets the statistics for data cache (buffer cache in SGA).

105 Collects statistics about instance memory.

103 Collects system information.

98 Upgrade patch to engine framework version 8.0.

97 Collects database uptime statistics.

95 Collects information (size and extent number) for the largest segments in the database.

93 Checks segment storage definition in tablespaces where extent management is not set to local.

81 Collects user memory statistics.

80 Collects SQL statements status for oracle engine. (for "Oracle 10g" only)

79 Collects rollback segment statistics.

77 Gets the SQL*NET status.

72 Collects disk reads statistics from v$system_event performance view for db file sequential read evnet (a single-block read, f.exp. index fetch by ROWID) and a db file scattered read event (a multiblock read, f.exp a full-table scan).

70 Collects environment information about the database.

60 Runs performance test on database.The procedure executes SELECT, INSERT, UPDATE, DELETE andTRUNCATE statements on dbwatch engine schema test tables.

58 Checks for errors in a log file (e.i. backup log).

55 Gets information about redo-log files from some performance tables.

53 This check can be used to trace the memory usage per server-process (session).

51 Collects latch status statistics.

49 Collects DBMS waits statistics from the v$system_event performance view.

48 Allows Oracle to read/write files from file-systems.

47 Checks if the standby database is recieving archive files from master database.

36 This is description

6 Collects statistics of total number and size of all type of segments per segment-owner and tablespace_name.

CheckID Status Acknowledgement Suspended113 OK 1 0

112 OK 1 0

111 OK 1 0

110 OK 0 0

109 OK 1 0


16.5. Acknowledged tasksThe table shows checks history. Each row represents one execution result of one particular check.

108 OK 1 0

107 OK 1 0

93 OK 1 0

58 WARNING 1 0

53 OK 1 0

48 WARNING 1 0

47 OK 1 0

CheckID StatusID Status Occured (date) Execution Details108 3 WARNING 10/8/2009 16:21 SYSAUX 3,275% left, SYSTEM ,8653% left,

53 2 ALARM 10/8/2009 16:18 backgr. process running program ORACLE.EXE(LGWR) is usaging 4,9 MB of memory

53 1 ALARM 10/8/2009 16:17 backgr. process running program ORACLE.EXE(LGWR) is usaging 4,9 MB of memory

108 2 WARNING 10/8/2009 16:14 SYSAUX 3,275% left, SYSTEM ,8653% left,

108 1 WARNING 10/8/2009 16:09 SYSAUX 3,275% left, SYSTEM ,8653% left,

48 1559 WARNING 10/8/2009 12:13 Listener log path not configured

58 101 WARNING 9/8/2009 05:15 backup log path not configured


























16.6. Dbwatch version trackingThe table shows dbwatch version tracking information.












Source

MajorVersion

MinorVersion

PatchNumber

BuildNumber

ScriptFile Name(date)

InstalledOn

Author EngineDescription

engine_oracle_10

5 1 10 dbWatch 2006 \engine_framework\Source\project_dbwatch_2006\oracle\oracle10_engine\Release\engine_oracle_10.xml

6/3/200713:56

dbWatchAS

engine_oracle_10_5.1_P10.xml

health check report for oracle 10g database

Documents