Shared memory not initialized for Informix7.30

Help! We took our INformix 7.30 online server down and thenthe solaris box it runs on down also for some hardware work this weekend. The RAID Array was switched from 2 controllers to 1 temporarily and one of the scsi boards pulled. Solaris box rebooted fine- no errors Informix is now giving errors when I try to bring it back up "shared memory not initialized for Myservername" We returned the hardware config to normal( which should not have affected it) but it still will not come back up. How do I get it to reinitialize this shared memory? What could have become corrupted? I have tried using both oninit, oninit -s and onmonitor. It should be noted that the db gets taken down and rebooted without a hitch weekly for system backups....so this is not the first time it has been down and then up again. All help appreciated Nancy

Nancy D Glenn wrote in message <36B698E6.603@ic.delcoelect.com>... >Help! > >We took our INformix 7.30 online server down and thenthe solaris box it >runs on down also for some hardware work this weekend. > >The RAID Array was switched from 2 controllers to 1 temporarily and one >of the scsi boards pulled. Solaris box rebooted fine- no errors > >Informix is now giving errors when I try to bring it back up "shared >memory not initialized for Myservername" Can you provide some more details, viz: 1. What messsages are there in your online log? 2. Do you actually see any shared memory segments for Informix (ipcs -m)? Are you using links to your disks, or pointing to the actual disks themselves? So, in your $ONCONFIG file, is the definition of ROOTDBS somethink like /dev/chunk1, which is then a pointer to /dev/rdsk/c1t1d0s0 (or whatever), or is it set directly to the raw device? If it's the latter, this could well be your problem, as the reconfigure boot may have renamed some of your devices. Neil Truby Londis Stores Hampton Hill UK

Neil, thanks so much for your quick response! Neil Truby wrote: > > Nancy D Glenn wrote in message <36B698E6.603@ic.delcoelect.com>... > >Help! > > > >We took our INformix 7.30 online server down and thenthe solaris box it > >runs on down also for some hardware work this weekend. > > > >The RAID Array was switched from 2 controllers to 1 temporarily and one > >of the scsi boards pulled. Solaris box rebooted fine- no errors > > > >Informix is now giving errors when I try to bring it back up "shared > >memory not initialized for Myservername" > > Can you provide some more details, viz: > > 1. What messsages are there in your online log? Here is wht I am able to get it to replicate consistantantly whenever and however I try to bring it to quiescent mode.: sym.out file is corrupted. 00:06:46 Event alarms enabled. ALARMPROG = '/usr/informix/etc/no_log.sh' 00:06:48 DR: DRAUTO is 0 (Off) 00:06:49 Assert Failed: Internal Error - Bus Error 00:06:49 Who: Session(1, informix@fs007eng, 0, 217038872) Thread(21, main_loop(), ced8018, 1) 00:06:49 Results: OnLine must abort 00:06:49 Action: Reinitialize shared memory 00:06:49 See Also: /da0/lun2/af.1587e8, shmem.1587e8.0 00:07:19 rsinit.c, line 9947, thread 21, proc id 4091, Bus Error. 00:07:19 PANIC: Attempting to bring system down > 2. Do you actually see any shared memory segments for Informix (ipcs -m)? nope, nothing listed at all > > Are you using links to your disks, or pointing to the actual disks > themselves? So, in your $ONCONFIG file, is the definition of ROOTDBS > somethink like /dev/chunk1, which is then a pointer to /dev/rdsk/c1t1d0s0 > (or whatever), or is it set directly to the raw device? If it's the latter, > this could well be your problem, as the reconfigure boot may have renamed > some of your devices. hmm. well, the Rootpath is not a link,and does not point to a raw device. The mapping of the RAID drive is done with a vfstab file( do I have that right guys?) But this DID change when we rebooted. SO, if the file pointer is still correct /mountpoint/Lun#/filename.chk and gets me there ok, but the mapping in the vfstab changes, woudl this be enough to bring it down? If so, how do we fix that? We may actually be making progress here... Nancy

You need to provide some more information like what else is in the database log file. Did your /etc/system file change where you might be missing Informix recommended memory and semaphore parameters? Run ipcs to see if you have any memory or semaphore facilities that need to be brought down with ipcrm command. Just a few things to look at. Frank Testa Manager of DBA Columbia House Company In article <36B698E6.603@ic.delcoelect.com>, ndglenn@ic.delcoelect.com wrote: > Help! > > We took our INformix 7.30 online server down and thenthe solaris box it > runs on down also for some hardware work this weekend. > > The RAID Array was switched from 2 controllers to 1 temporarily and one > of the scsi boards pulled. Solaris box rebooted fine- no errors > > Informix is now giving errors when I try to bring it back up "shared > memory not initialized for Myservername" > > We returned the hardware config to normal( which should not have > affected it) but it still will not come back up. How do I get it to > reinitialize this shared memory? What could have become corrupted? I > have tried using both oninit, oninit -s and onmonitor. > > It should be noted that the db gets taken down and rebooted without a > hitch weekly for system backups....so this is not the first time it has > been down and then up again. > All help appreciated > > Nancy > -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own

Nancy D Glenn wrote: > > Help! > > We took our INformix 7.30 online server down and thenthe solaris box it > runs on down also for some hardware work this weekend. > > The RAID Array was switched from 2 controllers to 1 temporarily and one > of the scsi boards pulled. Solaris box rebooted fine- no errors > > Informix is now giving errors when I try to bring it back up "shared > memory not initialized for Myservername" > > We returned the hardware config to normal( which should not have > affected it) but it still will not come back up. How do I get it to > reinitialize this shared memory? What could have become corrupted? I > have tried using both oninit, oninit -s and onmonitor. Did this maintenance include building a new kernel? If so perhaps the Informix required parameters were lost from the kernel configuration files when the new kernel was built. Art S. Kagel

In article <36B75A27.E82@bloomberg.net>, kagel@bloomberg.net (Art S. Kagel) wrote: [cutting] > Did this maintenance include building a new kernel? If so perhaps > the Informix required parameters were lost from the kernel > configuration files when the new kernel was built. > > Art S. Kagel > Unless the /etc/system file is changed then kernel will be fine. The replaced controllers will automatically detected, and depending on how the machine was rebooted the disks will just be there or can be easily brought back into the system once the machine is running Paul Watson # I don't suffer from WF Software Ltd. # stress, I'm just Tel. (+44) 1436 674729 # a carrier Fax. (+44) 1436 678693 # www.wfsoftware.co.uk