Known Issues for Interactive SQL

Descriptions of known issues for Interactive SQL.

Use dbisql, instead of dbisqlc , unless instructed to do otherwise for specific tasks. dbisqlc is supported, but does not contain all the features of dbisql. dbisqlc will be deprecated in a future release.

Interactive SQL issues
CR#	Description
733451	Column order in multi-column UNIQUE index definition on an RLV-enabled table must match order in table definition – If a multi-column UNIQUE index (including a multi-column primary key) exists on an RLV-enabled table, and the column order in the index definition differs from the column order in the table definition, the server fails on inserts, updates and loads of that table.
732734	ALTER TABLE PARTITION BY and ALTER TABLE SUBPARTITION BY RANGE statements are unsupported – Documentation erroneously includes unsupported syntax. See the ALTER TABLE statement in Documentation Changes > Reference: Statements and Options. Workaround – For ALTER TABLE PARTITION BY HASH, drop the table and create a new table with a hash partition.
731331	SYSTEM PROCEDURE AS DEFINER ON clause disables FORWARD TO statement – After you run ALTER DATABASE UPGRADE with the SYSTEM PROCEDURE AS DEFINER ON clause, the FORWARD TO statement stops working. SAP Sybase IQ attempts to connect as the user who created the system procedure, not the user executing FORWARD TO. Workaround – Set the following connection property to re-enable FORWARD TO: SET OPTION public.extern_login_credentials = login_user
668445	Read-only field restrictions for dsedit and iqdsedit – When using dsedit or iqdsedit, if you try to modify any field other than Server Address, you may get an error indicating that this operation is not allowed, followed by a shutdown. These fields are read-only and should not be edited.
n/a	Import option unsupported – Do not use the Import option on the dbisql Data menu (or Command \| Options \| Input Format in dbisqlc). This option is not supported for use with IQ databases. Use the LOAD TABLE statement or the INSERT statement to load data into IQ tables.
n/a	Creating output files in quiet mode – If you run dbisql (Interactive SQL) with the -q (quiet mode) option, and the data extraction commands (primarily setting the option `TEMP_EXTRACT_NAME1` to an output file) are in a command file, you must first set and make permanent the dbisql option “Show multiple result sets.” If you do not set this option, the output file is not created.
n/a	Show multiple result sets – To set the option “Show multiple result sets,” click Tools \| Options in the dbisql window, choose “Sybase IQ,” and select the “Results” tab. Then select “Show all results sets.”
n/a	Query plan on the Plan tab – The query plan in the dbisql Plan tab is a SQL Anywhere style query plan. For an SAP Sybase IQ query plan, refer to the IQ .iqmsg file.
n/a	Unable to initialize screen routines – If you set the terminal type on UNIX and Linux systems to “dumb” or “unknown” and then start dbisqlc, SAP Sybase IQ returns an error. For example: % setenv TERM dumb % dbisqlc `error at line 1Unable to initialize screen routines` Workaround – To avoid problems, run dbisql (Interactive SQL) instead, or use an xterm window to run dbisqlc on UNIX and Linux systems. For example, to start an xterm window with a scroll bar, enter: % xterm -sb