To start and run, SAP Sybase IQ must find and access several types of files. Several directories or files with identical names may reside on a system.
Understanding how SAP Sybase IQ finds these files is important to ensure that you use the correct files. The types of files include but are not limited to:
Libraries – might include product libraries or system libraries. File name extensions include .so.nnn or .so on UNIX, or .dll or .lib on Windows. These files are required to run SAP Sybase IQ. If an incorrect DLL is found, a version mismatch error may occur. For example, library files might be found in $IQDIR16/lib64 or $SYBASE/$SYBASE_OCS/lib64 on UNIX, or %IQDIR16%\bin32 or %SYBASE\%SYBASE_OCS\dll on Windows. An empty directory, $IQDIR16/usrlib, lets you supersede default libraries with custom libraries and patches, because start_iq includes usrlib before regular library directories. SAP Sybase IQ uses both SAP® Sybase Adaptive Server Enterprise and SQL Anywhere libraries. If either of these products have already been installed on your system, note the directory where they are installed to avoid confusion.
Interface files – required to run SAP Sybase IQ. For example, .odbc.ini and utility_db.ini on UNIX, and util_db.ini on Windows. For more information about these files, see Administration: User Management and Security.
Configuration files – used to specify connection parameters. Examples include default.cfg on Windows or iqdemo.cfg.
Database files – store the data and metadata. For example: iqdemo.db, iqdemo.iq, iqdemo.iqmsg, iqdemo.iqtmp.
Log files – store information about the current session on the server and connected database. For example, a server log might be named %ALLUSERSPROFILE%/logfiles/yourservername.0006.srvlog. The database log (for example, %ALLUSERSPROFILE%/demo/iqdemo.log) is created when you connect to the database. For more information about these files, see Administration: Database and Utility Guide.
Product scripts – are sample files that show how to create, populate, and upgrade databases.
User files – include flat files used with the LOAD command and SQL scripts used with tools such as Interactive SQL.
Temporary files – created by to store temporary information for operations like performing sorts for queries.
Some file names are specified in SQL statements and must be located at runtime. Examples of SQL statements that use file names include the following:
INSTALL statement – the name of the file that holds Java classes.
LOAD TABLE statement – the name of the file from which data should be loaded.
CREATE DATABASE statement – A file name is needed for this statement and similar statements that can create files.
In some cases, SAP Sybase IQ uses a simple algorithm to locate files. In other cases, a more extensive search is carried out.