Re: Logical Logs U----B------ status

I haven't used IDS for NT but . . . . What's the specific error you are getting? It looks like your logs are backed up and available ('B'). Sounds like you may be getting a long transaction. On unix, the tape device would be set to /dev/null - is NUL correct for NT? You should be able to avoid this problem by turning logging off on this database for the load and then turning it back on. Marshall Turner

Marshall, >On unix, the tape device would be set to /dev/null - is NUL correct for NT? Yes, it is. I even confirmed this with Informix tech support cuz I started off trying 'NULL' instead (the way I'm used to seeing it spelled with MSSQL, Oracle, etc...) ;-) Thanks for your help, but it turns out my app requires the transaction logging... I eventually was able to get my logs humming along nicely by dropping all of the ones in rootdbs out of there, making fewer, larger ones in another dbspace and doing a level 0 backup :) ------------------ Doug Castell GoldMine Software --Simply Powerful http://www.goldminesw.com