Re: logging change error

OK, let's do this quickly: 1. In your onconfig file, set: TAPEDEV /dev/null # if UNIXor TAPEDEV NUL # if NT 2. ontape -s -L 0 -U ausatst Aside, do you really need unbuffered logging? It's quite slow compared to buffered logging, and if this is just a test database.... The command would be: ontape -s -L 0 -B ausatst HTH. From: "Karl Hewlett" <kzhw@xtra.co.nz> > >I am a new Informix DBA - and have never use Informix before :) (I have an >Oracle background) > >Yesterday I dbimported a database (ausatst -thank god it is a test >database, >but still v. important at this stage of the project). I had not set >logging >on (didn't know I had to) and had to go to a meeting. The PeopleSoft >administrator (my backup) attempted to set logging on with "ontape -s -U >ausatst" and encountered some sort of error. I think he may have done a >level 2 ontape. > >Anyway the present situation is that onmonitor reports a logging status of >N. Any attempt to alter the logging status results in the following error > >informix:ps7testshm@zircon>ontape -s -U aufstst >Error changing logging status - 'aufstst'. iserrno 107. > > >I have attempted to do "ontape -s -N ausatst" with the same result. > ontape -s -B ausatst gives the result "invalid logging change" or some>very >similar error. I have dropped and reimported the database. I have stopped >and resarted the instance. The docos refer to an onarchive command that >stops a partly completed logging change but we don't use onarchive and it >doesn't run - I tried it. > >Any help greatfull appreciated. As I do not have newsgroup access at work >please reply to k.hewlett@auckland.ac.nz Thank you. ________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com