A Transaction is Running Very Slowly (Oracle)
As a database administrator, end users will often ask you to investigate why a particular transaction or set of transactions are running slow. There are many factors to take into account when tracking down these types of problems. As this search may take a considerable amount of your time, you should gather as much background information as possible from the responsible parties before you begin.
Questions you should ask the end users include:
Having gathered this information, the DBA can try to identify where the performance bottleneck resides. Keep in mind that performance tuning is an iterative process and you will probably have to involve the end users at some point to determine whether the tuning steps you have taken have alleviated their problems.
If you feel this issue may be isolated to one particular transaction, program or application, you may also need assistance from the application developers. They will better understand the process flow of the application and can help to change and test statements in the program. It is not unusual for a program to function correctly in a development environment and then to perform poorly in production. A production system frequently has more data and more users than a test system.
There are three major areas which you should check when the above symptoms are reported.
Monitoring the shared SQL area (Oracle) Monitoring the Shared SQL Area (Oracle)