...

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

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 Image Modified.

You must proceed as follows:

...

...

 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

...

2. Copy the downloaded jar file to the $MZ_HOME/persistent/3pp

...

1. folder

...

1. on

...

1. the

...

1. plaform-0

...

1. pod.

...

1.  

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

...

2. Restart

...

1. the

...

1. platform

...

1. and

...

1. EC

...

1. pods.

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

...

2. Restart

...

1. the

...

1. Desktop.

Close Pooled Connections

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

int closePooledConnections
     (string dbProfile)

Parameters

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

...

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.

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

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

Deploy the EC again in the Web Interface or with:
$ kubectl delete pod <ec-pod> -n <namespace>

By default there is no timeout value defined for the socket tied to a database connection. This means that a running query could get stuck, in case the database suddenly becomes unreachable. To specify a timeout valueThere 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 property sybase.jdbc.socketread.timeout .properties in the relevant <pico>.conf file.

For Helm deployed ECs, in values.yaml add at:
systemProperties:
  - config.properties.sybase.jdbc.socketread.timeout=600000 
 For Web Interface deployed ECs,- config.properties.sybase.jdbc.socketconnect.timeout=20000
For ECs deployed in WebDesktop InterfaceOnline, 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 theDesktop WebOnline Interface or with:
$ kubectl delete pod <ec-pod> -n <namespace