Information to Collect or Consider On Receipt of Performance Related SR
(Doc ID 2103159.1)
Last updated on NOVEMBER 05, 2024
Applies to:
Oracle Life Sciences Argus Safety - Version 5.1 to 8.0.1 [Release 5.1 to 8.0]Information in this document applies to any platform.
Purpose
Questions to Ask when A New Argus Performance SR is Raised to Support
Scope
For Oracle Argus Support Engineers (LSGBU)
Details
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
| Purpose |
| Scope |
| Details |
| Confirm a count of the number of cases in the database (run query as Argus Application Schema owner e.g. ARGUS_APP) |
| Confirm a rough number of active users on the system when the slowdown is apparent, query below can be used as DBA user: |
| Examine database server resource utilization on the db server during slow down period (See Note 2103419.1) |
| Examine resource utilization on the Web Server during slow down period. this can be checked using process below: |
| Examine resource utilization on the Transaction (AG) Server during the period of slowdown (repeat process above to open resource monitor on Transaction server) |
| Confirm when DBMS_STATS were last collected for ESM and ARGUS_APP schemas ? |
| Check Tablespace free space on the Oracle Database e.g. run below query from SQL*Developer or SQL*Plus as DBA user: |
| Check CMN_ERROR_LOG for any reported issues on date of slowdown E.G. |
| Check Argus [Utilities] - Error Logs from Argus UI |
| How many web, report, transactional servers are there? If customers have a network diagram then please get that diagram |
| Gather AWR (Automatic Workload Repository), ASH (Active Session History), ADDM (Automatic Database Diagnostic Monitor) reports (As needed - Note only required if confirmed to be DB related.) |
| If slow performing queries are known – Get the Explain plan of the query with cardinality, cost, time, io. |
| Gather a Database trace for the duration/session. |
| If slowdown is for AG Service Tasks consider Database Session Log Capture (How to take Database Session Logs for Argus Safety AG Service Tasks? (Doc ID 1508041.1)) |
| Check Database Alert log if anything is failing on the database front. |
| Capture SQLTimes for application during the slow access period (See Note 1087179.1: Enabling Debug (SQLTIMES) - Oracle Life Sciences Argus Safety) |
| Confirm if Using Load Balancer on Web Servers ? |
| Confirm if installation is Single or Multi-tenant ? |
| Confirm if any Argus or Microsoft Patches been applied since the slowdown period was noted |
| Additional Checklist: |
| References |