Known Issues for IQ InfoPrimer Server

SySAM reports incorrect number of licenses obtained when insufficient licenses are available.

Insufficient SY_INFOPRIMER_SERVER licenses. Sybase IQ InfoPrimer Server 
requires 4 SY_INFOPRIMER_SERVER licenses but only 4 could be obtained. Check whether 
additional licenses are available at the Sybase Product Download Center.

sysam status -a

Grid engine fails on UNIX or Linux machine when LANG variable set to ja.

ERROR : 1100: The detected locale character set 'US-ASCII' is incorrect 
or invalid. Configure the character set in the configuration file.

Charset=eucJP

Incremental loading fails if bulk copy and dynamic SQL options are enabled in Replication Server.

Workaround: Set the bulk copy and dynamic SQL options to "off" in Replication Server.

Port structure displays incorrect column length.

The column length that appears for the port structure in the Size column of the Port Structure Viewer does not match the value defined in the SQL statement used to generate the table.

Workaround: None.

Application stops responding when named pipes are used on UNIX.

If Sybase IQ InfoPrimer Server is running on UNIX and you use named pipes to load data to IQ, you may encounter an error that causes the application to stop responding.

Workaround: Terminate the process, restart the application, and load data from a file instead of through a named pipe. Sybase IQ InfoPrimer Server does not support the use of named pipes on UNIX.

SQL Anywhere 11 installation fails on Solaris 10.

Workaround: In the PATH variable, include /bin before /usr/ucb/bin.

No table name verification.

If you do not provide a new table name in the “schema.name” format and a table with that name already exists, errors occur when you attempt to create the table.

Workaround: Specify the new table name in the “schema.name” format. For example: dbo.table1.

Scheduled task not repeated after restart.

If you restart IQ InfoPrimer Development or IQ InfoPrimer Server, the Repeat Task option specified for a schedule is ignored; the task is not repeated at the specified time.

Workaround: Create individual scheduled tasks for each repeat schedule.

Replication is not dropped successfully in Replication Server.

When you manually drop replication, the replication state changes to “Dropped.” However, sometimes replication may not actually be dropped in Replication Server.

Workaround: Manually drop replication again:

Alert e-mail notification does not display the total number of rows processed.

If you have included the [ProcessRows] Event Property in your alert e-mail definition, the total number of rows that were processed is evaluated, instead of the total number of rows that were loaded into the destination tables. See “Configuring alerts for runtime events,” in Sybase IQ InfoPrimer 15.3 Users Guide > About Sybase IQ InfoPrimer > Alerts.

Workaround: None.

SQL statements with IQ temporary options are not executed when ODBC is used to connect to IQ.

Workaround: Use the Sybase interface to connect to IQ.

IQ InfoPrimer Server fails to restart if svc.conf file is not saved in UTF-8 format.

Sybase IQ InfoPrimer Server fails to start if svc.conf file in the etc subdirectory is updated and saved in a non UTF-8 encoding format.

Workaround: Use a text editor to open the svc.conf file and change the file format to UTF-8 encoding.

Tables not returned with Adaptive Server Enterprise source and ODBC interface.

If you are using Adaptive Server Enterprise as the source database and ODBC as the interface for connectivity, not all the tables created in the database are always returned. This issue is related to the user role. If you create tables without the sa_role, but later grant it, tables that were created before the sa_role was granted do not appear when you request for the list of tables.

Creating a repository connection to SQL Anywhere 11 database using OCS may fail.

If you are using the latest EBF of the SQL Anywhere 11 database and you try to create a repository connection to this database using OCS connectivity, you may encounter errors.

Workaround: Install the version of SQL Anywhere 11 that is packaged with Sybase IQ InfoPrimer or access SQL Anywhere 11 with ODBC connectivity.

On Windows 2008, the message that appears after a project prints successfully as XML displays an incorrect file path.

Workaround: Go to the reports folder in the installation directory and manually open the file to view.

Sybase IQ InfoPrimer Server fails to start on Sun Solaris.

Sybase IQ InfoPrimer Server fails to start on Sun Solaris if you select Install for all users during installation, and you have not set the HOME directory.

Workaround: Set the HOME directory variable to your correct home directory or a directory on which you have write permission.

SySAM license expiration warning only in English.

On all UNIX platforms, except HP-UX, the Sybase Software Asset Management System (SySAM) license expiration warning message appears only in English, regardless of the language selected during installation.

Workaround: None.

Project execution may fail on certain HP-UX 11v23 machines.

Workaround: Download and install these patches:

getaddrinfo function limitation on Solaris.

Sybase IQ InfoPrimer Server displays error messages while using getaddrinfo function on Solaris machine.

Workaround: Download and install the #solaris_10u5(s10u5_07) patch on your machine.

System error in JavaScript editor while debugging large scripts.

The default maximum size of the JavaScript engine runtime is 20000000 bytes, or 19.07MB. When debugging large scripts or long-running scripts such as a script with many loop iterations, you may encounter a memory issue.

Workaround: In the Default.ini file, configure the maximum memory size for the JavaScript engine:

Monitoring loader components.

If you use a Web browser to monitor projects that include the IQ Loader File via Load Table and IQ Loader DB via Insert Location components of an ETL project, you may not be able to view the execution progress status.

Workaround: None.

Unable to monitor projects started from command line.

Web-based remote monitoring fails to monitor the execution of projects started from the command line. In Sybase IQ InfoPrimer, you can only monitor jobs started from the command line.

Workaround: Create a simple job and include the project in it that you want to monitor.

Sybase IQ InfoPrimer cannot be installed in the same directory as Sybase IQ.

Installation fails when Sybase IQ InfoPrimer and Sybase IQ are installed in the same directory. Since Sybase IQ creates an “uninstall” directory during installation, and Sybase IQ InfoPrimer also creates a file with the same name, installation fails with an error message.

Workaround: Do not install Sybase IQ InfoPrimer in the same directory as Sybase IQ.

Use server name caching to connect to a specific Sybase IQ server.

Sybase IQ InfoPrimer may not connect to a specific Sybase IQ server using ODBC if there are multiple Sybase IQ servers with the same server name, database name, and port number.

CommLinks=tcpip(DoBroadCast=DIRECT;host=iq server;port=2638)

Sybase IQ InfoPrimer Server stops responding if there is insufficient temp space in Sybase IQ.

Sybase IQ InfoPrimer Server may stop responding if there is insufficient temporary space on the source Sybase IQ database server when transferring a large amount of data from Sybase IQ.

Workaround: Increase the temporary space for the Sybase IQ server to a minimum of 1GB.

Exceeding connection limit locks connections to Sybase IQ.

When multiple connections from Sybase IQ InfoPrimer to Sybase IQ remain open after projects and jobs execute, connections to Sybase IQ can lock when open connections exceed the Sybase IQ connection limit. Users receive error messages that Sybase IQ InfoPrimer cannot retrieve column descriptions, Sybase IQ InfoPrimer has exceeded the database connection limit, and Sybase IQ InfoPrimer cannot connect to Sybase IQ.

Workaround: Increase the connection limit in Sybase IQ. See Sybase IQ 12.7 System Administration Guide > Chapter 12, “Managing User IDs and Permissions” > “Managing IQ user accounts and connections”.

Special characters in the installation path of Sybase IQ InfoPrimer Development or Server may lead to problems in accessing databases.

For example, connecting to an Oracle database client returns the following error when Sybase IQ InfoPrimer Server is installed in a path containing parentheses, such as C:\Program Files (x86)\Sybase:

ORA-12154: TNS:could not resolve the connectidentifier specified

Workaround: Sybase recommends that you select installation paths that contain only alphanumeric characters. To avoid parentheses issues, remove “(x86),” which is added by the Windows 2003 EE 64-bit operating system, from the default target directory during installation.