shared memory not initialized for INFORMIXSERVER

Posted in 2009

Summary

User on IDS 7.31.UC5 under SCO UNIX 5.0.5 couldn't start the server, getting "shared memory not initialized for INFORMIXSERVER"; oninit -v hung at "Allocating and attaching to shared memory". Responders asked for version and online.log and suggested checking INFORMIXDIR/INFORMIXSERVER/ONCONFIG/SQLHOSTS. A newer online.log then showed repeated "Exception Recursion ... MT_EX_OS, Context: mem" PANICs with warnings that shared memory segments may not have been removed. Art Kagel diagnosed an engine bug, advising to clear leftover segments (onmode -ky) and restart with oninit -v, and to contact IBM support or upgrade. No confirmation of success is recorded.

Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.

Topics: General Discussion

MAREK JASINSKI — Sun, 15 Nov 2009 20:34:58 — source: IIUG Forums & Mailing Lists

When I try to start Informix Dynamix Server the following massage appears: shared memory not initialized for INFORMIXSERVER Any idea???

↪ replying to MAREK JASINSKI

Jarrod Teale — Sun, 15 Nov 2009 20:49:35 — source: IIUG Forums & Mailing Lists

Please post version, platform and relevant bit from the online log Jarrod -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of MAREK JASINSKI Sent: Monday, 16 November 2009 9:35 a.m. To: ids@iiug.org Subject: shared memory not initialized for INFORMIXSERVER [18109] When I try to start Informix Dynamix Server the following massage appears: shared memory not initialized for INFORMIXSERVER Any idea??? ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum. DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/

↪ replying to Jarrod Teale

MAREK — Sun, 15 Nov 2009 21:02:22 — source: IIUG Forums & Mailing Lists

IDS 7.31 UNIX SCO 5.0.5 20:34:14 Requested shared memory segment size rounded from 8000KB to 8192KB Wed Oct 28 20:34:15 2009 20:34:15 Event alarms enabled. ALARMPROG = '/usr/informix/etc/log_full.sh' 20:34:20 DR: DRAUTO is 0 (Off) 20:34:20 Requested shared memory segment size rounded from 588KB to 4096KB 20:34:20 Informix Dynamic Server Version 7.31.UC5 20:34:23 Informix Dynamic Server Initialized -- Shared Memory Initialized. 20:34:23 Physical Recovery Started. 20:34:23 Physical Recovery Complete: 0 Pages Restored. 20:34:23 Logical Recovery Started. 20:34:26 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks 20:34:27 Dataskip is now OFF for all dbspaces 20:34:27 On-Line Mode 20:34:27 Checkpoint Completed: duration was 0 seconds. 21:27:22 Informix Dynamic Server Stopped.

↪ replying to MAREK

Jarrod Teale — Sun, 15 Nov 2009 21:11:35 — source: IIUG Forums & Mailing Lists

So nothing happened between 20:34 and 21:27? No checkpoints? The Infomrix stopped message indicates that the server was shutdown normally. If you run "oninit -v" what happens? Jarrod -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of MAREK JASINSKI Sent: Monday, 16 November 2009 10:02 a.m. To: ids@iiug.org Subject: Re: RE: shared memory not initialized for INFO.... [18111] IDS 7.31 UNIX SCO 5.0.5 20:34:14 Requested shared memory segment size rounded from 8000KB to 8192KB Wed Oct 28 20:34:15 2009 20:34:15 Event alarms enabled. ALARMPROG = '/usr/informix/etc/log_full.sh' 20:34:20 DR: DRAUTO is 0 (Off) 20:34:20 Requested shared memory segment size rounded from 588KB to 4096KB 20:34:20 Informix Dynamic Server Version 7.31.UC5 20:34:23 Informix Dynamic Server Initialized -- Shared Memory Initialized. 20:34:23 Physical Recovery Started. 20:34:23 Physical Recovery Complete: 0 Pages Restored. 20:34:23 Logical Recovery Started. 20:34:26 Logical Recovery Complete. 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks 20:34:27 Dataskip is now OFF for all dbspaces 20:34:27 On-Line Mode 20:34:27 Checkpoint Completed: duration was 0 seconds. 21:27:22 Informix Dynamic Server Stopped. ************************************************************************ ******* Forum Note: Use "Reply" to post a response in the discussion forum. DISCLAIMER: This email contains confidential information and may be legally privileged. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this email. You may not use, disclose or copy this email or its attachments in any way. Any opinions expressed in this email are those of the author and are not necessarily those of the Fonterra Co-operative Group. http://www.fonterra.com/

↪ replying to Jarrod Teale

MAREK — Sun, 15 Nov 2009 21:44:25 — source: IIUG Forums & Mailing Lists

There are no more checkpoints in the onine.log oninit -v Checking group membership to determine server run modesucceeded Reading configuration file '/usr/informix/etc/onconfig'...succeeded Creating /INFORMIXTMP/.infxdirs ... succeeded Creating infos file "/usr/informix/etc/.infos.imc5" ... "/usr/informix/etc/.conf.imc5" ... succeeded Writing to infos file ... succeeded Checking config parameters...succeeded Allocating and attaching to shared memory... and after few minutes stops or suspends

↪ replying to MAREK

Art Kagel — Sun, 15 Nov 2009 22:47:34 — source: IIUG Forums & Mailing Lists

This shows that someone shutdown the Informix engine at 9:27PM on October 28th. It doesn't show any attempt to restart it since. Make certain that you have the correct set of environment variables set (INFORMIXDIR, INFORMIXSERVER, ONCONFIG, and optionally SQLHOSTS or INFORMIXSQLHOSTS). Art Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Sun, Nov 15, 2009 at 4:02 PM, MAREK JASINSKI <blaberus@gmail.com> wrote: > IDS 7.31 > UNIX SCO 5.0.5 > > 20:34:14 Requested shared memory segment size rounded from 8000KB to 8192KB > > Wed Oct 28 20:34:15 2009 > > 20:34:15 Event alarms enabled. ALARMPROG = '/usr/informix/etc/log_full.sh' > 20:34:20 DR: DRAUTO is 0 (Off) > 20:34:20 Requested shared memory segment size rounded from 588KB to 4096KB > 20:34:20 Informix Dynamic Server Version 7.31.UC5 > 20:34:23 Informix Dynamic Server Initialized -- Shared Memory Initialized. > 20:34:23 Physical Recovery Started. > 20:34:23 Physical Recovery Complete: 0 Pages Restored. > 20:34:23 Logical Recovery Started. > 20:34:26 Logical Recovery Complete. > > 0 Committed, 0 Rolled Back, 0 Open, 0 Bad Locks > > 20:34:27 Dataskip is now OFF for all dbspaces > 20:34:27 On-Line Mode > 20:34:27 Checkpoint Completed: duration was 0 seconds. > 21:27:22 Informix Dynamic Server Stopped. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0015173fe650975a09047870adc0

↪ replying to Art Kagel

MAREK — Mon, 16 Nov 2009 22:53:13 — source: IIUG Forums & Mailing Lists

I've found the other online.log file, the newest one: 21:30:17 Exception Recursion while handling: MT_EX_OS, Context: mem 21:30:17 PANIC: Attempting to bring system down 21:30:17 mt_shm_remove: WARNING: may not have removed all/correct segments 21:49:37 Exception Recursion while handling: MT_EX_OS, Context: mem 21:49:37 PANIC: Attempting to bring system down 21:49:37 mt_shm_remove: WARNING: may not have removed all/correct segments 22:04:48 Exception Recursion while handling: MT_EX_OS, Context: mem 22:04:48 PANIC: Attempting to bring system down 22:04:48 mt_shm_remove: WARNING: may not have removed all/correct segments 23:20:52 Exception Recursion while handling: MT_EX_OS, Context: mem 23:20:52 PANIC: Attempting to bring system down 23:20:52 mt_shm_remove: WARNING: may not have removed all/correct segments 23:26:06 Exception Recursion while handling: MT_EX_OS, Context: mem 23:26:06 PANIC: Attempting to bring system down 23:26:06 mt_shm_remove: WARNING: may not have removed all/correct segments 23:27:06 Exception Recursion while handling: MT_EX_OS, Context: mem 23:27:06 PANIC: Attempting to bring system down 23:27:06 mt_shm_remove: WARNING: may not have removed all/correct segments 00:26:53 Exception Recursion while handling: MT_EX_OS, Context: mem 00:26:53 PANIC: Attempting to bring system down 00:26:53 mt_shm_remove: WARNING: may not have removed all/correct segments 00:36:06 Exception Recursion while handling: MT_EX_OS, Context: mem 00:36:06 PANIC: Attempting to bring system down 00:36:06 mt_shm_remove: WARNING: may not have removed all/correct segment

↪ replying to MAREK

Art Kagel — Mon, 16 Nov 2009 23:05:20 — source: IIUG Forums & Mailing Lists

OK! You hit a bug in the engine. If this is a recent and supported version, call IBM tech support and report it and get help. If your engine is an older unsupported version of IDS, upgrade! Either way, for right now, remove the shared memory segments that may have been left around (easiest way: run onmode -ky) and restart the instance with oninit -v Art Art S. Kagel Oninit (www.oninit.com) IIUG Board of Directors (art@iiug.org) Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Oninit, the IIUG, nor any other organization with which I am associated either explicitly or implicitly. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Mon, Nov 16, 2009 at 5:53 PM, MAREK JASINSKI <blaberus@gmail.com> wrote: > I've found the other online.log file, the newest one: > > 21:30:17 Exception Recursion while handling: MT_EX_OS, Context: mem > 21:30:17 PANIC: Attempting to bring system down > 21:30:17 mt_shm_remove: WARNING: may not have removed all/correct segments > > 21:49:37 Exception Recursion while handling: MT_EX_OS, Context: mem > 21:49:37 PANIC: Attempting to bring system down > 21:49:37 mt_shm_remove: WARNING: may not have removed all/correct segments > > 22:04:48 Exception Recursion while handling: MT_EX_OS, Context: mem > 22:04:48 PANIC: Attempting to bring system down > 22:04:48 mt_shm_remove: WARNING: may not have removed all/correct segments > > 23:20:52 Exception Recursion while handling: MT_EX_OS, Context: mem > 23:20:52 PANIC: Attempting to bring system down > 23:20:52 mt_shm_remove: WARNING: may not have removed all/correct segments > > 23:26:06 Exception Recursion while handling: MT_EX_OS, Context: mem > 23:26:06 PANIC: Attempting to bring system down > 23:26:06 mt_shm_remove: WARNING: may not have removed all/correct segments > > 23:27:06 Exception Recursion while handling: MT_EX_OS, Context: mem > 23:27:06 PANIC: Attempting to bring system down > 23:27:06 mt_shm_remove: WARNING: may not have removed all/correct segments > > 00:26:53 Exception Recursion while handling: MT_EX_OS, Context: mem > 00:26:53 PANIC: Attempting to bring system down > 00:26:53 mt_shm_remove: WARNING: may not have removed all/correct segments > > 00:36:06 Exception Recursion while handling: MT_EX_OS, Context: mem > 00:36:06 PANIC: Attempting to bring system down > 00:36:06 mt_shm_remove: WARNING: may not have removed all/correct segment > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --0023545309c0f30d0e0478850a8f

Glossary

shared memory