Oracle 11g tuning tips for ITNM
clarkrob 0600007N7W Visits (1899)
This article is intended for ITNM users who find themselves with an Oracle database, perhaps managed by another group, and are starting to question the database performance. There a few places where ITNM has a heavy transaction load on the database where scalability and performance effects can be magnified if the database is slow, especially at times when they overlap. The heavy hitters are,
I’ll describe how to use Oracle’s Automatic Workload Repository (AWR) reports to check and resolve two main causes of database slowness – available memory and redo log size. In addition, we can run the Active Database Diagnostic Monitor (ADDM) report to identify the top “findings” affecting performance and recommended actions to resolve each issue. Plus other tips we have come across in the field.
If you have any Oracle tips, maybe to get around a problem, please share them!