This appendix provides instructions for how to complete configuration tasks manually that Cluster Verification Utility (CVU) and Oracle Universal Installer normally complete during installation. Use this appendix as a guide if you cannot use the fixup script.
This appendix contains the following information:
During installation, you can generate and run the Fixup script to check and set the kernel parameter values required for successful installation of the database. This script updates required kernel packages if necessary to minimum values.
If you cannot use the Fixup scripts, then verify that the kernel parameters shown in the following table are set to values greater than or equal to the minimum value shown. The procedure following the table describes how to verify and set the values manually.
Note:
The kernel parameter values in this section are minimum values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the system. Refer to your operating system documentation for more information about tuning kernel parameters.Note:
If the current value for any parameter is higher than the value listed in this table, then do not change the value of that parameter.
The following kernel parameters are obsolete on HP-UX 11.31. You do not specify values for these parameters:
msgmap
msgseg
If you do not use HFS, then retain the default ninode
value.
To display the current value or formula specified for these kernel parameters, and to change them if necessary:
For HP-UX Itanium:
Enter the following command to start the kcweb
application:
# /usr/sbin/kcweb -F
Check the value or formula specified for each of these parameters and, if necessary, modify that value or formula.
If necessary, refer to the kcweb
online Help for more information about completing this step.
Note:
If you modify the value of a parameter that is not dynamic, then you must restart the system.If you do not use a Fixup script or CVU to set ephemeral ports, then use NDD to ensure that the kernel TCP/IP ephemeral port values are broad enough to provide enough ephemeral ports for the anticipated server workload. Set the port value high enough to avoid reserved ports for any applications you may intend to use.
Use the following commands to check your current range for ephemeral ports:
# /usr/bin/ndd /dev/tcp tcp_largest_anon_port 65535
In the preceding example, tcp_largest_anon_port
is set to the default value.
If necessary, edit the file /etc/rc.config.d/nddconf
and add entries to update the UDP and TCP ephemeral port values. For example:
TRANSPORT_NAME[0]=tcp NDD_NAME[0]=tcp_largest_anon_port NDD_VALUE[0]=65500 TRANSPORT_NAME[1]=udp NDD_NAME[1]=udp_largest_anon_port NDD_VALUE[1]=65500
Ensure that the entries are numbered in proper order. For example, if there are two entries present for the TCP and UDP ports in nddconf
, then they are numbered 0 through 1: TRANSPORT_NAME[0]=tcp and TRANSPORT_NAME[1]=udp.
See Also:
"Setting TCP Network Protocol Buffer for Direct NFS Client" if you use Direct NFS Client