Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

initializing shared memory

0 views
Skip to first unread message

Gene Terry Sanford

unread,
Sep 17, 1996, 3:00:00 AM9/17/96
to

We are runnning informix 4.1 on SCO OpenSever 5.02.
When we run tbinit to initialize shared memory we get
the following error:

tbinit: shmat[EINVAL][22]: shared memory base address
illegal using 0x80480000, needs 0x80000000
tbinit: fatal error in shared memory creation.

Our tbconfig file has SHMBASE = 0x80400000
Anyone have any idea what the problem is. It sounds like the
shared memory base address for SCO needs to be changed.

Terry Sanford

DSA-W

unread,
Sep 18, 1996, 3:00:00 AM9/18/96
to


> Gene Terry Sanford <tsan...@csti-md.com> schrieb im Beitrag
<323F15...@csti-md.com>...

Try SHMBASE=0x0 in your tbconfig file. That will work.

Bye, Thomas Muth

Rajiv Jhaveri

unread,
Sep 18, 1996, 3:00:00 AM9/18/96
to

} From: Gene Terry Sanford <tsan...@csti-md.com>
} Subject: initializing shared memory

}
} We are runnning informix 4.1 on SCO OpenSever 5.02.
} When we run tbinit to initialize shared memory we get
} the following error:
}
} tbinit: shmat[EINVAL][22]: shared memory base address
} illegal using 0x80480000, needs 0x80000000
} tbinit: fatal error in shared memory creation.
}
} Our tbconfig file has SHMBASE = 0x80400000
} Anyone have any idea what the problem is. It sounds like the
} shared memory base address for SCO needs to be changed.
}
} Terry Sanford
}
}

Terry,

Try checking the $INFORMIXDIR/release/ONLINE* files, may be it will shed
more light on what to set SHMBASE to.


--
Rajiv Jhaveri
DBA

( raj...@qsun.ho.att.com)

Mark D. Stock

unread,
Sep 18, 1996, 3:00:00 AM9/18/96
to

> Gene Terry Sanford <tsan...@csti-md.com> wrote:
>
> We are runnning informix 4.1 on SCO OpenSever 5.02.
> When we run tbinit to initialize shared memory we get
> the following error:
>
> tbinit: shmat[EINVAL][22]: shared memory base address
> illegal using 0x80480000, needs 0x80000000
> tbinit: fatal error in shared memory creation.
>
> Our tbconfig file has SHMBASE = 0x80400000
> Anyone have any idea what the problem is. It sounds like the
> shared memory base address for SCO needs to be changed.

This message on SCO generally refers to the kernal parameter SHMMAX.
This should be a multiple of 2Mb, eg. 2097152, 4194304, etc.

Hope that helps,
--

Mark.

+-------------------------------------------------------------------------+
|Mark D. Stock - The West Solutions Group http://www.west.co.za |
| |
|mailto:ma...@west.co.za +------------------------------------------------+
|Tel: +27 11 803 2151 |If it doesn't work... force it! |
|Fax: +27 11 803 2189 |If it breaks... it needed replacing anyway! |
|Cell: +27 83 250 2325 |Well, that's how I code anyway! |
+------------------------+------------------------------------------------+

Nils Myklebust

unread,
Sep 20, 1996, 3:00:00 AM9/20/96
to

Gene Terry Sanford <tsan...@csti-md.com> wrote:

:We are runnning informix 4.1 on SCO OpenSever 5.02.
:When we run tbinit to initialize shared memory we get
:the following error:

: tbinit: shmat[EINVAL][22]: shared memory base address
: illegal using 0x80480000, needs 0x80000000
: tbinit: fatal error in shared memory creation.

:Our tbconfig file has SHMBASE = 0x80400000
:Anyone have any idea what the problem is. It sounds like the
:shared memory base address for SCO needs to be changed.

Informix 4.1 on SCO 5.0.2 is a non supported combination, and there
where many changes from 3.2.4.2 to 5.0.2 of SCO. I once tried out
Informix 7.10.UC1 for SCO 3.2.4.2 on 5.0.2 without any luck.
Your only serious option is to upgrade to a supported version of
Informix. Sometimes non supported stuff runs, but with OnLine I
wouldn't bet on that. (With SE until ver. 5.x we have had great
success in runing on non supported OSes like an Interactive Unix
version still runing fine on different versions of SCO.)

Otherwise we are using SHMBASE = 0x0 on 7.10.UC1 on SCO 3.2.4.2
I don't have access to the 5.0.2 machine right now, so I am not shure
what it is there, but my guess is the same adress.
I have no idea whether this would work for Informix 4.1, and even if
it does you might find many other things that doesn't work.


Nils.My...@idg.no <- New E-mail adress
NM Data AS, P.O.Box 9090 Gronland, N-0133 Oslo, Norway
My opinions are those of my company


Malcolm Weallans

unread,
Sep 22, 1996, 3:00:00 AM9/22/96
to

> Gene Terry Sanford <tsan...@csti-md.com> wrote:
>
> :We are runnning informix 4.1 on SCO OpenSever 5.02.
> :When we run tbinit to initialize shared memory we get
> :the following error:
>
> : tbinit: shmat[EINVAL][22]: shared memory base address
> : illegal using 0x80480000, needs 0x80000000
> : tbinit: fatal error in shared memory creation.
>
> :Our tbconfig file has SHMBASE = 0x80400000
> :Anyone have any idea what the problem is. It sounds like the
> :shared memory base address for SCO needs to be changed.
Have you tried modifying SHMBASE to Ox80000000?

I have installed a number of SCO UNIX systems at different levels and
found that to be necessary. But don't ask me why?


Malcolm Weallans
Online Database Consultancy
Phone 01628-72154
Fax 01628-37463
CIX - onlinedbc

David Williams

unread,
Sep 23, 1996, 3:00:00 AM9/23/96
to

In article <Dy5no...@cix.compulink.co.uk>, "\"Malcolm Weallans\""
<onli...@cix.compulink.co.uk> writes

It is the address that each VP uses to attach the first segment of
shared memory to it's own virtual address space. That is the address to
which it maps the first segment of shared memory. This needs to be set
such that is does not collide with

a) Text segments which store code.
b) Data segments which store static/global segments
c) The stack segment (which can grow with the stack as nested function
are called).
d) Other data segments where the heap is stored which grow as memory
is malloc'ed.

Different UNIX's map a)-d) at different address and so different
SHMBASE's are needed to avoid collisions of memory segments.

Note some UNIX's support a value of 0 which means the UNIX kernel will
choose the correct value automatically. Clearly SCO is not one of
those.

--
David Williams

Malcolm Weallans

unread,
Sep 26, 1996, 3:00:00 AM9/26/96
to
I would point out that the user is using 4.1 which does not have VPs. My
answer still stands.
Sorry David.

David Williams

unread,
Sep 26, 1996, 3:00:00 AM9/26/96
to

In article <DyCqt...@cix.compulink.co.uk>, "\"Malcolm Weallans\""

:%s/VP/sqlturbo/g (Subsitute sqlturbo for VP)


--
David Williams

Stefan Weideneder

unread,
Sep 28, 1996, 3:00:00 AM9/28/96
to

Malcolm Weallans wrote:
>
> > Gene Terry Sanford <tsan...@csti-md.com> wrote:
> >
> > :We are runnning informix 4.1 on SCO OpenSever 5.02.
> > :When we run tbinit to initialize shared memory we get
> > :the following error:
> >
> > : tbinit: shmat[EINVAL][22]: shared memory base address
> > : illegal using 0x80480000, needs 0x80000000
> > : tbinit: fatal error in shared memory creation.
> >
> > :Our tbconfig file has SHMBASE = 0x80400000
> > :Anyone have any idea what the problem is. It sounds like the
> > :shared memory base address for SCO needs to be changed.
> Have you tried modifying SHMBASE to Ox80000000?
>
> I have installed a number of SCO UNIX systems at different levels and
> found that to be necessary. But don't ask me why?
>
> Malcolm Weallans
> Online Database Consultancy
> Phone 01628-72154
> Fax 01628-37463
> CIX - onlinedbc

Am I the last one ?

Years ago we had exactly the same problem. Now I looked at the
default configuration file and saw that the default value is
really 0x80400000. But I have another version running with the
SHMBASE value of 0x0.

Well, the solution to the problems years ago was "never trust
the error messages of Informix". I think you have a mismatch
in your kernel configuration. Make sure that your kernel
parameter SHMMAX is at least the value of your Resident Shared
Memory Segment. If SHMMAX is lower than the size of the segment
that Informix needs, than Informix will allocate a new segment,
but the chaining of segments does not work with SCO and would
result in the mentioned error message.

Try this, if the setting of SHMBASE to 0x80000000 would result
in an error message like


: tbinit: shmat[EINVAL][22]: shared memory base address

> > : illegal using 0x80000000, needs 0x80e10000


> > : tbinit: fatal error in shared memory creation.
> >

Whenever I tried it with a new address, Informix suggested a new
one, until I relinked the kernel.

Good luck


Stefan

ste...@www.weideneder.de

0 new messages