Page History
...
| 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 |
...
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 |
 |
...
| 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 |
...
| 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 |
...
the |
...
 | 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 |
...
the |
...
| 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 |
...
the |
...
 | 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 |
Understanding Non-In Sybase session states
The table below describes the Non-In Sybase session states.
Table 2-5 Non5 Non-In Sybase session statesIcon State Description
Request Wait The
| 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 |
...
 | 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 |
 |
...
| 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 |
...
the |
About Statement identifiers
Each statement is identified by the following parameters:Text The
- 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
| Info |
|---|
If the Precise for Sybase Collector agent is down, the instance availability status reported is "Unknown. |
...
" |
| Anchor | ||||
|---|---|---|---|---|
|
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).
| Info |
|---|
...
You must have local administrator privileges on the server where the StartPoint is running. |
To launch Precise for Sybase using Precise StartPoint1. Type
- 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.
...
- Specify your authorized role name and password.
By default, both role name and password areadmin. For more information about role names, see the Precise Administration Guide.
...
- Click Login.
The StartPoint page opens. This is the Precise home page.
...
- 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 > >