Error Message :
Performance issues seen in Applications Manager is generally caused by the Oracle Database. This can be seen if there are too many Jobs in the backlog, keeping to much historical data, lack of database tuning and maintenance. These types of slowness can seen by running our AMhealth script (request from Support if needed) or by reviewing logs or backlog load.
However, if sever slowness is seen while the previously listed indicators have been reviewed and determined to be not an issue, the issue may be outside Applications Manager. Reviewing what other Applications and/or Users that are connecting to the same Oracle installation can show that they are consuming database resources.
Some symptoms seen during performance degradation include:
- Slowness in Java Web Client log in
- Slowness in Client refresh such as Job updates
- Timeout Errors caused by random Client actions
- Unable to delete Jobs
- Automation Engine refresh timer not resetting
- Awinstall option 1 takes a long time to complete
- Awapi time out
OS Version: N/A
Root Cause: Other users/applications outside of Applications Manager is using DB resource
Reviewing what other Applications and/or Users that are connecting to the same Oracle installation can show that they are consuming database resources. In one case example, it was found that a large number of User connections was made to the database by another application and consumed all the available Oracle "temp" space. The lack of temp space caused the severe slowness seen in Applications Manager. Because Application Manager does not account for this, there is no clear error or indication that a lack of temp space was the root cause. Once the issue is resolved in the other application, Applications Manager slowness is also resolved.
Fix Status: No Fix