Version Information in Message Logs

Version information appears near the beginning of the message log file.

Version information is similar to the following:

Versn:
15.3.0.5071/100301/P/GA/Sun_Opteron/OS 5.10/64bit/2010-05-01 01:21:40

Version string elements
Version string element	Example	Comments
Major release	15.3	First two segments indicate major release
Minor release	15.3.`n`	Third segment indicates minor release
Internal build number	5071	Unique build number for internal use
Internal build date	100301	Date identifier for internal use
Internal build type	P	P = Production build
Release type	GA	GA = General Availability ESD = Engineering Software Distribution (Maintenance)
Hardware platform	Sun_Opteron	Identifier for hardware provider
Operating system version	OS 5.10	OS version and bit mode refer to the system on which the software was built, not where it is running currently.
Bit mode	64bit
Build date and time	2010-03-01 01:21:40	Shown as `YYYY-MM-DD hh:mm:ss` (ISO datetime format): 4-digit year 2-digit month number (0 – 12) 2-digit day of month number (01 – 31) 2-digit number of complete hours that have passed since midnight (00 – 23) 2-digit number of complete minutes that have passed since the start of the hour (00 – 59) 2-digit number of complete seconds that have passed since the start of the minute (00 – 59)

Collation Information in Message Logs

The message log captures collation information when you start the database.

Collation information captured in the message log shows the collation name, case sensitivity, blank padding state, and character translation table requirement. Comparisons are conditioned means that no translation table is required when comparing character data.

Connection Information in Message Logs

The message log captures connection information after the first transaction begins and before the next transaction starts.

A connect line that shows the connection handle and database user name is printed in the message log once per database connection.

For example:

I. 04/23 13:02:37. 0000000003 
Connect:  SA connHandle: 1  SA connID: 3  
IQ connID: 0000000003  User: DBA

You can use this connection information to match query plans in the .iqmsg file with query text. Run the stored procedure sp_iqcontext to determine what statement each connection is executing at a given moment.

Insert Notifications in Message Logs

The message log captures notification messages from insert and load operations.

You can turn off notification messages using parameters in the LOAD and INSERT statements.