Thread: Solaris 8 Problems redux
Thanks to those of you who responded in re my solaris 8 compilation errors.
I was able to compile and use initdb after a couple of hitches. (Had to
rebuild with LD_RUN_PATH set; this is what I get for overlooking the docs.)
My initdb didn't work initially because of an IPC memory create error. I was
able to get around that per the FAQ by throwing the -N option with an arg of
24. So the db works, but I wonder why I had that problem to begin with. If
anyone has a suggestion about what I could have done during Solaris install,
or can do with Solaris admin tools, to fix these errors I'd appreciate it.
This is a toy db at the moment, so it's not important that I've limited the
backend processes, but you never know when you'll be called on to do it for
real.
Thanks,
John
_____________________________
| J. Goodleaf |
| |
/ ) | Technology Coordinator |
/ / | FreeBSD Advocate |
( ( | email ==> |
(((\ \> |/ ) john@goodleaf.net |
(\\\\ \_/ /_________________________|
\ /
\ _/
/ /
/ /
Hi, Generally with Solaris and PostgreSQL (and some other programs like Oracle, SAP, etc) you'll have to change the /etc/system file to include higher limits for IPC. I could have sworn I've seen settings that work for PostgreSQL in the PostgreSQL manual or archives at some stage. If I had a Solaris box available here I'd give them to you now. Try looking at docs.sun.com. A quick search for shmseg gives some info at : http://docs.sun.com:80/ab2/coll.47.11/SYSADV2/@Ab2PageView/34355?DwebQuery=shmseg&oqt=shmseg&Ab2Lang=C&Ab2Enc=iso-8859-1 http://docs.sun.com:80/ab2/coll.707.1/SOLTUNEPARAMREF/@Ab2PageView/6980?DwebQuery=shmseg&oqt=shmseg&Ab2Lang=C&Ab2Enc=iso-8859-1 Make sure you backup the /etc/system file before doing this (you'll need to reboot for this to have an effect). Good luck. Regards and best wishes, Justin Clift Database Administrator/Programmer You should be able to so a search on the Net for "J.Goodleaf" wrote: > > Thanks to those of you who responded in re my solaris 8 compilation errors. > I was able to compile and use initdb after a couple of hitches. (Had to > rebuild with LD_RUN_PATH set; this is what I get for overlooking the docs.) > > My initdb didn't work initially because of an IPC memory create error. I was > able to get around that per the FAQ by throwing the -N option with an arg of > 24. So the db works, but I wonder why I had that problem to begin with. If > anyone has a suggestion about what I could have done during Solaris install, > or can do with Solaris admin tools, to fix these errors I'd appreciate it. > This is a toy db at the moment, so it's not important that I've limited the > backend processes, but you never know when you'll be called on to do it for > real. > Thanks, > John > _____________________________ > | J. Goodleaf | > | | > / ) | Technology Coordinator | > / / | FreeBSD Advocate | > ( ( | email ==> | > (((\ \> |/ ) john@goodleaf.net | > (\\\\ \_/ /_________________________| > \ / > \ _/ > / / > / /
On Wed, 7 Feb 2001, Justin Clift wrote:
> Generally with Solaris and PostgreSQL (and some other programs like
> Oracle, SAP, etc) you'll have to change the /etc/system file to include
> higher limits for IPC. I could have sworn I've seen settings that work
> for PostgreSQL in the PostgreSQL manual or archives at some stage.
From .../postgresql-7.0.3/doc/FAQ_Solaris (from the postgresql source
distribution):
1.3) Why am I getting "IpcMemoryCreate" errors when I try
to run the postmaster?
(See also 3.4 in the main FAQ file)
Under Solaris 2.6 and probably others, the default shared memory
maximum segment size kernel parameter is set too low. The solution
is to put something like the following line into /etc/system and
reboot the system.
set shmsys:shminfo_shmmax=0x7fffffff
Excellent info regarding shared memory under Solaris can be found here:
http://www.sunworld.com/swol-09-1997/swol-09-insidesolaris.html
--
Tod McQuillin