Agile Engineering Data Management (EDM) Performance Troubleshooting Guide
(Doc ID 1497912.1)
Last updated on FEBRUARY 16, 2019
Applies to:Oracle Agile Engineering Data Management - Version 184.108.40.206 and later
Information in this document applies to any platform.
This document provides a set of guidelines - essentially a checklist - to follow when troubleshooting performance issues with Agile Engineering Data Management (EDM).
These guidelines ensure that a standardized and efficient process is followed when troubleshooting EDM performance issues.
These guidelines deal with issues related to slow performance.
Distinguishing between good, acceptable and slow performance is difficult and depends on the action/function and the environment (hardware, network etc.). Upon first installation on a server, it is best to capture relevant statistics to establish a baseline of what performance should be. Over time, the performance is expected to degrade very gradually and should be monitored on regular intervals to identify potential issues. Also, regular maintenance should be performed to ensure peak performance.
This document is not intended to be used for issues concerning when Agile EDM cannot be started or functions are not working as expected.
Symptoms of EDM performance issues include:
- Overall Slowness of EDM
- Start of EDM client is slow
- Response times on UI activities are slow –e.g.
- Opening mask
- Loading records
- File Handling is slow
- Single file/Assembly
- Viewing files
- System becomes slower over time or after a certain event (e.g after changes in the network)
- Intermittent or continuous performance loss
NOTE: This document is targeted strictly towards experienced EDM Administrators.
Certain troubleshooting steps may also require actions from administrators from other areas of the deployment, for example network administrator, load balancer administrator, etc.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|1. Gather / clarify environment information|
|2. Gather / clarify symptoms in detail|
|3. Recommended steps based on identified issue|
|3.1. Client / Server Performance issue on main site (all users affected)|
|3.2. Remote sites (issue only on Remote sites)|
|4. List of all referenced knowledge base documents|
|5. List of additional knowledge base documents - related to troubleshooting, tracing possibilities, identified performance issues, etc.|