Question
Publicis Sapient
IN
Last activity: 7 Jan 2020 8:52 EST
Servers were unable to connect to the Database
Sudden increase of Load in servers due to database connectivity issues. We need a list of tables which are accessed by PEGA once the server is started so that troubleshooting could be initiated by database team.
Analyzing Logs
Sudden increase of Load in servers due to database connectivity issues. We need a list of tables which are accessed by PEGA once the server is started so that troubleshooting could be initiated by database team.
Analyzing Logs
We do know PEGA makes a connection from the start on with the database to gather the information for running the application. Does the application connects to a limited number of tables, or all tables? If limited, to which tables in a first instance is connected?
Accepted Solution
Swedbank AB
SE
Hello Ravi,
You can look for the following alerts in the PegaRULES-ALERT logs which are directly related to database performance:
Hello Ravi,
You can look for the following alerts in the PegaRULES-ALERT logs which are directly related to database performance:
- PEGA0002 - Commit operation time exceeds limit DB Commit Time
- PEGA0003 - Rollback operation time exceeds limit DB Rollback Time
- PEGA0004 - Quantity of data received by database query exceeds limit DB Bytes Read
- PEGA0005 - Query time exceeds limit DB Time
- PEGA0006 - Update operation time exceeds limit DB Time
- PEGA0007 - Database operation time exceeds limit DB Time
- PEGA0020 - Total connect interaction time exceeds limit Connect Total Time
- PEGA0025 - Performing list with blob due to non-exposed columns Reading BLOB Need Columns
- PEGA0026 - Time to connect to database exceeds limit Acquire DB Connection
- PEGA0027 - Number of rows exceeds database list limit DB List Rows
- PEGA0033 - Database query length has exceeded a specified threshold DB Query Length
- PEGA0039 - The size of a BLOB column read exceeds a threshold BLOB Size Read
- PEGA0040 - BLOB size written to the database exceeds a threshold BLOB Size Written
- PEGA0041 - Work object written to the pr_other table Work Object PR_OTHER
- PEGA0042 - Packaging of database query has exceeded operation time threshold DB Query
To know more about them, please refer below:
Thank you,
Pawan
Pegasystems Inc.
FR
Hello,
I believe your starting point should be a first analysis of your Pega logs. Especially ALERTS log I think, have you tried that already? Can you share those files with us? What Pega version are you running?
Accepted Solution
Swedbank AB
SE
Hello Ravi,
You can look for the following alerts in the PegaRULES-ALERT logs which are directly related to database performance:
Hello Ravi,
You can look for the following alerts in the PegaRULES-ALERT logs which are directly related to database performance:
- PEGA0002 - Commit operation time exceeds limit DB Commit Time
- PEGA0003 - Rollback operation time exceeds limit DB Rollback Time
- PEGA0004 - Quantity of data received by database query exceeds limit DB Bytes Read
- PEGA0005 - Query time exceeds limit DB Time
- PEGA0006 - Update operation time exceeds limit DB Time
- PEGA0007 - Database operation time exceeds limit DB Time
- PEGA0020 - Total connect interaction time exceeds limit Connect Total Time
- PEGA0025 - Performing list with blob due to non-exposed columns Reading BLOB Need Columns
- PEGA0026 - Time to connect to database exceeds limit Acquire DB Connection
- PEGA0027 - Number of rows exceeds database list limit DB List Rows
- PEGA0033 - Database query length has exceeded a specified threshold DB Query Length
- PEGA0039 - The size of a BLOB column read exceeds a threshold BLOB Size Read
- PEGA0040 - BLOB size written to the database exceeds a threshold BLOB Size Written
- PEGA0041 - Work object written to the pr_other table Work Object PR_OTHER
- PEGA0042 - Packaging of database query has exceeded operation time threshold DB Query
To know more about them, please refer below:
Thank you,
Pawan
Swedbank AB
SE
No problem Ravi,
If you're on Oracle, you also have the option to generate and review AWR reports.
Generally reviewing the hourly reports from the duration of similar issues is insightful.
In case you are on a different database, I'm sure there will be similar reports to gather insights, you can also raise a Support request with us to get this worked parallelly.
Thank you,
Pawan