Versions Compared

Old Version 9

changes.mady.by.user Nadja Pollard

Saved on

compared with

New Version Current

changes.mady.by.user Nadja Pollard

Saved on

Key

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

...

The Processes view shows information about batch processes performance on the Warehouse work station. The Processes table in the Main area includes the following columns:

ColumnDescription
Node

The specific Precise framework installation.

Info

A Precise system can have one or more framework deployments.

TechnologyThe name of the technology that the process gathers data for. Processes that maintain the PMDB itself are listed, but the technology column remains empty.
Process

The process name is a logical name that describes the process function. For example, “Calculate Baselines.”

Two types of processes gather PMDB data. One process type includes processes that are part of the PMDB FocalPoint and run on the PMDB server, such as the Summarize Data process. The other process type includes processes that are part of another product, such as the Schema Changes process in a Microsoft SQL Server instance that Precise for SQL Server monitors. These processes run on the product’s server and on the PMDB FocalPoint, which is in charge of scheduling them. See

“Batch

Batch processes in

Precise” on page 75

Precise.

ProductThe name of the product the process runs for.
Last RunThe last time the process that is named in this row ran.
Next Scheduled RunTime when the process that is named in this row is scheduled to run again.
StatusAn icon indicating the current status of the process that is named in this row.

...


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.

Anchor
ManualRunProcess
ManualRunProcess
Manually running 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.

You can manually configure these parameters according to the requirements of your environment. You can edit the default values or override them by defining instance-specific values. If a process does not include any configurable parameters, the Parameters button is disabled. See “About About configurable process parameters” on page 87parameters.

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

...

SybaseCollect Space Utilization
Sybase

...

Explain New Statements

Sybase    Load Data

...

SybaseLoad 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

Technology    Process

...

TechnologyProcess
DB2Calculate Objects Usage
Oracle

...

Collect Instance Definitions

...

OracleCollect Instance Statistics
Oracle

...

Collect Schema Changes
Oracle

...

StorageLoad Data
OraclePerform SmarTune Analysis on DB Behavior
SQL

...

ServerCollect Instance Statistics
SQL

...

ServerCollect DB File Statistics
SQL

...

ServerCollect Job Statistics
SQL Server (Storage)

...

Load Data
Sybase

...

Collect Instance Statistics

...

SybasePurge Internal Data
Sybase Replication

...

SAP    Organizational Mapping

...

ServerLoad Data
SAPOrganizational Mapping
PMDBData Maintenance (Daily)
.

...

NETLoad Data

...


Summarize Current Data

 To To configure process parameters1.    In

  1. In the Main area table, select the process whose parameters you want to configure.

...

  1. Click Parameters.

...

  1. In the Parameters dialog box, perform one of the following actions:

    To edit the default values for the selected technology

    Click Edit Default Values.

    In the Default Values dialog box, specify the values and click OK.

    Unless instance-specific values override these values, they apply to all monitored instances.

    To edit the values for a specific instance

    Select an instance in the table. Click Edit.

    In the Edit Instance dialog box, clear the Use Defaults check box. Specify the values to be used for this instance.

    Click OK.

...

  1. In the Parameters dialog box, click OK.

    Info

...

  1. After you change the default of the Minimum In Oracle time to load parameter in the Load Data process, you must stop and then restart the Precise for Oracle FocalPoint. The next step is to restart the Collector agents.

    Info

    Changing the “Load Data” value from “300” to “30” for Precise for J2EE can take up to ten minutes to take effect.

    Info

    You can also configure the Precise for Web URL mapping rule for a domain in a system:

...

  1. "Treat pages with different titles as different

...

  1. pages." Select to view the URL along with the various titles that belong to it. The collected data includes page URLs and page titles. When cleared, you can only differentiate between different URLs, not between page titles. In this case, the collected data includes the page URL and the first page title for any URL in the system.

Scheduling processes

When the default scheduling settings do not match the requirements of your environment, you can manually schedule processes. Processes on the Warehouse workstation let you enable or disable each process. You can also schedule each process individually and run it at any frequency and interval - every 8 hours, hourly, daily, weekly, or by slice.

...

The following table provides information on the default execution intervals of all Precise batch processes.

Table 5-3    Default 3 Default intervals of Precise processes

Default

...

Weekly    PMDB    Purge Data

...

IntervalTechnologyProcess
WeeklyPMDBPurge Data
WeeklyPMDBWarehouse Maintenance (Weekly)

...

WeeklyPMDBCalculate Baselines
WeeklyOracleCollect Instance Definitions
WeeklyOracleCollect Schema Changes
WeeklyOraclePurge Data
WeeklyOracleIdentity

Weekly    PMDB    Calculate Baselines

Weekly    Oracle    Collect Instance Definitions

Weekly    Oracle    Collect Schema Changes

Weekly    Oracle    Purge Data

...

Changes (SmarTune)

...

WeeklySQL ServerCollect Schema Changes

...

WeeklySQL ServerPurge Internal Data

...

WeeklySybasePurge Internal Data

Daily    Oracle    Explain Statements

...

DailyOracleExplain Statements
DailyOracleCollect Objects Statistics Changes

Daily    SQL Server    Explain Statements

Daily    SQL Server    Collect Space Utilization

Daily    Sybase    Explain Statements

Daily    Sybase    Collect Space Utilization

Daily    SAP    Organizational Mapping

Daily    PMDB    Warehouse Maintenance (Daily)

Hourly    J2EE    Load Data

Hourly    Oracle Storage    Load Data

Every 8 hours    PMDB    Summarize Data

Hourly    Oracle    Collect Instance Statistics

Hourly    Oracle    Analyze Database Behavior (SmarTune)

Hourly    SQL Server    Collect DB File Statistics

Slice    Oracle    Load Data

Slice    Web    Load Data

Slice    SQL Server    Load Data

Slice    SQL Server    Collect Instance Statistics

Slice    SQL Server    Explain New Statements

Slice    Sybase    Load Data

Slice    Sybase    Collect Instance Statistics

Slice    Sybase    Explain New Statements

Slice    Sybase Replication Server    Load Data

Slice    SAP    Load Data

Slice    WebSphere MQ    Load Data

Slice    Tuxedo    Load Data

Slice    Oracle Applications    Load Data

Slice    Network    Load Data

Slice    Operating System    Load Data

...

DailySQL ServerExplain Statements
DailySQL ServerCollect Space Utilization
DailySybaseExplain Statements
DailySybaseCollect Space Utilization
DailySAPOrganizational Mapping
DailyPMDBWarehouse Maintenance (Daily)
HourlyJ2EELoad Data
HourlyOracle StorageLoad Data
Every 8 hoursPMDBSummarize Data
HourlyOracleCollect Instance Statistics
HourlyOracleAnalyze Database Behavior (SmarTune)
HourlySQL ServerCollect DB File Statistics
SliceOracleLoad Data
SliceWebLoad Data
SliceSQL ServerLoad Data
SliceSQL ServerCollect Instance Statistics
SliceSQL ServerExplain New Statements
SliceSybaseLoad Data
SliceSybaseCollect Instance Statistics
SliceSybaseExplain New Statements
SliceSybase Replication ServerLoad Data
SliceSAPLoad Data
SliceWebSphere MQLoad Data
SliceTuxedoLoad Data
SliceOracle ApplicationsLoad Data
SliceNetworkLoad Data
SliceOperating SystemLoad Data
SliceInsight SmartLinkLoad Data


The following table lists processes that cannot be scheduled per instance.

Table 5-4    Precise 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

...

TechnologyProcess
PMDBCalculate Baselines
SAPOrganizational Mapping
WebSphere MQLoad Data
TuxedoLoad Data
Oracle ApplicationsLoad Data
OtherLoad Data


To schedule a process1.    Select

  1. Select a process in the Main area table and click Scheduling.

...

  1. 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:

      ...

          • 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.

      ...

      1. Click OK.

      Anchor
      BatchprocessesinPrecise
      BatchprocessesinPrecise
      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

      ProcessDescription
      Summarize

      ...

      DataAggregates 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.

      ...

      Info

      ...

      Although you can set the purge settings per instance, it is recommended to use the same settings for all instances in the same AppTier. Otherwise, a 'No Data Found' message appears when you launch from one product to another, and inconsistent information may be displayed in

      ...

      cross-AppTier products like Insight and Report Manager.

      Warehouse

      ...

      MaintenanceMaintains 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

      ...

      BaselinesTracks the exceptions of currently measured counters that are compared to their historical values.
      Load

      ...

      DataLoads 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

      ...

      MappingsA 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

      ProcessDescription
      Explain

      ...

      StatementsThe 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

      ...

      DefinitionsCollects the changes in the instance definition, such as changes of the init.ora file or database parameters.
      Collect Instance

      ...

      StatisticsCollects data on activity statistics of the Oracle server.
      Collect Schema

      ...

      ChangesCollects 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

      ...

      DataDeletes 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

      ProcessDescription
      Explain

      ...

      statementsGenerates 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

      ...

      StatisticsLoads 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

      ...

      StatisticsSamples 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

      ...

      UtilizationSamples 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

      ...

      ChangesIdentifies 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

      ...

      DataPurges data as part of maintenance, such as purging an Availability log file.
      Explain New

      ...

      StatementsSimilar 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

      ...

      StatisticsSamples 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 processesProcess    Description

      ProcessDescription
      Explain

      ...

      statementsGenerates 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

      ...

      StatisticsLoads 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

      ...

      UtilizationSamples 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

      ...

      DataPurges internal data as part of maintenance.
      Explain New

      ...

      StatementsSimilar 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

      ...

      DataLoads 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

      ProcessDescription
      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.

      ...

      Info

      ...

      The Load Performance parameter for Precise SmartLink does not have a “Technology”

      ...

      value in the Display Warehouse Processes Information table in AdminPoint>Warehouse.

       

      To change the Load Data slice size, see

      ...

      Modifying the Precise Load Data slice

      ...

      size.

      Anchor
      ModifyLoadData
      ModifyLoadData
      Modifying the Precise Load Data slice size

      Most process are specific to one technology. The “Load Data” 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

      1. Go to AdminPoint>Warehouse>Processes.

      ...

      1. From the table, select the

      ...

      1. Load Data process with an empty Technology value. Click Parameters.

      ...

      1. Select the relevant environment and click Edit.

      ...

      1. Mark the Use Defaults check box to enable editing.

      ...

      1. From the drop-down menu, select the desired slice size.

      ...

      1. Click OK>OK.

      ...

      1. Info

        Changing the Load Data value from “300” to “30” may take up to

      ...

      1. 10 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.

      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

      ...

      rows2000 rows
      Summarize to weekly level only top n

      ...

      rows3000 rows
      Summarize to monthly level only top n

      ...

      rows3000 rows

      Anchor
      AboutViewingTheStatus
      AboutViewingTheStatus
      About viewing the status of the PMDB

      Under the Warehouse menu, the view shows information on the PMDB load status of each instance in your Precise installation. The Status table in the Main area includes the following columns:•    Server

      • Server. The name or IP address of the server on which the instance runs.

      ...

      • Technology. The technology type of the instance.

      ...

      • Instance. The name of the instance.

      ...

      • Unmonitored. Indication by an icon when the instance is unmonitored.

      ...

      • First Loaded. The date and time the first instance information was loaded into the PMDB.

      ...

      • Most Recently Loaded. The date and time the latest instance data was loaded into the PMDB.

      ...

      • Status. Icon indicating the status of the last load.

      Using the Warehouse command buttons, you can get more detailed information on the actual PMDB tables that hold information on the specific instance. You can select any instance from the list and click Details to receive First Load and Most Recent Load information about specific tables in the PMDB.

      You can also use the Warehouse Status Command selector to refresh the information that is displayed on the screen.

      Viewing PMDB tables

      You can examine additional information about the PMDB tables that are loaded for each instance, for example to understand their summary level.

      To view the PMDB tables1.    Select

      1. Select an instance in the Main area table and click Tables.

      ...

      1. In the PMDB Tables dialog box, investigate all relevant data.

      ...

      1. Click Close.

      Anchor
      ViewPMDBProcesses
      ViewPMDBProcesses
      Viewing the PMDB processes

      You can examine additional information about the processes that are involved in loading information for this instance, for example to find out which tables were affected during the last execution of a process, which process failed during its last run, or when the next process is scheduled.

      To view the run history1.    Select

      1. Select an instance in the Main area table and click Processes.

      ...

      1. In the PMDB Processes dialog box, the top table lists all processes involved in loading information for this instance. Select the process you want to focus on, such as a process that failed during its last run (indicated by the status icon).
        The last run of this process affects the bottom table populated with detailed information on the PMDB tables. If an error occurred, focus on the details in the Error Message column.

      ...

      1. Investigate all relevant data. Then click Close.

       

       

      Precise. Performance intelligence from click to storage. Learn more > >

      ...


      Scroll Ignore
      scroll-pdftrue
      scroll-officetrue
      scroll-chmtrue
      scroll-docbooktrue
      scroll-eclipsehelptrue
      scroll-epubtrue
      scroll-htmltrue
      Newtabfooter
      aliasIDERA
      urlhttp://www.idera.com
       | 
      Newtabfooter
      aliasProducts
      urlhttps://www.idera.com/productssolutions/sqlserver
             | 
      Newtabfooter
      aliasPurchase
      urlhttps://www.idera.com/buynow/onlinestore
       | 
      Newtabfooter
      aliasSupport
      urlhttps://idera.secure.force.com/precise/
       | 
      Newtabfooter
      aliasCommunity
      urlhttp://community.idera.com
             |        
      Newtabfooter
      aliasResources
      urlhttp://www.idera.com/resourcecentral
       | 
      Newtabfooter
      aliasAbout Us
      urlhttp://www.idera.com/about/aboutus
              | 
      Newtabfooter
      aliasLegal
      urlhttps://www.idera.com/legal/termsofuse

      ...