Health Check Report for Oracle 10g Database

dbWatch Software AS www.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

Page 2


Databases The report encompasses information from the following databases: - ora10g1 ole

Page 2


1. Status overview 1.1. Status on check information The following table lists basic information on the installed checks. 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

1.2. Historical status - last 10 weeks The following table displays a list of Warnings/Alarms from the last 10 weeks. This gives a general indication on how the monitored system is responding with the current configuration. Week (#)

Warnings

Alarms

23

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

1.3. Warnings/Alarms per check The following table lists details of when the different W/A happened and which checks that actually generated them. Check

Warnings Last occured warning (date)

Alarms Last occured alarm (date)

Free space Check

3

2009-08-10 16:21:03.0

0


2 00

2009-08-10 12:13:07.0

0


1 01

2009-08-09 05:15:18.0

0

Page 3


1.4. Last 10 Warnings/Alarms The following table lists the 10 last occured warnings and alarms. Check

Status

Occured (date)

Free space Check

WARNING

10/8/2009 16:21


ALARM

10/8/2009 16:18


ALARM

10/8/2009 16:17

Free space Check

WARNING

10/8/2009 16:14

Free space Check

WARNING

10/8/2009 16:09


WARNING

10/8/2009 12:13


WARNING

9/8/2009 05:15


WARNING

7/8/2009 05:15


WARNING

6/8/2009 23:47


WARNING

6/8/2009 23:28

Page 4


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

2.1. Database information The table below lists the identification information for the database. SID

DBMS Type (vendor)

Version (#)

Database

Host

OS

ora10g1

Oracle

10.1.0.2.0

ORA10G1

OLE

32-bit Windows:

2.2. Database version The table below shows the Oracle version information. Banner Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - Prod PL/SQL Release 10.1.0.2.0 - Production CORE10.1.0.2.0 10.1.0.2.0Production Production TNS for 32-bit Windows: Version 10.1.0.2.0 - Production NLSRTL Version 10.1.0.2.0 - Production

2.3. Database Components The table below shows information from DBA_REGISTRY dictionary view which displays information about the components loaded into the database. Component ID

Status

Version

Component Name

AMD

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

Page 5


2.4. Availability statistics The table below shows availability information about the monitoring session. DBMS uptime

Monitored

Down

Uptime (%)

131 days 16 hours 3 min



92.98

2.5. DBMS uptime periods The 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. Period (#)

DBMS startup

Last sampled date

Period span (in days, hours and minutes)

8

10-09-2009 03:08

15-09-2009 17:35


7

16-08-2009 03:10

09-09-2009 15:49


6

13-08-2009 13:49

16-08-2009 03:08


5

12-08-2009 03:06

13-08-2009 11:26


4

11-08-2009 10:04

11-08-2009 20:16


3

30-07-2009 03:08

11-08-2009 08:31


2

11-06-2009 03:09

21-07-2009 14:01


1

27-04-2009 03:02

10-06-2009 15:53


2.6. Database growth rate The table below shows the total size of the database, space used and growth rate. Total size of DB (GB)

Space used (GB)

Growth rate (GB/year)

7.6

1.1

0.09

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

Page 6


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 of blocks (the smallest storage unit in Oracle). The blocks are connected to the file system blocks. A database usually consists of thousands of segments, so each cannot be monitored individually. We therefore retrieve detailed information about the segments that need to be monitored more closely, such as the largest segments in the database. This section displays information on all segment types and more detailed information on the largest segments.

3.1. Schemas The 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

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

Page 7


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

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

Page 8


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

3.5. Largest segments The 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)

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_ INDEX OBJ#_ICOL#_ST

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_HIST TABLE GRM_HISTORY

SYSAUX

25

10

SYS

I_SOURCE1

SYSTEM

25

10

INDEX

Page 9


3.6. Growth rate of the largest segments The 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

Page 10


4. Memory usage statistics This chapter shows memory statistics.

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

Path

spfile

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

4.2. Memory initialization parameters The 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. Dynamically allocated memory values are not visible to users and will be shown as zero values in the table below. 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.3. SGA pool size. The following chart shows SGA pool components' sizes in MB.

Page 11


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

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

Page 12


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

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 the applications using the system.

Page 13


5. Session statistics 5.1. Logon history Shows 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

Sessions

OlePC

24

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

Sessions

DBW

4

DBW_1702_1

4

DBW_DEMO

4

DBW_T4

4

DBW_T6

4

DB_WATCH

4

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

Sessions

dbWatch 9 (engine)

24

Page 14


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

Login time

Schema

Status

Hostname

Program name

DB_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

2009-09-15 17:26:11.0

DBW

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_1702_1

2009-09-15 17:26:10.0

DBW_1702_1

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)

DBW_T6

2009-09-15 17:26:08.0

DBW_T6

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_T6

2009-09-15 17:26:08.0

DBW_T6

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_DEMO

2009-09-15 17:26:08.0

DBW_DEMO

INACTIVE

OlePC

dbWatch 9 (engine)

DB_WATCH

2009-09-15 17:26:07.0

DB_WATCH

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_DEMO

2009-09-15 17:26:07.0

DBW_DEMO

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_T4

2009-09-15 17:26:07.0

DBW_T4

INACTIVE

OlePC

dbWatch 9 (engine)

DBW

2009-09-15 17:25:07.0

DBW

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_T6

2009-09-15 17:25:07.0

DBW_T6

INACTIVE

OlePC

dbWatch 9 (engine)

DB_WATCH

2009-09-15 17:25:07.0

DB_WATCH

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_T4

2009-09-15 17:25:07.0

DBW_T4

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_1702_1

2009-09-15 17:25:07.0

DBW_1702_1

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_T6

2009-09-15 17:24:59.0

DBW_T6

INACTIVE

OlePC

dbWatch 9 (engine)

DB_WATCH

2009-09-15 17:24:59.0

DB_WATCH

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_1702_1

2009-09-15 17:24:59.0

DBW_1702_1

INACTIVE

OlePC

dbWatch 9 (engine)

DBW

2009-09-15 17:24:59.0

DBW

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_DEMO

2009-09-15 17:24:59.0

DBW_DEMO

INACTIVE

OlePC

dbWatch 9 (engine)

DBW_T4

2009-09-15 17:24:56.0

DBW_T4

INACTIVE

OlePC

dbWatch 9 (engine)

Page 15


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

Page 16


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 to understand the use of the disk resources on the host machine. This chapter shows information concerning data files. The data files are physically located in the file 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 unit tablespace. Looking at the tablespace growth directly gives a more correct insight into how much disk resources particular applications (which typically have their own tablespaces) consume.

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

6.2. Statistics for data files with the highest average physical reads The 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 to satisfy 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 often it may be beneficial to store this file on its own disk.

Page 17


6.3. Datafiles with the highest average physical reads 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.4. Statistics for data files with the highest average physical writes The 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 the database. 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 your safest 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\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

Page 18


6.6. Aggregate IO history Shows aggregated reads and writes values per day.

6.7. File statistics The table below lists all data and temporary files in the database. File ID Size (MB)

Status

Type

Name

AUTOEXT Max Size (GB) ENSIBLE

Tablespace name (GB)

1

530

SYSTEM

DATA

E:\ORACLE\ORAD ATA\ORA10G1\SY STEM01.DBF

YES

32

SYSTEM

2

90

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\UN DOTBS01.DBF

32

UNDOTBS1

3

529

ONLINE

DATA

E:\ORACLE\ORAD ATA\ORA10G1\SY SAUX01.DBF

YES

32

SYSAUX

4

5

ONLINE

DATA

E:\ORACLE\ORAD ATA\ORA10G1\US ERS01.DBF

YES

32

USERS

5

100

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\KH UDIJA01.DBF

0

KHUDIJA

6

100

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\MA LABALA01.DBF

0

MALABALA

7

30

ONLINE

DATA

E:\ORACLE\ORAD ATA\ORA10G1\TO OLS01.DBF

NO

0

TOOLS

8

100

ONLINE

DATA

E:\ORACLE\ORAD ATA\ORA10G1\DB _WATCH01.DBF

YES

0

DB_WATCH

9

100

ONLINE

DATA

E:\ORACLE\ORAD ATA\ORA10G1\DB WATCH_01.DBF

YES

0

DBWATCH

10

100

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\DB WATCH_NO_DUM MY_01.DBF

0

DBWATCH_N O_DUMMY

Page 19

Health check report for Oracle 10g database 11

10

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\DB WATCH_OLE_01.D BF

1

DBWATCH_O LE

12

100

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\DB WATCH_T4_01.DB F

0

DBWATCH_T 4

13

100

ONLINE

DATA


0

DBWATCH_T 5

14

100

ONLINE

DATA


0

DBWATCH_T 6

15

100

ONLINE

DATA


0

DBWATCH_T 7

16

2

ONLINE

DATA


NO

0

DBWATCH

17

4

ONLINE

DATA


NO

0

DBWATCH

18

6

ONLINE

DATA


NO

0

DBWATCH

19

8

ONLINE

DATA


NO

0

DBWATCH

20

10

ONLINE

DATA


NO

0

DBWATCH

21

12

ONLINE

DATA


NO

0

DBWATCH

22

20

ONLINE

DATA

E:\ORACLE\ORAD ATA\ORA10G1\DB WATCH.DBF

YES

0

DBWATCH_T S_OLE

23

10

ONLINE

DATA

E:\ORACLE\ORAD YES ATA\ORA10G1\DB WATCH_TS_TEST. DBF

0

DBWATCH_T S_TEST

1

5420

ONLINE

TEMP

E:\ORACLE\ORAD ATA\ORA10G1\TE MP01.DBF

32

TEMP

Page 20

YES


7. Redolog analysis Redolog files contain information about transactions in the database. This information is used under 'media recovery' 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 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 archive activity 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 the redolog 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 switching so that switching can be performed regularly independent of the transactions.

7.1. Redolog files The table below lists existing redolog files. If several members (physical redolog files) belong to the same group they are mirrored (something which gives better 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)

Status

1

1

E:\ORACLE\ORADATA\ORA10G1\REDO01.LOG

10

INACTIVE

1

2


10

ACTIVE

1

3


10

CURRENT

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

Page 21


7.3. Redolog switch frequency per hour The 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 sure check that they are evenly distributed across the day.

7.4. Transaction frequency The chart below shows the transaction frequency.

Page 22


8. SQL*Net statistics 8.1. Logons statistics The following chart shows the history of the number of users connected to the system during the last 48 hours.

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

Page 23


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

Page 24


9. Tablespace statistics 9.1. Tablespaces The following table presents general statistics for the largest tablespaces (maximum 20 tablespaces will be shown). The “Free extents#” column may indicate defragmentation of the tablespace. 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.2. Tablespace size Used and free space in each of the 10 largest tablespaces.

Page 25


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

Page 26


10. Sorting and temporary space 10.1. Temporary data files The following table presents storage configuration for temporary files. Tablespace

Filename

Autoextensible (Y/N)

TEMP

E:\ORACLE\ORADATA\OR YES A10G1\TEMP01.DBF

Max size (GB)

Increment by (KB)

33

80

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 rows The following chart shows the number of rows sorted over the last 48 hours.

Page 27


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


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

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

Segment (type)

Segmentsize (MB)

Segments (#)

SYSTEM

ROLLBACK

0.38

1

UNDOTBS1

TYPE2 UNDO

38.81

34

11.2. Undo/Rollback segments statistics The table below lists statistics for the undo/rollback segments and their efficiency. The statistics to focus on are values in the columns "shrinks", "wraps" and "extends" of the first table. If the rollback segments are correctly defined, the "extends" values should be close to 0, and the values of "wraps" should be very low compared to values in the "writes" column. All rollback segments should also have "optimal size" value defined. For the segments that are not automatically managed the optimal size will tell how big the rollback segment is trying to be. In case it is set too low according to the amount of transactions you will se a high level of extends/shrinks in the following charts. If the segments are automatically managed the optimal size will be -1. For these segments you can configure the UNDO_RETENTION parameter in Oracle. ID Name Extents (#) Size (MB) Writes (#) Gets (#) Waits (#) Optimal size (MB)

Shrin Wraps ks (#) (#)

Exte nds (#)

0

SYSTE 6 M

0.37

28956

10185

8

-1

0

1

0

1

_SYSS 3 MU1$

1.12

57488474

57262

4

-1

15

115

30

2

_SYSS 3 MU2$

1.12

50638652

61235

10

-1

16

103

29

3

_SYSS 3 MU3$

1.12

45823014

54535

15

-1

17

116

39

4

_SYSS 3 MU4$

1.12

62239812

126754

11

-1

16

120

36

5

_SYSS 3 MU5$

1.12

26967046

96550

12

-1

13

86

42

6

_SYSS 3 MU6$

0.18

14298230

79994

19

-1

11

86

24

7

_SYSS 3 MU7$

0.18

5699136

56773

25

-1

10

75

16

Page 29


_SYSS 3 MU8$

0.18

12426092

64214

15

-1

5

27

8

9

_SYSS 2 MU9$

0.12

10477346

52472

17

-1

17

103

50

10

_SYSS 2 MU10$

0.12

7496808

39316

8

-1

5

23

6

11

_SYSS 2 MU11$

0.12

4113888

37493

15

-1

4

20

5

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 48 hours.

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 last 48 hours.

Page 30


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/undo segments 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.

Page 31


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

Page 32


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

12.1. Statistics for cursors with the highest value of rows processed The following table lists statistics for cursors with the highest value of records processed. Rows processed Average rows processed

Average buffer gets Hit ratio

Average CPU (sec) SQL text

203181

10

12

99.98

0.216

select privilege#,level from sysauth$ connect by grantee#=prior privilege# and privilege#>0 start with grantee#=:1 and privilege#>0

162380

10

4

97.84

0.381

select name,intcol#,segcol#,ty pe#,length,nvl(precision #,0),decode(type#,2,nvl( scale,127/*MAXSB1MINAL */),178,scale,179,scale, 180,scale,181,scale,182, scale,183,scale,231,scal e,0),null$,fixedstorage,n vl(deflength,0),default$, rowid,col#,property, nvl(charsetid,0),nvl(cha rsetform,0),spare1,spare 2,nvl(spare3,0) from col$ where obj#=:1 order by intcol#

87128

13

3

89.24

0.875

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

35956

1

5

99.12

0.191

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

34620

2

7

99.45

0.185

select pos#,intcol#,col#,spare1 ,bo#,spare2 from icol$ where obj#=:1

29209

3

9

99.46

0.224

select con#,type#,condlength,i ntcols,robj#,rcon#,matc h#,refact,nvl(enabled,0), rowid,cols,nvl(defer,0), mtime,nvl(spare1,0) from cdef$ where obj#=:1

Page 33


10846

85

53.29

31.168

SELECT switch_count as "Switch count (hour)", histr_date AS "History date" FROM db_watch.dbw_switch_ count_hour ORDER BY "History date"

21197

3

7

99.95

0.142

select privilege# from sysauth$ where (grantee#=:1 or grantee#=1) and privilege#>0

18938

2

3

94.62

0.291

select grantee#,privilege#,nvl( col#,0),max(mod(nvl(op tion$,0),2))from objauth$ where obj#=:1 group by grantee#,privilege#,nvl( col#,0) order by grantee#

15066

7533

362

37.01

380.793

SELECT a.owner_stype AS "Owner", a.total_count AS "Total count", a.total_size AS "Total Size", a.h_date AS "History date", b.counter AS "Position" FROM db_watch.dbv_all_owne r_stype_histr a, db_watch.dbv_largest_s chemas b WHERE a.owner = b.schema AND b.counter <3 ORDER BY "History date"

12.2. Statistics for cursors with the highest value of buffer gets The following table lists statistics for cursors with the highest value of buffer gets. Buffer gets Average buffer gets Hit ratio


1958353

249

91.36

12.47

DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN EMD_MAINTENANCE.EXECUTE_EM_DB MS_JOB_PROCS(); :mydate := next_date; IF broken 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


225059

1

100.0

0.077

COMMIT

207854

1267

99.23

181.729

BEGIN dbw_t4.dbw_executeTask(:1,:2); END;

Page 34


72

97.86

1.897

SELECT DBW_RUNSELECT (:B1 ) FROM DUAL

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 from icol$ where obj#=:1

86848

11

99.9

0.152

SELECT /*+ RULE */ STEP_ID FROM MGMT_JOB_EXECUTION E, MGMT_JOB J WHERE E.JOB_ID=J.JOB_ID AND STEP_STATUS IN (:B6 , :B5 , :B4 , :B3 , :B2 ) AND STEP_TYPE=:B1 AND J.EXECUTION_TIMEOUT > 0 AND (CAST(SYS_EXTRACT_UTC(SYSTIMESTA MP) AS DATE)-E.START_TIME) > (J.EXECUTION_TIMEOUT/24)

74724

9

99.46

0.224

select con#,type#,condlength,intcols,robj#,rcon#,matc h#,refact,nvl(enabled,0),rowid,cols,nvl(defer,0), mtime,nvl(spare1,0) from cdef$ where obj#=:1

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

Average disk reads

Hit ratio Average CPU (sec)

SQL text

185178

24

91.36

12.47

DECLARE job BINARY_INTEGER := :job; next_date DATE := :mydate; broken BOOLEAN := FALSE; BEGIN EMD_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

select obj#,type#,ctime,mtime,stime,status,da taobj#,flags,oid$, spare1, spare2 from obj$ where owner#=:1 and name=:2 and namespace=:3 and remoteowner is null and linkname is null and subname is null

4550

24

98.38

120.28

BEGIN db_watch.dbw_executeTask(:1,:2); END;

3619

2

97.86

1.897

SELECT DBW_RUNSELECT (:B1 ) FROM DUAL

3287

1

92.64

0.956

select owner#,name,namespace,remoteowner ,linkname,p_timestamp,p_obj#, nvl(property,0),subname,d_attrs from dependency$ d, obj$ o where d_obj#=:1 and p_obj#=obj#(+) order by order#

2517

0

89.24

0.875

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

1728

0

94.62

0.291

select grantee#,privilege#,nvl(col#,0),max(m od(nvl(option$,0),2))from objauth$ where obj#=:1 group by grantee#,privilege#,nvl(col#,0) order by grantee#

Page 35


1

83.25

1.284

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

1604

10

99.23

181.729

BEGIN dbw_t4.dbw_executeTask(:1,:2); END;

1591

18

97.2

41.279

BEGIN dbw_1702_1.dbw_executeTask(:1,:2); END;

12.4. Statistics of most executed cursors The following table lists statistics for most executed cursors. Executions Average buffer gets Hit ratio


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


15545

4

97.84

0.381

select name,intcol#,segcol#,type#,length,nvl(precisio n#,0),decode(type#,2,nvl(scale,127/*MAXSB1MINAL*/),178,scale,179,scale, 180,scale,181,scale,182,scale,183,scale,231,sca le,0),null$,fixedstorage,nvl(deflength,0),defaul t$,rowid,col#,property, nvl(charsetid,0),nvl(charsetform,0),spare1,spar e2,nvl(spare3,0) from col$ where obj#=:1 order by intcol#

15042

7

99.45

0.185

select pos#,intcol#,col#,spare1,bo#,spare2 from icol$ where obj#=:1

11959

3

87.22

1.014

select obj#,type#,ctime,mtime,stime,status,dataobj#,fl ags,oid$, spare1, spare2 from obj$ where owner#=:1 and name=:2 and namespace=:3 and remoteowner is null and linkname is null and 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 from hist_head$ where obj#=:1 and intcol#=:2

9290

3

94.62

0.291

select grantee#,privilege#,nvl(col#,0),max(mod(nvl(o ption$,0),2))from objauth$ where obj#=:1 group by grantee#,privilege#,nvl(col#,0) order by grantee#

9181

2

94.9

0.478

select col#, grantee#, privilege#,max(mod(nvl(option$,0),2)) from objauth$ where obj#=:1 and col# is not null group by privilege#, col#, grantee# order by col#, grantee#

8442

9

99.46

0.224

select con#,type#,condlength,intcols,robj#,rcon#,mat ch#,refact,nvl(enabled,0),rowid,cols,nvl(defer, 0),mtime,nvl(spare1,0) from cdef$ where obj#=:1

Page 36


12.5. History of resource demanding cursors The following table lists statistics for most resource demanding cursors. Collected Executions Average rows processed

Average buffer gets

Hit ratio

Page 37

Average CPU (sec) Average elapsed time (sec)

SQL text


13. Alert log 13.1. Status on check information The 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 history The table shows Alert-log checks history. Each row represents a warning result created by the Alert-log check. Status

Occured (date)

Execution Details

Page 38


14. Flash recovery area usage 14.1. Flash recovery area usage The 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 parameters The following table lists Oracle initialisation parameters related to Flash Recovery Area. The db_recovery_file_dest_size parameter value is a user-specified limit 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 underlying 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 Crosscheck You can free up space from flash recovery area by deleting unnecessary files using RMAN DELETE command. If an operating system command was used to delete files, then use RMAN CROSSCHECK and DELETE 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]

Page 39


15. RMAN backup statistics 15.1. RMAN Backup History The 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 history The chart below shows history of backup size. Presentation generation failed during retrieval of values from database. Technical error: Exception occured during 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 pieces The 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 Configuration The 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]

Page 40


16. dbWatch engine This chapter shows system overview statistics.

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

Occured (date) Code Message

EXCEPTION IN Free_Extents procedure

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_filelog procedure ... 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 operation ORA-06512: at "SYS.UTL_FILE", line 475 ORA-29283: invalid file operation


1/5/2007 22:13



1/5/2007 22:24



1/5/2007 22:34



1/5/2007 22:44



1/5/2007 22:54


16.2. Installed enabled tasks The table below shows installed enabled tasks. A task is an identifiable unit which can be scheduled for execution and performs some action when executed. Last run and next run indicates the date when the task was last run and when the task will next be run. The schedule computes the next run. It consists of four positions. The first position (from left) indicates minute(s) an hour. The second position indicates hour(s) a day. The third position indicates week day(s). The fourth indicates day(s) a month. The * indicates every minute, hour, day and month. A task is executable when it is enabled (1), or not executable when it is disabled (0). TaskID Task

Last run (date) Next run (date)

Schedule

115

15/9/2009 17:35

4,14,24,34,44, dbwatch.no 54 * * *

File IO statistics

15/9/2009 00:00

Page 41

Company Version 1.2


Session load

15/9/2009 17:35

15/9/2009 00:00

10,30,50 * * * dbwatch.no

1.1

113

AGRESSO Application Server

15/9/2009 14:30

15/9/2009 00:00

0,10,20,30,40, dbwatch.no 50 8-18 * *

1.2

112

AGRESSO DWS shadow tables

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, dbwatch.no 51 * * *

1.3

105

Database memory statistics

15/9/2009 17:33

15/9/2009 00:00

3,13,23,33,43, dbwatch.no 53 * * *

1.3

103

dbwatch system data

11/9/2009 07:03

12/9/2009 00:00

07**

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 ("old style" 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, dbwatch.no 57 * * *

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, dbwatch.no 58 * * *

1.1

77

Database network statistics (SQL*NET)

15/9/2009 17:37

15/9/2009 00:00

7,17,27,37,47, dbwatch.no 57 * * *

1.3

72

Disk read statistics

15/9/2009 17:36

15/9/2009 00:00

****

dbwatch.no

1

70

Oracle Environment Information 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, dbwatch.no 56 * * *

1.2

53


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, dbwatch.no 55 * * *

1.1

49

DBMS waits

15/9/2009 17:32

15/9/2009 00:00

2,12,22,32,42, dbwatch.no 52 * * *

1.2

6

Segment size collector (all segments -- aggregate)

11/9/2009 06:53

11/9/2009 00:00

50 6,17 * *

1.8

dbwatch.no

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

Description

115

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.

Page 42


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 and TRUNCATE 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.

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

Status

Acknowledgement

Suspended

113

OK

1

0

112

OK

1

0

111

OK

1

0

110

OK

0

0

109

OK

1

0

Page 43


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

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

StatusID

Status

Occured (date)

Execution Details

108

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


108

1

WARNING

10/8/2009 16:09


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

58

100

WARNING

7/8/2009 05:15


48

1558

WARNING

6/8/2009 23:47


48

1557

WARNING

6/8/2009 23:28


48

1556

WARNING

6/8/2009 23:08


48

1555

WARNING

6/8/2009 22:47


48

1554

WARNING

6/8/2009 22:27


48

1553

WARNING

6/8/2009 22:07


48

1552

WARNING

6/8/2009 21:47


48

1551

WARNING

6/8/2009 21:27


48

1550

WARNING

6/8/2009 21:07


48

1549

WARNING

6/8/2009 20:47


48

1548

WARNING

6/8/2009 20:27


48

1547

WARNING

6/8/2009 20:08


48

1546

WARNING

6/8/2009 19:47


48

1545

WARNING

6/8/2009 19:27


48

1544

WARNING

6/8/2009 19:07


48

1543

WARNING

6/8/2009 18:47


48

1542

WARNING

6/8/2009 18:27


48

1541

WARNING

6/8/2009 18:07


48

1540

WARNING

6/8/2009 17:47


48

1539

WARNING

6/8/2009 17:29


48

1538

WARNING

6/8/2009 17:07


48

1537

WARNING

6/8/2009 16:47


48

1536

WARNING

6/8/2009 16:27


Page 44


1535

WARNING

6/8/2009 16:07


48

1534

WARNING

6/8/2009 15:47


48

1533

WARNING

6/8/2009 15:27


48

1532

WARNING

6/8/2009 15:08


48

1531

WARNING

6/8/2009 14:47


48

1530

WARNING

6/8/2009 14:27


48

1529

WARNING

6/8/2009 14:08


48

1528

WARNING

6/8/2009 13:47


48

1527

WARNING

6/8/2009 13:27


48

1526

WARNING

6/8/2009 13:07


48

1525

WARNING

6/8/2009 12:47


48

1524

WARNING

6/8/2009 12:27


48

1523

WARNING

6/8/2009 12:07


48

1522

WARNING

6/8/2009 11:47


48

1521

WARNING

6/8/2009 11:28


48

1520

WARNING

6/8/2009 11:08


48

1519

WARNING

6/8/2009 10:47


48

1518

WARNING

6/8/2009 10:27


48

1517

WARNING

6/8/2009 10:07


48

1516

WARNING

6/8/2009 09:47


48

1515

WARNING

6/8/2009 09:27


48

1514

WARNING

6/8/2009 09:07


48

1513

WARNING

6/8/2009 08:48


48

1512

WARNING

6/8/2009 08:28


48

1511

WARNING

6/8/2009 08:07


48

1510

WARNING

6/8/2009 07:47


48

1509

WARNING

6/8/2009 07:27


48

1508

WARNING

6/8/2009 07:07


48

1507

WARNING

6/8/2009 06:47


48

1506

WARNING

6/8/2009 06:27


48

1505

WARNING

6/8/2009 06:08


48

1504

WARNING

6/8/2009 05:48


48

1503

WARNING

6/8/2009 05:27


58

99

WARNING

6/8/2009 05:15


48

1502

WARNING

6/8/2009 05:07


48

1501

WARNING

6/8/2009 04:47


48

1500

WARNING

6/8/2009 04:27


48

1499

WARNING

6/8/2009 04:07


48

1498

WARNING

6/8/2009 03:47


48

1497

WARNING

6/8/2009 03:27


48

1496

WARNING

6/8/2009 03:08


48

1495

WARNING

6/8/2009 02:48


48

1494

WARNING

6/8/2009 02:27


48

1493

WARNING

6/8/2009 02:07


Page 45


1492

WARNING

6/8/2009 01:47


48

1491

WARNING

6/8/2009 01:27


48

1490

WARNING

6/8/2009 01:07


48

1489

WARNING

6/8/2009 00:47


48

1488

WARNING

6/8/2009 00:28


48

1487

WARNING

6/8/2009 00:08


58

98

WARNING

5/8/2009 05:15


58

97

WARNING

4/8/2009 05:15


58

96

WARNING

3/8/2009 05:15


58

95

WARNING

2/8/2009 05:15


58

94

WARNING

1/8/2009 05:15


58

93

WARNING

31/7/2009 05:15


48

1486

WARNING

30/7/2009 23:47


48

1485

WARNING

30/7/2009 23:27


48

1484

WARNING

30/7/2009 23:07


48

1483

WARNING

30/7/2009 22:47


48

1482

WARNING

30/7/2009 22:27


48

1481

WARNING

30/7/2009 22:07


48

1480

WARNING

30/7/2009 21:48


48

1479

WARNING

30/7/2009 21:27


48

1478

WARNING

30/7/2009 21:07


48

1477

WARNING

30/7/2009 20:47


48

1476

WARNING

30/7/2009 20:27


48

1475

WARNING

30/7/2009 20:07


48

1474

WARNING

30/7/2009 19:47


48

1473

WARNING

30/7/2009 19:27


48

1472

WARNING

30/7/2009 19:07


48

1471

WARNING

30/7/2009 18:47


48

1470

WARNING

30/7/2009 18:27


48

1469

WARNING

30/7/2009 18:08


48

1468

WARNING

30/7/2009 17:47


48

1467

WARNING

30/7/2009 17:27


48

1466

WARNING

30/7/2009 17:07


48

1465

WARNING

30/7/2009 16:47


48

1464

WARNING

30/7/2009 16:27


48

1463

WARNING

30/7/2009 16:07


48

1462

WARNING

30/7/2009 15:47


48

1461

WARNING

30/7/2009 15:28


48

1460

WARNING

30/7/2009 15:07


48

1459

WARNING

30/7/2009 14:47


48

1458

WARNING

30/7/2009 14:27


48

1457

WARNING

30/7/2009 14:07


48

1456

WARNING

30/7/2009 13:47


48

1455

WARNING

30/7/2009 13:27


Page 46


1454

WARNING

30/7/2009 13:07


48

1453

WARNING

30/7/2009 12:48


48

1452

WARNING

30/7/2009 12:27


48

1451

WARNING

30/7/2009 12:07


48

1450

WARNING

30/7/2009 11:47


48

1449

WARNING

30/7/2009 11:27


48

1448

WARNING

30/7/2009 11:07


48

1447

WARNING

30/7/2009 10:47


48

1446

WARNING

30/7/2009 10:27


48

1445

WARNING

30/7/2009 10:07


48

1444

WARNING

30/7/2009 09:48


48

1443

WARNING

30/7/2009 09:27


48

1442

WARNING

30/7/2009 09:07


48

1441

WARNING

30/7/2009 08:47


48

1440

WARNING

30/7/2009 08:27


48

1439

WARNING

30/7/2009 08:07


48

1438

WARNING

30/7/2009 07:47


48

1437

WARNING

30/7/2009 07:27


48

1436

WARNING

30/7/2009 07:08


48

1435

WARNING

30/7/2009 06:47


48

1434

WARNING

30/7/2009 06:27


48

1433

WARNING

30/7/2009 06:07


48

1432

WARNING

30/7/2009 05:47


48

1431

WARNING

30/7/2009 05:27


58

92

WARNING

30/7/2009 05:16


48

1430

WARNING

30/7/2009 05:07


48

1429

WARNING

30/7/2009 04:47


48

1428

WARNING

30/7/2009 04:28


48

1427

WARNING

30/7/2009 04:07


48

1426

WARNING

30/7/2009 03:47


48

1425

WARNING

30/7/2009 03:27


58

91

WARNING

21/7/2009 05:16


58

90

WARNING

20/7/2009 05:16


58

89

WARNING

19/7/2009 05:15


58

88

WARNING

18/7/2009 05:15


58

87

WARNING

17/7/2009 05:15


48

1424

WARNING

16/7/2009 23:47


48

1423

WARNING

16/7/2009 23:27


48

1422

WARNING

16/7/2009 23:07


48

1421

WARNING

16/7/2009 22:47


48

1420

WARNING

16/7/2009 22:27


48

1419

WARNING

16/7/2009 22:07


48

1418

WARNING

16/7/2009 21:48


48

1417

WARNING

16/7/2009 21:27


Page 47


1416

WARNING

16/7/2009 21:07


48

1415

WARNING

16/7/2009 20:47


48

1414

WARNING

16/7/2009 20:27


48

1413

WARNING

16/7/2009 20:07


48

1412

WARNING

16/7/2009 19:48


48

1411

WARNING

16/7/2009 19:27


48

1410

WARNING

16/7/2009 19:07


48

1409

WARNING

16/7/2009 18:47


48

1408

WARNING

16/7/2009 18:27


48

1407

WARNING

16/7/2009 18:07


48

1406

WARNING

16/7/2009 17:47


48

1405

WARNING

16/7/2009 17:27


48

1404

WARNING

16/7/2009 17:08


48

1403

WARNING

16/7/2009 16:47


48

1402

WARNING

16/7/2009 16:27


48

1401

WARNING

16/7/2009 16:07


48

1400

WARNING

16/7/2009 15:47


48

1399

WARNING

16/7/2009 15:27


48

1398

WARNING

16/7/2009 15:07


48

1397

WARNING

16/7/2009 14:47


48

1396

WARNING

16/7/2009 14:27


48

1395

WARNING

16/7/2009 14:07


48

1394

WARNING

16/7/2009 13:47


48

1393

WARNING

16/7/2009 13:27


48

1392

WARNING

16/7/2009 13:07


48

1391

WARNING

16/7/2009 12:47


48

1390

WARNING

16/7/2009 12:28


48

1389

WARNING

16/7/2009 12:07


48

1388

WARNING

16/7/2009 11:47


48

1387

WARNING

16/7/2009 11:27


48

1386

WARNING

16/7/2009 11:07


48

1385

WARNING

16/7/2009 10:47


48

1384

WARNING

16/7/2009 10:27


48

1383

WARNING

16/7/2009 10:07


48

1382

WARNING

16/7/2009 09:47


48

1381

WARNING

16/7/2009 09:27


48

1380

WARNING

16/7/2009 09:07


48

1379

WARNING

16/7/2009 08:47


48

1378

WARNING

16/7/2009 08:27


48

1377

WARNING

16/7/2009 08:08


48

1376

WARNING

16/7/2009 07:47


48

1375

WARNING

16/7/2009 07:27


48

1374

WARNING

16/7/2009 07:07


48

1373

WARNING

16/7/2009 06:47


Page 48


1372

WARNING

16/7/2009 06:27


48

1371

WARNING

16/7/2009 06:07


48

1370

WARNING

16/7/2009 05:48


48

1369

WARNING

16/7/2009 05:27


58

86

WARNING

16/7/2009 05:15


48

1368

WARNING

16/7/2009 05:07


48

1367

WARNING

16/7/2009 04:47


48

1366

WARNING

16/7/2009 04:27


48

1365

WARNING

16/7/2009 04:07


48

1364

WARNING

16/7/2009 03:47


48

1363

WARNING

16/7/2009 03:27


48

1362

WARNING

16/7/2009 03:07


48

1361

WARNING

16/7/2009 02:48


48

1360

WARNING

16/7/2009 02:27


58

85

WARNING

15/7/2009 05:15


58

84

WARNING

2/7/2009 05:16


58

83

WARNING

1/7/2009 05:15


58

82

WARNING

20/6/2009 05:16


58

81

WARNING

17/6/2009 05:15


58

80

WARNING

16/6/2009 05:15


58

79

WARNING

9/6/2009 05:15


58

78

WARNING

5/6/2009 15:55


58

77

WARNING

5/6/2009 05:15


58

76

WARNING

26/5/2009 05:15


58

75

WARNING

24/5/2009 05:15


58

74

WARNING

23/5/2009 05:15


58

73

WARNING

22/5/2009 05:15


58

72

WARNING

21/5/2009 05:15


58

71

WARNING

20/5/2009 05:16


58

70

WARNING

19/5/2009 05:16


58

69

WARNING

18/5/2009 05:15


58

68

WARNING

17/5/2009 05:16


58

67

WARNING

16/5/2009 05:15


58

66

WARNING

15/5/2009 05:16


58

65

WARNING

14/5/2009 14:03


58

64

WARNING

14/5/2009 13:08


58

63

WARNING

14/5/2009 13:08


58

62

WARNING

14/5/2009 13:07


58

61

WARNING

14/5/2009 13:07


58

60

WARNING

14/5/2009 13:07


58

59

WARNING

14/5/2009 13:05


58

58

WARNING

14/5/2009 13:05


58

57

WARNING

14/5/2009 13:05


58

56

WARNING

14/5/2009 13:04


Page 49


55

WARNING

14/5/2009 11:17


58

54

WARNING

13/5/2009 16:32


58

53

WARNING

17/2/2009 10:45


58

52

WARNING

19/12/2008 05:15


58

51

WARNING

18/12/2008 05:15


58

50

WARNING

16/12/2008 05:15


58

49

WARNING

12/12/2008 05:15


58

48

WARNING

11/12/2008 05:15


58

47

WARNING

10/12/2008 05:15


58

46

WARNING

9/12/2008 05:15


58

45

WARNING

5/12/2008 05:15


58

44

WARNING

4/12/2008 05:16


58

43

WARNING

3/12/2008 05:15


58

42

WARNING

25/11/2008 05:15


58

41

WARNING

22/11/2008 05:15


58

40

WARNING

21/11/2008 05:16


58

39

WARNING

10/11/2008 05:15


58

38

WARNING

9/11/2008 05:15


58

37

WARNING

8/11/2008 05:15


58

36

WARNING

7/11/2008 05:15


58

35

WARNING

25/10/2008 05:16


58

34

WARNING

16/10/2008 05:15


58

33

WARNING

10/10/2008 05:15


58

32

WARNING

30/9/2008 05:15


58

31

WARNING

24/9/2008 05:15


58

30

WARNING

23/9/2008 05:15


58

29

WARNING

27/8/2008 13:34


58

28

WARNING

27/8/2008 12:20


58

27

WARNING

27/8/2008 11:56


58

26

WARNING

27/8/2008 11:41


58

25

WARNING

27/8/2008 11:27


58

24

WARNING

27/8/2008 11:26


58

23

WARNING

27/8/2008 11:23


58

22

WARNING

27/8/2008 10:17


58

21

WARNING

27/8/2008 10:07


58

20

WARNING

27/8/2008 10:01


58

19

WARNING

27/8/2008 09:46


58

18

WARNING

27/8/2008 09:45


58

17

WARNING

27/8/2008 09:45


58

16

WARNING

27/8/2008 09:43


58

15

WARNING

15/8/2008 05:15


58

14

WARNING

31/7/2008 05:15


58

13

WARNING

29/7/2008 05:15


58

12

WARNING

24/7/2008 14:00


Page 50

Health Check Report for Oracle 10g Database

Recommend Documents