Empty onconfig file

Online Version 7.23 UC1 AIX 4.3.2 RS6000 J30 I have continuous log backup going at all times. On Wed, last week I presumed that logical log backup had been stopped, CNTRL-C. But, alas this had not happened. Our nightly backup is done via a cronjob. We were closed Thurs & Friday. I checked the backups this morning and found that the backups had not been done. Continuous backup was still going on. Stopped continuous backup and tried manual backup. First error was "Could not write". Checked to see processes that were running. Three backup processes had been spawned. Killed those processes (softly :->>) and tried to do a manual backup (ontape -s). I got an error "Empty config file is not allowed" Yes my onconfig is indeed empty!!!!!! Wow!!! HOW could this have happened???? No, I was'nt (was not - for the purists) editing my onconfig file. And fortunately I have my OS backup - yech. HOW does an onconfig file suddenly become empty???? Appreciate any insights into this miracle. TIA -kudzi

The most common way is to rcp the file to itself through some alias (since rcp will not let you do that if it detects the problem). So if you are on host freddy and freddy also has an FDDI address called freddy_fddi and you rcp $ONCONFIG freddy_fddi:$INFORMIXDIR/etc/$ONCONFIG poof. You will get a message about the file size having changed and wham it's gone. That's one way. BTW before you hassle with the archives, do the following to recreate the onconfig file: dbaccess sysmaster - > unload to onconfig.sysconfig delimiter '<TAB>' > select cf_name, cf_original from sysconfig;> ^D^D mv onconfig.sysconfig $ONCONFIG It isn't pretty but it's all there. The only thing you HAVE to do is edit and remove the backslashes from parameters that had empty strings default in your original ONCONFIG file or were not present and have no default. Art S. Kagel Kudzi Muchaka wrote: > > Online Version 7.23 UC1 > AIX 4.3.2 > RS6000 J30 > > I have continuous log backup going at all times. On Wed, last week I > presumed that logical log backup had been stopped, CNTRL-C. But, alas > this had not happened. Our nightly backup is done via a cronjob. We were > closed Thurs & Friday. > > I checked the backups this morning and found that the backups had not > been done. Continuous backup was still going on. Stopped continuous > backup and tried manual backup. First error was "Could not write". Checked to see processes that were running. Three backup processes > had been spawned. Killed those processes (softly :->>) and tried to do a > manual backup (ontape -s). I got an error "Empty config file is not allowed" > Yes my onconfig is indeed empty!!!!!! Wow!!! HOW could this have > happened???? > > No, I was'nt (was not - for the purists) editing my onconfig file. And > fortunately I have my OS backup - yech. HOW does an onconfig file > suddenly become empty???? Appreciate any insights into this miracle. > > TIA > -kudzi

Was the filesystem that held the onconfig file full? Just a thought, really, I've never seen this happen, or even know if it could happen, but what if for some reason Informix was trying to rewrite the onconfig file and opened the file for write, during which time the filesystem filled. That would cause the fprintf (fwrite's, whatever) to fail. Just pondering... Anyone know if this is possible? In article <848fnp$j5h$1@news.xmission.com>, "Kudzi Muchaka" <KMuchaka@HAFresno.org> wrote: > > Online Version 7.23 UC1 > AIX 4.3.2 > RS6000 J30 > > I have continuous log backup going at all times. On Wed, last week I > presumed that logical log backup had been stopped, CNTRL-C. But, alas > this had not happened. Our nightly backup is done via a cronjob. We were > closed Thurs & Friday. > > I checked the backups this morning and found that the backups had not > been done. Continuous backup was still going on. Stopped continuous > backup and tried manual backup. First error was "Could not write". Checked to see processes that were running. Three backup processes > had been spawned. Killed those processes (softly :->>) and tried to do a > manual backup (ontape -s). I got an error "Empty config file is not allowed" > Yes my onconfig is indeed empty!!!!!! Wow!!! HOW could this have > happened???? > > No, I was'nt (was not - for the purists) editing my onconfig file. And > fortunately I have my OS backup - yech. HOW does an onconfig file > suddenly become empty???? Appreciate any insights into this miracle. > > TIA > -kudzi > > -- # unrm / ksh: unrm: not found # man cpio Sent via Deja.com http://www.deja.com/ Before you buy.