sybase: No Sybase PC client found in this environment
search cancel

sybase: No Sybase PC client found in this environment

book

Article ID: 6869

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Getting the following error when trying to setup a connection to a Sybase server using the sybase probe:

sybase: No Sybase PC client found in this environment

Environment

  • Release: DX UIM 20.4 or higher
  • sybase probe v4.32 GA
  • Sybase DB Server: OCS 16
  • Sybase 16 is currently not tested nor supported on Windows and won't work since there were significant changes in v16, e.g., lib files, etc.
  • Sybase Open Client: not installed yet, DBA to follow up when the Linux machine is ready.
  • OSes supported for the sybase probe include:
    • RHEL 7
    • RHEL8
    • SLES 12

Since the database server version is Sybase 16, the customer need to obtain a Linux machine with one of the supported OSes, and then after configuring the robot environment variables with customer/DBA-provided values, we can monitor any database server(s) on Windows OR Linux from that robot with the sybase probe installed.

Cause

  • Sybase Open client not installed on the remote robot machine

Resolution

Requirements

  • Sybase Open Client is a prerequisite for monitoring Sybase

  • Sybase Open Client is the interface we use to connect to the Sybase database server.

  • Remote (agentless) Monitoring
    We need at least one Sybase Open Client and in the same client, we can configure multiple connections and monitoring for all other Sybase DB servers.

  • If you need the Sybase Open Client installed, please ask your Sybase DBA to install the correct version and bit and configure it.

  • Local Monitoring
    Normally if you're monitoring the Sybase Database Server locally, with the sybase probe installed on the same database server (UIM Robot), it should already have the Sybase Open Client installed. The Sybase Open client and probe MUST be installed on the Sybase server.

  • What version of Sybase are you running on Windows?
    To display the current Sybase version you have installed, open a command prompt in the Cognos server where the Content manager is installed, then type in isql -v

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 the Configure Sybase Library Path section.

  • Sybase Client: 15.7, ASE 15.7, or ASE 16

  • Advanced Monitoring: Sybase Monitoring Server or Monitoring Tables must be installed and enabled.

  • Sybase: Sybase Monitoring Server must be up and running.

  • 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.

Note that Sybase 16 has not been tested and is currently not supported on Windows.

Other considerations:

Local firewall on the robot running the sybase probe needed to be disabled via sytemctl.

Trying to start the sybase probe manually yielded an expected error about not being able to find the shared libraries.

[root@usaslxapps340p sybase]# ./sybase_monitor
./sybase_monitor: error while loading shared libraries: libsybct_r64.so: cannot open shared object file: No such file or directory

The next step is to configure the controller->environment for the sybase environment and restart the probe.

Additional Information

An example of Robot environment variables for running the sybase probe is included in the KB Article below:

Unable to see Sybase probe after importing it from archive. Sybase Probe shows in red after security validation

If the database server version is Sybase 16, customers will have to obtain a Linux machine with one of the supported OSes, and then after configuring the robot environment variables with customer/DBA-provided values, we can monitor any database server(s) on Windows OR Linux from that robot with the sybase probe installed.

If the robot is already at 9.x version you can try just updating the robot to the latest robot version in the local archive.

Below is a KB Article on how to install a robot on Linux using the nimldr utility, when no robot is currently installed:
Installing a Unix or Linux robot using nimldr utility with install_LINUX_23_64.zip package

Powered by Wolken Software