Versions Compared

Old Version 1

changes.mady.by.user Jenni Wallin

Saved on

compared with

New Version Current

changes.mady.by.user Felicity Borrelli

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Note

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 Image RemovedUsage Engine. Follow these steps to set up the Sybase JDBC driver on the Platform:

...

Info

Example - Restart the Platform and EC Pods

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

  1. Restart the Desktop.

Close Pooled Connections

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

Note

Note!

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

Code Block
languagetext
int closePooledConnections
     (string dbProfile)

Parameters

Returned Value

Description

dbProfile

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

Info

Example - Using APL function closePooledConnections

Code Block
languagetext
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 sybasesysbase.iq.pool.maxlimit in the relevant EC.

...

Info

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

Code Block
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

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.

...