Known Issues for Third-Party Products

There are known issues for third-party products that require workarounds, when available.

Third-Party Product Issues
CR# Description
561733

Installing SQL Anywhere 11 in Japanese or Chinese on Windows displays an error.

Workaround: Ignore the error message.

550309, 550305

Retrieving or inserting multibyte data using ODBC drivers displays invalid characters.

On Windows and Solaris, if you are executing a project using SQL Anywhere 10 ODBC drivers to retrieve multibyte data from, or insert data to, a UTF8-encoded Sybase IQ 15.0 database, the multibyte data is retrieved from the destination database as invalid characters.

Workaround:

On Windows:

  1. Select Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC).

  2. Select SQL Anywhere 10 DSN name from the list of User Data Sources or System Data Sources.

  3. Click Configure.

  4. Click the Advanced tab.

  5. Enter UTF8 in the Character Set field.

  6. Click OK until you exit the ODBC Data Source Administrator window.

On Solaris:

Add Charset=utf8 in the ODBC configuration file.
548368

Creating a repository connection to SQL Anywhere 10 or 11 database using ODBC may fail.

Workaround: To successfully create the repository connection, manually enter the schema name in the Schema field in the Add Repository Connection window.

545145

Transferring large amount of data consumes excessive memory.

When you transfer large amount of data rows from Adaptive Server Enterprise to text, memory use increases, and memory is not released until the project successfully executes.

Workaround: Select Use Cursors when you configure the ODBC datasource for Adaptive Server.
540683

Sybase IQ InfoPrimer may stop responding if the query must retrieve large result sets.

Reinitializing the DB Data Provider Full Load component may cause Sybase IQ InfoPrimer Development to intermittently stop responding, if you are running a query to retrieve records from a table containing large number or rows. This may also cause Sybase IQ InfoPrimer Server to run out of virtual memory.

Workaround: Select Use Cursors when you configure the ODBC datasource for Adaptive Server.
539346

Projects on Windows platforms fail with pipe error messages.

Projects may fail with a pipe does not exist or pipe permission error when Sybase IQ Info Primer Server and Sybase IQ are on different Windows platforms.

Workaround:

  1. Verify that the Sybase IQ and Sybase IQ InfoPrimer Server hosts can both access the shared directories on each other:

    1. If Sybase IQ is running on Windows 2003, which is a multiuser operating system, ensure that you are logged in to the session where the target Sybase IQ server was started.

    2. Ensure you can see the target Sybase IQ server when you try to access the Sybase IQ InfoPrimer Server host from within the Sybase IQ host.

  2. If pipe errors still exist after following workaround 1, specify a data file instead of a pipe name for the Load Stage option in the IQ Bulk Load Sybase IQ component to execute the project containing the component. See Sybase IQ InfoPrimer Users Guide > Extract Transform and Load Projects > ETL Components > Destination Components > DB Bulk Load Sybase IQ.
538539

Wrong date format written to DB2 on IBM AIX.

Using DB Data Provider Index Load and Text Data Sink components, the output date format to DB2 on IBM AIX is incorrect.

Workaround: There are two workarounds:

  1. Set the read block size to 1. Be aware that reducing the read block size decreases performance.

  2. Use the CHAR function to change the query to convert the date or time column to the char datatype. For example, if col_1 is a date column, col_2 is a time column, and col_3 is a timestamp (which does not exhibit the problem), this SQL statement corrects the problem. This statement does not force the user to change the read block size and avoids performance degradation associated with larger block processing:

    select CHAR(col_1), CHAR(col_2),
 col_3 from DATE_TIME_TBL
    Text Data Sink component output is:
    COL_1,COL_2,COL_3
1963-12-08,12.00.00,1991-03-02 08:30:00.000
1967-04-10,12.01.01,1991-04-02 08:30:00.000
    If you do not use the CHAR function, the Text Data Sink output is:
    COL_1,COL_2,COL_3
1963-12-08,12:00:00,1991-03-02 08:30:00.000
0004-10-00,01:01:00,1991-04-02 08:30:00.000
    To view the data written to the DB2 table, for example, the DATE4_TBL table, enter:
    select * from DATE4_TBL

    The content in DATE4_TBL in DB2 is:

    COL_1      COL_2    COL_3
    ---------- -------- --------------------------
    12/08/1963 12:00:00 1991-03-02-08.30.00.000000
    04/10/1967 12:01:01 1991-04-02-08.30.00.000000
531861

No databases display if you have ODBC driver 15.0.105.

If you use Adaptive Server ODBC driver version 15.0.105 or earlier, IQ InfoPrimer Server does not display any database in the Host Name field of the Properties window when you select ODBC for your database interface.

Workaround: Manually enter the ODBC datasource name for the host you want to connect to.

500832

Sybase IQ InfoPrimer cannot display the binary, varbinary, or time value from Adaptive Server Enterprise using the ODBC interface.

Workaround: Select Use Cursors when you configure the ODBC datasource for Adaptive Server.
Parent topic: Known Issues