RE: Upgrade Solaris 2.6 to 2.8 and got memory fatal

Wayne In the Solaris upgrade did you allocate or reconfigure any disk space? Are you using any Volume manager such as Disksuite? If so you may need to do something to the volume manager. Are the new volumes pointing to the same place in disk as they did before the upgrade? The informix log may have more information. It looks like it is saying that the chunk is not as it expected to to be..something is now corrupt. MW > -----Original Message----- > From: owner-informix-list@iiug.org > [mailto:owner-informix-list@iiug.org]On Behalf Of Wayne > Sent: Wednesday, 5 May 2004 9:59 a.m. > To: informix-list@iiug.org > Subject: Upgrade Solaris 2.6 to 2.8 and got memory fatal > > > Hi All, > > After upgraded my Sun OS Solaris 2.6 to 2.8 and I can not start > Informix. I got the error messages, see below. I know one db chuck is > not accessable. But I believe, I still able to bring the engineer > online right? Any input I would be appreciated. Thanks > > -Wayne > > ********************************************************************* > iceberg% oninit -v> Checking group membership to determine server run modesucceeded > Reading configuration file > '/usr/informix/etc/onconfig.iceberg'...succeeded > Creating /INFORMIXTMP/.infxdirs ... succeeded > Creating infos file "/usr/informix/etc/.infos.on_iceberg" ... > "/usr/informix/etc/.conf.on_iceberg" ... succeeded > Writing to infos file ... succeeded > Checking config parameters...succeeded > Allocating and attaching to shared memory...succeeded > Creating resident pool 431654 kbytes...succeeded > Creating buffer pool 230002 kbytes...succeeded > Initializing rhead structure...succeeded > Initializing ASF ...succeeded > Initializing Dictionary Cache and SPL Routine Cache...succeeded > Bringing up ADM VP...succeeded > Creating VP classes...succeeded > Onlining 0 additional cpu vps...succeeded > Onlining 1 IO vps...succeeded > Forking main_loop thread...succeeded > Initialzing DR structures...succeeded > Forking 1 'ipcstr' listener threads...succeeded > Forking 1 'tlitcp' listener threads...succeeded > Starting tracing...succeeded > Initializing 1 flushers...succeeded > Initializing log/checkpoint information...succeeded > Opening primary chunks...succeeded > Opening mirror chunks...succeeded > Initializing dbspaces...succeeded > Validating chunks...succeeded > Initialize Async Log Flusher...succeeded > Forking btree cleaner...succeeded > iceberg% Initializing DBSPACETEMP list > Checking database partition index...FAILED > oninit: Fatal error in shared memory initialization sending to informix-list

Murray, My system disks lay out did not change. All I have done is upgrade Solaris to 2.8. BTW my IDS is 9.21. Here is my online.log. Do you think OS is 64bits causing the problem? Thank you for the input. --Wayne ******************************************************************* iceberg% oninit iceberg% oninit: Fatal error in shared memory initialization ******************************************************************* 15:53:26 Event alarms enabled. ALARMPROG = '/usr/informix/etc/log_full.sh' 15:53:26 Booting Language <c> from module <> 15:53:26 Loading Module <CNULL> 15:53:26 Booting Language <builtin> from module <> 15:53:26 Loading Module <BUILTINNULL> 15:53:30 Informix Dynamic Server 2000 Version 9.21.UC4 SoftwareSerial Numb er ACP#J267193 15:53:31 Informix Dynamic Server 2000 Initialized -- Shared MemoryInitialized. 15:53:31 Physical Recovery Started at Page(2:62916). 15:54:23 Physical Recovery Complete: 128542 Pages Examined 110578Pages Restore d. 15:54:23 Logical Recovery Started. 15:54:23 10 recovery worker threads will be started. 15:54:26 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks 15:54:27 Informix Dynamic Server 2000 Stopped. 15:54:27 mt_shm_remove: WARNING: may not have removed all/correctsegments ********************************************************************* "Murray Wood (IList)" <ifxmaillist@quanta.co.nz> wrote in message news:<c79evk$ujt$1@terabinaries.xmission.com>... > Wayne > > In the Solaris upgrade did you allocate or reconfigure any disk space? > Are you using any Volume manager such as Disksuite? If so you may need to do something to the volume manager. Are the new volumes pointing to the same place in disk as they did before the upgrade? > > The informix log may have more information. It looks like it is saying that the chunk is not as it expected to to be..something is now corrupt. > > MW >