Descriptions of known issues and workarounds for Sybase IQ operations from previous versions.
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).
Could not execute statement. Syntax error near '2010' on line 1 SQLCODE=-131, ODBC 3 State="42000" Line 1, column 1
Stop the server.
For Chinese locales, remove dblgzh_iq11.dll from %IQDIR15%\bin32 (for 32-bit installations) or %IQDIR15%\bin64 (for 64-bit installations).
For Japanese locales, remove dblgja_iq11.dll from %IQDIR15%\bin32 (for 32-bit installations) or %IQDIR15%\bin64 (for 64-bit installations).
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.
Msg 7225, Level 16, State 4: Line 1: Unknown datatype token 188 'BIGDATETIME NULL' encountered. Exited passthru mode from server 'QA_IQ15_ASECIS'.
Sybase IQ sends the data as BIGDATETIME and relies on Adaptive Server to convert appropriately. The BIGDATETIME data type was implemented in CIS in Adaptive Server Enterprise version 15.5 ESD #1, so this error occurs with Adaptive Server Enterprise 15.5 before any ESDs have been applied.
Workaround:
SET TEMPORARY OPTION RETURN_DATE_TIME_AS_STRING='ON' in Sybase IQ for each session. The Sybase IQ server sends all chronological data as strings and Adaptive Server completes the conversion. This workaround is for Adaptive Server Enterprise 15.5 GA connecting to 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 Adaptive Server returning chronological data types from Sybase IQ.
The JAWS screen reader may not read all interface items in the Sybase Central plug-in for Sybase IQ 12.7 or 15.x.
RSA certificate creation fails with the error createcert command not found because the createcert utility is missing. The utility is currently available only on the AIX64, LinuxAMD64, Sun64, and Win32 platforms. Please contact Sybase Technical Support, if you need this utility.
Execution of a FORWARD TO command from Sybase IQ to Adaptive Server Enterprise using the ASEODBC driver fails with ASA Error -660 “The identifier that starts with ‘<identifier>’ is too long. Maximum length is 28.”
Workaround:
Change the double quotes to single quotes.
FORWARD TO <remote server name> { SET QUOTED_IDENTIFIER OFF <SQL statement> }
FORWARD TO <remote server name> { SET QUOTED_IDENTIFIER OFF }
Attempting to create extremely large 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.