Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The current status of a process can be any of the following statuses:

 Icon 
  
  
  

...

Description
Image AddedThe process is running.
Image Added

...

The process completed successfully.
Image AddedThe process failed during the run.

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.

...

All processes are scheduled to automatically run at the set interval, but you may also manually run a process whenever required. See “Process parameters” on page 70 Process parameters.

To run a process manually•    In

  • In the Process table, select a process and click Run.

The process starts and the page refreshes to show the updated status icon.

...

You can examine additional information about the past executions of a process, for example to find out which tables were affected during a specific execution or which component has failed during a run.

To view the run history1.    In

  1. In the Process table, select a process and click Run History.

...

  1. In the Run History dialog box, in the top table, select the execution that you want to focus on, such as the last execution that failed (indicated by the status icon). The bottom table populates with detailed information on the performance processes tables that the execution affected.

...

  1. Investigate all relevant data and click Close.

...

  1. For example, if an error occurred, focus on the details in the Error Message column.

Anchor
ProcessParameters
ProcessParameters
Process parameters

Specific parameters define the execution behavior of performance processes. These parameters function as a filter in that they determine exactly which information is collected and saved in the Warehouse workstation.

...

The following table lists all the processes that you can configure per monitored instance.

Table 5-1    Processes 1 Processes configurable per instance

Technology    Process

DB2    Explain Statement

DB2    Explain New Statements

DB2    Load Data

DB2    Purge Internal Data

J2EE    Load Data

Oracle    Load Data

Oracle    Purge Data

...

TechnologyProcess
DB2Explain Statement
DB2Explain New Statements
DB2Load Data
DB2Purge Internal Data
J2EELoad Data
OracleLoad Data
OraclePurge Data
OracleExplain Statements
Oracle (SmarTune)

...

Changes
SQL

...

Server

Load Data

You can restrict the number of sessions that performance data is collected for by increasing the In

...

MS-SQL Time value. However, this value applies to the collapsed statement, including all of its children.

For example, if you set the In MS-SQL Time value to 2 and the collapsed statement includes five children that spent 1 second each in MS-SQL, this amounts to 5 seconds overall and causes Precise for SQL Server to collect the performance data for the collapsed statement, even though each child spent less than the defined 2 seconds in MS-SQL.

SQL

...

ServerExplain Statements
SQL

...

ServerExplain New Statements
SQL

...

ServerCollect Objects Performance
SQL

...

ServerCollect Operational Statistics
SQL

...

ServerCollect Space Usage
SQL

...

ServerCollect Schema Changes
SQL

...

ServerPurge Internal Data
SQL

...

ServerPerform SmarTune Analysis
Sybase

...

Explain Statements
Sybase

...

Collect Space Utilization

...

SybaseExplain New Statements
Sybase

...

Load Data

...

SAPLoad Data
Microsoft .

...

NETLoad Data
Microsoft .NET (SmarTune)

...

Perform SmarTune Analysis
Operating

...

SystemLoad Data
OtherLoad Data
TuxedoLoad Data
WebSphere MQLoad Data
PMDBPurge Data
PMDBSummarize Data
SmartLinkLoad Data
WebLoad

Other    Load Data

Tuxedo    Load Data

WebSphere MQ    Load Data

PMDB    Purge Data.

PMDB    Summarize Data

SmartLink    Load Data

...

Data

The following table lists the processes that you cannot configure.

Table 5-2    Processes 2 Processes that cannot be configured

...