Serial number |
Device type |
Content/Parameters |
Parameter type |
Note |
1 |
Operating system Hierarchy |
System log |
State |
Check the log for ERR or warning |
Number of processes |
Performance parameters |
Check that the number of system processes is relatively stable |
System CPU Utilization |
Performance parameters |
Reference value Idle > 50% |
System memory Utilization |
Performance parameters |
Reference value free > 10% |
System IO Requests/sec |
Performance parameters |
Reference Values < 4000 |
System IO Request volume/slightly |
Performance parameters |
Reference value < 100M |
Network traffic |
Performance parameters |
|
Space utilization |
Performance parameters |
Reference value free > 10% |
2 |
Database hierarchy |
Availability of the database system |
State |
Check that the database is available |
Database log |
State |
Check the log for ERR or warning |
Number of database processes/sessions |
Performance parameters |
Check that the number of database processes is relatively stable |
Database Buffer Area |
Performance parameters |
Reference value: 50%-70% of total memory |
Database buffer hit Ratio |
Performance parameters |
Reference Values > 95% |
Database Space Idle Rate |
Performance parameters |
Reference Values > 20% |
Database Space Fragmentation Rate |
Performance parameters |
Reference Values < 10% |
Memory Sort Rate |
Performance parameters |
Reference Values > 90% |
Lock wait |
Performance parameters |
Reference value: No lock wait |
|
|
|
|
|
Daily Database Maintenance Project |
Serial number |
Device type |
Maintenance jobs |
Cycle |
Note |
|
Operating system level |
System Log Check |
Days |
|
Log log Check |
Days |
|
Disk space Check |
Days |
|
CPU utilization Check (peak and average) |
Days |
|
Memory usage Check (peak and average) |
Days |
|
|
Database level |
Database status Checks |
Days |
|
Log file Check |
Days |
|
Backup Status Check |
Days |
|
Remaining space check |
Days |
|
Monitoring database Performance |
Days |
|
System Resource Check |
Days |
|
Fault Handling |
Days |
|
Check for invalid database objects |
Week |
|
Check for constraints that don't work |
Week |
|
Collect aggregated performance data based on monitoring services |
Month |
|
Analyze the performance data collected above to identify bottlenecks and optimize |
Month |
|
Compare historical data to pre-contract future performance issues |
Month |
|
|
|
|
This article is from the IT system operations blog, so be sure to keep this source http://hichuann.blog.51cto.com/1024435/1553564
Database monitoring and routine maintenance projects