Known Issues for SAP Sybase IQ Operations

Descriptions of known issues and workarounds for SAP Sybase IQ operations.

Open Client issues
CR# Description
662422
  • Remote query performance degrades with DATETIME column – SAP Sybase IQ16.0 and the default Open Client/Server included with SAP Sybase IQ16.0 support the TDS BIGDATETIME data type for remote queries.

    When an SAP Sybase IQ server executes a remote query using Open Client and fetches a DATETIME column on an IQ/SA remote server, the return data type is BIGDATETIME, instead of DATETIME. This may degrade performance.

    This performance degradation may not occur, when the remote server is an ASE server.

    To prevent the return of BIGDATETIME values, apply this workaround.

  • Workaround – Add these lines to the Open Client and Open Server configuration file $SYBASE/$SYBASE_OCS/config/ocs.cfg to prevent the return of BIGDATETIME values:
    [SAP Sybase IQ] 
    CS_CAP_RESPONSE = CS_DATA_NOBIGDATETIME

Server startup issues
CR# Description
682890
  • Red Hat 6.0 limits number of threads/processes – Starting SAP Sybase IQ may return a Resource temporarily unavailable message if the user process spawns too many processes.
  • Workaround
    1. Change the login profile of the user starting SAP Sybase IQ. For example, in the bash shell, enter the following command in the .bashrc file:
      ulimit -u 32000
    2. If the problem persists, try a stronger approach. As root, edit the file /etc/security/limits.conf and add this line:
      sybase -
663054
  • Database recovery fails if server started with -iqro 1 flag – A 15.2 database that is archived cannot be recovered if you specify the read-only flag -iqro 1 on the startup command in SAP Sybase IQ 16.0.

Related concepts
Known Issues for Installation and Configuration
Known Issues for Interactive SQL
Known Issues for Multiplex Environment
Known Issues for Sybase Control Center
Related reference
Restrictions