Re: Initialization question

So, here's the oninit -ivy output: Reading configuration file '/home/informix/etc/onconfig.ol_andris'...succeeded Creating /etc/.infxdirs ... succeeded Creating infos file "/home/informix/etc/.infos.ol_andris" ... "/home/informix/etc/.conf.ol_andris" ... succeeded Writing to infos file ... succeeded Checking config parameters...succeeded Allocating and attaching to shared memory...succeeded Creating resident pool 500 kbytes...succeeded Creating buffer pool 402 kbytes...succeeded Initializing rhead structure...succeeded Initializing ASF ...succeeded Initializing Dictionary Cache and Stored Procedure Cache...succeeded Onlining 0 additional cpu vps...succeeded Onlining 2 IO vps...succeeded Forking main_loop thread...succeeded Initialzing DR structures...succeeded Forking 1 'ipcshm' listener threads...succeeded Starting tracing...succeeded Initializing 1 flushers...succeeded oninit: Fatal error in shared memory initialization Online.log contains: Tue Jul 27 12:36:01 1999 12:36:01 Event alarms enabled. ALARMPROG = '/home/informix/etc/log_full.sh' 12:36:02 DR: DRAUTO is 0 (Off) 12:36:03 chunk failed sanity check 12:36:03 I/O error, Primary Chunk '/INFXDATA/ol_chunk' -- Offline (sanity) 12:36:03 INFORMIX-OnLine Stopped. 12:36:03 mt_shm_remove: WARNING: may not have removed all/correctsegments In addition I have to say, that I'm working on NT box, making a remote install on HP-UX. Could the problem be in sqlhosts? best regards ainars --- Octav Chiriac <com@netinfo-moldova.com> wrote: > Ok. I don't remember when this error message > happenes, but you could > try checking: > 1. The file ol_chunk has the right ownership and > group (informix) > and the right permissions (660, rw-rw----) > 2. There is enough disk place on the filesystem you > have > create the file ol_chunk (check out ROOTSIZE, > ROOTOFFSET) > 3. Check that ROOTPATH is the full path to this > file. > > Also you could check after 'oninit -i' that the size > of > ol_chunk have changed to ROOTSIZE+ROOTOFFSET KB. > > Of course it could be that your disk is failing. In > this > case you could try making a rootdbs of a smaller > size and check > what is happening, or check with an OS utility your > disk. > > May be someone in group will have more ideas on this > issue. > But if all I have pointed out above is all right > you'll > need to post some more information (the message log, > may be > the output of 'oninit -iv' command). > > > Best Regards, > Octav > > > On Fri, Jul 23, 1999 at 03:30:19AM -0400, ainars > ainars wrote: > > Thanks! > > > > But, can You explain this message in onlog file? > > It appears, when I try to run oninit -i command. > > 'chunk failed sanity check' > > > > Best regards > > ainars _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com