...
Table 13-35 Storage Contention on Device findings
...
| Column | Description |
|---|
| What to do |
...
| next | - Examine the device activity over time and database files contention.
|
...
- Examine storage contention in Physical Disks, Devices and Files on the same raid group.
|
...
- Examine disks statistics.
|
| Advice |
...
- If the device is loaded by the monitored database only and by a singular entity (e.g. a file, object, or partition), consider splitting this load (e.g. separating the objects in the file, partitioning the object, etc).
|
...
- To relieve inter application logical contention, check if the database's I/O activity is balanced.
Spread heavy I/O consuming files across the storage devices, to avoid a situation in which few heavy files reside on the same storage device.
|
...
- To relieve intra application logical contention, check whether there are additional applications using the storage device. For example, if the number of I/O requests processed by the storage device is significantly higher that the requests sent by the database, it means that the storage device is being used by an additional application.
|
...
- To relieve physical contention, check whether there is significant I/O activity in the underlying shared physical disks and raid group. Another potential cause of contention are the EMC adapters (front director and disk director). If the load is imbalanced, consult with the storage administrator about relocating the information to other disks which reside on a more vacant location.
|
...
- Consider storage tiering - a faster device may reduce the I/O wait time significantly.
|
| Anchor |
|---|
| StorageContentiononDeviceSymmetrixThick |
|---|
| StorageContentiononDeviceSymmetrixThick |
|---|
|
Storage Contention on Device (Symmetrix Thick)
...
Table 13-36 Storage Contention on Device findings
...
| Column | Description |
|---|
| What to do |
...
| next | - Examine the device activity over time and database files contention.
|
...
- Examine storage contention in Physical Disks, Devices and Files on the same raid group.
|
...
- Examine disks statistics.
|
| Advice |
...
- If the device is loaded by the monitored database only and by a singular entity (e.g. a file, object, or partition), consider splitting this load (e.g. separating the objects in the file, partitioning the object, etc).
|
...
- To relieve inter application logical contention, check if the database's I/O activity is balanced.
Spread heavy I/O consuming files across the storage devices, to avoid a situation in which few heavy files reside on the same storage device.
|
...
- To relieve intra application logical contention, check whether there are additional applications using the storage device. For example, if the number of I/O requests processed by the storage device is significantly higher that the requests sent by the database, it means that the storage device is being used by an additional application.
|
...
- To relieve physical contention, check whether there is significant I/O activity in the underlying shared physical disks and raid group. Another potential cause of contention are the EMC adapters (front director and disk director). If the load is imbalanced, consult with the storage administrator about relocating the information to other disks which reside on a more vacant location.
|
...
- Consider storage tiering - a faster device may reduce the I/O wait time significantly.
|
| Anchor |
|---|
| StorageContentiononDeviceSymmetrixThin |
|---|
| StorageContentiononDeviceSymmetrixThin |
|---|
|
Storage Contention on Device (Symmetrix Thin)
...
Table 13-37 Storage Contention on Device findings
Column Description
| Column | Description |
|---|
| What to do |
...
| next | - Examine the device activity over time and database files contention.
|
...
- Examine storage contention in Physical Disks, Devices and Files on the same raid group.
|
...
- Examine disks statistics.
|
...
| Advice | - If the device is loaded by the monitored database only and by a singular entity (e.g. a file, object, or partition), consider splitting this load (e.g. separating the objects in the file, partitioning the object, etc).
|
...
- To relieve inter application logical contention, check if the database's I/O activity is balanced.
Spread heavy I/O consuming files across the storage devices, to avoid a situation in which few heavy files reside on the same storage device.
|
...
- To relieve intra application logical contention, check whether there are additional applications using the storage device. For example, if the number of I/O requests processed by the storage device is significantly higher that the requests sent by the database, it means that the storage device is being used by an additional application.
|
...
- To relieve physical contention, check whether there is significant I/O activity in the underlying shared physical disks and raid group. Another potential cause of contention are the EMC adapters (front director and disk director). If the load is imbalanced, consult with the storage administrator about relocating the information to other disks which reside on a more vacant location.
|
...
- Consider storage tiering - a faster device may reduce the I/O wait time significantly.
|
| Anchor |
|---|
| StorageContentiononDeviceSymmetrixFASTVP |
|---|
| StorageContentiononDeviceSymmetrixFASTVP |
|---|
|
Storage Contention on Device (Symmetrix F.A.S.T. VP)
...
Table 13-38 Storage Contention on Device findings
Column Description
| Column | Description |
|---|
| What to do |
...
| next | - Examine the device activity over time and database files contention.
|
...
- Examine storage contention in Physical Disks, Devices and Files on the same raid group.
|
...
- Examine disks statistics.
|
...
| Advice | - If the device is loaded by the monitored database only and by a singular entity (e.g. a file, object, or partition), consider splitting this load (e.g. separating the objects in the file, partitioning the object, etc).
|
...
- To relieve inter application logical contention, check if the database's I/O activity is balanced.
Spread heavy I/O consuming files across the storage devices, to avoid a situation in which few heavy files reside on the same storage device.
|
...
- To relieve intra application logical contention, check whether there are additional applications using the storage device. For example, if the number of I/O requests processed by the storage device is significantly higher that the requests sent by the database, it means that the storage device is being used by an additional application.
|
...
- To relieve physical contention, check whether there is significant I/O activity in the underlying shared physical disks and raid group. Another potential cause of contention are the EMC adapters (front director and disk director). If the load is imbalanced, consult with the storage administrator about relocating the information to other disks which reside on a more vacant location.
|
...
- Consider storage tiering - a faster device may reduce the I/O wait time significantly.
|
| Anchor |
|---|
| StorageContentionbetweenLogandDatafiles |
|---|
| StorageContentionbetweenLogandDatafiles |
|---|
|
Storage Contention between Log and Datafiles
...
Table 13-39 Storage Contention between Log and Datafiles findings
Column Description
| Column | Description |
|---|
| What to do |
...
| next | - Examine the device activity over time and database files contention.
|
...
- Examine storage contention in Physical Disks, Devices and Files on the same raid group.
|
...
- Examine disks statistics.
|
| Advice |
...
| It has been detected that the Transaction Log files share the storage devices (LUNs) with other database files. Consult the storage administrator about provisioning the storage devices (LUNs) better to avoid this. |
| Anchor |
|---|
| UnbalancedStorageDevicesActivity |
|---|
| UnbalancedStorageDevicesActivity |
|---|
|
Unbalanced Storage Devices Activity
...
Table 13-40 Unbalanced Storage Device Activity findings
Column Description
| Column | Description |
|---|
| What to do |
...
| next | - Compare the storage devices activity over time.
|
...
- Examine the storage devices statistics.
|
| Advice |
...
- In the activity tab, check which database files are the most I/O consuming and spread them evenly across the storage devices.
|
...
- Consult with the storage administrator and check for other applications using the same storage devices or their underlying physical disks.
|
...
- Consult with the storage administrator about the RAID policy. A different striping may spread the
|
...
- I/O load across the storage devices.
|
| Anchor |
|---|
| StoragewithLowCacheHitRatio |
|---|
| StoragewithLowCacheHitRatio |
|---|
|
Storage with Low Cache Hit Ratio
The instance was waiting for I/O on storage devices with low cache read hit ratio.
...
Table 13-41 Storage with Low Cache Hit Ratio findings
...
...
| next | Examine the storage devices statistics and hit radio. |
| Advice |
...
- It has been detected that the storage devices (LUNs) that serve the instance get bad cache performance (i.e. low "hit ratio"). To relief the cache contention, consult the storage administrator about the following:
|
...
- Expanding the storage cache allocated to the database devices.
|
...
- Enabling "EMC Cache Partitioning", to isolate the instance cache and avoid external contentions.
|
| Anchor |
|---|
| StorageContentionontempdb |
|---|
| StorageContentionontempdb |
|---|
|
Storage Contention on tempdb
...
Table 13-42 Storage Contention on tempdb findings
...
| Column | Description |
|---|
| What to do |
...
| next | - Examine the device activity over time and database files contention.
|
...
- Examine storage contention in Physical Disks, Devices and Files on the same raid group.
|
...
- Examine disks statistics.
|
...
| Advice | It has been detected that the undo tablespace files share the storage devices (LUNs) with other database files. Consult the storage administrator about provisioning the storage devices (LUNs) better to avoid this. |
Precise. Performance intelligence from click to storage. Learn more > >