shared memory not initialized for INFORMIXSERVER
Any idea??????
Have you tried starting the Informix server?
--
Cheers,
Obnoxio The Clown
http://obotheclown.blogspot.com
I will now proceed to pleasure myself with this fish.
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.
Yes, by typing oninit but the same error apperas:
shared memory not initialized for INFORMIXSERVER
my system in UNIX SCO
what is in online.log?
have you tried
oninit -v
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 Software Serial Number
AAC#J638589
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.
>
> "Clive Eisen" <cl...@serendipita.com> wrote in message
> news:mailman.301.12583096...@iiug.org...
>> On 15/11/2009 18:21, blaberus wrote:
>>>
>>> "Obnoxio The Clown"<obn...@serendipita.com> wrote in message
>>> news:mailman.300.12583090...@iiug.org...
>>>> blaberus wrote:
>>>>> When I am trying to start informix server the following massage
>>>>> apears:
>>>>>
>>>>> shared memory not initialized for INFORMIXSERVER
>>>>>
>>>>> Any idea??????
>>>>
>>>> Have you tried starting the Informix server?
>>>>
>>>
>>> Yes, by typing oninit but the same error apperas:
>>>
>>> shared memory not initialized for INFORMIXSERVER
>>>
>>> my system in UNIX SCO
>>
>> what is in online.log?
>>
>> have you tried
>>
>> oninit -v
>
>
>
> 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 Software Serial
> Number AAC#J638589
> 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.
So, back in October, you shut the server down. You've not attempted to
restart it since then?
Or what did you do between 2009-10-28 and 2009-11-15 that would make
things fail?
Basically, it appears that your (archaic) version of IDS is not
attempting to use the online log file you showed us. This suggests that
perhaps someone has changed the environment in ways you don't expect.
--
Jonathan Leffler #include <disclaimer.h>
Email: jlef...@earthlink.net, jlef...@us.ibm.com
Guardian of DBD::Informix v2008.0513 -- http://dbi.perl.org/
publictimestamp.org/ptb/PTB-7641 sha160 2009-11-16 06:00:05
402D3412323B4122B1B4FB4751EB6CD7B4B84466
_______________________________________________
Informix-list mailing list
Inform...@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
touch a new file both as informix and root in the directory for the
online.log file to make sure informix and root can both create new
files in
that directory.
Shut the server down, rename the online.log file to something else and
start the server again, this time start the server with
oninit -vy
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
<da...@smooth1.co.uk> wrote in message
news:0a255640-f005-4909...@a31g2000yqn.googlegroups.com...