Page History
...
Under the Processes view (on the Warehouse workstation), you can run a process, view the execution history of a process, and configure the scheduling and the parameters of a process.
| Anchor | ||||
|---|---|---|---|---|
|
All processes are scheduled to automatically run at the set interval, but you may also manually run a process whenever required. See Process parameters.
...
Table 5-4 Precise processes not scheduled per instance
Technology Process
PMDB Calculate Baselines
SAP Organizational Mapping
WebSphere MQ Load Data
Tuxedo Load Data
Oracle Applications Load Data
Other Load Data
| Technology | Process |
|---|---|
| PMDB | Calculate Baselines |
| SAP | Organizational Mapping |
| WebSphere MQ | Load Data |
| Tuxedo | Load Data |
| Oracle Applications | Load Data |
| Other | Load Data |
To schedule a process1. Select
- Select a process in the Main area table and click Scheduling.
...
- In the Scheduling dialog box, perform any of the following tasks:
...
- Clear the Run this process in the PMDB check box to disable the process. This action removes the process from the PMDB Scheduler, but you can still run the process manually. See
...
- Manually running a
...
- process.
...
- Change the time that the process is scheduled to run.
...
- Each process runs at a predefined interval by default: Every 15 minutes (slice), hourly, daily, or weekly. You cannot change this interval, but you can set the exact time that the process runs, for example every 2 hours, 15 minutes after the hour.
...
- Schedule the process per instance (only available for some processes). This mechanism lets you perform the following tasks:
- Schedule the process per instance (only available for some processes). This mechanism lets you perform the following tasks:
...
- Disable a process for a specific instance by clearing the relevant check box in the first table column.
...
- Set the interval of an instance within the process. For example, if you set the Run Every... column to 2, the instance executes every 2 minutes (or other) run of the process.
...
- Click OK.
Batch processes in Precise
The following sections provide a description of all existing Precise batch processes. The following table lists all batch processes on the Warehouse workstation.
Table 5-5 Batch 5 Batch processes on the Warehouse workstationProcess Description
| Process | Description |
|---|---|
| Summarize |
...
| Data | Aggregates the loaded data into daily, weekly, and monthly summary tables. |
| Purge |
...
| Data | Deletes old and unnecessary data from the statistics tables in the Warehouse workstation. |
...
| ||
| Warehouse |
...
| Maintenance | Maintains the Warehouse workstation database. This process deletes old entries from the job history table and analyzes statistics and summary tables to update the database statistics. It also rebuilds and defrags indexes and maintains the normalization tables. |
| Calculate |
...
| Baselines | Tracks the exceptions of currently measured counters that are compared to their historical values. |
| Load |
...
| Data | Loads the data that is collected by a product into the database tables. This information lets you understand the behavior of your applications by examining their performance over time, identifying problematic time periods, and enabling you to drill down to the cause of the performance problem. Each product has its own Load Data process. |
| Organizational |
...
| Mappings | A daily process that maps each organization, as it appear 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. |
The following table lists all Precise for Oracle batch processes.
Table 5-6 Precise 6 Precise for Oracle batch processesProcess Description
| Process | Description |
|---|---|
| Explain |
...
| Statements | The PMDB can explain SQL statements that are loaded from the Precise for Oracle short-term history. This process explains new statements that have not yet been explained, or statements that have changed one of their dependent jobs. An object is considered changed either if its definition changes (for example when an index is created) or when its statistical data changes (for example the number of ‘dirty’ blocks in a table that is increased after running the Oracle Analysis command). |
| Collect Instance |
...
| Definitions | Collects the changes in the instance definition, such as changes of the init.ora file or database parameters. |
| Collect Instance |
...
| Statistics | Collects data on activity statistics of the Oracle server. |
| Collect Schema |
...
| Changes | Collects the schema definitions and statistics from the Oracle database, compares them to the definitions that are collected in the previous execution of the process, and stores changes in definitions. |
| Collect Objects Statistics Changes |
...
| Collects the statistics changes for tables, indexes, and columns (identified based on |
...
| DBMS_STATS execution). Also collects space utilization information for tablespaces. |
| Identify Changes (SmarTune) |
...
| Analyzes the changes to schema or instance settings to identify changes that affected the resource consumption or the response time (or both), either on the application level or even on the instance level. | |
Analyze Database Behavior (SmarTune) |
...
| Analyzes the instance behavior to detect places where your instance spends more time than expected. | |
| Purge |
...
| Data | Deletes old and unnecessary data that is related to instance definitions and schema changes. |
The following table lists all Precise for SQL Server batch processes.
Table 5-7 Precise 7 Precise for SQL Server batch processesProcess Description
| Process | Description |
|---|---|
| Explain |
...
| statements | Generates the execution plans for the statements that are collected by the Precise for SQL Server Collector agent and saves the execution plan information in the Warehouse workstation to enable you to tune these statements. This way, you can understand the execution plan that SQL Server chose for the statement, identify problematic operations in the execution plan, and analyze the objects that is referenced in this statement. |
| Collect Instance |
...
| Statistics | Loads the Instance Statistics counters that are sampled by the Precise for SQL Server Collector agent into the Warehouse workstation. These performance counters enable you to analyze various aspects of the performance of the SQL Server instance and the overall system (such as CPU, paging, I/O, Network) over time. |
| Collect DB File |
...
| Statistics | Samples SQL Server and collects I/O statistics for database files and saves the information that is sampled in the Warehouse workstation. This information lets you analyze the I/O activity of the database files over time and discover which files show heavy I/O activity so that you can make a sound judgment as to how these files should be dispersed amongst the various disks. |
| Collect Space |
...
| Utilization | Samples SQL Server to collect information on the space that is allocated and used by the tables, indexes, and database files and saves this information in the Warehouse workstation. This information lets you easily keep track of object growth over time and decide how to disperse database files over various disks and how to relate objects to FILEGROUPS in the specified database. |
| Collect Schema |
...
| Changes | Identifies the instance and database configuration changes, schema changes, and job changes that are performed in the SQL Server instance and saves the changes in the Warehouse workstation. This information lets you track and examine the changes that are performed on the instance and its entities and to understand how the changes affected the application’s performance. |
| Purge Internal |
...
| Data | Purges data as part of maintenance, such as purging an Availability log file. |
| Explain New |
...
| Statements | Similar to Explain Statements, but it is executed every 15 minutes and generates execution plans for a few of the most resource-consuming statements. This way, the execution plan information becomes available as soon as possible, and not only after the Explain Statements have been carried out (which would make the Execution plan information only available after a one-day delay). |
| Collect Job |
...
| Statistics | Samples SQL Server job runs and saves this information in the Warehouse workstation. This information lets you examine job runs over time, identify problematic time periods, and view the general trends in the job runs. |
The following table lists all Precise for Sybase batch processes.
Table 5-8 Precise 8 Precise for Sybase batch processes
| Process |
|---|
...
| Description |
|---|
| Explain |
...
| statements | Generates the execution plans for the statements that are collected by the Precise for Sybase Collector agent and saves the execution plan information in the PMDB to enable you to tune these statements. This way, you can understand the execution plan that Sybase chose for the statement, identify problematic operations in the execution plan, and analyze the objects that are referenced in this statement. |
| Collect Instance |
...
| Statistics | Loads the Instance Statistics counters that are sampled by Sybase Adaptive Server Enterprise (ASE) into the PMDB. These performance counters enable you to analyze various aspects of the performance of the Sybase instance (such as CPU, paging, I/O, Network) over time. |
| Collect Space |
...
| Utilization | Samples Sybase to collect information on the space that is allocated and used by the tables, indexes, segments, and database devices and saves this information in the PMDB. This information lets you easily keep track of object growth over time and decide how to disperse database files over various disks and how to relate objects to devices in the specified database. |
| Purge Internal |
...
| Data | Purges internal data as part of maintenance. |
| Explain New |
...
| Statements | Similar to Explain Statements, but it is executed every 15 minutes and generates execution plans for a few of the most resource-consuming statements. This way, the execution plan information becomes available as soon as possible, and not only after the Explain Statements have been carried out (which would make the Execution plan information only available after a one-day delay). |
| Sybase Replication Server: Load |
...
| Data | Loads the outbound processing Statistics counters that are sampled by the Sybase Replication Server Collector agent into the PMDB. These counters enable you to analyze the outbound processing phase of the replication system, and locate the specific component(s) which may be causing the latency in the replication system. |
The following table lists Precise SmartLink processes
Table 5-9 Precise 9 Precise SmartLink processesProcess Description
| Process | Description |
|---|---|
| Load |
...
| Data | Loads the data that is collected by a product into the database tables. This information lets you understand the behavior of your applications by examining their performance over time, identifying problematic time periods, and enabling you to drill down to the cause of the performance problem. |
...
|
...
To change the Load Data slice size, see |
...
...
size. |
| Anchor | ||||
|---|---|---|---|---|
|
Most process are specific to one technology. The “Load Data” process that does not have a Technology value is shared by SmartLink and J2EE. All changes to this value affect the slice size not only in SmartLink tabs, but also in all J2EE instances in that environment.
To modify the Precise SmartLink/J2EE Load Data Performance slice size1. Go
- Go to AdminPoint>Warehouse>Processes.
...
- From the table, select the “Load Data” process with an empty Technology value. Click Parameters.
...
- Select the relevant environment and click Edit.
...
- Mark the “Use Defaults” check box to enable editing.
...
- From the drop-down menu, select the desired slice size.
...
Click OK>OK.
...
Info Changing the “Load Data” value from “300” to “30” may take up to ten minutes to take affect in Precise for J2EE.
About the PMDB Summarize Data process parameters
The table below describes the configurable process parameters and default values in the PMDB Summarize Data process.NOTE The
| Info |
|---|
The following set of parameters is defined for each technology, server, and instance which is installed in the Precise system. |
Table 5-10 Configurable 10 Configurable process parameters and their default values
| Parameter |
|---|
...
| Default value |
|---|
| Summarize to daily level only top n |
...
| rows | 2000 rows |
| Summarize to weekly level only top n |
...
| rows | 3000 rows |
| Summarize to monthly level only top n |
...
| rows | 3000 rows |
| Anchor | ||||
|---|---|---|---|---|
|
...