SAP Sybase IQ Operations Known Issues from Previous Versions

• Red Hat 6 Requires Compatibility Libraries – Installation of SAP Sybase IQ 15.3 on Red Hat 6.0 fails with an InvocationTargetException error unless you install the required 32-bit compatibility libraries:
  • libXext-devel.i686
  • libXtst-devel.i686

• PHP Bound Parameters on Big Endian Platforms – In SAP Sybase IQ 15.2, PHP: Hypertext Preprocessor (PHP) drivers on big endian platforms require bound parameters to be initialized before the call to sasql_stmt_bind_param for INT and BIGINT data types.

  This example shows the values properly initialized before the call to sasql_stmt_bind_param:

  $stmt = sasql_prepare($conn, "insert into
  testdefault(c1, c2, c3, c5) values(?,?,?,?)");
  #Binding parameters with statement prepared
  $c1=22;  $c2=33;  $c3="col3data";  $c5="col5data";
  sasql_stmt_bind_param
  ($stmt,"iiss", $c1, $c2, $c3, $c5);
  #executing statement
  sasql_stmt_execute($stmt);

• dbisql Reports Java Stack Trace Error – On rare occasions, the Interactive SQL utility (dbisql) may encounter a Java stack trace error when you highlight text:

  Index Array Out of Bounds

  This is due to a problem in the Java Runtime Environment. See Bug ID 6921603 in the Java Bug Database on the Oracle Sun Developer Network (SDN).

• sp_iqstatus Returns Error on Chinese and Japanese Locale Installations – On SAP Sybase IQ servers that are set up for Chinese and Japanese locales, running sp_iqstatus returns an error similar to:

  Could not execute statement.
  Syntax error near '2010' on line 1
  SQLCODE=-131, ODBC 3 State="42000"
  Line 1, column 1

• Workaround: –
  1. Stop the server.
  2. For Chinese locales, remove dblgzh_iq11.dll from %IQDIR16%\bin64.

     For Japanese locales, remove dblgja_iq11.dll from %IQDIR16%\bin64.

  3. Restart the server.

After this procedure, certain strings in the .iqmsg files and the output of sp_iqmpxinfo, sp_iqstatistics, and sp_iqstatus are in English, instead of Chinese or Japanese.

• ASE Connections to SAP Sybase IQ with BIGDATETIME – When a version 15.5 GA SAP Adaptive Server Enterprise server uses Component Integration Services (CIS) to connect to an SAP Sybase IQ server version that has BIGDATETIME and BIGTIME capability, any chronological data type sent to the SAP Adaptive Server Enterprise server using CIS results in the error:

  Msg 7225, Level 16, State 4:
  Line 1:
  Unknown datatype token 188 'BIGDATETIME NULL'
  encountered.
  Exited passthru mode from server 'QA_IQ16_ASECIS'.

  SAP Sybase IQ sends the data as BIGDATETIME and relies on SAP Adaptive Server Enterprise to convert appropriately. The BIGDATETIME data type was implemented in CIS in SAP Adaptive Server Enterprise version 15.5 ESD #1, so this error occurs with SAP Adaptive Server Enterprise 15.5 before any ESDs have been applied.

• Workaround – SET TEMPORARY OPTION RETURN_DATE_TIME_AS_STRING='ON' in SAP Sybase IQ for each session. The SAP Sybase IQ server sends all chronological data as strings and SAP Adaptive Server Enterprise completes the conversion. This workaround is for SAP Adaptive Server Enterprise 15.5 GA connecting to SAP Sybase IQ in passthrough mode.

  You can also use this workaround in the definition of a remote stored procedure, but it is not a solution for proxy tables created on SAP Adaptive Server Enterprise returning chronological data types from SAP Sybase IQ.

• dbisql Does Not Start on Linux Red Hat 5.3 – The Interactive SQL utility dbisql fails to start on Linux Red Hat 5.3, and issues a message similar to:

  Error! could not load the Java Virtual machine DLL:
  /root/users/user1/050509/shared/JRE-
  6_0_7_32BIT/lib/i386/client/libjvm.so

• Workaround – Run:

  % cd $IQDIR16/bin32
  % dbisql -batch  # creates below
  % dbisql.sh

• FORWARD TO from SAP Sybase IQ to ASE Fails – Execution of a FORWARD TO command from SAP Sybase IQ to Adaptive Server using the ASEODBC driver fails with ASA Error -660 “The identifier that starts with ‘<identifier>’ is too long. Maximum length is 28.”

• Workaround – To avoid this problem, do one of the following after creating a remote Adaptive Server server using either server class aseodbc or server class asejdbc and before executing a SQL statement that contains a string with double quotes against the remote server using the FORWARD TO statement:
  1. Change the double quotes to single quotes.
  2. Include the database option SET QUOTED_IDENTIFIER OFF before the SQL statement to be executed:

     FORWARD TO <remote server name> {
     SET QUOTED_IDENTIFIER OFF
     <SQL statement>
     }

  3. Set the QUOTED_IDENTIFIER database option to OFF using a separate FORWARD TO statement:

     FORWARD TO <remote server name> { 
     SET QUOTED_IDENTIFIER OFF }

• Creating Very Large Databases – Attempting to create extremely large SAP Sybase IQ databases on certain Windows configurations may fail with an exception occurring in the module hos_bion.cxx at or near line 182.

  If you require a database that exceeds 100GB, try creating a database of that size to see if your system configuration exhibits the problem. If you create a smaller database and later try to add dbspaces, correcting the problem at that time may be more difficult and time consuming.

  This problem is intermittent but tends to occur if you have approximately 180GB of open files. Changing the setting of the OS_File_Cache_Buffering database option could trigger the problem. In some cases, you might see an INSUFFICIENT_RESOURCES Windows error message.

  The best way to avoid this problem is to create on a raw device any databases that may become larger than 180GB.

  If you create a very large database on a file system, and either the CREATE DATABASE statement fails as described above, or you see the INSUFFICIENT_RESOURCES message, apply Microsoft corrections. The problem is caused by a bug in the Windows kernel. More information is available on the Microsoft support Web site:

  • Microsoft Knowledge Base Article - 192409
  • Microsoft Knowledge Base Article - 236964
  • Microsoft Knowledge Base Article - 171458