Configure Kernel Parameters on Solaris10 for oracle10g

Hi all:
Before install oracle,we need configure Kernel Parameters in /etc/systme,such as shmsys:shminfo_shmmax,but accroding solaris document:Solaris Tunable Parameters Reference Manual,they have removed some parameters used by oracle,such as semsys:seminfo_semvmx.I'm confused by that manual,if i still change this params,the ORA-03113 error will appear when i create database.Can anyone help me about this?Thank you for Your attations!

Hi,
Try out this thread
Re: Installing OCS 10g R1 on Solaris 10
Bye

Similar Messages

Calculating Kernel parameters for Oracle 11g R2 db on solaris 10u9

Hi Everyone,
I have query regarding calculating the kernel parameters for deploying oracle 11g R2 db on solaris 10 v 5.10 update 09 machine , we have Ram size of 64gb.
My question is how to calculate shared memory ,shared memory identifiers,semaphores, semaphores identiifiers for creating resource control for the project(user.oracle).
And how to fine out the available semphore values allocated in system..
Thanks in Advance.
Edited by: 898979 on Dec 15, 2011 10:24 PM

Hi;
For those setting mention in installation guide which is already shared previous post.
I suggest also see:
Oracle Database on Unix AIX,HP-UX,Linux,Mac OS X,Solaris,Tru64 Unix Operating Systems Installation and Configuration Requirements Quick Reference (8.0.5 to 11.2) [ID 169706.1]
Regard
Helios

Request for any Best Practice document for configuring Service Parameters on CUCM 9.1.1

Hi Team,
Could you please send if you have any Best Practice document for configuring Service Parameters on CUCM 9.1.1. That would really help.
Thanks,
Guru

Hi
There's no 'best practice' as such, but there are a few that I think should be default:
Enabling CDR, On-Hook Pickup, CFwdAll Override... but really the settings are specific to the requirements of the deployment.
Aaron

Regarding configuration of "Parameters for determining the basic dates"

Hi All,
Can anyone give inputs in which scenario we need to use the configuration "Parameters for determining the basic dates".
1)Do we have any restrictions for usage of above IMG configuration, 2) any pre-requisites to use the configuration of "Parameters for determining the basic dates" and 3)does configuration of this task is having any integration with any other modules, if yes what is the point of integration with other modules.
Thanks in advance.

Dear Aditya,
Parameters for determining the basic dates in production order are used to calculate the Basic Start date & End date of Production order. It Determines if and how the basic dates or the dependent requirements dates are adjusted during lead time scheduling. You can customize this in OPU3 for planned order & OPU5 for Production Order.
There are the following possibilities:
1.The basic dates are adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
2.The basic dates are not adjusted and the dependent requirements are scheduled for the start dates of the relevant operations.
3.The basic dates are adjusted and the dependent requirements are scheduled for the order basic start date.
4.The basic dates are not adjusted and the dependent requirements are scheduled for the order basic start date.
1)Do we have any restrictions for usage of above IMG configuration
For scheduling this has to be. If you want that start date should be calculated based on Inhouse production time & not on routing select opetion 2 or 4
2) any pre-requisites to use the configuration of "Parameters for determining the basic dates"
Not as such
3)does configuration of this task is having any integration with any other modules
Not directly but with MM to determine dependent requirement Proposal.
Regards
ABhijit Gautam.

Kernel parameters for ebs 11.5.10 and db 10.2.0.4

HI,
is there any doc describing the kernel parameters(settings) in order to install the 11.5.10 EBS System on Linux Enterprise Edition(v. 4.6).... something like the Metalink note: 265121.1(Requirements for Installing Oracle9i R2 (9.2.0) on RHEL3)...
Thank you,
Sim

Sim,
Please refer to:
Note: 294932.1 - Recommendations to Install Oracle Applications 11i
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=294932.1
Note: 316806.1 - Oracle Applications Installation Update Notes, Release 11i (11.5.10.2)
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=316806.1

Problems Installing Oracle 10GR2 & kernel parameters

Hi there,
I'm trying to install Oracle 10G on a new Solaris10 machine. After extensivley reading the oracle install guide and proceeding my install failed with an out of memory error.
Ive read the posts regarding many similar problems and to set the kernel parameters in /etc/system. My question for the experts is:
1). Is there a problem with the oracle install scripts and it not recognising the new features in Solaris?
2). Is there a more deep-rooted problem with oracle and solaris?
ANY help/advice would be much appreciated. There are hundreds of posts like this on the web and surely someone must have the answer? I mean surely oracle did not hack /etc/system to get their install to work did they??
Nibs

It IS a terrible experince to install oracle 10g on solaris 10. Tell us your system configuration and your installation step. For I have installed three times and each time a different problem. Suggest you go to oracle forum to get more help.

Tuxedo configuration global parameters

Hi
I have tuxedo configuration related question which I am unable to understand.
There are two parts to the question:
1. We have an already running tuxedo configuration which is working with certain values of global parameters. My concern is that if we have to increase the number of servers that are booted up by the tuxedo configuration, which global parameters will be required to be modified?
2. Since our deployment is on Windows 2003 server based, there are also parameters defined under the "BEA Tuxedo" item of control panel applet. My question is that if we increase the number of tuxedo servers booted in one of tuxedo servers, do we have to change the value in this control panel item as well. How are the values in this control panel item calculated?
We are using tuxedo 8.1 version.
Thanks

Hi Asim,
Without monitoring your system, it is impossible to say whether any configuration changes are necessary. The key thing to keep in mind is that Tuxedo uses IPC resources for all inter-process communication. That includes the request and the reply for a tpcall(). The best thing to do when deciding whether you need to make changes is examine the current usage of the IPC queue resources (assuming that is what you are concerned about, as there are other System V IPC resources such as shared memory, locks, etc., that may come into play). The ipcs command is the best tool for doing this as it will tell you how much of each queue is being used. If your current configuration isn't close to the limits under load, then you are probably OK adding additional servers. As for other IPC resources such as shared memory segments, locks, etc., using the tmloadcf -c option is helpful in that it will tell you the minimum IPC resources Tuxedo needs in order to boot the application. Generally it is a good idea to configure substantially more than that as the cost in real resources is small, and it saves you from having to change the IPC resource configuration all the time. In Windows, the IPC resources are controlled by the Tuxedo entry in the Control Panel. In other operating systems, they may be controlled by kernel parameters in /etc/sysconfig or other places. Check out http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/ada/adtun.html#wp1031892 for more information in IPC resource usage in Tuxedo.
Definitely check out http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/ada/admon.html to understand how to monitor your Tuxedo application. Also check out the Tuxedo System and Application Monitor add-one product for more information on monitoring your Tuxedo applications. Check out http://download.oracle.com/docs/cd/E18050_01/tuxedo/docs11gr1/ada/adtun.html for more information on tuning a Tuxedo application.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Checking Linux Kernel Parameters before installation

Hi Everyone.
I am planning to install Oracle 10g XE and I know that with the installation kernel parameters will change. As I don`t know what will happen that in relation to the system, I would like to check default kernel parameters. I know it`s a Linux question but it`s indirectly related with the installation. So... I want to save that information if something goes wrong.
Can you help me?

Hi.
Thanks for the clue.
I did:
less /etc/sysctl.conf
and the output is:
# Kernel sysctl configuration file for Red Hat Linux
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 0
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
# Controls the use of TCP syncookies
net.ipv4.tcp_syncookies = 1
I don`t recognize here any of the kernel parameters listed in the installation guide for Oracle 10g XE. http://www.oracle.com/technology/software/products/database/xe/files/install.102/b25144/toc.htm (2.1.3 Server Component Kernel Parameter Requirements)
what do you mean with backup? Just copy&paste the output? If not I do I perform backup?
Can you help me?
thanks,
Kind Regards

[SOLVED]Systemd: removing quiet in kernel parameters

Hello
I am configuring systemd according to systemd's page in the Archlinux's wiki:
https://wiki.archlinux.org/index.php/Systemd
I have a doubt about the first point in the suplementary information section. This one says:
If you have quiet in your kernel parameters, you might want to remove it for your first couple of systemd boots, to assist with identifying any issues during boot
Does it mean I must remove the word quiet in the section GRUB_CMDLINE_LINUX_DEFAULT, in the file /etc/default/grub?
Thanks in advance.
Last edited by zuargo (2013-04-19 01:21:37)

wingsuit wrote:
hobarrera wrote:Yes, that's what it's refering to. You should check the output of the boot process the first couple of times to fix any warnings/errors. Once everything is running smoothly, you can add the "quite" parameter back if you like a silent boot.
quiet* right?
Yes, "quiet", that was just a typo.

Understanding mkinitcpio, kernel parameters, and hooks.

I have a fairly complex setup involving dm-crypt volumes being unlocked pre-boot, so I'm somewhat familiar with mkinitcpio.conf and grub.cfg. However, I still have a burning question: are kernel parameters actually interpreted by the kernel? For example, the ip= parameter is included in the kernel documentation, leading me to believe that the kernel interprets this parameter and acts upon it during boot. On the other hand, the cryptdevice= parameter appears to be specific to the mkinitcpio encrypt hook (does not appear in kernel documentation) which interprets it and runs cryptsetup in early userspace. In this case, are kernel parameters simply being used as a vehicle in order to pass information from the boot loader to early userspace? If so, why couldn't this be done by including a configuration file directly in the initcpio, which could be parsed at boot-time? Such a configuration file seems like a superior means of passing information to early userspace, as different files could be used for different hooks, they could be of different formats (i.e. contain linebreaks), and would not be subject to the maximum kernel command line length.
In fact, it looks like some hooks already do this. For example, the sd-encrypt hook includes a file /etc/crypttab file directly in the initcpio image. Why would other hooks use kernel parameters when the early userspace filesystem is available for use?
I'm primarily asking just for educational purposes. Explanations are appreciated.

Spider.007 wrote:I think the ip-parameter is coincidentally the same as the net-module uses.
I found this in the mkinitcpio-nfs-utils ipconfig README:
These [parameters] (along with the ugliness of the long form) are present for compatibility with the in-kernel ipconfig code from 2.4 and earlier kernels.
which supports the hypothesis that the kernel parameter is left over from a time when network configurations were done in kernel-space. The syntax remained the same in the initcpio hook to maintain backwards comparability with older bootloader configurations. At least that's the impression I'm under.
Spider.007 wrote:The kernel is still responsible for mounting the rootfs; what has changed is that most distro's switched to initcpio's for reasons that are repeated on the wiki: ...
Yes, I believe the kernel itself performs the mount(2) which overwrites the / mountpoint with the real root filesystem after it is available. (But for all I know, a hook could be performing a mount(8) instead of the kernel!) What I meant was that the kernel no longer is responsible for all of the initializations necessary for the real root filesystem to become available (so the kernel can mount it), hence the need for initrd/initramfs/initcpio. Take dropbear_initrd_encrypt for example. Dropbear is a userspace SSH server. Without early userspace, an SSH server would have to be embedded in the kernel just for the 0.01% of users out there who need to be able to unlock volumes remotely. Early userspace allows complex systems like this (and other very different ones) to be configured without the need for patching the kernel.
I assume that some low-level kernel parameters (maxcpus= for example) are still relevant solely to the kernel, as things like SMP process scheduling can't easily be implemented in userspace.
Am I getting this right so far?
Last edited by EscapedNull (2015-01-13 19:40:50)

Kernel parameters problem (512 mb RAM)

Hi,
I've installed Oracle on RedHat 5.2 (2.0.36) on a machine with
512 mb memory.
First I've recompiled the kernel how Oracle says and basing in
some documents (like
http://jordan.fortwayne.com/oracle/oralinux.html). Of course I've
saved a copy of the old kernel. The linux was ok, the command
ipcs -l shows the new values of the kernel parameters, but Oracle
didn't start. I've restored the copy of the kernel, the ipcs -l
shows the old values and now Oracle is running, with a SGA of
almost 300 mb.
Is there some problem in that? Will the machine loose performance
because the miminum values of the kernel parameters?
Best regards,
Ari
null

Ari Arantes (guest) wrote:
: Hi,
: I've installed Oracle on RedHat 5.2 (2.0.36) on a machine with
: 512 mb memory.
: First I've recompiled the kernel how Oracle says and basing in
: some documents (like
: http://jordan.fortwayne.com/oracle/oralinux.html). Of course
I've
: saved a copy of the old kernel. The linux was ok, the command
: ipcs -l shows the new values of the kernel parameters, but
Oracle
: didn't start. I've restored the copy of the kernel, the ipcs -
l
: shows the old values and now Oracle is running, with a SGA of
: almost 300 mb.
: Is there some problem in that? Will the machine loose
performance
: because the miminum values of the kernel parameters?
: Best regards,
: Ari
I have a setup similar to yours (384 MB instead of 512 MB),
and I spent some time looking at the parameters.
You CANNOT use the value for SHMMAX from the Oracle manual!
As it says at http://jordan.fortwayne.com/oracle/oralinux.html
"Should you decided to change these parameters, if you set
the SHMMAX to what Oracle says, you are telling the system
to allow a shared memory segment to grow as large as 4 Gigs.
Many users have reported problems setting the value this
high."
Sounds like you are another one of those users, eh?
If you read on down, the guy who wrote that web page never
used over 128 MB for SHMMAX. I'd take a strong hint from that.
=====
Oracle wants you to use 4GB-1 as the SHMMAX value. That
equates to (1<<32)-1. As we shall see, that is not allowed
without "breaking the rules" for the i386 architecture.
If you carefully read through the header file, you will find
out that the **actual maximum value** for SHMMAX is 256 MB.
You can tell this two ways. Take a look at the file at:
/usr/src/linux/include/asm/shmparam.h
Near the top of the file is:
/* address range for shared memory attaches if
no address passed to shmat() */
#define SHM_RANGE_START 0x50000000
#define SHM_RANGE_END 0x60000000
Note that the above is 256 MB (0x10000000), or (1<<28). This
is one potential source of trouble. I don't know if some other
files someplace else in the kernel specify uses for address
ranges adjacent to the above range, which I take to be the
"practical maximum" without redefining that range. Personally,
I wouldn't want to mess with the above unless I **really**
knew what I was doing (and I'll be the first to admit I don't).
=====
Farther down you will see some more lines (not together)
that look like this:
#define SHMID_BITS 7
#define SHMIDX_BITS 15
* SHMID_BITS + SHMIDX_BITS must be <= 24 on the i386 and
* SHMMAX <= (PAGE_SIZE << SHMIDX_BITS).
#define SHMMAX 0x2000000 /* max shared seg
size (bytes) */
Now, 7 + 15 is 22, so you could go up a couple of bits if you
had to. To avoid making the table any larger, I would suggest:
#define SHMIDX_BITS 17
But, 17 turns out to produce a result larger than the "practical
maximum" (256 MB) above. To see why takes a little more
explaining.
And if you don't change this at all, then the maximum possible
value for SHMMAX is 4096 [the PAGE_SIZE) << 15 [_SHM_IDX_BITS],
or rather (1<<27).
Now, that is exactly half of the (1<<28) "practical maximum" I
mentioned above.
So, if you always want the maximum amount of shared memory,
then change the definition of SHMMAX to the following:
#define SHMMAX (PAGE_SIZE<<_SHM_IDX_BITS) /* max shared seg
size (bytes) */
That gives you 128 MB in and of itself (as compared with 32 MB
as Red Hat 5.2 is delivered).
If you want the full 256 MB that is allowed for in the memory
map, then you need to also change:
#define SHMIDX_BITS 16
The above value is **exactly** what is recommended on the web
page you were following (above).
If you want to keep going up, you will need to change the
memory space allocated for shared memory as defined by
SHM_RANGE_START and SHM_RANGE_END, something I advise against.
=====
Even on a machine with 512 MB of "real" memory, I find it hard
to believe that there would be any substantial benefit to
having a maximum shared memory space greater than 256 MB. The
reason is that Oracle can use multiple shared memory spaces.
It requires a minimum of ten (10), according to the installation
manual, but the Red Hat 5.2 distribution supplies SHMMNI (128)
of them. That will allow each Oracle process to have a total
of up to 32 GB of shared memory (128 times 256 MB) and all it
asks for is 40 GB (10 times 4 GB), so it has plenty, IMHO.
=====
Let me say a few more words about the web page you were using
for configuration advice. That person actually **reduced** the
amount of shared memory segments by specifying **lower values**
for SHMMNI and SHMSEG (not to mention the semaphores).
I'd **STRONGLY** recommend **NOT CHANGING** those other values!
Its my understanding that Oracle can make up for the smaller
maximum shared memory segment size by using more shared memory
segments. So, if you reduce those, you are essentially shooting
yourself in the foot by taking away what you are giving with
increasing the maximum segment size.
=====
Good luck, and may this farce be with you!
null

Unable to set kernel parameters using Reource Control

HI,
I'm trying to install DB2 8.2 on solaris 10.the problem i'm encountering in installation is unable to set MSGMAX and MSGMNB kernel parameters. I tried setting the new replacement parameter process.max-msq-qbytes through projects->Resource Control from the management console.but still uinable to set the parameters.
Can anyone help me in setting the above kernel parameters.
Its not possible to set it thru /etc/system.
thanx
guru

I finally had some time to find the actual syntax for tuning process.max-msq-qbytes and process.max-msg-messages. prctl will change those paramaters for an existing process.
As a proof of concept I changed process.max-msg-messages to a 64k. process 2221 is my shell.
prctl -n process.max-msg-messages -r -v 64k 2221
bash-3.00# prctl 2221
process: 2221: -csh
NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
process.max-port-events
        privileged      65.5K       -   deny                                 -
        system          2.15G     max   deny                                 -
process.max-msg-messages
        privileged      64.0K       -   deny                                 -
        system          4.29G     max   deny                                 -
process.max-msg-qbytes
        privileged      64.0KB      -   deny                                 -
        system          4.00GB    max   deny                                 -And now to make this persist across reboots...
So long as I'm experimenting, I'll use projadd and add a new project which just includes me and not the rest of the users in the group staff.
bash-3.00# projadd -p 115 -U testuser \
-K "process.max-msg-messages=(priv,64K,deny)" \
-K "process.max-msg-qbytes=(priv,64K,deny)" \
user.me This creates the following /etc/project:
(note the last line is all on one line in the real file minus the \.)
placer% cat /etc/project
system:0::::
user.root:1::::
noproject:2::::
default:3::::
group.staff:10::::
user.me:115::testme::\
process.max-msg-messages=(priv,64000,deny);process.max-msg-qbytes=(priv,65536,deny)After a reboot I checked the values by loging in under my user and running prctl.
placer% prctl $$
process: 419: -csh
NAME    PRIVILEGE       VALUE    FLAG   ACTION                       RECIPIENT
process.max-port-events
        privileged      65.5K       -   deny                                 -
        system          2.15G     max   deny                                 -
process.max-msg-messages
        privileged      64.0K       -   deny                                 -
        system          4.29G     max   deny                                 -
process.max-msg-qbytes
        privileged      64.0KB      -   deny                                 -
        system          4.00GB    max   deny                                 -
process.max-sem-ops
        privileged        512       -   deny                                 -
        system          2.15G     max   deny                                 -
...Solaris 10 has different tunables and default values from 8 and 9. It's default tunables should be good for most applications per a given system's hardware. There are some great blog articles, and discussions on opensolaris.org and blogs.sun.com on tuning that explain the intent of tuning and why we shouldn't have to tune.
Cheers,
~~sa

IOMMU explanation of kernel parameters

Hello!
I've set up an HTPC with an AMD A4-5300 CPU, A75 (Hudson-D3) chipset and a PCIe sound card (Asus Xonar DX). Whenever I tried to get a sound out of it (e.g. aplay blubb.wav) I only got dozens of these messages in the kernel log:
[ 46.215678] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.0 domain=0x0000 address=0x0000000000100000 flags=0x0050]
The messages appeared only on the first aplay command. When the program finished and I ran it again, I got no additional messages but sadly also no sound.
Spending two evenings on this problem with google I found out it might be some trouble with IOMMU features of the processor or mainboard. So after trying out several of the options, I found iommu=soft in the kernel parameters got the sound to work fine. I have the possible options from here: https://www.kernel.org/doc/Documentatio … ptions.txt
But I don't really understand what's the matter with this IOMMU thing. It seems like a memory management for I/O Components and seems related to DMA access. But what does the IOMMU do? Which side effects come with these options? I understand the "soft" option in that way, that some features present in hardware are now managed in software. "can be used to prevent the of an available hardware IOMMU" sounds even worse since the option might completely disable the hardware feature. But is this really bad? I mean with the option I finally have good quality audio output but for what price? Can I expect disadvantages from this setting? Since I'm not really into all this kernel and hardware stuff, this all seems so confusing. Or is it possible that the error causing the above message has a totally different source and it's just luck that the option kind of worked around it?
Can anyone here maybe explain even a little bit about the IOMMU and what might have caused these problems?
I opened a thread in the multimedia section here where I asked for help to get audio output but no one replied. So I think the people living over there are also not familiar with the topic. And since I found kind of a workaround which is hardware related I hope it is ok to open this other thread to maybe get some explanation about what I have really done there...

Thanks for the detailed explanation!
But isn't the GART something Video Card related? Or is it that what you mean with "abusing" the GART?
So when I set "iommu=soft" the IOMMU basically gets disabled? Quoting the file about the boot options, it says:
3. <arch/x86_64/kernel/pci-swiotlb.c> : Software IOMMU implementation. Used
e.g. if there is no hardware IOMMU in the system and it is need because
you have >3GB memory or told the kernel to us it (iommu=soft))
Kernel boot message: "PCI-DMA: Using software bounce buffering
for IO (SWIOTLB)"
What I don't fully understand... Is the IOMMU actually a CPU feature or is it on the mainboard's hand? For what I read, the A-Processors from AMD are IOMMU supported, so my setup should work with it. Or could it be my mainboard not having correct support for it? (MSI FM2-A75IA-E53)
For testing, I disabled the IOMMU switch in GRUB, dmesg shows the kernel already automatically chooses software buffering. ("[ 0.654086] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)") but then I get those tons of AMD-Vi messages. When I set the IOMMU to force software buffering, I have not a single problem. The entry in dmesg also tells it is using software bounce buffering. But shouldn't there be no difference if the kernel chooses the software option or if I force it to do so?

Kernel parameters -maximum threads per process

How can we change the kernel parameters also how can we increase the maximum number of threads allowed .
How can we increase maimum perocess per used id .

There is no kernel parameter limiting the maximum
number of threads allowed. If you are talking about
user level threads, you will run into virtual address
space limitations at about 3000 for a process
assuming 32-bit address space and default
stack size of 1M per thread, and assuming you are
not using the alternate thread library (see threads(3thr))
or Solaris 9. If you need more than this many
threads at the same time, I suspect you are doing something
incorrectly. Otherwise, try using a smaller stack size
per thread. If you are running on Solaris 9, or using
the alternate thread library, both give you a 1x1
thread model, i.e., each user thread has a corresponding
kernel entity (lwp). In this case, you will cause
your machine to hang by eating up all available
space for lwp's. In either case, the question should be:
"how do I limit the number of threads per process?", since
there is currently no limitation other than space.
In Solaris 9, you can use resource management to
limit the number of lwp's (and therefore user threads)
per process.

Kernel Parameters on Red Hat Linux

The installation instructions require us to set cetain kernel
parameters, such as SHMMAX, SHMSEG, SEMMNS, and so on.
Does anyone know how this is done for Red Hat Linux? I have
been hunting around the documentation and public domain web-
sites for a couple of weeks now and I haven't found any
reference to how to set these parameters.
Eternally grateful for any insights...
Cheers!
Stuart Housden
null

I had problems with 8i and 32Meg of SHMMAX (sometimes, when I
published an EJB, Oracle crashed). I didn't recompiled the
kernel, only did
echo 134217728 > /proc/sys/kernel/shmmax.
This limited the maximum shared memory to 128Meg (I installed
with JavaVM enabled), and I my problems got away.
Robson.
Anwar (guest) wrote:
: Stuart Housden (guest) wrote:
: : The installation instructions require us to set cetain kernel
: : parameters, such as SHMMAX, SHMSEG, SEMMNS, and so on.
: : Does anyone know how this is done for Red Hat Linux? I have
: : been hunting around the documentation and public domain web-
: : sites for a couple of weeks now and I haven't found any
: : reference to how to set these parameters.
: : Eternally grateful for any insights...
: : Cheers!
: : Stuart Housden
: This question was replied to multiple times on the list before,
: but here goes. Check out:
: http://jordan.fortwayne.com/oracle
: Basically, you have to edit the kernel header files, and
: recompile the kernel. Read the Kernel-HOWTO too.
: Anwar.
null

Configure Kernel Parameters on Solaris10 for oracle10g

Similar Messages

Maybe you are looking for