tbinit in debug mode? -Reply

Zhenling I can speak for oninit, I have never tried this in tbinit. It is possible to set an environment variable AFDEBUG=1 which will cause the RDBMS engine to hang instead of crashing on an abnormal abort. The purpose of this is to allow Informix to dial in and examine the instance while it is still up. If you have not organised with Informix to do this, you may find the utility of this limited. There is also another debug facility called sqlidebug which dumps out information to disk files. I have never used these without instruction from an Informix SE. If you feel the need to debug your instance perhaps you should talk to your support. rgds -- -- Peter Tashkoff <tashkop@kiwi.co.nz> NZ Kiwifruit Marketing Board Usual disclaimers apply. This posting may not be used by any party to vilify another. >>> <zsun@br00dbss.med.osd.mil> 12/September/1996 02:47am >>> Hi, Has anyone heard of, or used tbinit in debug mode? I was told there was/is an un-documented option to run tbinit in debug mode, unfortunately the person who said that used it a long time ago and does not remember which option now. We have a database which has lots of physical/index read locking problem, tbcheck with varies options does not show any problems in the database. We know it could be caused by lots of other things, but we would like to run tbinit in debug mode first (if there is such an option). Operating System: SCO Unix ODT 2.0 Informix OnLine: OnLine 5.02 UC3 Thanks in advance, Zhenling Sun EDS D/SIDDOMS zsun@br00dbss.med.osd.mil