Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: A comp.databases.oracle.server FAQ
Howard J. Rogers wrote:
> FM wrote:
>
>
>>Howard J. Rogers wrote: >> >>>FM wrote: >>> >>> >>> >>>>Howard J. Rogers wrote: >>>> >>>> >>>> >>>>>Joel Garry wrote: >>>>> >>>>> >>>>> >>>>> >>>>>>Methinks Howard ought to thank Obnoxio the Clown for that >>>>>>smart-questions link :-) (ref the flamefest "database market share >>>>>>2003" >>>>>>http://groups.google.com/groups?selm=cadl7j%24fec%241 >>>>> >>>>>40news.xmission.com&output=gplain >>>>> >>>>> >>>>>Well, whaddya know... nothing new under the sun, no? I found it whilst >>>>>attempting to find some Suse advice. Maybe I should just read posts here >>>>>more carefully! >>>>> >>>>>Cheers >>>>>HJR >>>>> >>>> >>>>I have something under construction: >>>>http://www.gesinet.it/oracle/oracleonsuse.html >>>>maybe you can find something useful... >>>> >>>>And I'd like a couple of feedback. >>> >>> >>> >>>Haven't had a chance to look at your material yet. >>> >>>10g on Suse 9.1, however, suffers from the same kernel-induced issue as >>>Fedora Core 2 -namely, the need to rename oracle to oracle.bin and create >>>a wrapper script to invoke it. Otherwise, it installs as painlessly as on >>>any other distro. >>> >>>Regards >>>HJR >> >>Have you tried echo "1" > /proc/sys/vm/disable_cap_mlock? >> >>It didn't worked for me but I was on SLES9 and on a x86-64 architecture.
I'm still working on a way to make oracle work with hugetlb.
If you set DISABLE_HUGETLBFS=1 in the user env only it is not passed by
java to the oracle binary. You can see it with the command
cat /proc/<PID>/environ
The java processes show DISABLE_HUGETLBFS=1 but not the oracle one
called by the former...
I was only curios about the disable_cap_mlock. I don't have the chance to try it by myself :(
-- Fabrizio Magni fabrizio.magni_at_mycontinent.com replace mycontinent with europeReceived on Mon Aug 23 2004 - 05:34:08 CDT