Page History
Configuring PMDB process parameters
This section includes the following topic:• About
- About configurable process parameters
About configurable process parameters
With the Load Data process parameters you are able to filter the Load Data results better, providing you with a better overview of the actual data. After selecting this parameter, you can select the instance for which you want to make changes to the default settings.
The following parameters that can be edited in AdminPoint>Warehouse Processes. Technology is the basis for the division of the process parameters:• DB2
- DB2
...
- J2EE
...
- MS .NET
...
- Operating System
...
- Oracle
...
- Oracle Applications
...
- Other
...
- PMDB
...
- SAP
...
- SQL Server
...
- Sybase
...
- Sybase Replication Server
...
- Tuxedo
...
- Web
...
- WebSphere MQ
...
| Info |
|---|
PMDB processes will not be executed if any of the following collector instances is down: SQL Server, Oracle, Sybase, or DB2. |
About the DB2 Explain Statements process parameters
The DB2 Explain Statements process automatically explains the top n statements. By default, this process is run only once a night.
The following table describes the configurable process parameter and default value in the DB2 Explain Statements process.
Table 7-1 Configurable 1 Configurable process parameter and its default value
| Parameter |
|---|
...
| Default value |
|---|
| Explain only Top-N Statements (based on their In DB2 time) |
...
| 100 | |
| Timeout if the Explain Process takes more than n |
...
| minutes | 60 |
| Explain process stops after N Statements fail to be |
...
| explained | 100 |
About the DB2 Explain New Statements process parameters
The DB2 Explain New Statements process automatically explains the top n statements. By default, this process is run every 15 minutes.
The following table describes the configurable process parameter and default value in the DB2 Explain Statements process.
Table 7-2 Configurable 2 Configurable process parameter and its default value
| Parameter |
|---|
...
| Default value |
|---|
| Explain only Top-N Statements (based on their In DB2 time) |
...
| 30 |
About the DB2 Load Data process parameters
The following table describes the configurable process parameter and default value in the DB2 Load Data process.
Table 7-3 Configurable 3 Configurable process parameter and its default valueParameter Default
| Parameter | Default value |
|---|---|
| Load only Top-N Programs |
...
| information | 300 |
| Load only Top-N Statements |
...
| information | 500 |
About the DB2 Purge Internal Data process parameters
The DB2 Purge Internal Data process automatically purges old internal data from the PMDB tables. By default, this process is run once a week.
The following table describes the configurable process parameter and default value in the DB2 Purge Internal Data process.
Table 7-4 Configurable 4 Configurable process parameter and its default valueParameter Default
| Parameter | Default value |
|---|---|
| Purge plans data older than n |
...
| days | 14 |
| Save the last n plans for each Explain |
...
| Statement | 3 |
About the J2EE Load Data process parameters
The following table describes the configurable process parameter and default value in the J2EE Load Data process.
Table 7-5 Configurable 5 Configurable process parameter and its default value
Parameter Default value
| Parameter | Default value |
|---|---|
| Collect only Top-N |
...
| records | 1000 |
| Number of executions over total service |
...
| time | Low |
| Load |
...
| Data | 30 |
About the Microsoft .NET Perform SmarTune Analysis process parameters
The following table describes the configurable process parameters and default values in the Perform SmarTune Analysis process.
Table 7-6 Configurable 6 Configurable process parameters and their default valuesParameter Default
| Parameter | Default value |
|---|---|
| Too many queued ASP.NET |
...
| requests | Maximum request queue length n queued items (5). |
| Long wait time for ASP.NET |
...
| requests | Maximum request wait time n milliseconds (1000). |
| Incorrect ASP.NET API cache usage - low hit |
...
| ratio | Minimum cache hit ratio n percent (80). |
| Incorrect ASP.NET API cache usage - high turnover |
...
| rate | Maximum cache turnover ratio n turnovers/second (100). |
| Incorrect ASP.NET output cache usage - low hit |
...
| ratio | Minimum cache hit ratio n percent (80). |
| Incorrect ASP.NET output cache usage - high turnover |
...
| rate | Maximum cache turnover ratio n turnovers/second (100) |
| Too many ASP.NET |
...
| errors | Maximum errors per request ratio (5). |
| Too many unhandled ASP.NET |
...
| exceptions | Maximum number of unhandled exceptions (0). |
| Too much time in garbage |
...
| collection | Normal CPU utilizations n percent (70). |
...
Maximum time in garbage collection for low CPU utilization n percent (5). Maximum time in garbage collection for high CPU utilization n percent (10). | |
| Object allocation problem | |
Maximum problem Maximum ratio garbage collection generations n percent (20).
...