Known Issues for Replication Server and Sybase IQ InfoPrimer Integration

These known issues concern the integration of Replication Server and Sybase IQ InfoPrimer.

Replication Server and Sybase IQ InfoPrimer Integration Known Issues
CR#	Description
668621	The Replication Server materialization scripts do not execute correctly on Windows server. Workaround: Before running the Replication Server materialization scripts: Install MKS Toolkit 9.4. You can download the MKS Toolkit environment at http://mkssoftware.com. Set the TK_DUALCASE_IN_CASE_STATEMENTS environment variable to 1. Start Sybase IQ InfoPrimer Server from the %SYBASE%\SybaseIQIPServer\scripts\replication directory: GridNode GridNode --port 5500 In the Processing tab of your EL project, insert "sh " at the beginning of the command line. For example: sh {ScriptPath}\replication\mat_api.sh --env-pds "{env_pds}" --env-pdb "{env_pdb}" --env-pdb_user ....
668152	Unexpected column mapping may occur in SQL Transformation projects. By default, staging table columns may not map to base table columns as expected if a base table column is: An included attribute (column) in the Target tab in the Generic Transformation editor A key attribute (column) Has an expression specified in the Target tab of the Generic Transformation editor Workaround: For an update staging table, all transformations must be described in the Target tab of the Generic Transformation editor. All base table columns that are included attributes (columns) in the Target tab in the Generic Transformation editor must have expressions specified in the Target tab.
668147	Incorrect SQL may be generated for update operations. A SQL transformation for an update must check the bitmap column or columns of the update staging table to determine if transformations must be applied to base table columns. These transformations are specified in the Function column of the Attributes tab of the Generic Transformation editor and should be wrapped in CASE statements in the Generated Transformation. SQL statements, constant or calculated values, and functions that take more than one argument may not be properly wrapped in CASE statements. Workaround: Manually edit the Generated Transformation.
665408	Tables with Java-type or encrypted columns are not supported when no primary key is specified. In constructing the delete and update staging tables, Sybase IQ InfoPrimer includes only primary-key columns as published in the replication definition for the primary table. If no primary-key columns are specified, Sybase IQ InfoPrimer uses all published columns in the delete and update staging table schema, excluding LOB columns, Java columns, encrypted columns, and floating-point columns. However, Sybase IQ InfoPrimer cannot distinguish between Java columns and columns that have user-defined datatypes, nor can it determine which columns might be encrypted. Sybase IQ InfoPrimer therefore does not support primary tables containing Java-type or encrypted columns and for which you specify no primary key.