Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

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. 

Example - Copy the Sybase JDBC File into the Directory

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

  1. Restart the platform and EC pods.

Example - Restart the Platform and EC Pods

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

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

persistent int profileUsageCnt; 
      .... 
      if ( profileUsageCnt > 100 ) { 
         closePooledConnections("sybase_iq.mydb"); 
         profileUsageCnt = 0; 
      }

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.

Example - Setting the maximum number of connections for Sybase IQ

For Helm deployed ECs, in values.yaml add at:
systemProperties:
  - config.properties.sybase.iq.pool.maxlimit=20

For ECs deployed in Desktop Online, add:
EC Deployment, Execution Context, Configure EC: System Properties: Add -> 
config.properties.sybase.iq.pool.maxlimit=20 

Deploy the EC again either in Desktop Online or with:
$ kubectl delete pod <ec-pod> -n <namespace>

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.

Example - Setting the timeout for a socket tied to a Sybase IQ connection

For Helm deployed ECs, in values.yaml add at:
systemProperties:
  - config.properties.sybase.jdbc.socketread.timeout=600000 
  - config.properties.sybase.jdbc.socketconnect.timeout=20000

For ECs deployed in Desktop Online, add in:
EC Deployment, Execution Context, Configure EC: System Properties: Add ->
config.properties.sybase.jdbc.socketread.timeout=600000 
config.properties.sybase.jdbc.socketconnect.timeout=20000

Deploy the EC again either in Desktop Online or with:
$ kubectl delete pod <ec-pod> -n <namespace

Note!

When using the timeout property you must ensure that you set a limit that exceeds your longest running query, otherwise you might terminate a connection while it is executing a query.

  • No labels