sybase (Sybase Monitoring) Release Notes
The Sybase Monitoring (sybase) probe allows you to monitor real-time events occurring in the Sybase server. The probe provides parameters to measure the real-time database operations. The probe also allows you to create custom checkpoints as required to define monitoring profiles. You can set up multiple monitoring profiles using these checkpoints to extract vital information about the database servers at specified intervals. You can also configure these profiles to generate alarms and QoS when the specified threshold of an event is breached and identify performance issues in servers. You can then diagnose and resolve these issues, and take preventive measures to ensure an optimal server run time.
uimpga-ga
sybase_RN
The Sybase Monitoring (sybase) probe allows you to monitor real-time events occurring in the Sybase server. The probe provides parameters to measure the real-time database operations. The probe also allows you to create custom checkpoints as required to define monitoring profiles. You can set up multiple monitoring profiles using these checkpoints to extract vital information about the database servers at specified intervals. You can also configure these profiles to generate alarms and QoS when the specified threshold of an event is breached and identify performance issues in servers. You can then diagnose and resolve these issues, and take preventive measures to ensure an optimal server run time.
The probe can be deployed and configured on the same system as the Sybase server (local) or as a remote probe.
Contents
Revision History
This section describes the history of the revisions for this probe.
Support case(s) may not be viewable to all customers.
Version | Description | State | Date |
4.32 | What's New:
| GA | June 2020 |
4.31 | Fixed Defects:
| GA | October 2016 |
4.30 | What's New:
Fixed Defects:
| GA | October 2015 |
4.21 | Fixed Defects:
| GA | January 2015 |
4.20 | What's New:
Fixed Defects:
| GA | September 2014 |
4.14 | Fixed Defects:
| January 2014 | |
4.11 |
| November 2012 | |
4.10 |
| September 2012 | |
3.53 |
| May 2011 | |
3.50 |
| February 2011 | |
3.42 |
| September 2010 | |
3.41 |
| September 2012 | |
3.40 |
| August 2010 | |
3.31 |
| August 2010 | |
3.30 |
| March 2010 | |
3.26 |
| November 2008 | |
3.24 |
| August 2008 | |
3.23 |
| July 2008 | |
3.22 |
| June 2008 | |
3.20 |
| April 2008 | |
3.12 |
| February 2008 | |
3.11 |
| December 2007 | |
3.10 |
| September 2007 | |
2.06 |
| August 2006 | |
2.05 |
| November 2005 |
Probe Specific Hardware Requirements
The sybase probe is installed on systems with the following minimum resources:
- Memory: 2-4 GB RAM. The OOB configuration of probe requires 256MB of RAM.
- CPU: 3 GHz dual-core processor, 32-bit or 64-bit
Probe Specific Software Requirements
The sybase probe requires the following software environment:
- CA Unified Infrastructure Management 8.0 or later
- Robot 7.62 or later (recommended)
- Java JRE version 6 or later (required for Admin Console)
The probe must be configured on Windows, Linux, AIX, or Solaris platforms.
Installation Considerations
The sybase probe has the following prerequisites for installation:
- Libraries and Variables:The probe requires the following library configurations:
- libstdc++ 5 library must be present on the robot platform.
- Sybase libraries and environment variables must be set in the system path. For more information, see theConfigure Sybase Library Pathsection.
- Sybase Client:15.x, ASE 15.x, or ASE 16
- Sybase Server:15.x, ASE 15.x, or ASE 16.
- Advanced Monitoring:Sybase Monitoring Server or Monitoring Tables must be installed and enabled.
- Sybase:
- Adaptive Server Enterprise 15.7:The property net password encrypt must be updated to a value 2 to enable the encrypted communication between the probe and the Sybase database server.
Configure Sybase Library Path
You must set the LD_LIBRARY_PATH and the environment variables to specify the location of the shared libraries.
Ensure that the Sybase server is running and is accessible from the Linux system.
Follow these steps:
- Log in to the Linux system and verify the environment variable path using EXPORT command.
- Copy the following values of the environment variables to thecontrollerprobe.
- LD_LIBRARY_PATH:/opt/sybase/ASE-15_0/lib:/opt/sybase/DataAccess64/ODBC/lib:/opt/sybase/DataAccess/ODBC/lib:/opt/sybase/OCS-15_0/lib:/opt/sybase/OCS-15_0/lib3p64:/opt/sybase/OCS-15_0/lib3p:/opt/sybase/ASE-15_0/lib:/opt/sybase/DataAccess64/ODBC/lib:/opt/sybase/DataAccess/ODBC/lib:/opt/sybase/OCS-15_0/lib:/opt/sybase/OCS-15_0/lib3p64:/opt/sybase/OCS-15_0/lib3p
- SYBASE:/opt/Sybase
- SYBASE_ASE:ASE-15_0
- SYBASE_JRE_RTDS:/opt/sybase/shared/SAPJRE-7_1_011_64BIT
- SYBASE_OCS:OCS-15_0
- SYBASE_WS:WS-15_0
- SYBROOT:/opt/sybase
The probe operates in basic and advanced modes. In the basic mode, the probe collects information from the sybase table accessible to the user. In the advanced mode, the probe uses monitoring tables from the Sybase Adaptive Server Enterprise (ASE) to collect monitoring information of the database from the ASE.
Basic Mode
Access to following tables is needed to run the probe in basic mode:
- sysdatabases
- spt_values
- sysusgaes
- sysprocesses
- syscurconfigs
- sysconfigures
Advanced Mode
Consider the following points to connect to the database in advanced mode:
- User credentials to access Sybase server requires 'mon_role' authorization to connect to the database using Monitoring Tables.
- Sybase System Administrator account such as 'sa' is used to run the probe using Monitoring Server API.
For configuring the probe on Sybase server, Sybase Monitoring Server or Monitoring Tables must be installed and activated.
ASE Configuration
You must configure the following values in the ASE for monitoring the data collection of tables:
buf_cachehit_ratio
- enable monitoring = 1
lock_requests, lock_requests_db, lock_requests_granted_db, lock_requests_waited_db
- enable monitoring = 1
- per object statistics = 1
- object lockwait timing = 1
total_disk_io
- enable monitoring = 1
stp_cachehit_ratio
- enable monitoring = 1
locked_users (advanced, with sql text)
- enable monitoring = 1
- max SQL text monitored = 1024 or more
- SQL batch capture = 1
- sql text pipe active = 1
- sql text pipe max messages = 256 or more (depends on interval length and server activity)
Migration Considerations
The probe has the following migration considerations:
- Before upgrading the probe, delete the utility folder from the installation directory of the probe. The utility folder contains reference links from the previous version.
- If you migrate the probe from previous releases, only the old configuration file (sysbase_monitor.cfg) is migrated into a release 3 configuration file (sysbase_monitor_v3.cfg). Every instance from V2 is converted into one connection and one monitoring profile in V3. Every profile starts one thread for SQL queries and one process as Monitor Server data collector.
- From version 4.2 onward, the probe does not support advanced monitoring using Monitoring Server. This is because the Monitoring Server is not a part of the Adaptive Server Enterprise version 15.7 and later.
Troubleshooting
Profile test connection/check_dbalive, is not connected to <server_name>, err: The parameter %1! cannot be NULL.
Symptom:
When trying to test a connection to a Sybase instance using the sybase probe encounter the following error:
Profile test connection/check_dbalive, is not connected to <instance_name>, err: The parameter %1! cannot be NULL
Solution:
Ensure that the name defined in the sql.ini file matches with the server name. The server name is case sensitive. Use the same name when creating the connection to a Sybase instance using the sybase probe.
Limitations
- Custom checkpoint creation is not possible via Admin Console GUI.
Known Issues and Workarounds
The sybase probe has the following known issues:
- (For version 4.30 and earlier)The probe does not automatically clear alarms for thelocked_usercheckpoint. Before you upgrade the probe to version 4.31 or later, for the first time, you must manually clear pending alarms for this checkpoint. However, all future alarms are automatically cleared, as applicable.
- In user defined templates with more than one threshold, the probe does not display the threshold operator in the list view.
- The probe must be configured using either the Infrastructure Manager (IM) GUI or the Admin Console (AC) GUI.
- The probe configuration for both the IM GUI and AC GUI is separate. For example, any profile that is created in the IM GUI is not available on the AC GUI and must be recreated.
- With Sybase OCS 15.0, the Sybase Monitoring Server API can end in a CPU loop if the probe agent does not close connection to the Sybase server properly. This issue is solved by applying Sybase maintenance (15.0.2 or higher).