Filter
Top Products
Troubleshooting startup, shutdown, and connections
96
• Check that all of the files exist for the database you have requested. At a
minimum, there must be an IQ Store (dbname.iq), a Catalog Store
(dbname.db), an IQ Temporary Store (dbname.iqtmp), a transaction log
(dbname.log This may be missing if the database is newly created and has
not been modified.), and a message file (dbname.iqmsg). The names
shown here in parentheses are the default format; yours may be different.
• Check that any restores have completed successfully.
See also “How Adaptive Server IQ makes connections”.
Stopping a database server in an emergency (UNIX)
Always try first to stop the server using the methods described in “Stopping the
database server”. If you are unable to stop it using those methods, and if you
started the database server as a batch or background process (using
start_asiq),
try the following:
1 If possible, you should make sure that no users are connected to the
database.
2 At the UNIX prompt, enter the following command:
kill -hup
pid
where pid is the process id of the database server you are stopping.
See also Adaptive Server IQ Troubleshooting and Error Messages Guide.
Resolving problems with your DBISQL window on UNIX
The interactive DBISQL utility on UNIX uses character-based windows.
These windows rely on line-drawing characters that are part of the ASCII
character set, and some other character sets as well. The ability of DBISQL to
display these windows correctly depends on the type of terminal you use, and
the character set translation your operating system uses. If your windows
appear to be drawn with accented characters rather than line-draw characters,
you can still use them to enter commands and receive output as described
throughout this book.
DBISQL uses function keys for many operations. Some UNIX windowing
environments may not support these function keys, unless you make some
adjustments.