SAP Sybase IQ Operations Known Issues from Previous Versions

Red Hat 6 Requires Compatibility Libraries [CR #686818]

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 [CR #627872]

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);

sp_iqstatus Returns Error on Chinese and Japanese Locale Installations [CR #622928]

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:

Run these commands:

For Chinese locales:

% cd $IQDIR16/res
% rm dblgzh_iq11_eucgb.res
% rm dblgzh_iq11_cp936.res

For Japanese locales:

% cd $IQDIR16/res
% rm dblgja_iq11_eucjis.res
% rm dblgja_iq11_sjis.res

Restart SAP Sybase IQ.

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 [CR #622007]

When a version 15.5 GA 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 Adaptive Server 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 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 SAP Sybase IQ for each session. The SAP 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 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 Adaptive Server returning chronological data types from SAP Sybase IQ.

dbisql Does Not Start on Linux Red Hat 5.3 [CR #571993]

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

SELinux Policy Requirement for Sybase IQ 15.x on Linux PowerPC x64 [CR #571627]

You must install selinux-policy-2.4.6-25.e15 or later to use the java -version command with SELinux enabled. If the policy version is incorrect, the system displays this message:

Errorloading: /libjvm.so: cannot restore segment prot
after reloc: Permission denied

This is the preferred method to meet this policy requirement, but alternatively, you can disable SELinux.

RSA Certificate Creation Fails [CR #557702]

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, Win32, and Win64 platforms. Please contact Technical Support if you need this utility.

FORWARD TO from SAP Sybase IQ to ASE Fails [CR #539484]

Execution of a FORWARD TO command from SAP 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:

To avoid this problem, do one of the following after creating a remote Adaptive Server Enterprise 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:

Change the double quotes to single quotes.
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>
} 
```
Set the QUOTED_IDENTIFIER database option to OFF using a separate FORWARD TO statement:
```
FORWARD TO <remote server name> { 
SET QUOTED_IDENTIFIER OFF }
```