Identifying Read/Write (I/O) Problems - Database

To achieve optimal database performance, 110 activity (read/write accesses) should be evenly distributed on the database's hard drives. You should avoidhot spots.

You can find important key figures on the 110 performance for an Oracle database in the DBA Cockpit via the following menu path:
PERFORMANCE • WAIT EVENT ANALYSIS • FILESYSTEM REQUESTS

There is a risk of an I/O bottleneck if individual drives show very high levels of utilization (UTIL. > 50% for hourly average)

You can resolve an I/0 bottleneck by improving the table distribution on the file system. In particular, ensure that the disks with high load contain no additional. frequently accessed files that could be relocated.

Examples of Files and Database Objects with High Read/Write Activity

Database System  File or Database ObjectIndependentOperating system swap space(high priority)SAP MaxDBLog area, system devspaceDB2Online log directory (high priority) Offline log directory (medium priority)OracleRedo log files (high priority) Tablespace PSAPROLL (medium priority)Directory for the offline redo log files (SAP ARCH)(medium priority)SQL ServerTransaction log (high priority) Tempdb (medium priority)