The getiqinfo script collects all of the following information:
Type of hardware, amount of memory, CPU type, speed, number of CPUs
Operating system (for example, Sun Solaris 2.9)
Operating system patch level
Swap space size
IQ version and EBF level, and Anywhere version
Stack trace file for the date and time this problem occurred, named stktrc-YYYYMMDD-HHMMSS_#.iq, in the directory where you started the database server. (UNIX and Linux platforms only)
Command or query that produced the error
Message log file, named dbname.iqmsg, located by default in the directory where you started the database server.
Query plan (recorded in .iqmsg file; see the Note below)
Server logs
For UNIX, ASIQ-12_6/logfiles/<servername>.00n.stderr and ASIQ-12_6/logfiles/<servername>.00n.srvlog
On Windows platforms, if needed, you must restart the server and manually collect a copy of the console window.
Startup and connection option settings, from the configuration file (by default, dbname.cfg)
Database option settings and output from sa_conn_properties (if the server is still running)
On multiplex databases, you must execute getiqinfo on the write server and/or query servers, and the following information is also collected:
servername.out on query servers
write_server_name/repDirs/logfiles/servername.dbrlog on the write server
The following information is not collected by getiqinfo, but may also be requested by Technical Support:
Connectivity protocol used (for example, ODBC, JDBC, TDS)
Open Client version
Configuration type (single user or multi-user)
Front end tool used (for example, Brio Query)
Schema and indexes for the database
Output from sp_iqcheckdb procedure
A checklist for recording information that Technical Support may need is provided at the end of this chapter, in the unlikely event that you need to collect this information manually.
Query plan detail is collected automatically by getiqinfo if
the options below are set. You can also collect this information
manually, by setting the options and then rerunning the command
that produced the error.
SET TEMPORARY OPTION QUERY_PLAN = 'ON'
SET TEMPORARY OPTION QUERY_DETAIL = 'ON'
The plan will be in the message log file. The default for databases created as of Version 12.5 is Query_Plan = ON, and Query_Detail = OFF.
If you have performance problems, set the following option:
SET TEMPORARY OPTION QUERY_PLAN_AFTER_RUN = 'ON'
This will enable technical support to see which steps in the query processing used the time.
