ubAdmin 1.0.0 Administrator Manual info@ubTools.com http://www.ubTools.com

Contents

Introduction

User Interface

File

Configurations

User Interface Parameters List

ubAdmin Error Codes Manual

Generic User Manual

Introduction

ubAdmin is a web based tool which configures ubTools products.

User Interface

The user interface of ubAdmin is as below:

File

Name of file to be configured.

Configurations

There are basically 4 configuration files used by ubAdmin:

• Parameters
• Authorized Clients
• Tuning Advices
• Idle Waits

Note: Servlet Container should be re-started to make changes visible by itrprof SQL Analyzer and iStatsPackAnalyzer.

Parameters

Parameter file is the file which includes the initialization parameters for the products. The following table gives the name of parameter files:

The parameter file of ubAdmin includes the following parameter:

Here is a sample value for UBTOOLS_HOME: /home/resin/resin-2.1.9/webapps/ubtools-2.1.0.1

The parameter files of itrprof SQL Analyzer and iStatsPackAnalyzer include the following parameters:

You can change any parameter except LICENSE_KEY. If you change a parameter, you have to re-start your servlet container.

Any blank lines or lines starting with '#' or '!' as a non-whitespace character are ignored in these files.

Note: No parameter should be wrapped. Each parameter should be in a single line.

Authorized Clients

Authorized Clients file is the file which includes machine names and/or IP addresses of clients which are permitted to run the products. The following table gives the name of Authorized Clients files:

When a request is sent from user machine to the products, user machine name is checked first. If servlet container doesn't return user machine name, the products use IP address of user machine.

If un-authorized users try to run the products, the following message is printed:

<error_code> : Not authorized.
Cause : Not Authorized Clients : <Name or IP address of machine>
Action : Contact support.

To make users authorized, add their machine names or IP addresses to Authorized Clients file. The products read just first number of available lines in Authorized Clients file. Number of read lines are determined in license key.

Any blank lines or lines starting with '#' or '!' as a non-whitespace character are ignored in these files.

Tuning Advices

Tuning Advices file is the file which includes the initialization parameters for itrprof SQL Analyzer. The following table gives the name of tuning advices file:

You can write your own dynamic tuning advices for itrprof SQL Analyzer. The following tables provide the variable names:

STATISTIC TOTALS FOR {NON-SYS | SYS | STATEMENT}

WAIT TOTALS FOR {NON-SYS | SYS | UN-KNOWN | STATEMENT}

You can use these variable names as standalone or computation in your tuning texts. Whenever itrprof SQL Analyzer reads your tuning text and encounters these variables, it replaces these variables with their values and implements computations if available.

Sample

A sample tuning advice text:

execute per parse = execute count / parse count (total)
                            = |exec.cnt / parse.cnt|

This ratio should be as high as possible (parse once, execute many). Low ratio is an indicator of usually inefficient application design, small SHARED_POOL_SIZE, frequent logon/logoffs.

There are 2 variables in the above example: exec.cnt and parse.cnt. And, one computation: |exec.cnt / parse.cnt|. Whenever itrpof SQL Analyzer encounters these variables, it replaces these variables with their values. And then implement a computation between '|' characters.

Sample output for the above tuning advice text:

execute per parse = execute count / parse count (total)
                            = 1.00

This ratio should be as high as possible (parse once, execute many). Low ratio is an indicator of usually inefficient application design, small SHARED_POOL_SIZE, frequent logon/logoffs.

Note: Any space character (' ') in event names should be replaced with underscore ('_') character. For example, SQL*Net break/reset to client event should be as SQL*Net_break/reset_to_client.

Idle Waits

Idle Waits file is the file which includes the names of Oracle idle wait events. It's used by iStatsPackAnalyzer for instance level analysis only. The events in this file are ignored in response time analysis. The following table gives the name of idle wait files:

Any blank lines or lines starting with '#' or '!' as a non-whitespace character are ignored in these files.

User Interface Parameters List

This part reports user interface parameters selected by user.

Sample

(P1,P2,P3) correspond to (latch address,latch number#,0 for latch activity test otherwise prosess# of possibly deceased latch holder) respectively.


Waited for PMON to check if process holding the latch died and its latch cleaning up.



itrprof SQL Analyzer with minimum waitgroup of (name,P1,P2) reports latch number.



- Check operating system CPU scheduling, which may prevent the latch holder from releasing the latch quickly.

- Check Oracle bugs.

Operation, Event name, Event value is reported When Tuning Advices is selected.

ubAdmin 1.0.0 Administrator Manual info@ubTools.com http://www.ubTools.com