Operating System - HP-UX
1822158 Members
3485 Online
109640 Solutions
New Discussion юеВ

Shared Memory Not Initialized

 
Laurie_2
Advisor

Shared Memory Not Initialized

Hi All,

Our HP-UX 360 11.0, is not
coming up correctly from a reboot. Unix comes up OK.

But our Informix Engine (7.3) is not coming up.

It says
"shared memory not initialized
for INFORMIXSERVER servername"

We used ipcrm command to
removed the shmid and then
tried rebooting again.

Same thing.

Any thoughts?

We didn't change anything
in the unix and informix
stuff.

Any thoughts,
Laurie
How can you make the world a better place
5 REPLIES 5
Jeff Schussele
Honored Contributor

Re: Shared Memory Not Initialized

Hi Laurie,

If you also use OmniBack check these 2 threads:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xdbbd854994d9d4118fef0090279cd0f9,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x0adaf841489fd4118fef0090279cd0f9,00.html

HTH,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Laurie_2
Advisor

Re: Shared Memory Not Initialized

We don't used OMNIBACK.

Our informix error log:

Network Driver cannot bind a
name to the port

System Error-227

Help
How can you make the world a better place
SHABU KHAN
Trusted Contributor

Re: Shared Memory Not Initialized

Laurie,

What does an

ipcs -a | grep -i informix

show ?

-Shabu
Steven Sim Kok Leong
Honored Contributor

Re: Shared Memory Not Initialized

Hi,

Were there any related error messages flagged in /etc/rc.log after the reboot? Confirm that no changes were made to the kernel parameters. Are there any other programs utilising shared memory segments from the ipcs output?

Apart from the shared memory, you may also like to check on the semaphores as well to be on the safe side.

# ipcs -b -s

Hope this helps. Regards.

Steven Sim Kok Leong
Laurie_2
Advisor

Re: Shared Memory Not Initialized

OK it's fixed now.

This is werid but this is
what we had to do:

/etc/resolv.conf and
removed all the nameserver
IP stuff so we just had this

domain domainname.com

Then in the /etc/nsswwitch.conf
file we had to took comma
out in front of dsn.

hosts: files [NOTFOUND=continue] dns

System reboot fine and the
informix engine came back up.

The error message in informix
log was:

Network driver cannot bind a name to the port System Error
227.

Since since is back up, we
then edited nsswitch.conf
and resolv.conf back to what
they were so email would work.

Strange thing.
Thanks for your help,
Laurie
How can you make the world a better place