Skip to Content

How to get the debugging information when connection and communication issues happen.

1. Problem

IQ has a communication and connection problem as follows.

[Example : Communication Error]

Starting server hpita_iqdemo on hpita at port 4444 (06/01 09:57:47)

Run Directory       : /gjang/IQ-16_0/demo
Server Executable   : /gjang/IQ-16_0/bin64/iqsrv16
Server Output Log   : /gjang/IQ-16_0/logfiles/hpita_iqdemo.0065.srvlog
Server Version      : 16.0.0.809/sp08.32

        ....

DBSPAWN ERROR:  -85
Communication error

2. To get more detailed information regarding connection and communication.

This switch "-z" displays diagnostic communication messages, and other messages, for troubleshooting purposes.

Information is logged to standard output in the srvlog file.

[Example : -z switch with srvlog]

1) Startup

I. 06/01 10:11:42. Trying to start SharedMemory link ...
I. 06/01 10:11:42.     SharedMemory link started successfully
I. 06/01 10:11:42. Trying to start TCPIP link ...
I. 06/01 10:11:42. Could not bind to address (::):4444
I. 06/01 10:11:42. TCPIP communication link not started
I. 06/01 10:11:42. Unable to initialize requested communication links
E. 06/01 10:11:42. Unable to initialize requested communication links
I. 06/01 10:11:42. Database server shutdown due to startup error
I. 06/01 10:11:42. Disallowing new connections
I. 06/01 10:11:42. Shutting down databases
I. 06/01 10:11:42. Starting checkpoint of "iqdemo" (iqdemo.db) at Mon Jun 01 2015 10:11
I. 06/01 10:11:42. Finished checkpoint of "iqdemo" (iqdemo.db) at Mon Jun 01 2015 10:11
I. 06/01 10:11:42. Completing server shutdown
I. 06/01 10:11:42. Database server stopped at Mon Jun 01 2015 10:11

or

2) select * from gjang;

I. 05/28 10:56:23. TDS 5: language SQL: 'select * from gjang\x0A'
I. 05/28 10:56:23. <,6,EXEC_ANY_IMM,select * from "gjang"
I. 05/28 10:56:23. TDS 5: result set: c1 _int(4), c2 _int(4)
I. 05/28 10:56:23. P,6,vt_1<seq>
I. 05/28 10:56:23. TDS 5: result row: 2, 1
I. 05/28 10:56:23. TDS 5: result row: 2, 1
I. 05/28 10:56:23. TDS 5: result row: 2, 1
I. 05/28 10:56:23. TDS 5: result row: 2, 1
I. 05/28 10:56:23. TDS 5: result row: 2, 1
I. 05/28 10:56:23. TDS 5: result row: 1, 1
I. 05/28 10:56:23. W,6,100,Row not found
I. 05/28 10:56:23. P,6,vt_1<seq>
I. 05/28 10:56:23. W,6,105,Procedure has completed
I. 05/28 10:56:23. >.,6
I. 05/28 10:56:23. TDS 5: request complete
I. 05/28 10:56:33. TDS 5: logout
I. 05/28 10:56:33. <,6,DISCONNECTs

3. Caution


- This should only be used when tracking problems.

- SUPPRESS_TDS_DEBUGGING optioin restricts the debugging information about TDS that appears in the server window.

   ex) set option public.suppress_tds_debugging='ON';


===

Gi-Sung Jang

No comments