Sybase IQ(3.2)

Owned by Jenni Wallin
Last updated: Apr 02, 2024
2 min read

This section contains information that is specific to the database type Sybase IQ.

Note!

The Sybase IQ database type requires jConnect v16.0 and later. 

Supported Functions

The Sybase IQ database can be used with:

  • Audit Profile

  • Database Collection/Forwarding Agents

  • Event Notifications

Preparations

The Sybase JDBC driver that is included in the SDK has to be downloaded to the Platform in order to connect to a Sybase IQ database from . Follow these steps to set up the Sybase JDBC driver on the Platform:

  1. Set up a persistent file system.

  2. Go to the SAP Software Solutions web page for information about the SDK and included drivers: https://www.sap.com/index.html

  3. Copy the downloaded jar file to the $MZ_HOME/persistent/3pp folder on the plaform-0 pod. 

    $ kubectl cp jconn4.jar platform-0:/opt/mz/persistent/3pp -n <namespace>

  4. Restart the platform and EC pods.

    $ kubectl delete pod platform-0 -n <namespace>

  5. Restart the Desktop.

Close Pooled Connections

  The APL function closePooledConnections enables you to close a pooled connection with the Sybase IQ server. This feature helps you eliminate invalid connections.

Note!

This function only closes inactive connections, regardless of how long the connections have been idle.  

int closePooledConnections (string dbProfile)

Parameters

Returned Value

Description

dbProfile

The name of the database where the table is stored, preceded by the folder name.

Example - Using APL function closePooledConnections

Performance Tuning

The default maximum number of connections on an Execution Context is five. You can tune this number by setting the Execution Context property sybase.iq.pool.maxlimit in the relevant EC.

There are two properties available for handling timeout of socket connections and socket threads:

sybase.jdbc.socketread.timeout with default value 180000 (3 minutes in milliseconds)

sybase.jdbc.socketconnect.timeout  with default value 30000 (30 seconds in milliseconds)

To specify other timeout values, in milliseconds, set the Execution Context properties in the relevant <pico>.conf file.