Setting explicit fetch size in SAS/SHARE based Information Links returns additional garbage rows.

Setting explicit fetch size in SAS/SHARE based Information Links returns additional garbage rows.

You may find that additional rows of garbage data are returned when accessing data via SAS/SHARE based Information Links. This can also result in extra empty rows in both data and Information Link prompts.

Symptoms:
Additional rows of garbage data are returned when accessing data via SAS/SHARE based Information Links. This can also result in extra empty rows in the data and in Information Link prompts. In this case, the fetch size on the SAS/SHARE will have a positive value. This can be seen when a prompt is added to the Information Link since a single column will be queried, thus returning the number of rows equal to the fetch size. If the fetch size is very large, the client may become unresponsive when trying to handle the high number of empty rows .

Cause:
A defect in the JDBC SAS/Share connect.jar driver as used by the SAS\SHARE data source template where the driver will return as many rows as the fetch size is set to. If the amount of data is less than the set value of the fetch size in the Information Link in the Information Designer, the driver will return as many rows as the fetch size is set to. The actual data will be returned and then all additional rows will either be empty or garbage characters until the fetch size is reached. In the Information Designer, edit SAS\SHARE data source which the Information Link is based on and set the fetch size to 0. Doc: Data Source Tab

• https://docs.tibco.com/pub/sfire-analyst/10.3.1/doc/html/en-US/TIB_sfire-analyst_UsersGuide/id/id_data_source_tab.htm