Page History
...
Table 5-2 Processes that cannot be configured
Technology Process
...
| Technology | Process |
|---|---|
| DB2 | Calculate Objects Usage |
| Oracle |
...
| Collect Instance Definitions |
| Oracle |
...
| Collect Instance Statistics |
| Oracle |
...
| Collect Schema Changes |
| Oracle |
...
| Storage | Load Data |
...
| Oracle | Perform SmarTune Analysis on DB Behavior |
| SQL |
...
| Server | Collect Instance Statistics |
| SQL |
...
| Server | Collect DB File Statistics |
| SQL |
...
| Server | Collect Job Statistics |
| SQL Server (Storage) |
...
| Load Data | |
| Sybase |
...
| Collect Instance Statistics |
...
| Sybase | Purge Internal Data |
| Sybase Replication |
...
SAP Organizational Mapping
...
| Server | Load Data |
| SAP | Organizational Mapping |
| PMDB | Data Maintenance (Daily) |
| . |
...
| NET | Load Data |
...
| Summarize Current Data |
To To configure process parameters1. In
- In the Main area table, select the process whose parameters you want to configure.
...
- Click Parameters.
...
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.
...
In the Parameters dialog box, click OK.
Info
...
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: “Treat pages with different titles as different 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.
...
Oracle Applications Load Data
Other Load Data
To schedule a process
1. Select a process in the Main area table and click Scheduling.
...
o 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.
3. 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.
...
Purge Data Deletes old and unnecessary data from the statistics tables in the Warehouse workstation.
Note: 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.
...
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.
...
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.
Note: 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” on page 77.
Modifying the Precise Load Data slice size
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.
...
NOTE 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.
...
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
- Select an instance in the Main area table and click Tables.
...
- In the PMDB Tables dialog box, investigate all relevant data.
...
- Click Close.
| Anchor | ||||
|---|---|---|---|---|
|
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
- Select an instance in the Main area table and click Processes.
...
- 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.
...
- Investigate all relevant data. Then click Close.
...
...
Precise. Performance intelligence from click to storage. Learn more > >
...