Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Help: 10g on Fedora Core 2, ORA-27125
Howard J. Rogers wrote:
> On 7 Aug 2004 15:33:43 -0700, David Fitzjarrell <fitzjarrell_at_cox.net>
> wrote:
>
>> David Freeman <$d$a$v$i$d$@nospam.davidfreeman.net> wrote in message >> news:<pan.2004.08.07.17.30.25.953782_at_nospam.davidfreeman.net>... >> >>> On Mon, 31 May 2004 19:36:33 -0700, andi wrote: >>> >>> > Hi All, >>> > I installed Oracle 10g (10.1.0.2) on Fedora Core 2 (kernel 2.6.6.x), >>> > RAM: 512 MB swap 1GB. >>> > followed the instructions at www.dizwell.com, the software >>> > installation went smoothly, but then when I tried to create a database >>> > using dbca, there's an error message: ORA-27125 unable to create share >>> > memory segment. >>> > Tried to export DISABLE_HUGETLBFS=1 as suggested at OTN linux forum >>> > with no luck.
>>> Renaming the $ORACLE_HOME/bin/oracle executable to oracle.bin and then >>> creating a script that invokes it and ensures that this variable is >>> utilized: >>> ======================================================= >>> This from http://www.orafaq.com/msgboard/linux/messages/568.htm : >>> ======================================================= >>> cd $ORACLE_HOME/bin >>> >>> mv oracle oracle.bin >>> >>> cat >oracle <<"EOF" >>> #!/bin/bash >>> >>> export DISABLE_HUGETLBFS=1 >>> exec $ORACLE_HOME/bin/oracle.bin $@ >>> EOF >>> >>> chmod +x oracle >>> >>> ========================================================= >>>
>>> >>> I hope this sets you right; please repost to the newsgroup to confirm. >>> >>> Sincerely looking for a job right now, >>> >>> >>> David Freeman >>> http://www.davidfreeman.net/DavidFreemanResume.txtOn Tue, 01 Jun 2004 >>> 21:39:34 +0200, Igor Racic wrote: >>> >> >> Renaming the oracle executable to oracle.bin and writing a wrapper >> script was unnecessary since you could easily place the 'export >> DISABLE_HUGETLBFS=1' code in the .profile or .bash_profile for the >> oracle Linux user account, thus setting it without the workaround you >> coded. >> >> David Fitzjarrell
"The execle function also [explicitly] specifies the environment of the executed process [...] The other [exec] functions take the environment for the new process image from the external variable environ in the current process."
So one possible explanation is that the oracle binary is using execle, thus using exec instead in the wrapper script causes the existing environment to be passed along as desired.
As one poster in comp.os.linux.misc stated, "[Unix is] the result of 31 years of tradition, hacking, and stuff that worked in the field. Hence logic was discarded in favor of pragmatism....". And Linux is just the youngest bastard child of all Unices that went before, so what can you expect?
--Mark Bole Received on Sun Aug 08 2004 - 13:29:14 CDT