Page History
This section includes the following topic:
...
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:
...
| Table of Contents |
|---|
...
|
...
|
| Info |
|---|
PMDB processes will not be executed if any of the following collector instances is down: SQL Server, Oracle, Sybase, or DB2. |
DB2
About the DB2 Explain Statements process parameters
...
| Parameter | Default value |
|---|---|
| Purge plans data older than n days | 14 |
| Save the last n plans for each Explain Statement | 3 |
J2EE
About the J2EE Load Data process parameters
...
| Parameter | Default value |
|---|---|
| Collect only Top-N records | 1000 |
| Number of executions over total service time | Low |
| Load Data | 30 |
Microsoft .NET
About the Microsoft .NET Perform SmarTune Analysis process parameters
...
| 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 ratio garbage collection generations n percent (20). |
| Too many garbage collection calls by user | Maximum number of induced garbage collection calls (0) |
| Too many exceptions thrown | Maximum number of thrown exceptions per second (50). |
| Contention rate too high | Maximum number of unsuccessful locks per second (50). |
| Incorrect connection string usage | Maximum number of different connection strings to database (10). |
| Slow database open connection | Maximum database open connection time n seconds (2). |
| Slow database requests execution | Maximum database execution time n seconds (10). |
| Slow page load | Maximum page load time n seconds (5). |
| Slow Web service invocation | Maximum Web service invocation time n seconds (5). |
| Slow XML document load | Maximum XML load time n seconds (2). |
| Incorrect garbage collection usage | Maximum number of garbage collection calls (0). |
| Slow serialization | Maximum serialization time per invocation time ratio n percent (10). |
| Slow de-serialization | Maximum de-serialization time per invocation time ratio n percent (10). |
| Too many calls for serialization | Maximum number of serialization invocations per second (100). |
| Too many calls for de-serialization | Maximum number of de-serialization invocations per second (100). |
| Incorrect usage of the Finalize method | Maximum number of calls to the finalized method (0). |
| Too many method invocations | Maximum method time n seconds (0.3). Maximum number of method invocations (100). |
| Too much time in lock | Maximum time in lock n seconds (0.2). |
Oracle
About the Oracle Collect Bind Variables process parameter
...
| Parameter | Default value |
|---|---|
| Collect only Top-N records | 1000 |
| Number of executions over total service time | Low |
Operating system
About the Operating System Load Data process parameters
...
| Parameter | Default value |
|---|---|
| Collect only Top-N records | 1000 |
| Size of memory over total CPU time | Low |
| Include Process ID details in time slice summary level | Cleared |
| Include Command and Process ID only got processes with CPU time greater than n seconds per time slice | 10 |
| Mask command according to | No default value |
Other
About the Other Load Data process parameters
...
| Parameter | Default value |
|---|---|
| Collect only Top-N records | 1000 |
| Number of executions over total service time | Low |
| Mask Client IP according to | No default value |
PMDB
About the PMDB Purge Data process parameters
...
| Parameter | Default value |
|---|---|
| Use Defaults | 30 seconds |
SAP
About the SAP Load Data process parameters
...
| Parameter | Default value |
|---|---|
Maps each organization, as it appears in the SAP system, to the physical site where its employees are located. Each organization can be mapped to more than one location. This mapping data is used to show SAP workload statistics according to locations. | Daily |
SQL Server
About the SQL Server Collect Operational Statistics process parameters
...
| Parameter | Default value |
|---|---|
| Preserve execution plan details | 6 months |
| Preserve access path and cost changes history | 18 months |
| Preserve schema change log | 6 weeks |
Sybase
About the Sybase Collect Space Utilization process parameters
...
| Parameter | Default value |
|---|---|
| Load only Top-N Statements information | 500 |
Tuxedo
About the Tuxedo Load Data process parameters
...
| Parameter | Default value |
|---|---|
| Collect only Top-N records | 1000 |
| Number of executions over total service time | Low |
Web Load Data
About the Web Load Data process parameters
...
| Parameter | Default value |
|---|---|
| Collect only Top-N URL records | 1000 |
| Number of executions weight over average URL service +network time | Medium |
| Consider SLA breach when filtering data | Selected |
| Collect only Top-N page records | 100 |
| Number of executions over average page response time | Medium |
| Consider SLA breach when filtering data | Selected |
| Collect Client IP | Cleared |
| Collect country | Cleared |
| Collect state | Cleared |
| Collect city | Cleared |
| Mask Client IP according to | No default value |
| Mask Private IP according to | No default value |
WebSphere MQ
About the WebSphere MQ Load Data process parameters
...