Re: TRANSACTION LOGGING

It is a pretty simple task, but not one you could normally do from within an application. To make the switch the database must be in quiescent mode. Next type 'ontape -N {database name}' (I think the syntax is right, is it?). After this put the enginr back on-line. To switch back to logging however, the database must have a level 0 archive performed. What I do, sometimes, is archive to the /dev/null device. It is quick and gets you on your way. That is all I willing to regurgitate from the manual this time. It's all there all you have to do is RTFM. rmcall@on-ramp.ior.com poppy@cftnet.com (Poppy Asokarathinam) wrote: >Hi, >I want to know how to turn on and turn off transaction logging. When exporting >and importing large databases, I would want to be able to control the logging >feature so that I will not run out of log space. I read somewhere that it >could be done while using dbaccess and not having to use tbmonitor a informix. >Any help/pointers would be greatly appreciated. >thanks >poppy >poppy@cftnet.com -------------------------------------------------------- Rob McAllister rmcall@on-ramp.ior.com Spokane, WA "On all good programmers a little core must dump"