10g R2 Install - OS checks failed

[KenEwald]

What is rmem and wmem?

Checking for rmem_default=262144; found rmem_default=65535. Failed <<<<
Checking for rmem_max=262144; found rmem_max=131071. Failed <<<<
Checking for wmem_default=262144; found wmem_default=65535. Failed <<<<
Checking for wmem_max=262144; found wmem_max=131071. Failed <<<<
Check complete. The overall result of this check is: Failed <<<<

[bazza]

Ha I thought! Has Ken not googled this?! So I did it, and could barely find anything.

I got this from alinux tuning guide at http://www.laukas.com/knbase/linux_special/

6. Networking

Enabling and disabling some of the advanced features of TCP: (Usually it is a good idea for these to be enabled)

/proc/sys/net/ipv4/tcp_timestamps
/proc/sys/net/ipv4/tcp_window_scaling
/proc/sys/net/ipv4/tcp_sack

To enable all these features, for example, do the following as root:

echo 1 > /proc/sys/net/ipv4/tcp_timestamps
echo 1 > /proc/sys/net/ipv4/tcp_window_scaling
echo 1 > /proc/sys/net/ipv4/tcp_sack

Tuning the default and maximum window sizes:

/proc/sys/net/core/rmem_default - default receive window
/proc/sys/net/core/rmem_max - maximum receive window
/proc/sys/net/core/wmem_default - default send window
/proc/sys/net/core/wmem_max - maximum send window

/proc/sys/net/ipv4/tcp_rmem - memory reserved for TCP rcv buffers
/proc/sys/net/ipv4/tcp_wmem - memory reserved for TCP snd buffers

The following values would be reasonable for path with a large BDP:

echo 8388608 > /proc/sys/net/core/wmem_max
echo 8388608 > /proc/sys/net/core/rmem_max

Means nothing to me however...

[bazza]

Got a bit more from http://nfs.sourceforge.net/nfs-howto/performance.html:

5.7. Memory Limits on the Input Queue
On 2.2 and 2.4 kernels, the socket input queue, where requests sit while they are currently being processed, has a small default size limit (rmem_default) of 64k. This queue is important for clients with heavy read loads, and servers with heavy write loads. As an example, if you are running 8 instances of nfsd on the server, each will only have 8k to store write requests while it processes them. In addition, the socket output queue - important for clients with heavy write loads and servers with heavy read loads - also has a small default size (wmem_default).

Several published runs of the NFS benchmark SPECsfs97 specify usage of a much higher value for both the read and write value sets, [rw]mem_default and [rw]mem_max. You might consider increasing these values to at least 256k. The read and write limits are set in the proc file system using (for example) the files /proc/sys/net/core/rmem_default and /proc/sys/net/core/rmem_max. The rmem_default value can be increased in three steps; the following method is a bit of a hack but should work and should not cause any problems:

[KenEwald]

Thanks, good info. I ignored the warnings and the install finished without a hitch.

I'm guessing that since 10gR2's ADAM (Automated Diagnostics and Monitoring) is taking paging into consideration for query optimization, maybe there's more focus on memory params.

-Ken

[marist89]

Thanks, good info. I ignored the warnings and the install finished without a hitch.

Yeah, me too. Click, Click, Click, Done. It's almost like Windoz...

[hannah00]

I got the below error when running the Installer:

$Xlib: connection to "test:0.0" refused by server
Xlib: No protocol specified

Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using 'test:0.0' as the value of the DISPLAY variable.
at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
at sun.awt.X11GraphicsEnvironment.(Unknown Source)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(Unknown Source)
at java.awt.Window.init(Unknown Source)
at java.awt.Window.(Unknown Source)
at java.awt.Frame.(Unknown Source)
at oracle.ewt.popup.PopupFrame.(Unknown Source)
at oracle.ewt.lwAWT.BufferedFrame.(Unknown Source)
at oracle.sysman.oio.oioc.OiocOneClickInstaller.(OiocOneClickInstaller.java:378)
at oracle.sysman.oio.oioc.OiocOneClickInstaller.main(OiocOneClickInstaller.java:2091)



I did have my DISPLAY set as follow:

export DISPLAY=test:0.0


Any thoughts???

[marist89]

I got the below error when running the Installer:

$Xlib: connection to "test:0.0" refused by server
Xlib: No protocol specified


I did have my DISPLAY set as follow:

export DISPLAY=test:0.0

Um, like "test" is not a valid hostname? Or "test" is not allowing X connections?

[davey23uk]

but looking at the title it is called 'Quick and Dirty index' how professional