Page History
...
- Switching to a different tab
- Selecting a time frame
- Selecting an entity
- Filtering data
- Associating entities with data that meet specific criteria
- Saving a statement
- Focusing on information in overtime graphs
- Sending an email message
- Adding, viewing, and deleting Favorites
- Determining which table columns to display
- Copying data to the clipboard
- Exporting to the Precise Custom Portal
| Anchor | ||||
|---|---|---|---|---|
|
...
Tables are used to display information about the set of related entities in the Main and Association areas. It is possible to determine which columns to display in the Association area tables.
To determine which columns to display in the Association area1. Click
- Click the Table icon on the upper right-hand side of a table and select Column Chooser.
...
- In the Table columns dialog box, click the arrows to move the names of the columns that you want to display to the Visible box and the ones that you do not want to display to the Invisible box.
...
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
At times you may want to save data displayed in the table area in a Microsoft Excel spreadsheet for further analysis or save an image of a graph to the clipboard.
To copy data displayed in the Association area to the clipboard
1. Click , click the Table icon on the upper right-hand side of a table and select Copy to clipboard.
The table can be pasted into Microsoft Excel or as an HTML file.
To copy a graph to the clipboard
1. Right, right-click a graph and choose Copy to clipboard.
You can now paste the image into any application that works with the clipboard.
Exporting to the Precise Custom Portal
The Export to the Precise Custom Portal Portlet feature enables you to export the view of the chosen table or graph and generate a portlet with that view in the Precise Custom Portal, so that it will provide you with another way of monitoring your application.
Prerequisites
To be able to use this feature, you need to have the following rights in Precise:
• View , view permissions to all Tiers in the application
. If you do not have sufficient rights, you will get an error message when trying to execute this feature.
| Anchor | ||||
|---|---|---|---|---|
|
You can either export a table view or a graph view.
| Info |
|---|
...
The name field has the following restrictions: maximum 100 characters. |
To export a table view1. Click
- Click the Column Chooser icon.
...
- Select Export to the Precise Custom Portal Portlet.
...
- Insert a name in the name field that clearly describes the table view.
...
- Click OK.
To export a graph view1. Right
- Right-click the graph.
...
- Select Export to the Precise Custom Portal Portlet.
...
- Insert a name in the name field that clearly describes the graph view.
...
- Click OK.
| Anchor | ||||
|---|---|---|---|---|
|
The Roles management feature in Precise for Sybase lets you assign roles to users and control whether they will be able to do the following operations:• Gen
- Gen_Estimated_Plan (explain)
...
- . Lets you generate a new execution plan.
...
- Launch_Sybase_
...
- Tool. Lets you launch external Sybase tools.
It is possible to grant permissions to all roles or to revoke permission from individual roles. Permission is a combination of permission type (such as: INSTALL, ADMIN, MONITOR) and operation (such as: VIEW, UPDATE).
Certain types of permission enforce permission dependencies. For example, if you grant a TUNE.RECOMMEND permission it will automatically grant TUNE.EXPLAIN. In the same manner, if you revoke TUNE.EXPLAIN then the TUNE.RECOMMEND permission is also revoked. You can configure permissions and roles in AdminPoint.
For more information on configuring permissions and roles, see the Precise Administration Guide.
| Anchor | ||||
|---|---|---|---|---|
|
Precise for Sybase collects and displays performance data that enables quick and accurate performance monitoring and analysis. To understand the information displayed in the various graphs, tables and views, it is important to understand how information is collected.
About duration values
Precise for Sybase displays duration values for several entities.
The table below describes the duration value for each type of entity:.
Table 2-3 Duration 3 Duration values for entities
| Entity |
|---|
...
| Description |
|---|
| Current |
...
| Session | The time that has elapsed since the session started (login time). This is not the time the session was active executing statements. For example, if a session was connected to Sybase for one hour without executing any statement, the duration will still be one hour. |
| Programs (Logins, Machines, DB Users, Databases, Time Units, and so on.) |
...
The elapsed time of the sessions executing the program. The time is not measured from the login time (as it is in the Current session entity), but from the moment the Collector agent started. The average duration counter displays the average time each program has been running. | |
| Statement (batch) |
...
The time that elapsed while the statement was executed. This is very similar to the duration of programs (see above); but since the statement is almost always active, this duration also indicates the time the statement was active. The average duration counter displays the average execution time of the statement. |
About session states
Sybase provides reporting on many different types of events. Precise for Sybase groups events according to logical relationships to enable you to easily pinpoint heavy resource consumers.
For example, when the Collector agent samples the Sybase, it assigns a state for each connection. An application may wait for many events in Sybase. To simplify analysis, and help you to easily identify the source of resource consumption, Precise for Sybase groups various wait types into wait groups or states and defines the status of sessions currently connected to Sybase by their states. The state is divided into two types of states: In Sybase and Non-In Sybase. The session states are described in the following table:.
Understanding In Sybase session states
The In Sybase session states signify that the session is performing activities in Sybase. The table below describes the In Sybase session states.
Table 2-4 In 4 In Sybase session states
| Icon |
|---|
...
| In Sybase State | Description | |
|---|---|---|
 | Using CPU | The session is currently executing and is not waiting for any other event. For versions lower than version 12.5.0.3, the Using CPU state is usually identified by sysprocesses status = Runnable/Running. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value in Wait Class 1 (waiting to be scheduled). Usually this state is an ideal state, but verify that the amount of CPU usage is reasonable compared to the transaction being performed. In addition monitor this state over time and verify that a growth in the CPU usage is a result of a growth in load and not a result of any change that caused the performance to degrade. |
| I/O Wait | ||
 | Lock Wait | |
| Log Full Wait | ||
 | Log Wait | |
| Buffer Wait | ||
 | Latch Wait | |
| Remote Wait | ||
 | Network I/O Wait |
Table 2-4 In Sybase session states
Icon In Sybase State Description
I/O Wait This state indicates the session is waiting for an I/O operation to terminate. For versions lower than version 12.5.0.3, this state is usually identified by sysprocesses status = sleeping, unless the cmd field = COMMIT/ROLLBACK/LOG SUSPEND. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value in Wait Classes 2 or 3 (waiting for a disk read / write to complete).
Lock Wait The session is waiting for a lock to be released. The lock is held by another session.
For versions lower than version 12.5.0.3, this state is identified by sysprocesses status = lock sleep. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value in Wait Class 5 (waiting to take a lock).
Log Full Wait The session is waiting for an operation of the log file to terminate. This state is generally encountered during a transaction log full.
For versions lower than version 12.5.0.3, this state is identified by sysprocesses cmd = LOG SUSPEND. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value of 259.
Log Wait The session is waiting for an operation of the log file to terminate. This state is generally encountered during a commit or rollback operation.
For versions lower than version 12.5.0.3, this state is identified by sysprocesses status = sleeping, and the cmd field is COMMIT or ROLLBACK. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value of 283.
Buffer Wait The session is waiting to access a user log cache. For versions lower than version 12.5.0.3, this state is identified by sysprocesses status = PLC sleep. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value in Wait Class 6 (waiting for memory or a buffer).
Latch Wait The session is waiting for an internal lock to be released.
Latches are short term light weight synchronization objects. Latches are not held for the duration of a transaction. Latches are used for datapage and datarow locking, including OAM and allocation pages, but not for allpages locking. They mostly occur in SMP applications. For versions lower than version 12.5.0.3, this state is identified by sysprocesses status = latch sleep. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value in Wait Class 9 (waiting for internal system event).
Remote Wait The session is waiting for a remote query to terminate. For all versions, this state is identified by sysprocesses status =remote I/O.
Network I/O Wait The session is completing a network I/O operation. Network I/O occurs if results from a large result set are transferred to the client using shared memory netlibs or TCP/IP.
For versions lower than version 12.5.0.3, this status is identified by a status of send sleep or recv sleep. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value in Wait Classes 7 or 8 (waiting for network input/output).
Understanding Non-In Sybase session states
The table below describes the Non-In Sybase session states.
Table 2-5 Non-In Sybase session states
Icon State Description
Request Wait The session is waiting for the client to issue a request.
For versions lower than version 12.5.0.3, this state is identified by sysprocesses cmd = AWAITING COMMAND. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing a value of 250.
Other Wait Sessions waiting in states not described here are assigned the Other wait state.
Waitfor command The session is executing the WAITFOR DELAY command.
For versions lower than version 12.5.0.3, this state is identified by sysprocesses status = alarm sleep. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing values of 260-263.
Parallel Sync Wait The session is waiting for a synchronization message from another process in the family. For versions lower than version 12.5.0.3, this state is identified by sysprocesses status = sync sleep. For version 12.5.0.3 and higher, this state is identified by the monProcess WaitEventID field containing values of 152, 307 or 308.
About Statement identifiers
Each statement is identified by the following parameters:
Text The actual statement text.
Database Each statement is associated with a single database.
User Each statement is associated with a single user (also called the parsing user).
For example, the statement "select * from sysobjects" executed in the master and pubs3 databases is represented by two different statements in the product. The ability to roll-up the performance of those statements to one is also important. This is supplied using the collapsed statement entity.
How Precise for Sybase monitors availability
The Precise for Sybase Collector agent monitors Sybase every second and collects data regarding resource consumption. If the instance status (Up/Down) was changed, a message code is sent by the Collector agent and causes the current availability of the instance saved in the PMDB to be changed. In addition, the availability of the instance is saved, over time, in the PMDB. During a planned downtime period the instance availability is showed as it was available during this period.
NOTE If the Precise for Sybase Collector agent is down, the instance availability status reported is "Unknown.”
...
Precise is a Web-based application. You can access the Precise user interface using the Internet Explorer browser, version 6.0, or later.
The syntax of the Precise URL address is: http://<server>:<port>,where <server> refers to the Precise FocalPoint and <port> refers to the port number used by the GUI Web server. By default, the port number is 20790. For example: http://beanotown:20700.
This URL provides secure access to the StartPoint using authorized roles. From here, you can launch all Precise products. It gives you a quick overview of the status of your applications and access to the AdminPoint, where you can perform various management tasks (For more information, see the Precise Administration Guide).
NOTE You must have local administrator privileges on the server where the StartPoint is running.
To launch Precise for Sybase using Precise StartPoint
1. Type the address of the StartPoint user interface into the Address bar of your browser and click Enter.
The Precise login page opens. The login page provides secure access to Precise and to your specific product.
2. Specify your authorized role name and password.
By default, both role name and password are admin. For more information about role names, see the Precise Administration Guide.
3. Click Login.
The StartPoint page opens. This is the Precise home page.
4. On the Product Selection bar, from the drop-down list, select the product you want to launch.
Precise. Performance intelligence from click to storage. Learn more > >