Sybase Troubleshooting dbisql and dbspawn Errors in Adaptive Server IQ

User-defined variable issue Adaptive Server IQ 12.4.0

To avoid truncated output, increase the length by setting the truncation_length option as follows:

SET OPTION DBO.TRUNCATION_LENGTH = 80

Alternatively, from the DBISQL menu select Command→Options and enter a higher value for Limit Display Columns and/or Limit Output Columns.

7.3.3 User-defined variable issue

User-defined variables will core dump if used in IQ queries.

7.3.4 DBSPAWN ERROR when starting a server

When attempting to start a server, you may get the following message:

DBSPAWN ERROR -96 -- database engine already running

This means that dbspawn is finding the shared memory segment of a previously started server, and is unable to create a shared memory segment.

To resolve this issue, subsequent servers should be started with the parameter -hswhich will turn off shared memory. For example:

start_asiq @kent.cfg kent.db -hs

All servers can be started with shared memory “off”. Note that if shared memory is turned off, then you will have to connect to the server using TCP/IP, instead of using the default shared memory connection.

7.3.5 Unsupported terminal types cause DBISQL error

If you set the terminal type to “dumb” or “unknown”, then start DBISQL,

Adaptive Server IQ returns an error. For example:

%setenv TERM dumb % dbisql Error at line 1

Unable to initialize screen routines

To avoid problems, use an xterm window to run DBISQL on UNIX systems.

For example, you can start an xterm window with a scroll bar as follows:

%xterm -sb

7.3.6Adding a raw disk dbspace

Do not specify the optional SIZE clause when adding a raw disk dbspace.

Adaptive Server IQ will correctly calculate the size of the raw disk without it.

12 Release Bulletin for Digital UNIX