Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Red Hat Enterprise Linux Oracle Tuning Guide
Red Hat Enterprise Linux 5
Performance tips and guidelines for Oracle® 9i and 10g databases on Red Hat Enterprise Linux 5, 4, 3 and 2.1
Edition 1.6
Abstract
This article is a step by step guide for tuning and optimizing Red Hat Enterprise Linux on x86 and x86-64 platforms running Oracle® 9i (32 bit or 64 bit) and Oracle® 10g (32 bit or 64 bit) standalone and RAC databases. It covers Red Hat Enterprise Linux Advanced Server 3 and 4 and the older version 2.1.
Part I. Tuning and Optimizing Red Hat Enterprise Linux for Oracle Database 9i and 10g
링크 복사링크가 클립보드에 복사되었습니다!
Chapter 1. Introduction
링크 복사링크가 클립보드에 복사되었습니다!
This white paper covers optimizations for Red Hat Enterprise Linux x86 (32 bit) and x86_64 (64 bit) platforms running Oracle 9i R2 (32 bit or 64 bit) and Oracle 10g R1/R2 (32 bit or 64 bit) standalone and RAC databases. This white paper covers Red Hat Enterprise Linux Advanced Server 2.1, 3, 4 and 5. Various workarounds covered in this article are due to the 32 bit address limitations of the x86 platform. However, many steps described in this document also apply to x86-64 platforms. Sections that do not specifically say that its only applicable to 32bit or 64bit apply to both platforms. If you think that a section is not very clear on that, let me know.For supported system configurations and limits for Red Hat Enterprise Linux releases, see http://www.redhat.com/rhel/details/limits/. For instructions on installing Oracle 10g and 9i databases on Red Hat Enterprise Linux, see Appendix A and Appendix B respectively.
Chapter 2. Hardware Architectures and Linux Kernels
링크 복사링크가 클립보드에 복사되었습니다!
2.1. General
링크 복사링크가 클립보드에 복사되었습니다!
When it comes to large databases the hybrid x86-64 architecture platform is strongly recommended over the 32 bit x86 platform. 64 bit platforms can access more than 4GB of memory without workarounds. With 32 bit platforms there are several issues that require workaround solutions for databases that use lots of memory, for example refer to Chapter 17, Using Very Large Memory (VLM). If you are not sure whether you are on a 32 bit or 64 bit hardware, run
dmidecode or cat /proc/cpuinfo. Running uname -a can be misleading since 32 bit Linux kernels can run on x86-64 platforms. But if uname -a displays x86-64, then you are running a 64 bit Linux kernel on a x86_64 platform.
2.2. 32 bit Architecture and the hugemem Kernel
링크 복사링크가 클립보드에 복사되었습니다!
In Red Hat Enterprise Linux 3, 4 or 5 the smp kernel can be used on systems with up to 16 GB of RAM. The hugemem kernel is required in order to use all the memory on systems that have more than 16GB of RAM up to 64GB. However, it is recommend to use the hugemem kernel even on systems that have 8GB of RAM or more due to the potential issue of "low memory" starvation (see next section) that can happen on database systems with 8 GB of RAM. The stability you get with the hugemem kernel on larger systems outperforms the performance overhead of address space switching.
With x86 architecture the first 16MB-896MB of physical memory is known as "low memory" (ZONE_NORMAL) which is permanently mapped into kernel space. Many kernel resources must live in the low memory zone. In fact, many kernel operations can only take place in this zone. This means that the low memory area is the most performance critical zone. For example, if you run resource-intensive applications or have a lot of memory installed and are simultaneously running resource-intensive applications, memory addresses below 896MB can become constrained. This happens because more kernel structures must be allocated to these low memory addresses. Low memory starvation happens when
LowFree in /proc/meminfo becomes very low accompanied by a sudden spike in paging activity. To free up memory in the low memory zone, the kernel bounces buffers aggressively between low memory and high memory which becomes noticeable as paging (do not confuse it with paging to the swap partition). If the kernel is unable to free up enough memory in the low memory zone, then the kernel can hang the system.
Paging activity can be monitored using the
vmstat command or using the sar command (option '-B') which comes with the sysstat RPM. Since Linux tries to utilize the whole low memory zone, a low LowFree in /proc/meminfo does not necessarily mean that the system is out of low memory. However, when the system shows increased paging activity when LowFree gets below 50MB, then the hugemem kernel should be installed. The stability you gain from using the hugemem kernel makes up for any performance impact resulting from the 4GB-4GB kernel/user memory split in this kernel (a classic 32 bit x86 system splits the available 4 GB address space into 3 GB virtual memory space for user processes and a 1 GB space for the kernel). To see some allocations in the low memory zone, refer to /proc/meminfo and slabtop(1) for more information. Note that Huge Pages would free up memory in the low memory zone since the system has less bookkeeping to do for that part of virtual memory, see Chapter 17, Using Very Large Memory (VLM).
If you install the Red Hat Enterprise Linux 3, 4 or 5 hugemem kernel ensure that any proprietary drivers you are using (e.g. proprietary multipath drivers) are certified with the hugemem kernel.
In Red Hat Enterprise Linux 2.1, the smp kernel is capable of handling up to 4GB of RAM. The
kernel-enterprise kernel should be used for systems with more than 4GB of RAM up to 16GB.
In Red Hat Enterprise Linux 5, a 32 bit kernel is always a hugemem kernel so there is no need to install a special kernel.
2.3. The 64 bit Architecture
링크 복사링크가 클립보드에 복사되었습니다!
This is the architecture that should be used whenever possible. If you can go with a x86_64 platform ensure that all drivers you need are supported on x86_64 (for example proprietary multipath drivers) Furthermore, ensure that all the required applications are supported on x86_64 as well.
Chapter 3. Kernel Upgrades
링크 복사링크가 클립보드에 복사되었습니다!
Make sure to install the latest kernel where all proprietary drivers, if applicable, are certified and supported. Note that proprietary drivers are often installed under
/lib/modules/<kernel-version>/kernel/drivers/addon. For example, the EMC PowerPath drivers can be found in the following directory when running the 2.4.21-32.0.1.ELhugemem kernel:
Therefore, when you upgrade the kernel you must ensure that all proprietary modules can be found in the right directory so that the kernel can load them. To check which kernels are installed, run the following command:
rpm -qa | grep kernel
$ rpm -qa | grep kernel
To check which kernel is currently running, execute the following command:
uname -r
$ uname -r
For example, to install the 2.4.21-32.0.1.ELhugemem kernel, download the kernel-hugemem RPM and execute the following command:
rpm -ivh kernel-hugemem-2.4.21-32.0.1.EL.i686.rpm
# rpm -ivh kernel-hugemem-2.4.21-32.0.1.EL.i686.rpmNote
Never upgrade the kernel using the RPM option '
-U'. The previous kernel should always be available if the newer kernel does not boot or work properly.
To make sure the right kernel is booted, check the
/etc/grub.conf file if you use GRUB and change the "default" attribute if necessary. Here is an example:
In this example, the "
default" attribute is set to "0" which means that the 2.4.21-32.0.1.ELhugemem kernel will be booted. If the "default" attribute would be set to "1", then 2.4.21-32.0.1.ELsmp would be booted. After you installed the newer kernel reboot the system. Once you are sure that you do not need the old kernel anymore, you can remove the old kernel by running:
rpm -e <OldKernelVersion>
# rpm -e <OldKernelVersion>
When you remove a kernel, you do not need to update
/etc/grub.conf.
Chapter 4. Kernel Boot Parameters
링크 복사링크가 클립보드에 복사되었습니다!
4.1. General
링크 복사링크가 클립보드에 복사되었습니다!
The Linux kernel accepts boot parameters when the kernel is started. Very often it is used to provide information to the kernel about hardware parameters where the kernel would have problems or to overwrite default values. Red Hat Enterprise Linux 3 uses 2.4 based kernels, Red Hat Enterprise Linux 4 and 5 use 2.6 based kernels.
For a list of kernel parameters in Red Hat Enterprise Linux 4 and 5, see
/usr/share/doc/kernel-doc-2.6.9/Documentation/kernel-parameters.txt. This file does not exist if the kernel-doc RPM is not installed. And for a list of kernel parameters in Red Hat Enterprise Linux3 and Red Hat Enterprise Linux 2.1, see /usr/src/linux-2.4/Documentation/kernel-parameters.txt which comes with the kernel-doc RPM.
4.2. The I/O Scheduler
링크 복사링크가 클립보드에 복사되었습니다!
Starting with the 2.6 kernel, for example Red Hat Enterprise Linux 4 or 5, the I/O scheduler can be changed at boot time which controls the way the kernel commits reads and writes to disks. For more information on various I/O scheduler, see Choosing an I/O Scheduler for Red Hat Enterprise Linux 4 and the 2.6 Kernel . Red Hat Enterprise Linux 5 allows users to change I/O schedulers dynamically, one way this can be done is by executing the command
echo sched_name > /sys/block/<sdx>/queue/scheduler.
The Completely Fair Queuing (CFQ) scheduler is the default algorithm in Red Hat Enterprise Linux 4 which is suitable for a wide variety of applications and provides a good compromise between throughput and latency. In comparison to the CFQ algorithm, the Deadline scheduler caps maximum latency per request and maintains a good disk throughput which is best for disk-intensive database applications. Hence, the Deadline scheduler is recommended for database systems. Also, at the time of this writing there is a bug in the CFQ scheduler which affects heavy I/O, see Metalink Bug:5041764. Even though this bug report talks about OCFS2 testing, this bug can also happen during heavy IO access to raw or block devices and as a consequence could evict RAC nodes.
To switch to the Deadline scheduler, the boot parameter
elevator=deadline must be passed to the kernel that is being used. Edit the /etc/grub.conf file and add the following parameter to the kernel that is being used, in this example 2.4.21-32.0.1.ELhugemem:
title Red Hat Enterprise Linux Server (2.6.18-8.el5) root (hd0,0) kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/sda2 elevator=deadline initrd /initrd-2.6.18-8.el5.img
title Red Hat Enterprise Linux Server (2.6.18-8.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/sda2 elevator=deadline
initrd /initrd-2.6.18-8.el5.img
This entry tells the
2.6.18-8.el5 kernel to use the Deadline scheduler. Make sure to reboot the system to activate the new scheduler.
Chapter 5. Memory Usage and Page Cache
링크 복사링크가 클립보드에 복사되었습니다!
5.1. Checking the Memory Usage
링크 복사링크가 클립보드에 복사되었습니다!
To determine the size and usage of memory, you can enter the following command:
grep MemTotal /proc/meminfo
grep MemTotal /proc/meminfo
You can find a detailed description of the entries in
/proc/meminfo at http://www.redhat.com/advice/tips/meminfo.html.
Alternatively, you can use the
free(1) command to check the memory:
In this example the total amount of available memory is 4040360 KB. 264224 KB are used by processes and 3776136 KB are free for other applications. Do not get confused by the first line which shows that 28160KB are free! If you look at the usage figures you can see that most of the memory use is for buffers and cache. Linux always tries to use RAM to speed up disk operations by using available memory for buffers (file system metadata) and cache (pages with actual contents of files or block devices). This helps the system to run faster because disk information is already in memory which saves I/O operations. If space is needed by programs or applications like Oracle, then Linux will free up the buffers and cache to yield memory for the applications. If your system runs for a while you will usually see a small number under the field "
free" on the first line.
5.2. Tuning the Page Cache
링크 복사링크가 클립보드에 복사되었습니다!
Page cache is a disk cache which holds data of files and executable programs, for example pages with actual contents of files or block devices. Page cache (disk cache) is used to reduce the number of disk reads. To control the percentage of total memory used for page cache in Red Hat Enterprise Linux 5, change the
pagecache kernel parameter. The lower the percentage, the more the system favors reclaiming unmapped pagecache memory over mapped memory. High values (like the default value of 100) are not recommended for databases.
The
pagecache parameters can be changed in the proc file system without reboot:
echo "40" > /proc/sys/vm/pagecache
# echo "40" > /proc/sys/vm/pagecache
Alternatively, you can use
sysctl(8) to change it:
sysctl -w vm.pagecache="40"
# sysctl -w vm.pagecache="40"
To make the change permanent, add the following line to the file
/etc/sysctl.conf. This file is used during the boot process.
echo "vm.pagecache=40" >> /etc/sysctl.conf
# echo "vm.pagecache=40" >> /etc/sysctl.conf
You can also adjust the minimum free pages using the following command:
echo 1024 > /proc/sys/vm/min_free_kbytes
# echo 1024 > /proc/sys/vm/min_free_kbytes
To make this change permanent, add the following line to the file
/etc/sysctl.conf:
echo vm.min_free_kbytes=1024 >> /etc/sysctl.conf
# echo vm.min_free_kbytes=1024 >> /etc/sysctl.confChapter 6. Swap Space
링크 복사링크가 클립보드에 복사되었습니다!
6.1. General
링크 복사링크가 클립보드에 복사되었습니다!
In some cases it is good for the swap partition to be used. For example, long running processes often access only a subset of the page frames they obtained. This means that the swap partition can safely be used even if memory is available because system memory could be better served for disk cache to improve overall system performance. In fact, in the 2.6 kernel used in Red Hat Enterprise Linux 4 and 5, you can define a threshold when processes should be swapped out in favor of I/O caching. This can be tuned with the
/proc/sys/vm/swappiness kernel parameter. The default value of /proc/sys/vm/swappiness is 60 which means that applications and programs that have not done a lot lately can be swapped out. Higher values will provide more I/O cache and lower values will wait longer to swap out idle applications. Swappiness percentage may be tuned using:
echo 10 > /proc/sys/vm/swappiness
# echo 10 > /proc/sys/vm/swappiness
or,
echo vm.swappiness=10 >> /etc/sysctl.conf
# echo vm.swappiness=10 >> /etc/sysctl.conf
Depending on your system profile you may see that swap usage slowly increases with the time the system is up. To display swap usage you can run the
free(1) command or you can check the /proc/meminfo file. When the system uses swap space it will sometimes not decrease afterward. This saves I/O if memory is needed and pages do not have to be swapped out again when the pages are already in the swap space. However, if swap usage gets close to 80% - 100% (your threshold may be lower if you use a large swap space), then a closer look should be taken at the system, see also Section 6.2, “Checking Swap Space Size and Usage”. Depending on the size of your swap space, you may want to check swap activity with vmstat or sar if swap allocation is lower than 80%. But these numbers really depend on the size of the swap space. The vmstat or sar command output the number of pages swapped. This output field is an important metric. This number should be low or zero as constant page swapping should be avoided at all costs.
Note
Never add a permanent swap file to the system due to the performance impact on the file system layer.
Swap Size Recommendations According to Oracle9i Installation Guide Release 2 a minimum of 512MB of RAM is required to install Oracle9i Server. According to Oracle Database Installation Guide 10g Release 2 at least 1024MB of RAM is required for 10g R2.
For 10g R2, Oracle gives the following swap space requirement:
| RAM | Swap Space |
|---|---|
| 1 GB - 2 GB | 1.5 times the size of RAM |
| 2 GB - 8 GB | Equal to the size of RAM |
| Greater than 8GB | 0.75 times the size of RAM |
6.2. Checking Swap Space Size and Usage
링크 복사링크가 클립보드에 복사되었습니다!
You can check the size and current usage of swap space by running the command:
grep SwapTotal /proc/meminfo
Swap usage may slowly increase as shown above but should stop at some point. If swap usage continues to grow steadily or is already large, then one of the following choices may need to be considered:
- Adding more RAM.
- Reducing the size of the SGA.
- Increasing the size of the swap space.
If you see constant swapping, then you need to either add more RAM or reduce the size of the SGA. Constant swapping should be avoided at all cost. You can check current swap activity using the following commands:
The fields si and so show the amount of memory paged in from disk and paged out to disk, respectively. If the server shows continuous swap activity then more memory should be added or the SGA size should be reduced. To check the history of swap activity, you can use the sar command. For example, to check swap activity from Oct 12th:
The fields
pswpin and pswpout show the total number of pages brought in and out per second, respectively.
If the server shows sporadic swap activity or swap activity for a short period time at certain intervals, then you can either add more swap space or RAM. If swap usage is already very large, do not confuse very large swap usage with constant swapping, then more RAM is recommended.
Chapter 8. Setting Semaphores
링크 복사링크가 클립보드에 복사되었습니다!
Semaphores can best be described as counters which are used to provide synchronization between processes or between threads within a process for shared resources like shared memories. System V semaphores support semaphore sets where each one is a counting semaphore. So when an application requests semaphores, the kernel releases them in sets. The number of semaphores per set can be defined through the kernel parameter SEMMSL.
To see all semaphore settings, run:
ipcs -ls
ipcs -ls8.1. The SEMMSL Parameter
링크 복사링크가 클립보드에 복사되었습니다!
This parameter defines the maximum number of semaphores per semaphore set.
Oracle recommends SEMMSL to be at least 250 for 9i R2 and 10g R1/R2 databases except for 9i R2 on x86 platforms where the minimum value is lower. Since these recommendations are minimum settings, it is best to set it always to at least 250 for 9i and 10g databases on x86 and x86-64 platforms.
Note
If a database gets thousands of concurrent connections where the
ora.init parameter PROCESSES is very large, then SEMMSL should be larger as well. Note what Metalink Note:187405.1 and Note:184821.1 have to say regarding SEMMSL: "The SEMMSL setting should be 10 plus the largest PROCESSES parameter of any Oracle database on the system". Even though these notes talk about 9i databases this SEMMSL rule also applies to 10g databases. I have seen low SEMMSL settings to be an issue for 10g RAC databases where Oracle recommended to increase SEMMSL and to calculate it according to the rule mentioned in these notes. An example for setting semaphores for higher PROCESSES settings can be found at Section 8.6, “An Example of Semaphore Settings”.
8.2. The SEMMNI Parameter
링크 복사링크가 클립보드에 복사되었습니다!
This parameter defines the maximum number of semaphore sets for the entire Linux system.
Oracle recommends SEMMNI to be at least 128 for 9i R2 and 10g R1/R2 databases except for 9i R2 on x86 platforms where the minimum value is lower. Since these recommendations are minimum settings, it is best to set it always to at least 128 for 9i and 10g databases on x86 and x86-64 platforms.
8.3. The SEMMNS Parameter
링크 복사링크가 클립보드에 복사되었습니다!
This parameter defines the total number of semaphores (not semaphore sets) for the entire Linux system. A semaphore set can have more than one semaphore, and as the
semget(2) man page explains, values greater than SEMMSL * SEMMNI makes it irrelevant. The maximum number of semaphores that can be allocated on a Linux system will be the lesser of: SEMMNS or (SEMMSL * SEMMNI).
Oracle recommends SEMMSL to be at least 32000 for 9i R2 and 10g R1/R2 databases except for 9i R2 on x86 platforms where the minimum value is lower. Setting SEMMNS to 32000 ensures that SEMMSL * SEMMNI (250*128=32000) semaphores can be be used. Therefore it is recommended to set SEMMNS to at least 32000 for 9i and 10g databases on x86 and x86-64 platforms.
8.4. The SEMOPM Parameter
링크 복사링크가 클립보드에 복사되었습니다!
This parameter defines the maximum number of semaphore operations that can be performed per
semop(2) system call (semaphore call). The semop(2) function provides the ability to do operations for multiple semaphores with one semop(2) system call. Since a semaphore set can have the maximum number of SEMMSL semaphores per semaphore set, it is often recommended to set SEMOPM equal to SEMMSL.
Oracle recommends to set SEMOPM to a minimum value of 100 for 9i R2 and 10g R1/R2 databases on x86 and x86-64 platforms.
8.5. Setting Semaphore Parameters
링크 복사링크가 클립보드에 복사되었습니다!
To determine the values of the four described semaphore parameters, run:
cat /proc/sys/kernel/sem 250 32000 32 128
# cat /proc/sys/kernel/sem
250 32000 32 128
These values represent SEMMSL, SEMMNS, SEMOPM, and SEMMNI.
Alternatively, you can run:
ipcs -ls
# ipcs -ls
All four described semaphore parameters can be changed in the proc file system without reboot:
echo 250 32000 100 128 > /proc/sys/kernel/sem
# echo 250 32000 100 128 > /proc/sys/kernel/sem
Alternatively, you can use sysctl(8) to change it:
sysctl -w kernel.sem="250 32000 100 128"
sysctl -w kernel.sem="250 32000 100 128"
To make the change permanent, add or change the following line in the file
/etc/sysctl.conf. This file is used during the boot process.
echo "kernel.sem=250 32000 100 128" >> /etc/sysctl.conf
echo "kernel.sem=250 32000 100 128" >> /etc/sysctl.conf8.6. An Example of Semaphore Settings
링크 복사링크가 클립보드에 복사되었습니다!
On systems where the
ora.init parameter PROCESSES is very large, the semaphore settings need to be adjusted accordingly.
As shown at Section 24.1, “Optimal Flexible Architecture (OFA) for 10g R1 (10.1.0.2)” the SEMMSL setting should be 10 plus the largest
PROCESSES parameter of any Oracle database on the system. So if you have one database instance running on a system where PROCESSES is set to 5000, then SEMMSL should be set to 5010.
As shown at Section 8.3, “The SEMMNS Parameter” the maximum number of semaphores that can be allocated on a Linux system will be the lesser of: SEMMNS or (SEMMSL * SEMMNI). Since SEMMNI can stay at 128, we need to increase SEMMNS to 641280 (5010*128).
As shown at Section 8.4, “The SEMOPM Parameter” a semaphore set can have the maximum number of SEMMSL semaphores per semaphore set and it is recommended to set SEMOPM equal to SEMMSL. Since SEMMSL is set to 5010 the SEMOPM parameter should be set to 5010 as well.
Hence, if the
ora.init parameter PROCESSES is set to 5000, then the semaphore settings should be as follows:
sysctl -w kernel.sem="5010 641280 5010 128"
sysctl -w kernel.sem="5010 641280 5010 128"Chapter 9. Setting File Handles
링크 복사링크가 클립보드에 복사되었습니다!
The maximum number of file handles denotes the maximum number of open files on a Linux system.
Oracle recommends that the file handles for the entire system is set to at least 65536 for 9i R2 and 10g R1 and R2 for x86 and x86-64 platforms.
To determine the maximum number of file handles for the entire system, run:
cat /proc/sys/fs/file-max
cat /proc/sys/fs/file-max
To determine the current usage of file handles, run:
cat /proc/sys/fs/file-nr 1154 133 8192
$ cat /proc/sys/fs/file-nr
1154 133 8192
The
file-nr file displays three parameters:
- the total allocated file handles.
- the number of currently used file handles (with the 2.4 kernel); or the number of currently unused file handles (with the 2.6 kernel).
- the maximum file handles that can be allocated (also found in /proc/sys/fs/file-max).
The kernel dynamically allocates file handles whenever a file handle is requested by an application but the kernel does not free these file handles when they are released by the application. The kernel recycles these file handles instead. This means that over time the total number of allocated file handles will increase even though the number of currently used file handles may be low.
The maximum number of file handles can be changed in the
proc file system without reboot:
echo 65536 > /proc/sys/fs/file-max
# echo 65536 > /proc/sys/fs/file-max
Alternatively, you can use
sysctl(8) to change it:
sysctl -w fs.file-max=65536
# sysctl -w fs.file-max=65536
To make the change permanent, add or change the following line in the file
/etc/sysctl.conf. This file is used during the boot process.
echo "fs.file-max=65536" >> /etc/sysctl.conf
echo "fs.file-max=65536" >> /etc/sysctl.confChapter 10. Adjusting Network Settings
링크 복사링크가 클립보드에 복사되었습니다!
10.1. Changing Network Adapter Settings
링크 복사링크가 클립보드에 복사되었습니다!
To check the speed and settings of network adapters, use the
ethtool command which works now for most network interface cards. To check the adapter settings of eth0 run:
ethtool eth0
# ethtool eth0
To force a speed change to 1000Mbps, full duplex mode, run:
ethtool -s eth0 speed 1000 duplex full autoneg off
# ethtool -s eth0 speed 1000 duplex full autoneg off
To make a speed change permanent for
eth0, set or add the ETHTOOL_OPT environment variable in /etc/sysconfig/network-scripts/ifcfg-eth0:
ETHTOOL_OPTS="speed 1000 duplex full autoneg off"
ETHTOOL_OPTS="speed 1000 duplex full autoneg off"
This environment variable is sourced in by the network scripts each time the network service is started.
10.2. Changing Network Kernel Settings
링크 복사링크가 클립보드에 복사되었습니다!
Oracle now uses User Datagram Protocol (UDP) as the default protocol on Linux for interprocess communication, such as cache fusion buffer transfers between the instances. However, starting with Oracle 10g network settings should be adjusted for standalone databases as well.
Oracle recommends the default and maximum send buffer size (
SO_SNDBUF socket option) and receive buffer size (SO_RCVBUF socket option) to be set to 256 KB. The receive buffers are used by TCP and UDP to hold received data until it is read by the application. The receive buffer cannot overflow because the peer is not allowed to send data beyond the buffer size window. This means that datagrams will be discarded if they do not fit in the socket receive buffer. This could cause the sender to overwhelm the receiver.
The default and maximum window size can be changed in the proc file system without reboot:
The default setting in bytes of the socket receive buffer:
sysctl -w net.core.rmem_default=262144
# sysctl -w net.core.rmem_default=262144
The default setting in bytes of the socket send buffer:
sysctl -w net.core.wmem_default=262144
# sysctl -w net.core.wmem_default=262144
The maximum socket receive buffer size which may be set by using the SO_RCVBUF socket option:
sysctl -w net.core.rmem_max=262144
# sysctl -w net.core.rmem_max=262144
The maximum socket send buffer size which may be set by using the SO_SNDBUF socket option:
sysctl -w net.core.wmem_max=262144
# sysctl -w net.core.wmem_max=262144
To make the change permanent, add the following lines to the
/etc/sysctl.conf file, which is used during the boot process:
net.core.rmem_default=262144 net.core.wmem_default=262144 net.core.rmem_max=262144 net.core.wmem_max=262144
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144
To improve fail over performance in a RAC cluster, consider changing the following IP kernel parameters as well:
net.ipv4.tcp_keepalive_time net.ipv4.tcp_keepalive_intvl net.ipv4.tcp_retries2 net.ipv4.tcp_syn_retries
net.ipv4.tcp_keepalive_time
net.ipv4.tcp_keepalive_intvl
net.ipv4.tcp_retries2
net.ipv4.tcp_syn_retries
Changing these settings may be highly dependent on your system, network, and other applications. For suggestions, see Metalink Note:249213.1 and Note:265194.1.
On Red Hat Enterprise Linux systems the default range of IP port numbers that are allowed for TCP and UDP traffic on the server is too low for 9i and 10g systems. Oracle recommends the following port range:
sysctl -w net.ipv4.ip_local_port_range="1024 65000"
# sysctl -w net.ipv4.ip_local_port_range="1024 65000"
To make the change permanent, add the following line to the /etc/sysctl.conf file, which is used during the boot process:
net.ipv4.ip_local_port_range=1024 65000
net.ipv4.ip_local_port_range=1024 65000
The first number is the first local port allowed for TCP and UDP traffic, and the second number is the last port number.
10.3. Flow Control for e1000 Network Interface Cards
링크 복사링크가 클립보드에 복사되었습니다!
The e1000 network interface card family do not have flow control enabled in the 2.6 kernel on Red Hat Enterprise Linux 4 and 5. If you have heavy traffic, then the RAC interconnects may lose blocks, see Metalink Bug:5058952. For more information on flow control, see Wikipedia Flow control.
To enable Receive flow control for e1000 network interface cards, add the following line to the
/etc/modprobe.conf file:
options e1000 FlowControl=1
options e1000 FlowControl=1
The e1000 module needs to be reloaded for the change to take effect. Once the module is loaded with flow control, you should see e1000 flow control module messages in
/var/log/messages.
Chapter 11. Setting Shell Limits for the Oracle User
링크 복사링크가 클립보드에 복사되었습니다!
Most shells like Bash provide control over various resources like the maximum allowable number of open file descriptors or the maximum number of processes available to a user.
To see all shell limits, run:
ulimit -a
ulimit -a
For more information on
ulimit for the Bash shell, see man bash and search for ulimit.
Note
On some Linux systems setting "hard" and "soft" limits in the following examples might not work properly when you log in as user oracle via SSH. It might work if you log in as root and
su to oracle. If you have this problem try to set UsePrivilegeSeparation to "no" in /etc/ssh/sshd_config and restart the SSH daemon by executing service sshd restart. The privilege separation does not work properly with PAM on some Linux systems. Make sure to talk to the people in charge of security before disabling the SSH security feature "Privilege Separation".
11.1. Limiting Maximum Number of Open File Descriptors for the Oracle User
링크 복사링크가 클립보드에 복사되었습니다!
After
/proc/sys/fs/file-max has been changed, see Chapter 9, Setting File Handles, there is still a per user limit of maximum open file descriptors:
su - oracle ulimit -n
$ su - oracle
$ ulimit -n
1024
$
To change this limit, edit the
/etc/security/limits.conf file as root and make the following changes or add the following lines, respectively:
oracle soft nofile 4096 oracle hard nofile 63536
oracle soft nofile 4096
oracle hard nofile 63536
The "soft limit" in the first line defines the number of file handles or open files that the Oracle user will have after they log in. If the Oracle user gets error messages about running out of file handles, then the Oracle user can increase the number of file handles like in this example up to 63536 ("hard limit") by executing the following command:
ulimit -n 63536
ulimit -n 63536
You can set the "soft" and "hard" limits higher if necessary.
Note
It is not recommend to set the "hard" limit for nofile for the oracle user equal to
/proc/sys/fs/file-max. If you do that and the user uses up all the file handles, then the entire system will run out of file handles. This may prevent users logging in as the system cannot open any PAM modules that are required for the login process. That is why the hard limit should be set to 63536 and not 65536.
That these limits work you also need to ensure that
pam_limits is configured in the /etc/pam.d/system-auth file, or in /etc/pam.d/sshd for ssh, /etc/pam.d/su for su, or /etc/pam.d/login for local access and telnet and disable telnet for all log in methods. Here are examples of the two session entries in the /etc/pam.d/system-auth file:
session required /lib/security/$ISA/pam_limits.so session required /lib/security/$ISA/pam_unix.so
session required /lib/security/$ISA/pam_limits.so
session required /lib/security/$ISA/pam_unix.so
Log in to the oracle user account since the changes will become effective for new login sessions only. Note the
ulimit options are different for other shells.
su - oracle ulimit -n
$ su - oracle
$ ulimit -n
4096
$
The default limit for oracle is now 4096 and the oracle user can increase the number of file handles up to 63536:
To make this change permanent, you could add "
ulimit -n 63536" ,for bashbash, to the ~oracle/.bash_profile file which is the user start up file for the bash shell on Red Hat Enterprise Linux (to verify your shell execute echo $SHELL). To do this you could simply copy and paste the following commands for oracle's bash shell:
su - oracle cat >> ~oracle/.bash_profile << EOF ulimit -n 63536 EOF
su - oracle
cat >> ~oracle/.bash_profile << EOF
ulimit -n 63536
EOF
To make the above changes permanent, you could also set the soft limit equal to the hard limit in
/etc/security/limits.conf:
oracle soft nofile 63536 oracle hard nofile 63536
oracle soft nofile 63536
oracle hard nofile 6353611.2. Limiting Maximum Number of Processes Available for the Oracle User
링크 복사링크가 클립보드에 복사되었습니다!
After reading the procedure on, Section 11.1, “Limiting Maximum Number of Open File Descriptors for the Oracle User” you should now have an understanding of "soft" and "hard" limits and how to change shell limits.
To see the current limit of the maximum number of processes for the oracle user, run:
su - oracle ulimit -u
$ su - oracle
$ ulimit -uNote
The
ulimit options are different for other shells.
To change the "soft" and "hard" limits for the maximum number of processes for the oracle user, add the following lines to the
/etc/security/limits.conf file:
oracle soft nproc 2047 oracle hard nproc 16384
oracle soft nproc 2047
oracle hard nproc 16384
To make this change permanent, you could add "
ulimit -u 16384",for bash, to the ~oracle/.bash_profile file which is the user start up file for the bash shell on Red Hat Enterprise Linux (to verify your shell execute echo $SHELL). To do this you could simply copy and paste the following commands for oracle's bash shell:
su - oracle cat >> ~oracle/.bash_profile << EOF ulimit -u 16384 EOF
su - oracle
cat >> ~oracle/.bash_profile << EOF
ulimit -u 16384
EOF
To make the above changes permanent, you could also set the soft limit equal to the hard limit in
/etc/security/limits.conf:
oracle soft nproc 16384 oracle hard nproc 16384
oracle soft nproc 16384
oracle hard nproc 16384Chapter 12. Enabling Asynchronous I/O and Direct I/O Support
링크 복사링크가 클립보드에 복사되었습니다!
Asynchronous I/O permits Oracle to continue processing after issuing I/Os requests which leads to higher I/O performance. Red Hat Enterprise Linux also allows Oracle to issue multiple simultaneous I/O requests with a single system call. This reduces context switch overhead and allows the kernel to optimize disk activity.
To enable asynchronous I/O in Oracle Database, it is necessary to relink Oracle 9i and 10g Release 1.
Note
10g Release 2 is shipped with asynchronous I/O support enabled and does not need to be relinked. But you may have to apply a patch, see below.
12.1. Relinking Oracle9i R2 to Enable Asynchronous I/O Support
링크 복사링크가 클립보드에 복사되었습니다!
Note
Oracle 9iR2 on Red Hat Enterprise Linux 3, 4 and 5 the 9.2.0.4 patchset or higher needs to be installed together with another patch for asynchronous I/O, see Metalink Note:279069.1.
To relink Oracle 9i R2 for asynchronous I/O, execute the following commands:
If asynchronous I/O needs to be disabled, execute the following commands:
12.2. Relinking Oracle 10g to Enable Asynchronous I/O Support
링크 복사링크가 클립보드에 복사되었습니다!
Ensure that for 10g Release 1 and 2 the
libaio and libaio-devel RPMs are installed on the system:
rpm -q libaio libaio-devel
# rpm -q libaio libaio-devel
libaio-0.3.96-5
libaio-devel-0.3.96-5
If you relink Oracle for asynchronous I/O without installing the
libaio RPM, then you will get an error message similar to this one:
SQL> connect / as sysdba oracleorcl: error while loading shared libraries: libaio.so.1: cannot open \ shared object file: No such file or directory ERROR: ORA-12547: TNS:lost contact
SQL> connect / as sysdba
oracleorcl: error while loading shared libraries: libaio.so.1: cannot open \
shared object file: No such file or directory
ERROR:
ORA-12547: TNS:lost contact
The
libaio RPMs provide a native Linux asynchronous I/O API. In other words this is a kernel accelerated asynchronous I/O for the POSIX asynchronous I/O facility.
Note
10g Release 2 is shipped with asynchronous I/O support enabled. This means that 10g Release 2 does not need to be relinked. However, there is a bug in Oracle 10.1.0.2 that causes asynchronous I/O not to be installed correctly which can result in poor DB performance, see Bug:3438751 and Note:270213.1.
To relink Oracle 10g R1 for asynchronous I/O, execute the following commands:
If asynchronous I/O needs to be disabled, run the following commands:
12.3. Enabling Asynchronous I/O in Oracle 9i and 10g
링크 복사링크가 클립보드에 복사되었습니다!
If you use file systems instead of raw devices or ASM for data files, then you need to ensure that the data files reside on file systems that support asynchronous I/O (OCFS/OCFS2, ext2 and ext3). To do asynchronous I/O on file systems the
filesystemio_options parameter needs to be set to "asynch".
filesystemio_options=asynch
filesystemio_options=asynch
This parameter is platform specific. By default, this parameter is set to none for Linux and thus needs to be changed:
The
filesystemio_options can have the following values with Oracle 9i R2:
asynch: This value enables asynchronous I/O on file system files.directio: This value enables direct I/O on file system files.setall: This value enables both asynchronous and direct I/O on file system files.none: This value disables both asynchronous and direct I/O on file system files.
If you also want to enable Direct I/O Support which is available in Red Hat Enterprise Linux 4 or 5, set
filesystemio_options to "setall".
Important
In Red Hat Enterprise Linux 3, it is recommended you use direct I/O only for ext2, ext3, GFS, NFS and OCFS file systems.
Important
In Red Hat Enterprise Linux 4 and 5, it is strongly recommended to use the “
setall” parameter for ext2, ext3, GFS, NFS and OCFS file systems.
12.4. Tuning Asynchronous I/O for Oracle 9i and 10g
링크 복사링크가 클립보드에 복사되었습니다!
For Red Hat Enterprise Linux 3 it is recommended to set
aio-max-size to 1048576 since Oracle uses I/Os of up to 1MB. It controls the maximum I/O size for asynchronous I/Os.
Note
The
aio-max-size tuning parameter is not applicable to the 2.6 kernel on Red Hat Enterprise Linux 4 or 5.
To determine the maximum I/O size in bytes, execute:
cat /proc/sys/fs/aio-max-size 131072
$ cat /proc/sys/fs/aio-max-size
131072
To change the maximum number of bytes without reboot:
echo 1048576 > /proc/sys/fs/aio-max-size
# echo 1048576 > /proc/sys/fs/aio-max-size
Alternatively, you can use
sysctl(8) to change it:
sysctl -w fs.aio-max-size=1048576
# sysctl -w fs.aio-max-size=1048576
To make the change permanent, add the following line to the
/etc/sysctl.conf file. This file is used during the boot process:
echo "fs.aio-max-size=1048576" >> /etc/sysctl.conf
$ echo "fs.aio-max-size=1048576" >> /etc/sysctl.conf12.5. Verifying Asynchronous I/O Usage
링크 복사링크가 클립보드에 복사되었습니다!
To verify whether
$ORACLE_HOME/bin/oracle was linked with asynchronous I/O, you can use the Linux commands ldd and nm.
In the following example,
$ORACLE_HOME/bin/oracle was relinked with asynchronous I/O:
ldd $ORACLE_HOME/bin/oracle | grep libaio nm $ORACLE_HOME/bin/oracle | grep io_getevent
$ ldd $ORACLE_HOME/bin/oracle | grep libaio
libaio.so.1 => /usr/lib/libaio.so.1 (0x0093d000)
$ nm $ORACLE_HOME/bin/oracle | grep io_getevent
w io_getevents@@LIBAIO_0.1
$
In the following example,
$ORACLE_HOME/bin/oracle has NOT been relinked with asynchronous I/O:
ldd $ORACLE_HOME/bin/oracle | grep libaio nm $ORACLE_HOME/bin/oracle | grep io_getevent
$ ldd $ORACLE_HOME/bin/oracle | grep libaio
$ nm $ORACLE_HOME/bin/oracle | grep io_getevent
w io_getevents
$
If
$ORACLE_HOME/bin/oracle is relinked with asynchronous I/O it does not necessarily mean that Oracle is really using it. You also have to ensure that Oracle is configured to use asynchronous I/O calls, see Enabling Asynchronous I/O Support.
To verify whether Oracle is making asynchronous I/O calls, you can take a look at the
/proc/slabinfo file assuming there are no other applications performing asynchronous I/O calls on the system. This file shows kernel slab cache information in real time.
On a Red Hat Enterprise Linux 3 system where Oracle does not make asynchronous I/O calls, the output looks like this:
egrep "kioctx|kiocb" /proc/slabinfo
$ egrep "kioctx|kiocb" /proc/slabinfo
kioctx 0 0 128 0 0 1 : 1008 252
kiocb 0 0 128 0 0 1 : 1008 252
$
Once Oracle makes asynchronous I/O calls, the output on a Red Hat Enterprise Linux 3 system will look like this:
egrep "kioctx|kiocb" /proc/slabinfo
$ egrep "kioctx|kiocb" /proc/slabinfo
kioctx 690 690 128 23 23 1 : 1008 252
kiocb 58446 65160 128 1971 2172 1 : 1008 252
$
The numbers in red (number of active objects) show whether Oracle makes asynchronous I/O calls. The output will look a little bit different in Red Hat Enterprise Linux 4 and 5. However, the numbers in red will show same behavior in Red Hat Enterprise Linux 3 and Red Hat Enterprise Linux 4 and 5. The first column displays the cache names kioctx and kiocb. The second column shows the number of active objects currently in use. And the third column shows how many objects are available in total, used and unused.
To see kernel slab cache information in real time, you can also use the slabtop command:
Slab caches are a special memory pool in the kernel for adding and removing objects, such as data structures or data buffers, of the same size. Its a cache for commonly used objects where the kernel does not have to re-allocate and initialize the object each time it is being reused, and free the object each time it is being destroyed. The slab allocator scheme basically prevents memory fragmentation and it prevents the kernel from spending too much time allocating, initializing, and freeing the same objects.
Chapter 13. Configuring I/O for Raw Partitions
링크 복사링크가 클립보드에 복사되었습니다!
13.1. General
링크 복사링크가 클립보드에 복사되었습니다!
Raw partitions allow Oracle to bypass the OS cache. A raw device can be assigned or bound to block devices such as disk or disk partitions. When a raw device is bound to a disk, any read or write access to the raw device will perform a raw I/O with the disk. A raw I/O through the
/dev/raw interface bypasses the kernel's block buffer cache entirely that is normally associated with block devices and goes right to the low level device itself. By bypassing the cache it accesses a physical device directly which allows applications such as Oracle databases to have more control over the I/O to the physical device. In fact, Oracle does it is own data caching and raw devices allow Oracle to ensure that data gets written to the disk immediately without OS caching.
Since Automatic Storage Management (ASM) is the recommended option for large amounts of storage in RAC environments, the focus of this article and section is on the usage of raw devices and block devices for ASM. ASM offers many advantages over conventional file systems. The ASM file system is not buffered and supports asynchronous I/O. It allows you to group sets of physical disks to logical entities as disk groups. You can add or remove disks without downtime. In fact, you could move a whole database from one SAN storage to another SAN without downtime. ASM spreads I/O over all the available disks automatically to avoid hot spots. ASM does also it is own striping and offers mirroring. ASM can be setup using the ASM library driver or raw devices. Starting with 10g R2, neither is necessarily required.
Note
Raw I/O was briefly deprecated by the Linux community, so Oracle 10g R2 no longer requires raw devices for the database. Oracle 10g R2 automatically opens all block devices such as SCSI disks using the
O_DIRECT flag, thus bypasses the OS cache. Support for raw devices was reinstated in Red Hat Enterprise Linux 5.4 and later.
For older Oracle Database and Red Hat Enterprise Linux versions raw devices are still a recommended option for ASM and data files, and remain supported. For more information on using block devices, see Section 13.4, “Using Block Devices for Oracle 10g Release 2 in Red Hat Enterprise Linux 4 and 5”. Unfortunately, Oracle Clusterware R2 OUI still requires raw devices or a Cluster File System.
Warning
The name of the devices are assigned by the Linux and is determined by the scan order of the bus. Therefore, the device names are not guaranteed to persist across reboots. For example, SCSI device
/dev/sdb can change to /dev/sda if the scan order of the controllers is not configured. To force the scan order of the controllers, aliases can be set in /etc/modprobe.conf. For example:
alias scsi_hostadapter1 aic7xxx
alias scsi_hostadapter1 aic7xxxalias scsi_hostadapter2 lpfc
alias scsi_hostadapter2 lpfc
These settings will guarantee that the Adaptec adapter for local storage is used first and then the Emulex adapter(s) for SAN storage. Fortunately, Red Hat Enterprise Linux 4 and 5 have already addressed this issue by delaying the loading of lpfc (Emulex) and various qla (QLogic) drivers until after all other SCSI devices have been loaded. This means that the alias settings in this example would not be required in Red Hat Enterprise Linux 4 and 5. For more information, see Red Hat Enterprise Linux AS 4 Release Notes. Be also careful when adding/removing devices which can change device names on the system. Starting Oracle with incorrect device names or raw devices can cause permanent damage to the database. For stable device naming in Linux 2.4 and 2.6, see Optimizing Linux I/O.
13.2. Basics of Raw Devices
링크 복사링크가 클립보드에 복사되었습니다!
To bind the first raw device
/dev/raw/raw1 to the /dev/sdz SCSI disk or LUN you can execute the following command:
raw /dev/raw/raw1 /dev/sdz
# raw /dev/raw/raw1 /dev/sdz
Now when you run the
dd command on /dev/raw/raw1, it will write directly to /dev/sdz bypassing the OS block buffer cache:
Warning
The following command will overwrite data on
dev/sdz
dd if=/dev/zero of=/dev/sdz count=1
# dd if=/dev/zero of=/dev/sdz count=1
To permanently bind
/dev/raw/raw1 to /dev/sdz, add an entry to the /etc/sysconfig/rawdevices file:
/dev/raw/raw1 /dev/sdz
/dev/raw/raw1 /dev/sdz
Now when you run
/etc/init.d/rawdevices it will read the /etc/sysconfig/rawdevices file and execute the raw command for each entry:
/etc/init.d/rawdevices start
/etc/init.d/rawdevices start
To have
/etc/init.d/rawdevices run each time the system boot, it can be activated by executing the following command:
chkconfig rawdevices on
chkconfig rawdevices onNote
For each block device you need to use another raw device.
To bind the third raw device to the second partition of
/dev/sdz, the entry in /etc/sysconfig/rawdevices would look like this:
/dev/raw/raw3 /dev/sdz2
/dev/raw/raw3 /dev/sdz2
Or to bind the 100th raw device to
/dev/sdz, the entry in /etc/sysconfig/rawdevices would look like this:
/dev/raw/raw100 /dev/sdz
/dev/raw/raw100 /dev/sdz13.3. Using Raw Devices for Oracle Databases
링크 복사링크가 클립보드에 복사되었습니다!
The rawdevices service can only initialize devices named according to the
/dev/raw/rawN format. However, devices in this location do not have the correct ownership or permissions for an Oracle database file by default. Additionally, because these device names are owned by the dev package, each time the package is updated (for example, as part of an operating system update), all devices are recreated with the default ownership and permissions at boot. It is therefore necessary to set ownership and permissions each time the dev package is updated.
Procedure 13.1. Configure a raw device
- Configure the desired device in the
/etc/sysconfig/rawdevicesfile:/dev/raw/raw1 /dev/sdb1
/dev/raw/raw1 /dev/sdb1Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Start and enable the device by running:
service rawdevices start chkconfig rawdevices on
# service rawdevices start # chkconfig rawdevices onCopy to Clipboard Copied! Toggle word wrap Toggle overflow
At this point, you could set ownership and permissions with
chmod and chown. However, because these devices will be created dynamically at boot time, permissions set in this manner will not persist after a reboot.
Procedure 13.2. Configure persistent ownership and permissions
- To set specific ownership and/or permissions for the raw devices, add entries to
/etc/udev/rules.d/60-raw.rulesin the following format:ACTION=="add", KERNEL=="raw*", OWNER="root", GROUP="disk", MODE="0660"
ACTION=="add", KERNEL=="raw*", OWNER="root", GROUP="disk", MODE="0660"Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Test that the permissions you applied work as intended with
udevtest:udevtest /block/sdb/sdb1 | grep raw
# udevtest /block/sdb/sdb1 | grep raw main: run: '/bin/raw /dev/raw/raw1 /dev/.tmp-8-17'Copy to Clipboard Copied! Toggle word wrap Toggle overflow To test the ownership of a specific device, such as/dev/raw/raw1, use:udevtest /class/raw/raw1 | grep mode
# udevtest /class/raw/raw1 | grep mode udev_node_add: creating device node '/dev/raw/raw1', major = '162', minor = '1', mode = '0600', uid = '0', gid = '0'Copy to Clipboard Copied! Toggle word wrap Toggle overflow - Run the following command to activate the udev rules:
start_udev
# start_udevCopy to Clipboard Copied! Toggle word wrap Toggle overflow
13.4. Using Block Devices for Oracle 10g Release 2 in Red Hat Enterprise Linux 4 and 5
링크 복사링크가 클립보드에 복사되었습니다!
For Oracle 10g Release 2 in Red Hat Enterprise Linux 4 and 5 it is not recommended to use raw devices but to use block devices instead. Raw I/O is still available in Red Hat Enterprise Linux 4 and 5, but it is now a deprecated interface. In fact, raw I/O has been deprecated by the Linux community. It has been replaced by the
O_DIRECT flag, which can be used for opening block devices to bypass the operating system's cache. Unfortunately, Oracle Clusterware R2 OUI has not been updated and still requires raw devices or a Cluster File System. There is also another bug, see bug number 5021707.
By default, reading and writing to block devices are buffered I/Os. Oracle Database 10g R2 now automatically opens all block devices such as SCSI disks using the
O_DIRECT flag, thus bypassing the OS cache. For example, when you create disk groups for ASM and you want to use the SCSI block devices /dev/sdb and /dev/sdc, you can simply set the Disk Discovery Path to "/dev/sdb, /dev/sdc" to create the ASM disk group. There is no need to create raw devices and to point the Disk Discovery Path to it.
Using the ASM example from Section 13.3, “Using Raw Devices for Oracle Databases”, the Oracle data directory could be setup the following way:
ln -s /dev/emcpowera /u02/oradata/asmdisks/disk01 ln -s /dev/emcpowerb /u02/oradata/asmdisks/disk02 ln -s /dev/emcpowerc /u02/oradata/asmdisks/disk03 ln -s /dev/emcpowerd /u02/oradata/asmdisks/disk04
$ ln -s /dev/emcpowera /u02/oradata/asmdisks/disk01
$ ln -s /dev/emcpowerb /u02/oradata/asmdisks/disk02
$ ln -s /dev/emcpowerc /u02/oradata/asmdisks/disk03
$ ln -s /dev/emcpowerd /u02/oradata/asmdisks/disk04
And the following command needs to be executed after each reboot:
chown oracle.dba /u02/oradata/asmdisks/*
# chown oracle.dba /u02/oradata/asmdisks/*
You need to ensure that the ownership of block devices is changed to
oracle:dba or oracle:oinstall. Otherwise Oracle can not access the block devices and ASM disk discovery will not list them. You also need to ensure that the ownership of block devices is set after each reboot since Linux changes the ownership of block devices back to "brw-rw---- 1 root disk" at boot time.
Chapter 14. Large Memory Optimization, Big Pages, and Huge Pages
링크 복사링크가 클립보드에 복사되었습니다!
Note
As explained in detail in this section, enabling big pages helps reduce TLB misses. However, this performance benefit is realized primarily when using large SGA sizes. Once a portion of memory is locked down for big pages, applications that use normal pages cannot access that portion of the memory. It is very important to make sure that there is enough memory for normal pages for applications and users to avoid excessive swapping. So, it is recommended that big pages be used only on systems that have large amounts of physical memory and for SGA sizes of 16GB or greater.
Big Pages in Red Hat Enterprise Linux 2.1 and Huge Pages in Red Hat Enterprise Linux 3, 4 and 5 are very useful for large Oracle SGA sizes and in general for systems with large amount of physical memory. It optimizes the use of Translation Lookaside Buffers (TLB), locks these larger pages in RAM, and the system has less bookkeeping work to do for that part of virtual memory due to larger page sizes. This is a useful feature that should be used on x86 and x86-64 platforms. The default page size in Linux for x86 is 4KB.
Physical memory is partitioned into pages which are the basic unit of memory management. When a Linux process accesses a virtual address, the CPU must translate it into a physical address. Therefore, for each Linux process the kernel maintains a page table which is used by the CPU to translate virtual addresses into physical addresses. But before the CPU can do the translation it has to perform several physical memory reads to retrieve page table information. To speed up this translation process for future references to the same virtual address, the CPU saves information for recently accessed virtual addresses in its Translation Lookaside Buffers (TLB) which is a small but very fast cache in the CPU. The use of this cache makes virtual memory access very fast. Since TLB misses are expensive, TLB hits can be improved by mapping large contiguous physical memory regions by a small number of pages. So fewer TLB entries are required to cover larger virtual address ranges. A reduced page table size also means a reduction in memory management overhead. To use larger page sizes for shared memory, Big Pages (Red Hat Enterprise Linux 2.1) or Huge Pages (Red Hat Enterprise Linux 3, 4 and 5) must be enabled which also locks these pages in physical memory.
14.1. Big Pages in Red Hat Enterprise Linux 2.1 and Huge Pages in Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
In Red Hat Enterprise Linux 2.1 large memory pages can be configured using the Big Pages,
bigpages, feature. In Red Hat Enterprise Linux 3 or 4 Red Hat replaced Big Pages with a feature called Huge Pages, hugetlb, which behaves a little bit different. The Huge Pages feature in Red Hat Enterprise Linux 3 or 4 allows you to dynamically allocate large memory pages without a reboot. Allocating and changing Big Pages in Red Hat Enterprise Linux 2.1 always required a reboot. However, if memory gets too fragmented in Red Hat Enterprise Linux 3 or 4 allocation of physically contiguous memory pages can fail and a reboot may become necessary.
The advantages of Big Pages and Huge Pages for database performance are:
- increased performance through increased Translation Lookaside Buffer (TLB) hits.
- pages are locked in memory and are never swapped out which guarantees that shared memory such as SGA remains in RAM.
- contiguous pages are pre-allocated and cannot be used for anything else but for System V shared memory, for example SGA.
- less bookkeeping work for the kernel in that part of virtual memory due to larger page sizes.
14.2. Usage of Big Pages and Huge Pages in Oracle 9i and 10g
링크 복사링크가 클립보드에 복사되었습니다!
Big pages are supported implicitly in Red Hat Enterprise Linux 2.1. But Huge Pages in Red Hat Enterprise Linux 3, 4 and 5 need to be requested explicitly by the application by using the
SHM_HUGETLB flag when invoking the shmget() system call. This ensures that shared memory segments are allocated out of the Huge Pages pool. This is done automatically in Oracle 10g and 9i R2 (9.2.0.6) but earlier Oracle 9i R2 versions require a patch, see Metalink Note:262004.1.
14.3. Sizing Big Pages and Huge Pages
링크 복사링크가 클립보드에 복사되었습니다!
With the Big Pages and Huge Pages feature you specify how many physically contiguous large memory pages should be allocated and pinned in RAM for shared memory like Oracle SGA. For example, if you have three Oracle instances running on a single system with 2 GB SGA each, then at least 6 GB of large pages should be allocated. This will ensure that all three SGAs use large pages and remain in main physical memory. Furthermore, if you use ASM on the same system, then it is prudent to add an additional 200MB. I have seen ASM instances creating between 70 MB and 150 MB shared memory segments. And there might be other non-Oracle processes that allocate shared memory segments as well.
It is, however, not recommended to allocate too many Big or Huge Pages. These pre-allocated pages can only be used for shared memory. This means that unused Big or Huge Pages will not be available for other use than for shared memory allocations even if the system runs out of memory and starts swapping. Also take note that Huge Pages are not used for the
ramfs shared memory file system, see Section 14.8, “Huge Pages and Shared Memory File System in Red Hat Enterprise Linux 3”, but Big Pages can be used for the shm file system in Red Hat Enterprise Linux 2.1.
14.5. Configuring Big Pages in Red Hat Enterprise Linux 2.1
링크 복사링크가 클립보드에 복사되었습니다!
Before configuring Big Pages, ensure to have read Section 14.3, “Sizing Big Pages and Huge Pages”.
Note that Big Pages in x86 Red Hat Enterprise Linux 2.1 can only be allocated and pinned above approximately 860MB of physical RAM which is known as
Highmem or high memory region in x86. Thus, Big Pages cannot be larger than Highmem. The total amount of memory in the high region can be obtained by reading the memory statistic HighTotal from the /proc/meminfo file:
grep "HighTotal" /proc/meminfo
$ grep "HighTotal" /proc/meminfo
HighTotal: 9043840 kB
$
The Big Pages feature can be enabled with the following command:
echo "1" > /proc/sys/kernel/shm-use-bigpages
# echo "1" > /proc/sys/kernel/shm-use-bigpages
Alternatively, you can use
sysctl(8) to change it:
sysctl -w kernel.shm-use-bigpages=1
# sysctl -w kernel.shm-use-bigpages=1
To make the change permanent, add the following line to the file
/etc/sysctl.conf. This file is used during the boot process.
echo "kernel.shm-use-bigpages=1" >> /etc/sysctl.conf
echo "kernel.shm-use-bigpages=1" >> /etc/sysctl.conf
Setting
kernel.shm-use-bigpages to 2 enables the Big Pages feature for the shared memory file system (shmfs). Setting kernel.shm-use-bigpages to 0 disables the Big Pages feature. In Red Hat Enterprise Linux 2.1 the size of the Big Pages pool is configured by adding a parameter to the kernel boot command. For example, if you use GRUB and you want to set the Big Pages pool to 1000 MB, edit the /etc/grub.conf file and add the "bigpages" parameter as follows:
After this change the system must be rebooted:
shutdown -r now
# shutdown -r now
After a system reboot the 1000 MB Big Pages pool should show up under
BigPagesFree in /proc/meminfo.
grep BigPagesFree /proc/meminfo
grep BigPagesFree /proc/meminfo
Note that if
HighTotal in /proc/meminfo is 0 KB, then BigPagesFree will always be 0 KB as well since Big Pages can only be allocated and pinned above approximately 860MB of physical RAM.
14.6. Configuring Huge Pages in Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
Before configuring Big Pages, ensure to have read Section 14.3, “Sizing Big Pages and Huge Pages”.
In Red Hat Enterprise Linux 3 the desired size of the Huge Pages pool is specified in megabytes. The size of the pool should be configured by the incremental size of the Huge Page size. To obtain the size of Huge Pages, execute the following command:
grep Hugepagesize /proc/meminfo
$ grep Hugepagesize /proc/meminfo
Hugepagesize: 2048 kB
$
The number of Huge Pages can be configured and activated by setting
hugetlb_pool in the proc file system. For example, to allocate a 1GB Huge Page pool, execute:
echo 1024 > /proc/sys/vm/hugetlb_pool
# echo 1024 > /proc/sys/vm/hugetlb_pool
Alternatively, you can use
sysctl(8) to change it:
sysctl -w vm.hugetlb_pool=1024
# sysctl -w vm.hugetlb_pool=1024
To make the change permanent, add the following line to the file
/etc/sysctl.conf. This file is used during the boot process. The Huge Pages pool is usually guaranteed if requested at boot time:
echo "vm.hugetlb_pool=1024" >> /etc/sysctl.conf
# echo "vm.hugetlb_pool=1024" >> /etc/sysctl.conf
If you allocate a large number of Huge Pages, the execution of the above commands can take a while. To verify whether the kernel was able to allocate the requested number of Huge Pages, execute:
grep HugePages_Total /proc/meminfo
$ grep HugePages_Total /proc/meminfo
HugePages_Total: 512
$
The output shows that 512 Huge Pages have been allocated. Since the size of Huge Pages on this system is 2048 KB, a Huge Page pool of 1GB has been allocated and pinned in physical memory.
If
HugePages_Total is lower than what was requested with hugetlb_pool, then the system does either not have enough memory or there are not enough physically contiguous free pages. In the latter case the system needs to be rebooted which should give you a better chance of getting the memory.
To get the number of free Huge Pages on the system, execute:
grep HugePages_Free /proc/meminfo
$ grep HugePages_Free /proc/meminfo
Free system memory will automatically be decreased by the size of the Huge Pages pool allocation regardless whether the pool is being used by an application like Oracle database or not being used:
grep MemFree /proc/meminfo
$ grep MemFree /proc/meminfo
After an Oracle database starts up, verify the Huge Pages usage. The number of free Huge Pages should decrease.
grep HugePages_Free /proc/meminfo
$ grep HugePages_Free /proc/meminfo
To free the Huge Pages pool, you can execute:
echo 0 > /proc/sys/vm/hugetlb_pool
# echo 0 > /proc/sys/vm/hugetlb_pool
This command usually takes a while to finish.
14.7. Configuring Huge Pages in Red Hat Enterprise Linux 4 or 5
링크 복사링크가 클립보드에 복사되었습니다!
Before configuring Big Pages, ensure to have read Section 14.3, “Sizing Big Pages and Huge Pages”.
In Red Hat Enterprise Linux 4 or 5 the size of the Huge Pages pool is specified by the desired number of Huge Pages. To calculate the number of Huge Pages you first need to know the Huge Page size. To obtain the size of Huge Pages, execute the following command:
grep Hugepagesize /proc/meminfo
$ grep Hugepagesize /proc/meminfo
Hugepagesize: 2048 kB
$
The output shows that the size of a Huge Page on this system is 2MB. This means if a 1GB Huge Pages pool should be allocated, then 512 Huge Pages need to be allocated. The number of Huge Pages can be configured and activated by setting
nr_hugepages in the proc file system. For example, to allocate 512 Huge Pages, execute:
echo 512 > /proc/sys/vm/nr_hugepages
# echo 512 > /proc/sys/vm/nr_hugepages
Alternatively, you can use
sysctl(8) to change it:
sysctl -w vm.nr_hugepages=512
# sysctl -w vm.nr_hugepages=512
To make the change permanent, add the following line to the file
/etc/sysctl.conf. This file is used during the boot process. The Huge Pages pool is usually guaranteed if requested at boot time:
echo "vm.nr_hugepages=512" >> /etc/sysctl.conf
# echo "vm.nr_hugepages=512" >> /etc/sysctl.conf
If you allocate a large number of Huge Pages, the execution of the above commands can take a while. To verify whether the kernel was able to allocate the requested number of Huge Pages, run:
grep HugePages_Total /proc/meminfo
$ grep HugePages_Total /proc/meminfo
HugePages_Total: 512
$
The output shows that 512 Huge Pages have been allocated. Since the size of Huge Pages is 2048 KB, a Huge Page pool of 1GB has been allocated and pinned in physical memory.
If
HugePages_Total is lower than what was requested with nr_hugepages, then the system does either not have enough memory or there are not enough physically contiguous free pages. In the latter case the system needs to be rebooted which should give you a better chance of getting the memory.
To get the number of free Huge Pages on the system, execute:
grep HugePages_Free /proc/meminfo
$ grep HugePages_Free /proc/meminfo
Free system memory will automatically be decreased by the size of the Huge Pages pool allocation regardless whether the pool is being used by an application like Oracle DB or not:
grep MemFree /proc/meminfo
$ grep MemFree /proc/meminfoNote
In order that an Oracle database can use Huge Pages in Red Hat Enterprise Linux 4 or 5, you also need to increase the
ulimit parameter "memlock" for the oracle user in /etc/security/limits.conf if "max locked memory" is not unlimited or too small, see ulimit -a or ulimit -l. An example can be seen below.
oracle soft memlock 1048576 oracle hard memlock 1048576
oracle soft memlock 1048576
oracle hard memlock 1048576
The
memlock parameter specifies how much memory the oracle user can lock into its address space. Note that Huge Pages are locked in physical memory. The memlock setting is specified in KB and must match the memory size of the number of Huge Pages that Oracle should be able to allocate. So if the Oracle database should be able to use 512 Huge Pages, then memlock must be set to at least 512 * Hugepagesize, which on this system would be 1048576 KB (512*1024*2). If memlock is too small, then no single Huge Page will be allocated when the Oracle database starts. For more information on setting shell limits, see Chapter 22, Setting Shell Limits for Your Oracle User.
Log in as the oracle user again and verify the new memlock setting by executing
ulimit -l before starting the database.
After an Oracle DB startup you can verify the usage of Huge Pages by checking whether the number of free Huge Pages has decreased:
grep HugePages_Free /proc/meminfo
$ grep HugePages_Free /proc/meminfo
To free the Huge Pages pool, you can execute:
echo 0 > /proc/sys/vm/nr_hugepages
# echo 0 > /proc/sys/vm/nr_hugepages
This command usually takes a while to finish.
Chapter 15. Growing the Oracle SGA to 2.7 GB in x86 Red Hat Enterprise Linux 2.1 Without VLM
링크 복사링크가 클립보드에 복사되었습니다!
15.1. General
링크 복사링크가 클립보드에 복사되었습니다!
Due to 32 bit virtual address limitations workarounds have been implemented in Linux to increase the maximum size for shared memories. The workaround is to lower the Mapped Base Address (
mapped_base) for shared libraries and the SGA Attach Address for shared memory segments. Lowering the Mapped Base Address and the SGA Attach Address allows SGA sizes up to 2.7 GB. By default, the shared memory segment size can only be increased to roughly 1.7 GB in Red Hat Enterprise Linux 2.1.
To better understand the process of lowering the Mapped Base Address for shared libraries and the SGA Attach Address for shared memory segments, a basic understanding of the Linux memory layout is necessary.
15.2. Linux Memory Layout
링크 복사링크가 클립보드에 복사되었습니다!
The 4 GB address space in 32 bit x86 Linux is usually split into different sections for every process on the system:
- 0GB-1GB User space - Used for text, code and
brk/sbrkallocations.mallocusesbrkfor small chunks. - 1GB-3GB User space - Used for shared libraries, shared memory, and the stack. Shared memory and
mallocusemmap.mallocusesmmapfor large chunks. - 3GB-4GB Kernel Space - Used by and for the kernel itself
In older Linux systems the split between
brk(2) and mmap(2) was changed by setting the kernel parameter TASK_UNMAPPED_BASE and by recompiling the kernel. However, on all Red Hat Enterprise Linux systems this parameter can be changed dynamically as will be shown later. The mmap allocated memory grow bottom up from 1GB and the stack grows top down from around 3GB. The split between userspace and kernelspace is set by the kernel parameter PAGE_OFFSET which is usually 0xc0000000 (3GB).
By default, in Red Hat Enterprise Linux 2.1 the address space between
0x40000000 (1 GB) and 0xc0000000 (3 GB) is available for mapping shared libraries and shared memory segments. The default mapped base for loading shared libraries is 0x40000000 (1 GB) and the SGA attach address for shared memory segments is above the shared libraries. In Oracle 9i on Red Hat Enterprise Linux 2.1 the default SGA attach address for shared memory is 0x50000000 (1.25 GB) where the SGA is mapped. This leaves 0.25 GB space for loading shared libraries between 0x40000000 (1 GB) and 0x50000000 (1.25 GB).
The address mappings of processes can be checked by viewing the proc file
/proc/<pid>/maps where pid stands for the process ID. Here is an example of a default address mapping of an Oracle 9i process in Red Hat Enterprise Linux 2.1:
As this address mapping shows, shared libraries start at
0x40000000 (1 GB) and System V shared memory, in this case SGA, starts at 0x50000000 (1.25 GB). Here is a summary of all the entries:
The text (code) section is mapped at 0x08048000:
08048000-0ab11000 r-xp 00000000 08:09 273078 /ora/product/9.2.0/bin/oracle
08048000-0ab11000 r-xp 00000000 08:09 273078 /ora/product/9.2.0/bin/oracle
The data section is mapped at 0x0ab11000:
0ab11000-0ab99000 rw-p 02ac8000 08:09 273078 /ora/product/9.2.0/bin/oracle
0ab11000-0ab99000 rw-p 02ac8000 08:09 273078 /ora/product/9.2.0/bin/oracle
The uninitialized data segment .bss is allocated at 0x0ab99000:
0ab99000-0ad39000 rwxp 00000000 00:00 0
0ab99000-0ad39000 rwxp 00000000 00:00 0
The base address for shared libraries is 0x40000000:
40000000-40016000 r-xp 00000000 08:01 16 /lib/ld-2.2.4.so
40000000-40016000 r-xp 00000000 08:01 16 /lib/ld-2.2.4.so
The base address for System V shared memory, in this case SGA, is 0x50000000:
50000000-50400000 rw-s 00000000 00:04 163842 /SYSV00000000 (deleted)
50000000-50400000 rw-s 00000000 00:04 163842 /SYSV00000000 (deleted)
The stack is allocated at 0xbfffb000:
bfffb000-c0000000 rwxp ffffc000 00:00 0
bfffb000-c0000000 rwxp ffffc000 00:00 015.3. Increasing Space for the SGA in Red Hat Enterprise Linux 2.1
링크 복사링크가 클립보드에 복사되었습니다!
To increase the maximum default size of shared memory for the SGA from 1.7 GB to 2.7GB, the Mapped Base Address (
mapped_base) for shared libraries must be lowered from 0x40000000 (1 GB) to 0x10000000 (0.25 GB) and the SGA Attach Address for shared memory segments must be lowered from 0x50000000 (1.25 GB) to 0x15000000 (336 MB). Lowering the SGA attach address increases the available space for shared memory almost 1 GB. If shared memory starts at 0x15000000 (336 MB), then the space between 0x15000000 (336 MB) and 0xc0000000 (3GB) minus stack size becomes available for the SGA. Note the mapped base for shared libraries should not be above the SGA attach address, example, between 0x15000000 (336 MB) and 0xc0000000 (3GB).
To increase the space for shared memory in Red Hat Enterprise Linux 2.1, the mapped base for shared libraries for the Oracle processes must be changed by root. And the oracle user must relink Oracle to relocate or lower the SGA attach address for shared memory segments.
16.1. General
링크 복사링크가 클립보드에 복사되었습니다!
Due to 32 bit virtual address limitations workarounds have been implemented in Linux to increase the maximum size for shared memories. A workaround is to lower the Mapped Base Address for shared libraries and the SGA Attach Address for shared memory segments. This enables Oracle to attain an SGA larger than 1.7 GB. To get a better understanding of address mappings in Linux and what Mapped Base Address is, see Section 15.2, “Linux Memory Layout”.
The following example shows how to increase the size of the SGA without a shared memory file system. A shared memory file system must be used on x86 to increase SGA beyond 3.42 GB, see Section 14.8, “Huge Pages and Shared Memory File System in Red Hat Enterprise Linux 3”.
16.3. Oracle 10g SGA Sizes in Red Hat Enterprise Linux 3, 4 or 5
링크 복사링크가 클립보드에 복사되었습니다!
The following table shows how large the Oracle 10g SGA can be configured in Red Hat Enterprise Linux 3, 4 or 5 without using a shared memory file system. Shared memory file systems for the SGA are covered at Section 14.8, “Huge Pages and Shared Memory File System in Red Hat Enterprise Linux 3”Configuring Very Large Memory (VLM).
| Red Hat Enterprise Kernel Type | 10g Database Version | Default Supported SGA without VLM | Max Supported SGA without VLM | Comments |
|---|---|---|---|---|
| smp kernel (x86) | 10g Release 1 | Up to 1.7 GB | Up to 2.7 GB | 10g R1 must be relinked to increase the SGA size to approx 2.7 GB |
| hugemem kernel (x86) | 10g Release 1 | Up to 2.7 GB | Up to 3.42 GB | 10g R1 must be relinked to increase the SGA size to approx 3.42 GB |
| smp kernel (x86) | 10g Release 2 | Up to ~2.2 GB (*) | Up to ~2.2 GB (*) | No relink of 10g R2 is necessary but the SGA Attach Address is a little bit higher than in R1 |
| hugemem kernel (x86) | 10g Release 2 | Up to ~3.3 GB (*) | Up to ~3.3 GB (*) | No relink of 10g R2 is necessary but the SGA Attach Address is a little bit higher than in R1 |
(*) When performing test scenarios with 10g R2 the database was not able to start up if sga_target was larger than 2350000000 bytes on a smp kernel, and if sga_target was larger than 3550000000 bytes on a hugemem kernel.
In Oracle 10g R2 the SGA size can be increased to approximately 2.7 GB using the smp kernel and to approximately 3.42 GB using the hugemem kernel. The SGA attach address does not have to be changed for that. To accommodate the same SGA sizes in Oracle 10g R1, the Section 16.4, “Lowering the SGA Attach Address in Oracle 10g” must be lowered.
Note
Lowering the SGA attach address in Oracle restricts the remaining 32 bit address space for Oracle processes. This means that less address space will be available for e.g. PGA memory. If the application uses a lot of PGA memory, then PGA allocations could fail even if there is sufficient free physical memory. Therefore, in certain cases it may be prudent not to change the SGA Attach Address to increase the SGA size but to use Chapter 17, Using Very Large Memory (VLM) instead. Also, if the SGA size is larger but less than 4GB to fit in memory address space, then the Chapter 17, Using Very Large Memory (VLM) solution should be considered first before switching to the hugemem kernel on a small system, unless the system has lots of physical memory. The hugemem kernel is not recommended on systems with less than 8GB of RAM due to some overhead issues in the kernel, see also Section 2.2, “32 bit Architecture and the hugemem Kernel”. If larger SGA sizes are needed than listed in the above table, then Chapter 17, Using Very Large Memory (VLM) must obviously be used on x86 platforms.
16.4. Lowering the SGA Attach Address in Oracle 10g
링크 복사링크가 클립보드에 복사되었습니다!
Starting with Oracle 10g R2 the SGA attach address does not have to be lowered for creating larger SGAs. However, Oracle 10g R1 must be relinked for larger SGAs.
The following commands were executed on a 10g R1 database system:
ps -ef | grep "[o]ra_ckpt" cat /proc/3035/maps | grep SYSV
# ps -ef | grep "[o]ra_ckpt"
oracle 3035 1 0 23:21 ? 00:00:00 ora_ckpt_orcl
# cat /proc/3035/maps | grep SYSV
50000000-aa200000 rw-s 00000000 00:04 262144 /SYSV8b1d1510 (deleted)
#
The following commands were executed on a 10g R2 database system:
ps -ef | grep "[o]ra_ckpt" cat /proc/4998/maps | grep SYSV
# ps -ef | grep "[o]ra_ckpt"
oracle 4998 1 0 22:29 ? 00:00:00 ora_ckpt_orcl
# cat /proc/4998/maps | grep SYSV
20000000-f4200000 rw-s 00000000 00:04 4390912 /SYSV950d1f70 (deleted)
#
The output shows that the SGA attach address in 10g R2 is already lowered to 0x20000000 vs. 0x50000000 in 10g R1. This means that Oracle 10g R2 does not have to be relinked for creating larger SGAs. For 10g R1 the SGA attach address must be lowered from 0x50000000 to e.g. 0xe000000. You could also set it a little bit higher like 0x20000000 as its done by default in 10g Release 2.
The following example shows how to lower the SGA attach address to 0xe000000 in 10g R1 (see also Metalink Note:329378.1):
For a detailed description of these commands, see Lowering the SGA Attach Address for Shared Memory Segments in Oracle 9i.
You can verify the new lowered SGA attach address by running the following command:
objdump -t $ORACLE_HOME/bin/oracle |grep sgabeg
$ objdump -t $ORACLE_HOME/bin/oracle |grep sgabeg
0e000000 l *ABS* 00000000 sgabeg
$
Now when 10g R1 is restarted the SGA attach address should be at 0xe000000:
ps -ef | grep "[o]ra_ckpt" cat /proc/4998/maps | grep SYSV
# ps -ef | grep "[o]ra_ckpt"
oracle 4998 1 0 22:29 ? 00:00:00 ora_ckpt_orcl
# cat /proc/4998/maps | grep SYSV
0e000000-c1200000 rw-s 00000000 00:04 0 /SYSV8b1d1510 (deleted)
#
Now you should be able to create larger SGAs.
Note
If you increase the size of the SGA, essentially using more process address space for the SGA, then less address space will be available for PGA memory. This means that if your application uses a lot of PGA memory, PGA allocations could fail even if you have sufficient RAM. In this case, you need to set the SGA attach address to a higher value which will lower the SGA size.
Chapter 17. Using Very Large Memory (VLM)
링크 복사링크가 클립보드에 복사되었습니다!
17.1. General
링크 복사링크가 클립보드에 복사되었습니다!
This chapter does not apply to x86-64 (64 bit) systems.
With hugemem kernels on 32 bit systems, the SGA size can be increased but not significantly as shown at Section 16.3, “Oracle 10g SGA Sizes in Red Hat Enterprise Linux 3, 4 or 5”. Note the hugemem kernel is always recommended on systems with large amounts of RAM, see Section 2.2, “32 bit Architecture and the hugemem Kernel”. This chapter shows how the SGA can be significantly increased using VLM on 32 bit systems.
Starting with Oracle9i Release 2 the SGA can theoretically be increased to about 62 GB (depending on block size) on a 32 bit system with 64 GB RAM. A processor feature called Page Address Extension (PAE) provides the capability of physically addressing 64 GB of RAM. However, it does not enable a process or program to address more than 4GB directly or have a virtual address space larger than 4GB. Hence, a process cannot attach to shared memory directly if it has a size of 4GB or more. To address this issue, a shared memory file system (memory-based file system) can be created which can be as large as the maximum allowable virtual memory supported by the kernel. With a shared memory file system processes can dynamically attach to regions of the file system allowing applications like Oracle to have virtually a much larger shared memory on 32 bit systems. This is not an issue on 64 bit systems.
For Oracle to use a shared memory file system, a feature called Very Large Memory (VLM) must be enabled. VLM moves the database buffer cache part of the SGA from the System V shared memory to the shared memory file system. It is still considered one large SGA but it consists now of two different OS shared memory entities. It is noteworthy to say that VLM uses 512MB of the non-buffer cache SGA to manage VLM. This memory area is needed for mapping the indirect data buffers (shared memory file system buffers) into the process address space since a process cannot attach to more than 4GB directly on a 32 bit system. For example, if the non-buffer cache SGA is 2.5 GB, then you will only have 2 GB of non-buffer cache SGA for shared pool, large pool, and redo log buffer since 512MB is used for managing VLM. If the buffer cache is less than 512 MB, then the
init.ora parameter VLM_WINDOW_SIZE must be changed to reflect the size of the database buffer cache. However, it is not recommended to use VLM if db_block_buffers is not greater than 512MB.
In Red Hat Enterprise Linux 3, 4 and 5 there are two different memory file systems that can be used for VLM:
shmfs/tmpfs: This memory file system is pageable and swappable and cannot be backed by Huge Pages because Huge Pages are not swappable.ramfs: This memory file systems is not pageable or swappable and not backed by Huge Pages, see also Huge Pages and Shared Memory File System in Red Hat Enterprise Linux 3 and 4.
Note that the
shmfs file system is available in Red Hat Enterprise Linux 3 but not in Red Hat Enterprise Linux 4 or 5:
This means that if you try to mount a shmfs file system in Red Hat Enterprise Linux 4 or 5, you will get the following error message:
mount: fs type shm not supported by kernel
mount: fs type shm not supported by kernel
The difference between shmfs and tmpfs is you do not need to specify the size of the file system if you
mount a tmpfs file system.
17.2. Configuring Very Large Memory (VLM)
링크 복사링크가 클립보드에 복사되었습니다!
The following example shows how to use the RAM disk ramfs to allocate 8 GB of shared memory for the Oracle 10g database buffer cache on a 32 bit Red Hat Enterprise Linux 3, 4 or 5 systems (hugemem kernel). If this setup is performed on a server that does not have enough RAM, then Linux will appear to hang and the kernel will automatically start killing processes due to memory shortage (
ramfs is not swappable). Furthermore, ramfs is not backed by Huge Pages and therefore the Huge Pages pool should not be increased for database buffers, see Chapter 6, Swap Space. In fact, if there are too many Huge Pages allocated, then there may not be enough memory for ramfs.
Since ramfs is not swappable, it is by default only usable by root. If you put too much on a ramfs file system, you can easily hang the system. To mount the ramfs file system and to make it usable for the Oracle account, execute:
umount /dev/shm mount -t ramfs ramfs /dev/shm chown oracle:dba /dev/shm
# umount /dev/shm
# mount -t ramfs ramfs /dev/shm
# chown oracle:dba /dev/shm
When Oracle starts it will create a file in the
/dev/shm directory that corresponds to the extended buffer cache. Ensure to add the above lines to /etc/rc.local. If ointall is the primary group of the Oracle account, use chown oracle:oinstall /dev/shm instead. For security reasons you do not want to give anyone write access to the shared memory file system. Having write access to the ramfs file system allows you to allocate and pin a large chunk of memory in RAM. In fact, you can kill a machine by allocating too much memory in the ramfs file system.
To enable VLM, set the Oracle parameter
use_indirect_data_buffers to true:
use_indirect_data_buffers=true
use_indirect_data_buffers=true
For 10g R1 and R2 databases it is important to convert
DB_CACHE_SIZE and DB_xK_CACHE_SIZE parameters to DB_BLOCK_BUFFERS, and to remove SGA_TARGET if set. Otherwise you will get errors like these:
ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
ORA-00385: cannot enable Very Large Memory with new buffer cache parameters
Here is an example for configuring a 8 GB buffer cache for a 10g R2 database with Red Hat Enterprise Linux 3, 4 or 5
hugemem kernels:
use_indirect_data_buffers=true db_block_size=8192 db_block_buffers=1048576 shared_pool_size=2831155200
use_indirect_data_buffers=true
db_block_size=8192
db_block_buffers=1048576
shared_pool_size=2831155200
Note that
shmmax needs to be increased for shared_pool_size to fit into the System V shared memory. In fact, it should be slightly larger than the SGA size. Since shared_pool_size is less than 3 GB in this example, shmmax does not need to be larger than 3GB. The 8 GB indirect buffer cache will be in the RAM disk and hence it does not have to be accounted for in shmmax. On a 32 bit system the shmmax kernel parameter cannot be larger than 4GB, see also Section 7.3, “Setting SHMALL Parameter”.
In order to allow oracle processes to lock more memory into its address space for the VLM window size, the
ulimit parameter memlock must be changed for oracle. Ensure to set memlock in /etc/security/limits.conf to 3145728:
oracle soft memlock 3145728 oracle hard memlock 3145728 Login as Oracle again and check max locked memory limit: $ ulimit -l 3145728
oracle soft memlock 3145728
oracle hard memlock 3145728
Login as Oracle again and check max locked memory limit:
$ ulimit -l
3145728
If it is not working after a
ssh log in, then you may have to set the SSH parameter UsePrivilegeSeparation, see Chapter 22, Setting Shell Limits for Your Oracle User.
If
memlock is not set or too small, you will get error messages similar to this one:
ORA-27103: internal error Linux Error: 11: Resource temporarily unavailable
ORA-27103: internal error
Linux Error: 11: Resource temporarily unavailable
Now try to start the database. Note the database start up can take a while. Also, the
sqlplus banner or show sga may not accurately reflect the actual SGA size in older Oracle versions.
The 8GB file for the database buffer cache can be seen in the ramfs shared memory file system:
If the shared pool size is configured too large, you will get error messages similar to this one:
ORA-27103: internal error Linux Error: 12: Cannot allocate memory
ORA-27103: internal error
Linux Error: 12: Cannot allocate memoryPart II. Installing the Oracle Database 10g on Red Hat Enterprise Linux
링크 복사링크가 클립보드에 복사되었습니다!
Introduction and Information on Supported Setups for Oracle 10g
링크 복사링크가 클립보드에 복사되었습니다!
This article provides a step by step guide for installing Oracle Database 10g on Red Hat Enterprise Linux. This guide covers the following Oracle Database and Red Hat Linux versions:
| Oracle Database Version | Red Hat Enterprise Linux Version | Architecture | Comments |
|---|---|---|---|
| Oracle 10g R2 (10.2.0.1.0) | 4 and 5 | x86-64 | See also Oracle Database Installation Guide 10g Release 2 (10.2) for Linux x86-64. |
| Oracle 10g R2 (10.2.0.1.0) | 3, 4 and 5 | x86 | See also Oracle Database Release Notes 10g Release 2 (10.2) for Linux x86. |
| Oracle 10g R1 (10.1.0.3) | 4 | x86-64 | See also Oracle Database Installation Guide 10g Release 1 (10.1.0.3) for Linux x86-64 |
| Oracle 10g R1 (10.1.0.3) | 4 | x86 | See also Oracle Database Release Notes 10g Release 1 (10.1.0.3.0) for Linux x86. |
| Oracle 10g R1 (10.1.0.3) | 3 | x86-64 | See also Oracle Database Installation Guide 10g Release 1 (10.1.0.3) for Linux x86-64. |
| Oracle 10g R1 (10.1.0.3) | 3 | x86 | See also Oracle Database Installation Guide 10g Release 1 (10.1) for UNIX Systems. |
| Oracle 10g R1 (10.1.0.2) | 2.1 | x86 | See also Oracle Database Installation Guide 10g Release 1 (10.1) for UNIX Systems. |
For Validation and Certification information, see Oracle's Certification Matrices.
Chapter 18. Downloading and Unpacking Oracle 10g Installation Files
링크 복사링크가 클립보드에 복사되었습니다!
Download Oracle 10g (32 bit and 64 bit) for Linux from the following web site: http://otn.oracle.com/software/products/database/oracle10g/index.html
Note
To install an Oracle Database 10g (without RAC) you need to download the database file
ship.db.lnx32.cpio.gz, 10201_database_linux_x86_64.cpio or similar file.
Compute a cyclic redundancy check (CRC) checksum for the downloaded files and compare the checksum numbers against the numbers posted on the OTN website (where you downloaded the file from):
cksum ship.db.lnx32.cpio.gz
cksum ship.db.lnx32.cpio.gz
Uncompress the downloaded files:
gunzip ship.db.lnx32.cpio.gz
gunzip ship.db.lnx32.cpio.gz
Unpack
ship.db.lnx32.cpio:
Chapter 19. Pre-Installation Preparation and Verification
링크 복사링크가 클립보드에 복사되었습니다!
19.1. Verifying Memory and Swap Space
링크 복사링크가 클립보드에 복사되었습니다!
Oracle states that the system must have at least 512MB of RAM and 1GB of swap space or a swap space twice the size of the RAM. For systems with more than 2 GB of RAM it states the swap space can be between one and two times the size of the RAM. You might also want to read Swap Space.
To check the size of physical memory, execute:
grep MemTotal /proc/meminfo
grep MemTotal /proc/meminfo
To check the size of swap space, execute:
grep SwapTotal /proc/meminfo
grep SwapTotal /proc/meminfo19.2. Verifying Temporary(/tmp) Space
링크 복사링크가 클립보드에 복사되었습니다!
According to Oracle's documentation, the Oracle Universal Installer (
OUI) requires up to 400 MB of free space in the /tmp directory.
To check the space in
/tmp, run:
df /tmp
$ df /tmp
If you do not have enough space in the
/tmp file system, you can temporarily create a tmp directory in another file system. Here is how you can do this:
The
TEMP=/<AnotherFilesystem> file is used by Oracle. The TMPDIR=/<AnotherFilesystem> file is used by Linux programs like the linker "ld". Note as well <AnotherFilesystem> should be adjusted to fit your filesystem. When you are done with the Oracle installation, shut down Oracle and remove the temporary /tmp directory:
su - root rmdir /<AnotherFilesystem>/tmp unset TEMP unset TMPDIR
su - root
rmdir /<AnotherFilesystem>/tmp
unset TEMP
unset TMPDIR19.3. Verifying Software Packages (RPMs)
링크 복사링크가 클립보드에 복사되었습니다!
Before you install an Oracle Database 10g you need to check your system for required RPMs. Always use the latest stable RPMs and kernels for your system, Red Hat manages the repositories to ensure everything work safely, securely and accurately. This section contains a list Oracle Database versions and versions of Red Hat Enterprise Linux. The list details which packages are required and how to assess whether the correct RPMs are present.
For Oracle 10g R2 (64 bit), on Red Hat Enterprise Linux 4 and 5 x86-64 versions, the document Oracle Database Installation Guide 10g Release 2 (10.2) for Linux x86-64 lists the following required package versions or higher:
Note
Install the
libaio-0.3.96 RPM or a newer version, otherwise the OUI prerequisite check will fail.
To check if you are running the x86-64 kernel on a x86-64 platform, run:
uname -mi
# uname -mi
x86_64 x86_64
To check the RPMs, run:
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \
binutils compat-db control-center gcc gcc-c++ glibc glibc-common \
gnome-libs libstdc++ libstdc++-devel make pdksh sysstat xscreensaver \
libaio
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \
binutils compat-db control-center gcc gcc-c++ glibc glibc-common \
gnome-libs libstdc++ libstdc++-devel make pdksh sysstat xscreensaver \
libaio
It is important to have these x86-64 RPMs installed. The above command will list the architecture of each binary package. You will see that some RPMs are installed twice when you run this command (x86 RPM and x86-64 RPM). You need to ensure that all required x86-64 RPMs listed here are installed.
For Oracle 10g R2 (32 bit) on Red Hat Enterprise Linux 4 and 5 x86, the document Oracle Database Release Notes 10g Release 2 (10.2) for Linux x86 lists the following required package versions or higher:
Note
Install the
libaio-0.3.96 RPM or a newer version, otherwise the OUI prerequisite check will fail.
To check the RPMs, run:
rpm -q binutils compat-db control-center gcc gcc-c++ glibc glibc-common \ gnome-libs libstdc++ libstdc++-devel make pdksh sysstat xscreensaver libaio
rpm -q binutils compat-db control-center gcc gcc-c++ glibc glibc-common \
gnome-libs libstdc++ libstdc++-devel make pdksh sysstat xscreensaver libaio
For 10g R2 (32 bit) on Red Hat Enterprise Linux 3 x86, the document Oracle Database Installation Guide 10g Release 2 (10.2) for Linux x86 lists the following required package versions or higher:
Note
libaio-0.3.96 RPM or a newer version is required for the OUI to work successfully.
To check the RPMs, run:
rpm -q make gcc glibc compat-db compat-gcc compat-gcc-c++ compat-libstdc++ \ compat-libstdc++-devel openmotif21 setarch libaio
rpm -q make gcc glibc compat-db compat-gcc compat-gcc-c++ compat-libstdc++ \
compat-libstdc++-devel openmotif21 setarch libaio
For Oracle 10g R1 (64 bit) on Red Hat Enterprise Linux 3 x86-64, the document Oracle Database Installation Guide 10g Release 1 (10.1.0.3) for Linux x86-64 lists the following required package versions or higher:
To check if you are running the AMD64 or Intel 64(x86-64) kernel on an AMD64 or Intel 64 platform, run:
uname -mi
# uname -mi
x86_64 x86_64
To check the RPMs, run:
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \
make gcc glibc glibc-devel compat-db compat-gcc compat-gcc-c++ \
compat-libstdc++ compat-libstdc++-devel gnome-libs openmotif21 setarch \
libaio libaio-devel
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' \
make gcc glibc glibc-devel compat-db compat-gcc compat-gcc-c++ \
compat-libstdc++ compat-libstdc++-devel gnome-libs openmotif21 setarch \
libaio libaio-devel
It is important to have the right x86 and x86-64 RPMs installed. The above command will list the architecture of each binary package. And as you can see in the above list, glibc-devel and other RPMs are listed twice. This means that you have to install packages for both architectures, x86 and x86-64.
For Oracle 10g R1 (32 bit) on Red Hat Enterprise Linux 3 x86, the document Oracle Database Installation Guide 10g Release 1 (10.1) for UNIX Systems lists the following required package versions or higher:
To check the RPMs, run:
rpm -q make gcc glibc compat-db compat-gcc compat-gcc-c++ compat-libstdc++ \ compat-libstdc++-devel openmotif21 setarch
rpm -q make gcc glibc compat-db compat-gcc compat-gcc-c++ compat-libstdc++ \
compat-libstdc++-devel openmotif21 setarch
For Oracle 10g R1 (32 bit) on Red Hat Enterprise Linux 2.1, the document Oracle Database Installation Guide 10g Release 1 (10.1) for UNIX Systems lists the following required package versions or higher:
To check these RPMs, run:
rpm -q make glibc gcc gcc-c++ libstdc++ openmotif
rpm -q make glibc gcc gcc-c++ libstdc++ openmotif
For Red Hat Enterprise Linux 3 and 2.1 it is also important to have
binutils-2.11.90.0.8-12 or a newer version installed. Make sure you have the binutils RPM installed on Red Hat Enterprise Linux 4 and 5 as well:
rpm -q binutils
rpm -q binutilsImportant
OUI for x86 will also complain if the
openmotif package is missing (do not confuse it with the openmotif21 package). Red Hat changed the version naming schema from openmotif-2.2.2-16 in the original release to openmotif-2.2.3-5.RHEL3.2 in Red Hat Enterprise Linux 3 Update 5. This seems to confuse OUI in Red Hat Enterprise Linux3 U5 since it complaining that it can not find the right openmotif version. You can ignore this. The openmotif-2.2.3-5.RHEL3.2 is just a newer version of openmotif-2.2.2-16 which should work fine and should not cause any problems. To check the RPM, run:
rpm -q openmotif
rpm -q openmotif
Also, make sure the redhat-release package is installed. Earlier versions of Red Hat Enterprise Linux may not install it by default when you selected a minimum system installation:
rpm -q redhat-release
rpm -q redhat-release
The
setarch utility is new in Red Hat Enterprise Linux 3 and 4. It is used to tell the kernel to report a different architecture than the current one. It is also used to emulate a 3GB virtual address space for applications that do not run properly with a larger virtual address space. To check the RPM, run:
rpm -q setarch
rpm -q setarch19.4. Verifying Kernel Parameters
링크 복사링크가 클립보드에 복사되었습니다!
To see all kernel parameters, execute:
su - root sysctl -a
su - root
sysctl -a
For Oracle 10g, the following kernel parameters have to be set to values greater than or equal to the recommended values which can be changed in the
proc file system:
To verify
shmmax, execute:
cat /proc/sys/kernel/shmmax shmmax = 2147483648
cat /proc/sys/kernel/shmmax
shmmax = 2147483648
To verify
shmmni, execute:
cat /proc/sys/kernel/shmmni shmmni = 4096
cat /proc/sys/kernel/shmmni
shmmni = 4096
To verify the
shmall parameter, execute the command below. shmall is used in 10g R1.
cat /proc/sys/kernel/shmall shmall = 2097152
cat /proc/sys/kernel/shmall
shmall = 2097152
To verify shmmin, execute:
ipcs -lm |grep "min seg size" shmmin = 1
ipcs -lm |grep "min seg size"
shmmin = 1
Note that
shmseg is hardcoded in the kernel, the default is much higher.
shmseg = 10
shmseg = 10
To verify
semmsl, execute:
cat /proc/sys/kernel/sem | awk '{print $1}'
semmsl = 250
cat /proc/sys/kernel/sem | awk '{print $1}'
semmsl = 250
To verify
semmns, execute:
cat /proc/sys/kernel/sem | awk '{print $2}'
semmns = 32000
cat /proc/sys/kernel/sem | awk '{print $2}'
semmns = 32000
To verify
semopm, execute:
cat /proc/sys/kernel/sem | awk '{print $3}'
semopm = 100
cat /proc/sys/kernel/sem | awk '{print $3}'
semopm = 100
To verify
semmni, execute:
cat /proc/sys/kernel/sem | awk '{print $4}'
semmni = 128
cat /proc/sys/kernel/sem | awk '{print $4}'
semmni = 128
To verify
file-max, execute:
cat /proc/sys/fs/file-max file-max = 65536
cat /proc/sys/fs/file-max
file-max = 65536
To verify
ip_local_port_range, execute:
cat /proc/sys/net/ipv4/ip_local_port_range ip_local_port_range = 1024 65000
cat /proc/sys/net/ipv4/ip_local_port_range
ip_local_port_range = 1024 65000Note
Do not change the value of any kernel parameter on a system where it is already higher than listed as minimum requirement.
On the following versions of Red Hat Enterprise Linux 4 x86, 3 U5 x86, 3 U5 x86-64, and 2.1; you may have to increase the kernel parameters
shmmax, semopm, and filemax to meet the minimum requirement. On Red Hat Enterprise Linux 4 x86-64 you may have to increase shmmax and semopm.
Oracle also recommends to set the local port range
ip_local_port_range for outgoing messages to "1024 65000" which is needed for high usage systems. This kernel parameter defines the local port range for TCP and UDP traffic to choose from.
In order to meet these requirements, you may have to add the following lines to the
/etc/sysctl.conf file which are read during the boot process:
kernel.shmmax=2147483648 kernel.sem=250 32000 100 128 fs.file-max=65536 net.ipv4.ip_local_port_range=1024 65000
kernel.shmmax=2147483648
kernel.sem=250 32000 100 128
fs.file-max=65536
net.ipv4.ip_local_port_range=1024 65000
Adding these lines to the
/etc/sysctl.conf file will cause the system to change these kernel parameters after each boot using the /etc/rc.d/rc.sysinit script which is invoked by /etc/inittab. But in order that these new added lines or settings in /etc/sysctl.conf become effective immediately, execute the following command:
su - root sysctl -p
su - root
sysctl -p
For more information on shmmax, shmmni, shmmin, shmseg, and shmall, see Chapter 7, Setting Shared Memory. For more information on semmsl, semmni, semmns, and semopm, see Chapter 24, Creating Oracle Directories. For more information on filemax, see Chapter 9, Setting File Handles.
Starting with 10g R2 some network settings must be adjusted as well which is checked by OUI. Oracle recommends the default and maximum send buffer size (
SO_SNDBUF socket option) and receive buffer size (SO_RCVBUF socket option) to be set to 256 KB. The receive buffers are used by TCP and UDP to hold the received data for the application until it is read. This buffer cannot overflow because the sending party is not allowed to send data beyond the buffer size window. This means that datagrams will be discarded if they do not fit in the receive buffer. This could cause the sender to overwhelm the receiver.
The default and maximum window size can be changed in the proc file system without reboot by running the following commands: The default setting in bytes of the socket receive buffer.
sysctl -w net.core.rmem_default=262144
# sysctl -w net.core.rmem_default=262144
The default setting in bytes of the socket send buffer.
sysctl -w net.core.wmem_default=262144
# sysctl -w net.core.wmem_default=262144
The maximum socket receive buffer size which may be set by using the SO_RCVBUF socket option.
sysctl -w net.core.rmem_max=262144
# sysctl -w net.core.rmem_max=262144
The maximum socket send buffer size which may be set by using the SO_SNDBUF socket option.
sysctl -w net.core.wmem_max=262144
# sysctl -w net.core.wmem_max=262144
To make the change permanent, add the following lines to the
/etc/sysctl.conf file, which is used during the boot process:
net.core.rmem_default=262144 net.core.wmem_default=262144 net.core.rmem_max=262144 net.core.wmem_max=262144
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144Chapter 20. Installing Required Software Packages
링크 복사링크가 클립보드에 복사되었습니다!
The following sections provide a detailed set of instructions for installing the required software packages(RPMs) before you install your Oracle Database 10g (R1 and R2). These sections include the following possible configurations:
- 10g R2 on Red Hat Enterprise Linux 4 and 5 (x86-64),
- 10g R2 on Red Hat Enterprise Linux 4 and 5 (x86),
- 10g R1 on Red Hat Enterprise Linux 4 and 5 (x86-64),
- 10g R1 on Red Hat Enterprise Linux 4 and 5 (x86),
- 10g R1 and R2 on Red Hat Enterprise Linux 3 (x86),
- 10g R1 on Red Hat Enterprise Linux 3 (x86-64), and
- 10g R1 on Red Hat Enterprise Linux 2.1 (x86).
20.1. 10g R2 on Red Hat Enterprise Linux 4 and 5 x86-64 version
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 4 x86-64 you may have to install the following RPMs and dependencies:
You also need to install the following i386 and x86-64 RPMs if not already installed, otherwise you will get various different error messages.
For a detailed list of error messages, read Chapter 29, Oracle 10g and Linux Installation Errors and Troubleshooting.
If you are yet to install Update 3 or later, do not forget to install an updated
binutils RPM from https://rhn.redhat.com/ or from http://oss.oracle.com/. This command will install the newer version of binutils, remember to change the version number if the one you downloaded is newer.
rpm -Uvh --force binutils-2.15.92.0.2-13.0.0.0.2.x86_64.rpm
rpm -Uvh --force binutils-2.15.92.0.2-13.0.0.0.2.x86_64.rpm
If you do not install a newer binutil RPM from Oracle or RHN, then you will get the following error message:
/usr/bin/ld: /u01/app/oracle/oracle/product/10.2.0/db_1/lib//libirc.a(fast_memcpy.o):
relocation R_X86_64_PC32 against `_memcpy_mem_ops_method' can not
be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
/usr/bin/ld: /u01/app/oracle/oracle/product/10.2.0/db_1/lib//libirc.a(fast_memcpy.o):
relocation R_X86_64_PC32 against `_memcpy_mem_ops_method' can not
be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: Bad value
collect2: ld returned 1 exit status
For more information on this bug, see Bugzilla Bug 679.
Oracle lists the
control-center and xscreensaver RPMs as a requirements. But you should not have any problems when these RPMs are missing. But if you want to install them, you may have to install many additional RPMs in order to satisfy dependencies:
20.2. 10g R2 on Red Hat Enterprise Linux 4 and 5 (x86)
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 4 and 5 x86 you may have to install the following RPMs and dependencies to meet the software requirements:
Oracle lists the
control-center and xscreensaver RPMs as a requirements. But you should not have any problems when these RPMs are missing. If you want to install them, you may have to install many additional RPMs in order to satisfy dependencies.
20.3. 10g R1 on Red Hat Enterprise Linux 4 and 5 (x86-64)
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 4 x86-64 you may have to install the following RPMs and dependencies:
20.4. 10g R1 on Red Hat Enterprise Linux 4 and 5 (x86)
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 4 x86 you may have to install the following RPMs and dependencies to meet the software requirements:
Note
The 10g 10.1.0.3 OUI Product specific prerequisite check will fail for the
gcc, binutils, and openmotif versions. You can ignore these failed checks and proceed.
Important
The redhat-release RPM should already be installed by default. But note that 10.1.0.3.0 OUI does not recognize Red Hat Enterprise Linux 4 or 5 as a supported release yet. This means you will have to edit the
/etc/redhat-release file, see below, or you apply the 4153257 patch for 10g R1 on Red Hat Enterprise Linux 4 and 5.
20.5. Oracle 10g R1 and R2 on Red Hat Enterprise Linux 3 (x86)
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 3 x86 you may have to install the following RPMs and dependencies to meet the software requirements:
20.6. Oracle 10g R1 on Red Hat Enterprise Linux 3 (x86_64)
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 3 x86_64 you may have to install the following RPMs and dependencies to meet the software requirements:
Note: Red Hat Enterprise Linux 3 x86-64 U5 does not come with a i386 gnome-libs RPM
Note: Red Hat Enterprise Linux 3 x86-64 U5 does not come with a x86-64 openmotif21 RPM
Make sure to use the right i386 and x86_64 RPMs as listed above.
Note, if you do not install the i386
XFree86-libs RPM, you will get an error message similar to this one:
/tmp/OraInstall2005-06-15_07-36-25AM/jre/1.4.2/lib/i386/libawt.so: \ libXp.so.6: cannot open shared object file: No such file or directory
/tmp/OraInstall2005-06-15_07-36-25AM/jre/1.4.2/lib/i386/libawt.so: \
libXp.so.6: cannot open shared object file: No such file or directory
For more information, see Chapter 29, Oracle 10g and Linux Installation Errors and Troubleshooting.
20.7. Oracle 10g R1 on Red Hat Enterprise Linux 2.1 (x86)
링크 복사링크가 클립보드에 복사되었습니다!
On Red Hat Enterprise Linux 2.1 x86 you may have to install the following RPMs and dependencies to meet the software requirements:
You may have to upgrade
glibc in order to pass Oracle's "Product-specific Prerequisite" checks. Oracle's recommended glibc version is 2.2.4.31.7 or higher.
There is no setarch RPM for Red Hat Enterprise Linux 2.1.
Also, it is important to install a newer kernel version for Red Hat Enterprise Linux 2.1. Do not use a kernel older than 2.4.9-e.25. To check the kernel version run
uname -r.
20.8. Verifying and Updating the redhat-release File
링크 복사링크가 클립보드에 복사되었습니다!
Verify that the redhat-release RPM is installed on your Red Hat system:
rpm -q redhat-release
rpm -q redhat-release
This RPM is important for Red Hat Enterprise Linux since Red Hat Enterprise Linux 2.1, 3, 4 and 5 are Linux releases supported by Oracle. Without this RPM, Oracle 10g OUI will not be able to recognize it as a supported OS. However, the installer of 10g 10.1.0.3 does not recognize Red Hat Enterprise Linux 4 as a supported release yet. This means that you will have to edit the
/etc/redhat-release file. It is not recommend to execute "runInstaller -ignoreSysPrereqs" since this will disable other checks you may need.
On Red Hat Enterprise Linux 4 (for 10g R1) you have to change the
/etc/redhat-release file to make Oracle 10g believe it is running on a supported release.
Regarding Red Hat Enterprise Linux 4, the installer for 10g 10.1.0.3 does not recognize Red Hat Enterprise Linux 4 as a supported release but 10g R2 OUI does.
To change the
/etc/redhat-release file, you can simply copy and paste the following commands:
su - root # cp /etc/redhat-release /etc/redhat-release.orig # cat > /etc/redhat-release << EOF Red Hat Enterprise Linux AS release 3 (Taroon) EOF
su - root
# cp /etc/redhat-release /etc/redhat-release.orig
# cat > /etc/redhat-release << EOF
Red Hat Enterprise Linux AS release 3 (Taroon)
EOF
After you are done with the Oracle 10g installation, undo the changes you made to
/etc/redhat-release:
su - root # cp /etc/redhat-release.orig /etc/redhat-release
su - root
# cp /etc/redhat-release.orig /etc/redhat-releaseChapter 21. Sizing Disk Space for Oracle 10g
링크 복사링크가 클립보드에 복사되었습니다!
Oracle says that about 2.5 GB of disk space should be reserved for the Oracle software on Linux.
Here are examples to check a file system:
du -m -s /u01 du -m -s /u01/app/oracle/oradata
$ du -m -s /u01
1963 /u01
$ du -m -s /u01/app/oracle/oradata
720 /u01/app/oracle/oradata
If you also install additional software from the Oracle Database 10g Companion CD, then add at least 1 GB of free disk space.
So if you install Oracle 10g Enterprise Edition and additional software from the Oracle Database 10g Companion CD, then you need about 2.5 GB of disk for the Oracle software. And if you also want to add a pre-configured database on the same file system, make sure to add another 1 GB of disk space.
Note
If you do not put Oracle 10g on a separate file systems, then make sure the root file system "
/" has enough disk space. You can check the free space of the root file system with the following command:
df -h /
df -h /Chapter 22. Setting Shell Limits for Your Oracle User
링크 복사링크가 클립보드에 복사되었습니다!
Most shells like Bash provide control over various resources like the maximum allowable number of open file descriptors or the maximum number of processes available to a user. For more information on
ulimit for Bash, see man bash and search for ulimit.
If you just install a small test database, then you might be fine with the current settings. Please note that the limits very often vary from system to system. But for larger, production databases, you should increase the following shell limits to the following values recommended by Oracle:
nofile = 65536
nofile = 65536
To verify the above command execute
ulimit -n.
nproc = 16384
nproc = 16384
To verify the above command execute
ulimit -u.
The
nofile option denotes the maximum number of open file descriptors, and nproc denotes the maximum number of processes available to a single user.
To see all shell limits, execute:
ulimit -a
ulimit -a
The following procedures and links show how to increase these parameters for the
oracle user account:
- For more information on
nofileand how to increase the limit, see Section 11.1, “Limiting Maximum Number of Open File Descriptors for the Oracle User”. - For information on
nprocand how to increase the limit, see Section 11.2, “Limiting Maximum Number of Processes Available for the Oracle User”.
Chapter 23. Creating Oracle User Accounts
링크 복사링크가 클립보드에 복사되었습니다!
To create the oracle account and groups, execute the following commands:
su - root groupadd dba # group of users to be granted SYSDBA system privilege groupadd oinstall # group owner of Oracle files useradd -c "Oracle software owner" -g oinstall -G dba oracle passwd oracle
su - root
groupadd dba # group of users to be granted SYSDBA system privilege
groupadd oinstall # group owner of Oracle files
useradd -c "Oracle software owner" -g oinstall -G dba oracle
passwd oracle
For more information on the "
oinstall" group account, see when to use "OINSTALL" group during install of oracle.
Chapter 24. Creating Oracle Directories
링크 복사링크가 클립보드에 복사되었습니다!
For Oracle 10g you only need to create the directory for
$ORACLE_BASE:
su - root mkdir -p /u01/app/oracle chown oracle.oinstall /u01/app/oracle
su - root
mkdir -p /u01/app/oracle
chown oracle.oinstall /u01/app/oracle
If you want to comply with Oracle's Optimal Flexible Architecture (OFA), then you do not want to place the database files in the
/u01 directory but in another directory, file system or disk such as /u02:
su - root mkdir -p /u02/oradata/orcl chown oracle.oinstall /u02/oradata/orcl
su - root
mkdir -p /u02/oradata/orcl
chown oracle.oinstall /u02/oradata/orcl
In this example, "
orcl" stands for the name of the database which will also be the name of the instance. This is typically the case for single instance databases.
24.1. Optimal Flexible Architecture (OFA) for 10g R1 (10.1.0.2)
링크 복사링크가 클립보드에 복사되었습니다!
The OFA standard is a guideline created by Oracle to ensure reliable Oracle installations. For Oracle 10g Database, the OFA recommended Oracle home path has changed.
The home path for the first 10g (10.1.0) database installation on a system would be:
/u01/app/oracle/product/10.1.0/db_1
/u01/app/oracle/product/10.1.0/db_1
If you would install a second Oracle 10g Database 10g (10.1.0) on the same system, the Oracle home directory should be as follows:
/u01/app/oracle/product/10.1.0/db_2
/u01/app/oracle/product/10.1.0/db_2
If the Oracle 10g software is not owned by the user
oracle but by the user "oraowner", then the path of the Oracle home directory would be:
/u01/app/oraowner/product/10.1.0/db_1 /u01/app/oraowner/product/10.1.0/db_2
/u01/app/oraowner/product/10.1.0/db_1
/u01/app/oraowner/product/10.1.0/db_2
The standard directory name for Oracle 10g is "
app":
/u01/app/oracle/product/10.1.0/db_1
/u01/app/oracle/product/10.1.0/db_1
Oracle recommends to use mount points such as
/u01, /u02, and so on, complies with the OFA guidelines. But others can be used, for example:
/disk_1/app/oracle/product/10.1.0/db_1
/disk_1/app/oracle/product/10.1.0/db_1
The subtree for database files not stored in ASM disk groups should be named as follows:
/u02/oradata/<db_name_1> /u02/oradata/<db_name_2> /u03/oradata/<db_name_1> /u03/oradata/<db_name_2>
/u02/oradata/<db_name_1>
/u02/oradata/<db_name_2>
/u03/oradata/<db_name_1>
/u03/oradata/<db_name_2>
The mount point
/u01 should be used for the Oracle software only. /u02, /u03, /u04 and so on, should be used for the database files. The db_name represents the DB_NAME initialization parameter which is typically the same as the SID name for single instance databases.
Chapter 25. Setting Oracle Environments
링크 복사링크가 클립보드에 복사되었습니다!
Since the Oracle Universal Installer (OUI) "runInstaller" is run from the oracle account, some environment variables must be configured for this account before OUI is started.
Execute the following commands for the
Bash which is the default shell on Red Hat Enterprise Linux, to verify your shell run: echo $SHELL):
su - oracle export ORACLE_BASE=/u01/app/oracle export ORACLE_SID=orcl
su - oracle
export ORACLE_BASE=/u01/app/oracle
export ORACLE_SID=orclNote
If
ORACLE_BASE is used, then Oracle recommends that you do not set the ORACLE_HOME environment variable but that you choose the default path suggested by the OUI. You can set and use ORACLE_HOME after you finished running OUI.
The environment variables
ORACLE_HOME and TNS_ADMIN should not be set. If you set these environment variables, you can unset them by running the following commands:
unset ORACLE_HOME unset TNS_ADMIN
unset ORACLE_HOME
unset TNS_ADMIN
To have these environment variables set automatically each time you log on as
oracle, you can add these environment variables to the ~oracle/.bash_profile file which is the user start up file for the Bash on Red Hat Enterprise Linux. To do this you could simply copy and paste the following commands to make these settings permanent for your oracle accounts Bash shell:
su - oracle cat >> ~oracle/.bash_profile << EOF export ORACLE_BASE=/u01/app/oracle export ORACLE_SID=orcl EOF
su - oracle
cat >> ~oracle/.bash_profile << EOF
export ORACLE_BASE=/u01/app/oracle
export ORACLE_SID=orcl
EOFChapter 26. Installing Oracle Database 10g
링크 복사링크가 클립보드에 복사되었습니다!
This Chapter will guide you through the process of installing an Oracle 10g Database.
26.1. Installing Oracle 10g on a Remote Linux Server
링크 복사링크가 클립보드에 복사되었습니다!
If you want to install Oracle on a remote server, then you need to relink
X to your local desktop. The easiest way to do this is to use the "X11 forwarding" feature of ssh. This means that you do not have to run xhost and set the DISPLAY environment variable. Here is an example how to make use of the X11 forwarding feature of ssh. Simply run the following command from your local desktop:
ssh -X oracle@oracle_remote_server_name
$ ssh -X oracle@oracle_remote_server_name
Now when you run any GUI tool on the remote server, it will automatically be linked to your local desktop. If this is not working, verify that the
ForwardX11 setting is not set to "no" in /etc/ssh/ssh_config on the remote server:
su - root # grep ForwardX11 /etc/ssh/ssh_config | grep -v "^#" ForwardX11 yes #
su - root
# grep ForwardX11 /etc/ssh/ssh_config | grep -v "^#"
ForwardX11 yes
#26.2. Installing Oracle 10gR2 Cluster Ready Services (CRS) with MPIO
링크 복사링크가 클립보드에 복사되었습니다!
There is a bug installing Oracle 10gR2 CRS services using MPIO(Multipath I/O). The bug has been reported to Oracle and the bug number and description states:
BUG 5005148 - CANNOT USE BLOCK DEVICES IN VOTING DISK AND OCR DURING 10G RAC INSTALLATION
BUG 5005148 - CANNOT USE BLOCK DEVICES IN VOTING DISK AND OCR DURING 10G RAC INSTALLATION
This has been fixed in Oracle 11g.
Before attempting to install CRS, ensure that all firewalls are disabled:
service iptables stop chkconfig iptables off
service iptables stop
chkconfig iptables off
There are workarounds to successfully install CRS using MPIO. MPIO has to be disabled during installation. After the Vipca portion of the CRS installation is complete, the MPIO can be turned back on, restart CRS services. In the following examples using MPIO, friendly names are used for ease of manageability. In this example Oracle 10g R2 CRS is using internal redundancy for the
OCR and VOTING disks.
Read
/usr/share/doc/device-mapper-multipath-0.4.5/Multipath-usage.txt for more information on configuring multipath.
First, determine which block devices will be associated with MPIO devices with your OCR or Voting Disks and save the output to a log file.
Delete raw links to Multipath Devices on all nodes:
rm -f /dev/raw/*
rm -f /dev/raw/*
Shut down multipath:
multipath -F #shuts off Multipath
multipath -F #shuts off Multipath
Looking at the multipath.log output file, you can see which block devices will used for Oracle CRS. To be sure you have the correct disk on all nodes, look at
/proc/partitons. In this installation example, each device has a unique size so it is easier to map. Now link the block devices to the raw devices on all nodes by modifying /etc/sysconfig/rawdevices. Run ll on the device to get the major minor number for a block device, as seen below.
Change the configuration file
/etc/sysconfig/rawdevices using vi or your favorite editor and add the following block devices.
On the other nodes run
blockdev so the partition table are read again and created:
blockdev --rereadpt /dev/sdc blockdev --rereadpt /dev/sdd blockdev --rereadpt /dev/sde blockdev --rereadpt /dev/sdg blockdev --rereadpt /dev/sdh
# blockdev --rereadpt /dev/sdc
# blockdev --rereadpt /dev/sdd
# blockdev --rereadpt /dev/sde
# blockdev --rereadpt /dev/sdg
# blockdev --rereadpt /dev/sdh
Double check on the other nodes that the minor numbers for the block devices match. The second number in the example below, 8 in this case, is the minor number and 1 is the major number.
ll /dev/sdh1
$ ll /dev/sdh1
brw-rw---- 1 root disk 8, 113 Oct 1 13:14 /dev/sdh1
Copy
/etc/sysconfig/rawdevices to other nodes then restart it. You will see the created raw devices in /dev/raw.
Now check that the permissions are set for the Oracle installation.
Now you can commence an Oracle Clusterware installation.
Note
If during the installation process, Oracle says the raw devices are busy, then Multipath was left on in one of the nodes.
After the
VIPCA portion of the Oracle CRS is complete, you need to comment out the raw devices you created and copy /etc/sysconfig/rawdevices to the other nodes:
#/dev/raw/raw1 8 33 #/dev/raw/raw2 8 49 #/dev/raw/raw3 8 65 #/dev/raw/raw4 8 97 #/dev/raw/raw5 8 113
#/dev/raw/raw1 8 33
#/dev/raw/raw2 8 49
#/dev/raw/raw3 8 65
#/dev/raw/raw4 8 97
#/dev/raw/raw5 8 113
Check to be sure the Oracle Notification Services has started on all nodes.
ps -ef |grep ons
# ps -ef |grep ons
oracle 20058 1 0 13:49 ? 00:00:00 /ora/crs/opmn/bin/ons -d
oracle 20059 20058 0 13:49 ? 00:00:00 /ora/crs/opmn/bin/ons -d
root 20812 28286 0 13:50 pts/2 00:00:00 grep ons
The installation is now complete. Now you can to turn off Oracle CRS and start using MPIO.
Note
It is best to do this process one node at a time. No need for reboots during this process.
Shutdown the Oracle CRS Process.
Delete the raw devices created for Oracle CRS installation.
rm -f /dev/raw/*
$ rm -f /dev/raw/*
Turn on Multipath I/O (MPIO) again.
multipath
$ multipath
Create a simple script in
/etc/rc5.d/ (before CRS Starts but after MPIO starts) to bind raw devices using MPIO.
Then run the script,
/etc/rc5.d/, that you just created.
Verify the correct permissions are all set.
Restart CRS and be sure the ONS processes all start. This ensures Oracle CRS is functional on this node.
/ora/crs/bin/crsctl start crs
# /ora/crs/bin/crsctl start crs
Attempting to start CRS stack
The CRS stack will be started shortly
Repeat for the process for the rest of the nodes. Now the Oracle CRS installation is complete using Multipath I/O.
Once complete, you can check the status of the nodes:
26.3. Starting Oracle Universal Installer
링크 복사링크가 클립보드에 복사되었습니다!
Insert the Oracle CD that contains the image of the downloaded file
ship.db.lnx32.cpio, or change to the directory that contains the image directory Disk1.
Before you execute
runInstaller, make sure the Oracle environment variables are set, see Setting Oracle Environments. You can verify the settings by running the set command:
su - oracle oracle$ set
su - oracle
oracle$ set
If you install Oracle 10g from a CD, mount the CD by running the following commands in another terminal: On Red Hat Enterprise Linux 2.1 execute:
su - root mount /mnt/cdrom
$ su - root
# mount /mnt/cdrom
On Red Hat Enterprise Linux 3 and 4 execute:
su - root mount /media/cdrom
$ su - root
# mount /media/cdrom
To execute
runInstaller from the mounted CD, run the command corresponding to your version as the oracle user.
On Red Hat Enterprise Linux 2.1 execute:
oracle$ /mnt/cdrom/runInstaller
oracle$ /mnt/cdrom/runInstaller
On Red Hat Enterprise Linux 3 and 4 execute:
oracle$ /media/cdrom/runInstaller
oracle$ /media/cdrom/runInstaller26.4. Using Oracle Universal Installer (OUI)
링크 복사링크가 클립보드에 복사되었습니다!
The following example shows how to install x86 Oracle 10g Release 1 Database Software and a "General Purpose" database. Please note, the screens and questions will look different if you install 10g R2 or 64 bit 10g R1 database.
- Welcome Screen:
- Specify Inventory directory and credentials:
- Full path of the inventory directory:
Use the default: /u01/app/oracle/oraInventory
- Specify Operating System group name:
Use default: oinstall
- Full path of the inventory directory:
Use the default: /u01/app/oracle/oraInventory
- Specify Operating System group name:
Use default: oinstall
Click
- A window pops up to run the
orainstRoot.sh script:
Run the script in another terminal:
su - root # /u01/app/oracle/oraInventory/orainstRoot.sh Creating the Oracle inventory pointer file (/etc/oraInst.loc) Changing groupname of /u01/app/oracle/oraInventory to oinstall. #
su - root
# /u01/app/oracle/oraInventory/orainstRoot.sh
Creating the Oracle inventory pointer file (/etc/oraInst.loc)
Changing groupname of /u01/app/oracle/oraInventory to oinstall.
#
Then click
- Product-specific Prerequisite Checks:
Verify that all checks have been passed.
Verify that all checks have been passed.
Make sure that the status of each Check is set to "Succeeded".
On Red Hat Enterprise Linux AS 4 ignore the warnings for binutils, gcc, and openmotif and proceed.
If a check fails, see Chapter 29, Oracle 10g and Linux Installation Errors and Troubleshooting.
Note
The "" button does not work after you have fixed one of the failed checks.
Click
- Select Database Configuration then select "General Purpose".
Click
- Specify Database Configuration Options:
- Global Database Name: for example use "orcl". - SID: for example use "orcl".
- Global Database Name: for example use "orcl".
- SID: for example use "orcl".
Click
- Select Database Management Option then select "Use Database Control for Database Management".
Click
- Specify Database File Storage Option
Select "File System" in this example.
- File System
- Specify Database file location: /u01/app/oracle/oradata/
If you want to comply with OFA, you might want to select
another mount point than '/u01', for example /u02/oradata.
Select "File System" in this example.
- File System
- Specify Database file location: /u01/app/oracle/oradata/
If you want to comply with OFA, you might want to select
another mount point than '/u01', for example /u02/oradata.
Click
- Specify Backup and Recovery Options then select "Do no enable Automated Backups" for this example.
Click
- Specify Database Schema Passwords
Make sure that the passwords do not start with a number. this will cause an error message "ORA-00988 missing or invalid password" or something similar later.
Click
- Summary
Click
If Enterprise Manager configuration fails due to port allocation problems, read Chapter 29, Oracle 10g and Linux Installation Errors and Troubleshooting.
When a window pops up to run the
root.sh script, execute the script in another terminal as root:
Click
You have now reached the end of the Installation, click the button.
26.5. Updating after the Oracle Universal Installer
링크 복사링크가 클립보드에 복사되었습니다!
After Oracle 10g has been installed, make sure that
ORACLE_HOME, PATH, and LD_LIBRARY_PATH are set for the oracle account.
Note
The path for
ORACLE_HOME might be different on your system! Also note that LD_LIBRARY_PATH is needed for some Oracle binaries such as sysresv.
For 10g R1 (10.1.0.3) you may want to add the following lines to the
~oracle/.bash_profile file:
export ORACLE_HOME=$ORACLE_BASE/product/10.1.0/db_1 export PATH=$PATH:$ORACLE_HOME/bin export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export ORACLE_HOME=$ORACLE_BASE/product/10.1.0/db_1
export PATH=$PATH:$ORACLE_HOME/bin
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
For 10g R2 (10.2.0.1.0) you may want to add the following lines to the
~oracle/.bash_profile file:
export ORACLE_HOME=$ORACLE_BASE/oracle/product/10.2.0/db_1 export PATH=$PATH:$ORACLE_HOME/bin export LD_LIBRARY_PATH=$ORACLE_HOME/lib
export ORACLE_HOME=$ORACLE_BASE/oracle/product/10.2.0/db_1
export PATH=$PATH:$ORACLE_HOME/bin
export LD_LIBRARY_PATH=$ORACLE_HOME/lib
After that run the following command to set all environment variables in
~oracle/.bash_profile:
. ~oracle/.bash_profile
$ . ~oracle/.bash_profile
This command will add the environment variables to the
~oracle/.profile and source in the file for the current shell by executing ". ~oracle/.bash_profile".
Note
Do not add a trailing "
/" on the ORACLE_HOME environment variable. Otherwise you will get the error "ORACLE not available" when you try to connect to sys, see Chapter 29, Oracle 10g and Linux Installation Errors and Troubleshooting.
Chapter 27. Oracle Post Installation Tasks
링크 복사링크가 클립보드에 복사되었습니다!
Important
Before you continue, make sure you followed the steps at Section 26.5, “Updating after the Oracle Universal Installer”.
27.1. Startup and Shutdown of the Oracle 10g Database
링크 복사링크가 클립보드에 복사되었습니다!
This section contains details on how to start up and shut down your Oracle Database.
Start the database:
oracle$ sqlplus /nolog SQL> connect / as sysdba SQL> startup
oracle$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startup
Shut down the database:
oracle$ sqlplus /nolog SQL> connect / as sysdba SQL> shutdown
oracle$ sqlplus /nolog
SQL> connect / as sysdba
SQL> shutdown
The slash connects you to the schema owned by
SYS. In the above example you will be connected to the schema owned by SYS with the privilege SYSDBA. SYSDBA gives you the following privileges:
- sysoper privileges WITH ADMIN OPTION.
- create database.
- recover database until.
27.2. Shutdown of other Oracle 10g Background Processes
링크 복사링크가 클립보드에 복사되었습니다!
If you installed a pre-configured database using OUI, then several Oracle background processes are now running on your server. Execute the following command to see the background processes:
ps -ef
ps -ef
To shutdown the Oracle background processes after an Oracle Database 10g installation, you can execute the following commands:
- iSQL*PlusTo stop iSQL*Plus, run:
su - oracle isqlplusctl stop
su - oracle isqlplusctl stopCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Database Management ProcessesDuring the installation of Oracle 10g, OUI offered two Database Management Options:If you selected "Database Control for Database Management", then the Oracle Enterprise Manager Database Control (Database Control) can be shutdown with the following command which stops both the agent and the Oracle Containers for Java (OC4J) management service:
su - oracle emctl stop dbconsole
su - oracle emctl stop dbconsoleCopy to Clipboard Copied! Toggle word wrap Toggle overflow If you selected "Grid Control for Database Management" which is used for full "Grid Control" installations, then the Oracle Management Agent (standalone agent) for the Oracle Enterprise Manager Grid Control (Grid Control) can be stopped with the following command:su - oracle emctl stop agent
su - oracle emctl stop agentCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Oracle Net ListenerTo stop the listener, run:
su - oracle lsnrctl stop
su - oracle lsnrctl stopCopy to Clipboard Copied! Toggle word wrap Toggle overflow - Cluster Synchronization Services (CSS)To shutdown Oracle Cluster Synchronization Services (CSS) daemon, run:
su - root /etc/rc.d/init.d/init.cssd stop
su - root /etc/rc.d/init.d/init.cssd stopCopy to Clipboard Copied! Toggle word wrap Toggle overflow
Chapter 28. Tips and Hints for Oracle 10g on Red Hat Enterprise Linux
링크 복사링크가 클립보드에 복사되었습니다!
To reinstall Oracle 10g after a failed installation attempt, you might want to execute the following commands. Make sure you first used the "De-installation" option in the OUI.
su - root export ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1 . $ORACLE_HOME/bin/localconfig delete
su - root
export ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1
. $ORACLE_HOME/bin/localconfig delete
The above line stops the Oracle CSS daemon and deletes the configuration.
Make sure you comment out
ORACLE_HOME from ~oracle/.bash_profile.
Chapter 29. Oracle 10g and Linux Installation Errors and Troubleshooting
링크 복사링크가 클립보드에 복사되었습니다!
This chapter presents many common Oracle 10g problems and other issues.
Note
Most of the issues are caused by not following the installation procedure correctly. Some errors are caused by not using an Oracle supported Linux OS version such as Red Hat Enterprise Linux.
The Installation log file can be found in
$ORACLE_BASE/oraInventory/logs. The Database Creation log file can be found in $ORACLE_BASE/admin/$ORACLE_SID/create.
An Error While Starting the Oracle Universal Installer
You may receive the following error while running the Oracle Universal Installer:
A solution for how to fix this can be found at Section 20.8, “Verifying and Updating the redhat-release File”.
Note
The "" in the "" window does not work. When correcting errors, you must either set them manually to Passed or you restart OUI.
Checking for gcc-2.96; found Not found. Failed >>>>
Refer to Section 19.3, “Verifying Software Packages (RPMs)” for information on this problem and how to solve it.
Checking for shmmax=2147483648; found shmmax=33554432. Failed >>>>
Solution: Increase the shmmax kernel parameter.
See Section 19.4, “Verifying Kernel Parameters” for information on this problem and how to solve it.
Checking for semopm=100; found semopm=32. Failed <<<<
Increase the semopm kernel parameter.
See Section 19.4, “Verifying Kernel Parameters” for information on this problem and how to solve it.
Checking for filemax=65536; found filemax=26163. Failed <<<<
Increase the file-max kernel parameter.
See Section 19.4, “Verifying Kernel Parameters” for information on this problem and how to solve it.
ORA-01034: ORACLE not available, ORA-27101: shared memory realm does not exist, Linux Error: 2: No such file or directory, or ORA-01034: ORACLE not available
First check if ORACLE_SID is set correctly. If the ORACLE_SID is set correctly, then you probably have a trailing slash "/" on the ORACLE_HOME environment variable. Remove it and try again to connect to sys. For example, change ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1/ to ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1.
ORA-00988 missing or invalid password(s)
During the Oracle 10g installation you probably provided a password for the Oracle database accounts that started with a number. Ignore this error message and change the password when you are done with the Oracle 10g installation.
sysresv -i outputs sysresv: error while loading shared libraries: libclntsh.so.10.1: cannot open shared object file: No such file or directoryMake sure LD_LIBRARY_PATH is set to $ORACLE_HOME/lib by executing:
oracle$ export LD_LIBRARY_PATH=$ORACLE_HOME/lib
oracle$ export LD_LIBRARY_PATH=$ORACLE_HOME/libX11 connection rejected because of wrong authentication X connection to localhost:10.0 broken (explicit kill or server shutdown)
To rectify this problem, try to log in to the remote Oracle server again by using the "X11 forward" feature of ssh. Execute the following command, after changing oracle_remote_server_name to your server, from your local desktop:
ssh -X oracle@oracle_remote_server_name
$ ssh -X oracle@oracle_remote_server_name
Now when you try to run any GUI tool on the remote server, it should automatically be relinked to your local desktop. If this is not working, verify that the
ForwardX11 setting is not set to "no" in /etc/ssh/ssh_config on your remote server:
su - root # grep ForwardX11 /etc/ssh/ssh_config | grep -v "^#" ForwardX11 yes #
su - root
# grep ForwardX11 /etc/ssh/ssh_config | grep -v "^#"
ForwardX11 yes
#Note
If you use newer Red Hat Enterprise Linux versions as your desktop and you want to install the database on another machine, then you need to set the
DisallowTCP entry in /etc/X11/gdm/gdm.conf for the GNOME Display Manager to read: DisallowTCP=false.
After that you need to restart your X server. You can do this with the
init command:
su - root init 3 init 5
su - root init 3 init 5
If you are using
telnet you will have to set the DISPLAY variable manually.
Recovery Manager(
rman) hangs
You are probably running the wrong rman binary which belongs to the XFree86-devel RPM:
which rman
$ which rman
/usr/X11R6/bin/rmanORA-00988 missing or invalid password(s)
During the Oracle 10g installation you probably provided a password for the Oracle database accounts that started with a digit number. Ignore this error message and change the password when you are done with the Oracle 10g installation.
./runInstaller CrashesThe Oracle installer ./run Installer crashes with the
You may receive this error message on Red Hat Enterprise Linux 3 x86-64, Red Hat Enterprise Linux 4 x86-64, and on other systems. Even though you most probably have
/usr/X11R6/lib64/libXp.so.6 installed on your system, this error messages is complaining that it can not find the libXp.so.6 shared library for i386:
/tmp/OraInstall2005-06-15_07-36-25AM/jre/1.4.2/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
/tmp/OraInstall2005-06-15_07-36-25AM/jre/1.4.2/lib/i386/libawt.so: libXp.so.6: cannot open shared object file: No such file or directory
Follow the instructions below to install the i386 XFree86-libs package (XFree86-libs-4.3.0-81.EL.i386.rpm or newer) on Red Hat Enterprise Linux 3 x86-64 with 10g (10.1.0.3) . In order to satisfy dependencies for this i386 package, you may need to install a few other i386 RPMs as well:
In order to install 10g (10.1.0.3) on Red Hat Enterprise Linux 4 x86-64 update 1 you must install the i386
xorg-x11-deprecated-libs package (xorg-x11-deprecated-libs-6.8.2-1.EL.13.6.i386.rpm). The installation depends on the following packages, to install these packages execute the follow commands:
Installing 10g R2 (10.2.0.1.0) on Red Hat Enterprise Linux 4 x86-64 Update 2 requires the i386
xorg-x11-deprecated-libs package (xorg-x11-deprecated-libs-6.8.2-1.EL.13.20.i386.rpm). In order to satisfy dependencies for this i386 package, you may have to install a few other i386 RPMs as well:
An Oracle 10g R2 (10.2.0.1.0) install on Red Hat Enterprise Linux 4 x86 Update 2 system requires the following RPM:
rpm -Uvh xorg-x11-deprecated-libs-6.8.2-1.EL.13.20.i386.rpm
rpm -Uvh xorg-x11-deprecated-libs-6.8.2-1.EL.13.20.i386.rpm
After you have installed the appropriate RPMs, restart the installation by running
.runInstaller again.
An error in relinking during the Oracle install
You may get this error message or a similar one when installing 64 bit 10g on Red Hat Enterprise Linux4 x86-64.
On Red Hat Enterprise Linux4 U1 x86-64 to install 10g (10.1.0.3) you need the following i386 RPM to fix this problem:
rpm -Uvh glibc-devel-2.3.4-2.9.i386.rpm
# rpm -Uvh glibc-devel-2.3.4-2.9.i386.rpm
On Red Hat Enterprise Linux 4 U2 x86-64 to install 10g R2 (10.2.0.1.0) you need the following i386 RPM to fix this problem:
rpm -Uvh glibc-devel-2.3.4-2.13.i386.rpm
# rpm -Uvh glibc-devel-2.3.4-2.13.i386.rpmError while loading shared libraries: libaio.so.1: cannot open shared object file: No such file or directory
Make sure the libaio RPM is installed.
On Red Hat Enterprise Linux 3 x86:
rpm -Uvh libaio-0.3.96-5.i386.rpm
# rpm -Uvh libaio-0.3.96-5.i386.rpm
On Red Hat Enterprise Linux 4 Update 2 x86-64:
rpm -Uvh libaio-0.3.103-3.x86_64.rpm
# rpm -Uvh libaio-0.3.103-3.x86_64.rpm
Your version of
libaio may be different.
Error in invoking target 'all_no_orcl'
The error text in full:
Error in invoking target 'all_no_orcl' of makefile '/u01/app/oracle/oracle/product/10.2.0/db_1/rdbms/lib/ins_rdbms.mk'. See '/u01/app/oracle/oraInventory/logs/installActions2005-11-13_01-07-04AM.log' for details.
Error in invoking target 'all_no_orcl' of makefile '/u01/app/oracle/oracle/product/10.2.0/db_1/rdbms/lib/ins_rdbms.mk'.
See '/u01/app/oracle/oraInventory/logs/installActions2005-11-13_01-07-04AM.log' for details.
The log file shows the following error:
On Red Hat Enterprise Linux 4 U2 x86-64 with 10g R2 (10.2.0.1.0) install the following x86-64 RPM to fix this problem:
rpm -Uvh compat-libstdc++-33-3.2.3-47.3.x86_64.rpm
# rpm -Uvh compat-libstdc++-33-3.2.3-47.3.x86_64.rpmNote
You may already have the "i386"
compat-libstdc++-33 RPM installed on your systems but you need the "x86-64" RPM to fix this problem. To verify which compat-libstdc++-33 RPM you have installed on your system, run:
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' compat-libstdc++-33
# rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' compat-libstdc++-33Error in invoking target 'all_no_orcl ihsodbc'
The full error message:
Error in invoking target 'all_no_orcl ihsodbc' of makefile '/u01/app/oracle/oracle/product/10.2.0/db_1/rdbms/lib/ins_rdbms.mk'. See '/u01/app/oracle/oraInventory/logs/installActions2005-07-24_09-25-22AM.log' for details.
Error in invoking target 'all_no_orcl ihsodbc' of makefile '/u01/app/oracle/oracle/product/10.2.0/db_1/rdbms/lib/ins_rdbms.mk'.
See '/u01/app/oracle/oraInventory/logs/installActions2005-07-24_09-25-22AM.log' for details.
This means that the "33" version of the
compat-libstdc++ RPM is missing.
Installing 10g R2 (10.2.0.1.0) on Red Hat Enterprise Linux 4 Update 2 x86 you require the following RPM to fix this problem:
rpm -Uvh compat-libstdc++-33-3.2.3-47.3.i386.rpm
# rpm -Uvh compat-libstdc++-33-3.2.3-47.3.i386.rpm
You need the "33" version of the compat-libstdc++ RPM. For i386 there is also a "296" version of the
compat-libstdc++ RPM. Here are the two compat-libstdc++ RPMs that come with Red Hat Enterprise Linux 4 Update 2:
compat-libstdc++-296-2.96-132.7.2.i386.rpm compat-libstdc++-33-3.2.3-47.3.i386.rpm
compat-libstdc++-296-2.96-132.7.2.i386.rpm
compat-libstdc++-33-3.2.3-47.3.i386.rpm
After that hit in the error dialog window.
Error in invoking target 'all_no_orcl' of makefile
The full error is listed below.
Error in invoking target 'all_no_orcl' of makefile '/u01/app/oracle/oracle/product/10.2.0/db_1/rdbms/lib/ins_rdbms.mk'. See '/u01/app/oracle/oraInventory/logs/installActions2005-11-13_01-25-49AM.log' for details.
Error in invoking target 'all_no_orcl' of makefile '/u01/app/oracle/oracle/product/10.2.0/db_1/rdbms/lib/ins_rdbms.mk'.
See '/u01/app/oracle/oraInventory/logs/installActions2005-11-13_01-25-49AM.log' for details.
The log file shows the following error:
This error comes up when installing 10g R2 (10.2.0.1.0) on Red Hat Enterprise Linux 4 x86-64. Make sure to upgrade to Red Hat Enterprise Linux 4 Update 3, or higher, otherwise to download the
binutils RPM from https://rhn.redhat.com/ or from http://oss.oracle.com/projects/compat-oracle/files/RedHat/. After you have downloaded the RPM install it:
rpm -Uvh --force binutils-2.15.92.0.2-13.0.0.0.2.x86_64.rpm
# rpm -Uvh --force binutils-2.15.92.0.2-13.0.0.0.2.x86_64.rpm
For more information on this bug, see Bugzilla Bug 679.
ORA-12547: TNS:lost contact
There can be many reasons for this error. This can happen during the ASM instance start up when the libaio RPM is not installed on the system.
You can test this by running
lsnrctl as the oracle user.
Make sure the
loopback entry in /etc/hosts is not missing when you start the listener:
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost.localdomain localhost
Now try to run
lsnrctl as the user oracle again.
Part III. Installing the Oracle9i 32 bit Database on Red Hat Enterprise Linux
링크 복사링크가 클립보드에 복사되었습니다!
Introduction and Information on Supported Setups for Oracle 9i
링크 복사링크가 클립보드에 복사되었습니다!
This article provides a step by step guide for installing Oracle9i databases on Red Hat Enterprise Linux. This guide covers the following Oracle Database and Red Hat Linux versions:
| Oracle Database Version | Red Hat Enterprise Linux Version | Architecture |
|---|---|---|
| Oracle9i R2 (9.2.0.6.0) | 4 | x86 (32 bit) |
| Oracle9i R2 (9.2.0.4.0) | 3 | x86 (32 bit) |
| Oracle9i R2 (9.2.0.1.0) | 2.1 | x86 (32 bit) |
For Validation and Certification information, see Oracle's Certification Matrices.
Chapter 30. Preparing Red Hat Enterprise Linux for an Oracle Database Installation
링크 복사링크가 클립보드에 복사되었습니다!
This chapter will guide you though the pre-installation procedures for installing Oracle 9i on Red Hat Enterprise Linux
30.1. Unpacking and Downloading the Oracle9i Installation Files
링크 복사링크가 클립보드에 복사되었습니다!
Download Oracle9i for Linux from http://otn.oracle.com/software/products/oracle9i/htdocs/linuxsoft.html.
Here are two methods for unpacking the Oracle installation files, choose one. First method - this method uses less disk space and should be faster:
zcat lnx_920_disk1.cpio.gz | cpio -idmv zcat lnx_920_disk2.cpio.gz | cpio -idmv zcat lnx_920_disk3.cpio.gz | cpio -idmv
zcat lnx_920_disk1.cpio.gz | cpio -idmv
zcat lnx_920_disk2.cpio.gz | cpio -idmv
zcat lnx_920_disk3.cpio.gz | cpio -idmv
Second method - this method first uncompresses then unpacks the installation files:
gunzip lnx_920_disk1.cpio.gz lnx_920_disk2.cpio.gz lnx_920_disk3.cpio.gz Linux9i_Disk3.cpio.gz cpio -idmv < lnx_920_disk1.cpio cpio -idmv < lnx_920_disk2.cpio cpio -idmv < lnx_920_disk3.cpio
gunzip lnx_920_disk1.cpio.gz lnx_920_disk2.cpio.gz lnx_920_disk3.cpio.gz Linux9i_Disk3.cpio.gz
cpio -idmv < lnx_920_disk1.cpio
cpio -idmv < lnx_920_disk2.cpio
cpio -idmv < lnx_920_disk3.cpio
You should now have 3 directories containing installation files, if
ls looks like this it worked correctly:
ls
$ ls
Disk1
Disk2
Disk330.2. Setting Swap Space
링크 복사링크가 클립보드에 복사되었습니다!
According to Oracle9i Installation Guide Release 2 a minimum of 512MB of RAM is required to install an Oracle9i Server. The swap space should be equal to RAM, or 1GB, whichever is greater. For more information on correctly sizing the swap space for your database, read Chapter 6, Swap Space..
To check the memory, run:
grep MemTotal /proc/meminfo
grep MemTotal /proc/meminfo
To check the swap space, run:
cat /proc/swaps
cat /proc/swaps30.4. Examining Temporary(/tmp) Space
링크 복사링크가 클립보드에 복사되었습니다!
The Oracle Universal Installer requires up to 400 MB of free space in the /tmp directory.
To find out the space in /tmp, run:
df /tmp
$ df /tmp
If you do not have enough space in the
/tmp directory, you can temporarily create a tmp directory in another file system. Here are the steps for doing it:
The
TEMP=/<AnotherFilesystem> file is used by Oracle. The TMPDIR=/<AnotherFilesystem> file is used by Linux programs like the linker "ld".
When you are done with your Oracle installation, shut down Oracle and remove the temporary directory:
su - root rmdir /<AnotherFilesystem>/tmp unset TEMP unset TMPDIR
su - root
rmdir /<AnotherFilesystem>/tmp
unset TEMP
unset TMPDIR30.5. Sizing Oracle Disk Space
링크 복사링크가 클립보드에 복사되었습니다!
You will need about 2.5 GB for the database software. If you perform a typical database installation and not a customized database installation, then you will need about 3.5 GB of disk space.
Chapter 31. Verifying Required Packages(RPMs)
링크 복사링크가 클립보드에 복사되었습니다!
You will need certain RPM development packages for the Oracle installer to build Oracle modules, otherwise you will get error messages similar to this one:
Error in invoking target ntcontab.o of makefile /u01/app/oracle/product/9.2.0/network/lib/ins_net_client.mk
Error in invoking target ntcontab.o of makefile
/u01/app/oracle/product/9.2.0/network/lib/ins_net_client.mkNote
Always ensure you use the latest stable versions of RPM.
See the Oracle9i Release Notes Release 2 (9.2.0.4.0) for Linux x86 for the list of required RPMs.
31.1. Required Packages for Red Hat Advanced Server 2.1
링크 복사링크가 클립보드에 복사되었습니다!
Ensure the following development packages are installed:
rpm -q gcc cpp compat-libstdc++ glibc-devel kernel-headers binutils
rpm -q gcc cpp compat-libstdc++ glibc-devel kernel-headers binutils
Most of these packages will be missing on Red Hat Advanced Server 2.1 if the "Software Development" package was not selected during the OS install. If these RPMs are missing, execute the command below, remember your versions may be newer. If they are not newer than those seen below update to a more recent version.
rpm -ivh cpp-2.96-108.1.i386.rpm \
glibc-devel-2.2.4-26.i386.rpm \
kernel-headers-2.4.9-e.3.i386.rpm \
gcc-2.96-108.1.i386.rpm \
binutils-2.11.90.0.8-12.i386.rpm
rpm -ivh cpp-2.96-108.1.i386.rpm \
glibc-devel-2.2.4-26.i386.rpm \
kernel-headers-2.4.9-e.3.i386.rpm \
gcc-2.96-108.1.i386.rpm \
binutils-2.11.90.0.8-12.i386.rpm31.2. Required Packages for Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
Ensure the following packages are installed by executing the command below:
31.3. Required Packages for Red Hat Enterprise Linux 4
링크 복사링크가 클립보드에 복사되었습니다!
Ensure the following packages are installed by executing the following command:
Many of these packages depend on other packages. For example,
compat-gcc-32 requires binutils, gcc and several other packages. You may have to install the following RPMs to satisfy Oracle's dependencies:
The X.org development libraries,
xorg-x11-deprecated-libs-devel and xorg-x11-devel, are required for the Oracle patch 4198954, the following RPMs may need to be installed:
The Gnome libraries,
gnome-libs and gnome-libs-devel, may require following RPMs to be installed:
Note
If you are using the Red Hat Network(RHN), you can run:
up2date gnome-libs gnome-libs-devel
up2date gnome-libs gnome-libs-devel
You can use the
up2date command for any packages. It takes care of dependencies by installing all required packages automatically.
To install the
compat-oracle-rhel4 and compat-libcwait packages you have to download the patch 4198954 from http://metalink.oracle.com. Make sure to select the Linux x86 platform. To unzip the downloaded p4198954_21_LINUX.zip file, run:
Note
The
compat-oracle-rhel4 and compat-libcwait packages require the xorg-x11-deprecated-libs and xorg-x11-deprecated-libs-devel packages, see above. To install the two RPMs from the 4198954 patch, run:
# rpm -Uvh 4198954/compat-oracle-rhel4-1.0-5.i386.rpm 4198954/compat-libcwait-2.0-2.i386.rpm
Chapter 32. Setting Up a Working Environment for Oracle
링크 복사링크가 클립보드에 복사되었습니다!
This chapter covers the creation of user accounts, directories and Oracle environments for your Oracle Database before you install.
32.1. Creating Oracle User Accounts
링크 복사링크가 클립보드에 복사되었습니다!
This section covers the command necessary to activate the required accounts to install an Oracle Database.
Create the group of users to be granted with SYSDBA system privilege:
su - root groupadd dba
su - root groupadd dba
Now create a group owner for Oracle files:
groupadd oinstall useradd -c "Oracle software owner" -g oinstall -G dba oracle passwd oracle
groupadd oinstall
useradd -c "Oracle software owner" -g oinstall -G dba oracle
passwd oracle
For more information on the "
oinstall" group account, see When to use OINSTALL group during install of oracle.
32.2. Creating Oracle Directories
링크 복사링크가 클립보드에 복사되었습니다!
Make sure that the Oracle file systems, in this example
/u01, is large enough, see Section 30.5, “Sizing Oracle Disk Space” for more information.
32.3. Setting Oracle Environment Variables
링크 복사링크가 클립보드에 복사되었습니다!
Make sure to set the following Oracle environment variables before you execute runInstaller.
As the oracle user, execute the following commands. Make sure to set the LD_ASSUME_KERNEL environment variable for Red Hat Enterprise Linux 3 and 4. Use the "Linuxthreads with floating stacks" implementation instead of NPTL.
export LD_ASSUME_KERNEL=2.4.1 # for Red Hat Enterprise Linux 3 export LD_ASSUME_KERNEL=2.4.19 # for Red Hat Enterprise Linux 4
export LD_ASSUME_KERNEL=2.4.1 # for Red Hat Enterprise Linux 3
export LD_ASSUME_KERNEL=2.4.19 # for Red Hat Enterprise Linux 4
For the Oracle Environment:
export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=$ORACLE_BASE/product/9.2.0 export ORACLE_SID=test export ORACLE_TERM=xterm
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/9.2.0
export ORACLE_SID=test
export ORACLE_TERM=xterm
You will need to export
TNS_ADMIN= Set if sqlnet.ora, tnsnames.ora and other variables are not present in $ORACLE_HOME/network/admin.
export NLS_LANG=AMERICAN; export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib export LD_LIBRARY_PATH
export NLS_LANG=AMERICAN;
export ORA_NLS33=$ORACLE_HOME/ocommon/nls/admin/data
LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
export LD_LIBRARY_PATH
Set the shell search paths:
export PATH=$PATH:$ORACLE_HOME/bin
export PATH=$PATH:$ORACLE_HOME/bin
You can add these environment settings to the end of the
~oracle/.bash_profile file if you use bash. This will ensure that the environment variables are set permanently when you log in as "oracle", or when you switch to the user "oracle" by executing "su - oracle".
Chapter 33. Starting runInstaller
링크 복사링크가 클립보드에 복사되었습니다!
Important
If you use CDs to install the database, do not change directory (
cd) to /mnt/cdrom to execute ./runInstaller! If you do so, the installation will fail because you will not be able to change the CDs.
Before you continue, make sure you have set the Oracle environment variables in Section 32.3, “Setting Oracle Environment Variables”.
Oracle no longer supports a character mode installer. Therefore, in order to execute runInstaller directly from a console of a machine you are logged into you need to set the DISPLAY environment variable. In the example the name of the node where Oracle is running is called "
oracleserver". First, make sure that you also allow runInstaller on "oracleserver" to display X information on your Linux desktop machine. In the example, the computer name where you are running an X Windows desktop like KDE or GNOME is called "yourdesktop". Programs running on remote machines cannot display information to your screen unless you give them the authority to do so.
Before you execute
runInstaller, execute xterm (or another terminal client of your choice) to see if your X setup is really working. If you are about to install Oracle on your desktop PC and not on a remote node, then you can skip step 1 and 3.
Step 1: Allow "
oracleserver" to display X information to your desktop PC "yourdesktop":
yourdesktop:user$ xhost +oracleserver
yourdesktop:user$ xhost +oracleserver
Step 2: Open a new window and log in to the Oracle server "
oracleserver" as the root user. This window will be used to mount and unmounting the Oracle CDs.
oracleserver:$ su - root oracleserver:root# mount /mnt/cdrom
oracleserver:$ su - root
oracleserver:root# mount /mnt/cdrom
Step 3: From the console of your Oracle server "
oracleserver" where you will run runInstaller, execute the following commands:
oracleserver:$ su - oracle oracleserver:oracle$ export DISPLAY=yourdesktop:0.0
oracleserver:$ su - oracle
oracleserver:oracle$ export DISPLAY=yourdesktop:0.0
Step 4: Now you can execute
runInstaller as "oracle" as shown in the next chapters. It is important that you do not change directory (cd) to /mnt/cdrom.
oracleserver:oracle$ /mnt/cdrom/runInstaller
oracleserver:oracle$ /mnt/cdrom/runInstallerChapter 34. Installing Oracle9i R2 (9.2.0.1.0) on Red Hat Advanced Server 2.1
링크 복사링크가 클립보드에 복사되었습니다!
You may get one or more errors during the Oracle installation. If you encounter a problem, read Chapter 38, Oracle Installation Errors. for more information and solutions. The errors can be addressed very easily using the prescribed solutions.
Chapter 35. Installing Oracle9i R2 (9.2.0.4.0) on Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
In order to install an Oracle9i R2 database on Red Hat Enterprise Linux 3, the "Oracle9iR2 Patch Set 3 9.2.0.4.0" patch set and a few other patches must be applied after the installation of Oracle9i Release 2 (9.2.0.1.0). Please note, there exists errors that can only be fixed by applying the 9.2.0.4 patch set.
35.1. Installing Oracle9i R2 (9.2.0.1.0) on Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
Note
Throughout this chapter, the symbol # represents a terminal owned by the root user. You can use the root account by using the commands
su - root or sudo if you have permissions.
Install the following required RPMs (read Oracle Note:252217.1 for more information) for compatibility:
Relink
gcc so that the older gcc will be used during the Oracle installation (see Oracle Note:252217.1 for more information):
su - root # mv /usr/bin/gcc /usr/bin/gcc323 # ln -s /usr/bin/gcc296 /usr/bin/gcc # mv /usr/bin/g++ /usr/bin/g++323 # ln -s /usr/bin/g++296 /usr/bin/g++
su - root
# mv /usr/bin/gcc /usr/bin/gcc323
# ln -s /usr/bin/gcc296 /usr/bin/gcc
# mv /usr/bin/g++ /usr/bin/g++323
# ln -s /usr/bin/g++296 /usr/bin/g++Note
If you received an error stating g++ does not exist after executing the above commands, then gcc-c++ has not been installed.
When you execute
runInstaller from the Oracle9i R2 (9.2.0) CD, you will get the following error message:
Error occurred during initialization of VM Unable to load native library: /tmp/OraInstall2003-10-25_03-14-57PM/jre/lib/i386/libjava.so: symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
Error occurred during initialization of VM
Unable to load native library: /tmp/OraInstall2003-10-25_03-14-57PM/jre/lib/i386/libjava.so:
symbol __libc_wait, version GLIBC_2.0 not defined in file libc.so.6 with link time reference
To resolve the
__libc_wait symbol issue, download the p3006854_9204 patch p3006854_9204_LINUX.zip from http://metalink.oracle.com. See bug 3006854 for more information. To apply the patch, run:
Important
If you get the following error when you run
rhel3_pre_install.sh:
rhel3_pre_install.sh: line 36: gcc: command not found
The error means you must install or link
gcc correctly. This will mean you cannot start any binaries any more, for example:
ls
# ls
ls: error while loading shared libraries: /etc/libcwait.so: cannot open shared objectfile: No such file or directory
file: No such file or directoryrm /etc/ld.so.preload
# rm /etc/ld.so.preload
rm: error while loading shared libraries: /etc/libcwait.so: cannot open shared object
To fix that, run the
echo. echo is a built-in shell command and not a binary so it will still work.
echo "" > /etc/ld.so.preload rm /etc/ld.so.preload
# echo "" > /etc/ld.so.preload rm /etc/ld.so.preload
Now you can start the process over from the beginning of the chapter.
Now
runInstaller can be started from the CD:
su - oracle $ echo $LD_ASSUME_KERNEL # it is important that this variable is set! 2.4.1 $ /mnt/cdrom/runInstaller
su - oracle
$ echo $LD_ASSUME_KERNEL # it is important that this variable is set!
2.4.1
$ /mnt/cdrom/runInstaller
- Welcome Screen: Click
- Inventory Location: Click
- Unix Group Name: Use "oinstall"
Click Next When asked to run
/tmp/orainstRoot.sh, run it before you click
- File Locations: Use the default values
- Available Products: Select "Oracle9i Database 9.2.0.1.0"
- Installation Types: Select
Custom since we only want to install the software for now
- Available Products: Click or add some more components.
- Components Locations: Accept default values and click
- Privileged Operating System Groups: You can use the default values: OSDBA Group = dba, OSOPER Group = dba
- Oracle Managent Server Repository: You can use the default choice
- Create database: Select
No since we first have to patch Oracle before a database can be created.
- Summary: Start the Install
- Configuration tools: The tools won't come up. Simply ignore it.
- At the end of the installation, exit
runInstaller.
You may get the following errors while using the installer.
"Error in invoking target install of
makefile /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk."
The
/u01/app/oracle/product/9.2.0/install/make.log file reads:
Click .
This will be fixed after you apply the patch 3119415 after the 9.2.0.4 patchset has been applied. You can not apply the patch 3119415 at this time since the file
/u01/app/oracle/oraInventory/ContentsXML/comps.xml does not exist yet. We will show you how to apply patch 3119415 later.
"Error in invoking target install of
makefile /u01/app/oracle/product/9.2.0/ctx/lib/ins_ctx.mk. "
The /u01/app/oracle/product/9.2.0/install/make.log file reads:
/usr/bin/ld: ctxhx: hidden symbol `stat' in /usr/lib/libc_nonshared.a(stat.oS) is referenced by DSO collect2: ld returned 1 exit status make: *** [ctxhx] Error 1
/usr/bin/ld: ctxhx: hidden symbol `stat' in /usr/lib/libc_nonshared.a(stat.oS) is referenced by DSO
collect2: ld returned 1 exit status
make: *** [ctxhx] Error 1
Click . This will be fixed when you apply the 9.2.0.4 patch set.
35.2. Patching Oracle9i to 9.2.0.4.0 on Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
To patch Oracle9i R2, download the Oracle9i Release 2 Patch Set 3 Version 9.2.0.4.0 for Linux x86 from http://metalink.oracle.com. Download the
p3095277_9204_LINUX.zip file to /tmp and run the following command:
To patch the
runInstaller, execute:
su - oracle $ echo $LD_ASSUME_KERNEL # it is important that this variable is set! 2.4.1 $ cd /tmp/Disk1/ $ ./runInstaller
su - oracle
$ echo $LD_ASSUME_KERNEL # it is important that this variable is set!
2.4.1
$ cd /tmp/Disk1/
$ ./runInstaller
- Welcome Screen: Click
- File Locations: Use default values
- Available Products: Select "Oracle Universal Installer 2.2.0.18.0"
- Components Locations: Accept default values and click
- Summary: Start the Install
- At the end of the installation, you must exit
runInstaller
To patch Oracle9i R2, execute:
su - oracle $ echo $LD_ASSUME_KERNEL # it is important that this variable is set! 2.4.1 $ cd $ORACLE_HOME/bin $ ./runInstaller
su - oracle
$ echo $LD_ASSUME_KERNEL # it is important that this variable is set!
2.4.1
$ cd $ORACLE_HOME/bin
$ ./runInstaller
- Welcome Screen: Click
- File Locations: Use default values
- Available Products: Select "Oracle9iR2 Patch Set 3 9.2.0.4.0 !"
- Summary: Start the Install
- At the end of the installation, exit
runInstaller
You may get the error: "Error in invoking target install of
makefile /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk".
The
/u01/app/oracle/product/9.2.0/install/make.log file reads:
Click ignore. This will be fixed by applying the patch 3119415 after the 9.2.0.4 patchset has been applied. The patch 3119415 cannot be applied while the patch process for the 9.2.0.4 patchset is running.
After the 9.2.0.4 patchset has been applied, download the patch
p3119415_9204_LINUX.zip from http://metalink.oracle.com. See bug 3119415 for more information. Also, download the opatch Release 2.2.0 utility from http://metalink.oracle.com. See bug 2617419 at http://metalink.oracle.com for more information.
To install
opatch, run:
su - oracle $ cp p2617419_210_GENERIC.zip /tmp $ cd /tmp $ unzip p2617419_210_GENERIC.zip
su - oracle
$ cp p2617419_210_GENERIC.zip /tmp
$ cd /tmp
$ unzip p2617419_210_GENERIC.zip
Before you apply the 3119415 patch, you need to make sure the fuser binary can be found by the oracle user, see the
PATH environment variable below. Otherwise the patch can not be applied because the fuser binary is used by opatch. To apply the 3119415 patch, run:
Now you should be able to create a database with dbca:
su - oracle dbca
$ su - oracle
$ dbca35.3. Patching Oracle Intelligent Agent on Red Hat Enterprise Linux 3
링크 복사링크가 클립보드에 복사되었습니다!
When you run "
agentctl start" (Oracle 9.2.0.4), dbsnmp will crash:
To resolve this problem, apply the patch
p3238244_9204_LINUX.zip from http://metalink.oracle.com, search for 3238244 to see the bug and patch information.
Before you apply the patch, make sure the instance is down!
Make sure the
opatch script appears in your $PATH. To verify if opatch is in your $PATH, run the following commands:
su - oracle which opatch
$ su - oracle
$ which opatch
/tmp/OPatch/opatch
$
Please note, the patch needs "
fuser" which should be located in /sbin, if it is not you will need to install it. To apply now the patch, run:
su - oracle unzip p3238244_9204_LINUX.zip cd 3238244 export PATH=$PATH:/sbin opatch apply
$ su - oracle
$ unzip p3238244_9204_LINUX.zip
$ cd 3238244
$ export PATH=$PATH:/sbin
$ opatch apply
Now you need to relink
dbsnmp. This is the binary that crashed when running agentctl start. To find which makefile handles the linking of dbsnmp, you can run:
su - oracle find $ORACLE_HOME -name "*.mk" | xargs grep -l dbsnmp
$ su - oracle
$ find $ORACLE_HOME -name "*.mk" | xargs grep -l dbsnmp
/u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk
/u01/app/oracle/product/9.2.0/network/lib/env_oemagent.mk
$
To relink
dbsnmp and all associated executable files which are maintained by the ins_oemagent.mk makefile, run:
su - oracle cd $ORACLE_HOME/network/lib make -f ins_oemagent.mk install
$ su - oracle
$ cd $ORACLE_HOME/network/lib
$ make -f ins_oemagent.mk install
Now you should be able to start the agent:
su - oracle agentctl start
$ su - oracle
$ agentctl startNote
Do not forget to undo the links to
/usr/bin/gcc and /usr/bin/g++ if you do not need them any more. You may also want to undo the changes in /etc/ld.so.preload file.
Chapter 36. Installing Oracle9i R2 (9.2.0.6.0) on Red Hat Enterprise Linux 4
링크 복사링크가 클립보드에 복사되었습니다!
In order to install Oracle9i Release 2 (9.2.0.6), the 9.2.0.6 patch set must be applied for the Oracle database server (patch number 3948480) after the Oracle9i Release 2 (9.2.0.4) installation. For more information, see Oracle9i Release Notes Release 2 (9.2.0.4.0) for Linux x86 - Red Hat Enterprise Linux 4 Certification Update.
36.1. Installing Oracle9i R2 (9.2.0.4.0) on Red Hat Enterprise Linux 4
링크 복사링크가 클립보드에 복사되었습니다!
Before you continue, ensure all the required RPMs are installed, see Checking Packages (RPMs). Also ensure LD_ASSUME_KERNEL is set to 2.4.19 (see Setting Oracle Environments):
su - oracle echo $LD_ASSUME_KERNEL
$ su - oracle
$ echo $LD_ASSUME_KERNEL
2.4.19
$
Now execute
runInstaller:
su - oracle echo $LD_ASSUME_KERNEL /media/cdrom/runInstaller
$ su - oracle
$ echo $LD_ASSUME_KERNEL
2.4.19
$ /media/cdrom/runInstaller
- Welcome Screen: Click
- Inventory Location: Click OK
- Unix Group Name: Use "oinstall" and click . When asked to run
/tmp/orainstRoot.sh enter the following into the command line
/tmp/orainstRoot.sh
/tmp/orainstRoot.sh
Then click
- File Locations: Use default values
- Available Products: Select ""
- Installation Types: Select since we only want to install the software for now
- Available Products: Click or add some more components and then click . - Components Locations: Accept the default values and click
- Privileged Operating System Groups: Use the default values:
OSDBA Group = dba, OSOPER Group = dba
- Oracle Managent Server Repository: Use the default choice
- Create database: Select since we first need to patch the Oracle database software
- Summary: Start the Install
36.2. Patching Oracle9i R2 to 9.2.0.6.0 on Red Hat Enterprise Linux 4
링크 복사링크가 클립보드에 복사되었습니다!
Download the patch 3948480, Oracle9i Patch Set Release 2 (9.2.0.6) Patch Set 5, from http://metalink.oracle.com and execute the following commands to extract it:
Now download the patch 4188455 from http://metalink.oracle.com. This patch is needed for launching the
runInstaller that came with the patch 3948480 we just downloaded above.
The
/tmp/oraparam.ini file will now be used for launching the runInstaller that came with the patch 3948480.
To patch the
runInstaller application, run:
su - oracle $ echo $LD_ASSUME_KERNEL 2.4.19 $ /tmp/Disk1/install/runInstaller - paramFile /tmp/oraparam.ini
su - oracle
$ echo $LD_ASSUME_KERNEL
2.4.19
$ /tmp/Disk1/install/runInstaller - paramFile /tmp/oraparam.ini
- Welcome Screen: Click
- File Locations: Use default values (in this example:
/tmp/Disk1/stage/products.xml)
- Available Products: Select ""
- Summary: Click
- At the end of the installation, you must exit runInstaller
Ensure that no Oracle processes are running:
ps -ef | grep ora
ps -ef | grep ora
Now patch Oracle9i R2:
su - oracle $ echo $LD_ASSUME_KERNEL # it is important that this variable is set! 2.4.19 $ /tmp/Disk1/install/runInstaller -paramFile /tmp/oraparam.ini
su - oracle
$ echo $LD_ASSUME_KERNEL # it is important that this variable is set!
2.4.19
$ /tmp/Disk1/install/runInstaller -paramFile /tmp/oraparam.ini
- Welcome Screen: Click
- File Locations: Use default values (in this example:
/tmp/Disk1/stage/products.xml)
- Available Products: Select ""
- Summary: Click
When you are asked to run
root.sh, run it before you click
- At the end of the installation, exit runInstaller.
After the 9.2.0.6 patchset has been applied, download the patch 4190568 from http://metalink.oracle.com. Download the
opatch utility for release 10.1.0.2 (patch 2617419) from http://metalink.oracle.com.
To install
opatch, run:
su - oracle $ cp p2617419_10102_GENERIC.zip /tmp $ cd /tmp $ unzip p2617419_10102_GENERIC.zip $ cp -a /tmp/OPatch/ $ORACLE_HOME
su - oracle
$ cp p2617419_10102_GENERIC.zip /tmp
$ cd /tmp
$ unzip p2617419_10102_GENERIC.zip
$ cp -a /tmp/OPatch/ $ORACLE_HOME
To apply the 4190568 patch, run
su - oracle $ unzip p4190568_9206_LINUX.zip $ cd 4193454 $ export PATH=$PATH:$ORACLE_HOME/OPatch $ opatch apply
su - oracle
$ unzip p4190568_9206_LINUX.zip
$ cd 4193454
$ export PATH=$PATH:$ORACLE_HOME/OPatch
$ opatch apply
If you intend to use Direct I/O Support, you must also download and apply patch 2448994.
Now you should be able to create a database with dbca:
su - oracle dbca
$ su - oracle
$ dbca
If
dbca dies on the system with the following error:
/u01/app/oracle/product/9.2.0/bin/dbca: line 124: 26649 Segmentation fault $JRE_DIR/bin/jre -DORACLE_HOME=$OH -DJDBC_PROTOCOL=thin -mx64m -classpath $CLASSPATH oracle.sysman.assistants.dbca.Dbca $ARGUMENTS
/u01/app/oracle/product/9.2.0/bin/dbca: line 124: 26649 Segmentation fault
$JRE_DIR/bin/jre -DORACLE_HOME=$OH -DJDBC_PROTOCOL=thin -mx64m -classpath $CLASSPATH oracle.sysman.assistants.dbca.Dbca $ARGUMENTS
You can execute the following command:
su - root touch /etc/rac_on
su - root
touch /etc/rac_on
Now you can restart the process to get
dbca to work.
Chapter 37. Starting and Shutting down the Oracle9i Database
링크 복사링크가 클립보드에 복사되었습니다!
This chapter shows two separate ways to start and shut down an Oracle9i Database; Using SQLplus and using the
ORACLE_HOME binaries.
37.1. sqlplus
링크 복사링크가 클립보드에 복사되었습니다!
Note
In Oracle9i
svrmgrl is no longer supported, however, you can now do everything with sqlplus so nothing is lost.
To start up the database, run the following commands:
oracle$ sqlplus /nolog SQL> connect / as sysdba SQL> startup
oracle$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startup
The slash connects you to the schema owned by SYS. So in this example you will be connected to the schema owned by SYS with the privilege
SYSDBA. SYSDBA gives you the following privileges:
sysoperprivileges WITH ADMIN OPTION- create databases
- recover one or more databases to a point
37.2. Using the Oracle binaries dbstart and dbstop
링크 복사링크가 클립보드에 복사되었습니다!
Note
The
dbstart and dbstop commands are in the $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut directories respectively.
You can use
$ORACLE_HOME/bin/dbstart to start up the database, and $ORACLE_HOME/bin/dbshut to shut down the database. To get $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut working, you need to change the third field for your Oracle SID in /etc/oratab from "N" to "Y".
No to read:
test:/u01/app/oracle/product/9.2.0:N
test:/u01/app/oracle/product/9.2.0:N
Yes to read:
test:/u01/app/oracle/product/9.2.0:Y
test:/u01/app/oracle/product/9.2.0:Y
In some cases you may have to copy the init file for your SID (in this example “
test”) from /u01/app/oracle/admin/test/pfile to $ORACLE_HOME/dbs to get dbstart and dbshut working. In the Below command remember to change test to something appropriate.
cp /u01/app/oracle/admin/test/pfile/inittest.ora.642002224936 \ $ORACLE_HOME/dbs/inittest.ora
cp /u01/app/oracle/admin/test/pfile/inittest.ora.642002224936 \
$ORACLE_HOME/dbs/inittest.ora
Then make sure that your init file already exists in
$ORACLE_HOME/dbs.
Chapter 38. Oracle Installation Errors
링크 복사링크가 클립보드에 복사되었습니다!
This chapter covers many common errors and pitfalls associated with installing an Oracle9i Database.
Log Files
Always check first the error logs for 9.2.0 in /tmp/OraInstall*, where "*" will be the date of the install, for example /tmp/OraInstall2002-07-04_09-50-19PM. When you problems with make, see also the $ORACLE_HOME/install/make.log file.
make ProblemsFirst ensure that gcc is installed on your system by executing:
which gcc
$ which gcc
/usr/bin/gcc
Here is the command to find the RPM package name for
/usr/bin/gcc:
rpm -qf /usr/bin/gcc
$ rpm -qf /usr/bin/gcc
gcc-2.96-98
Verify that your error is not one of the other error messages below. See Chapter 31, Verifying Required Packages(RPMs) for more information on whether you have the correct packages.
Error in invoking target install of makefile/u01/app/oracle/product/9.2.0/ctx/lib/ins_ctx.mk
You may see the following errors in $ORACLE_HOME/install/make.log:
/lib/libdl.so.2: undefined reference to `_dl_addr@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_open@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_close@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_sym@GLIBC_PRIVATE' /lib/libdl.so.2: undefined reference to `_dl_vsym@GLIBC_PRIVATE'
/lib/libdl.so.2: undefined reference to `_dl_addr@GLIBC_PRIVATE'
/lib/libdl.so.2: undefined reference to `_dl_open@GLIBC_PRIVATE'
/lib/libdl.so.2: undefined reference to `_dl_close@GLIBC_PRIVATE'
/lib/libdl.so.2: undefined reference to `_dl_sym@GLIBC_PRIVATE'
/lib/libdl.so.2: undefined reference to `_dl_vsym@GLIBC_PRIVATE'
This error comes up when the following step is executed:
/usr/bin/make -f ins_ctx.mk install ORACLE_HOME=/u01/app/oracle/product/9.2.0
/usr/bin/make -f ins_ctx.mk install ORACLE_HOME=/u01/app/oracle/product/9.2.0
Edit the file
$ORACLE_HOME/ctx/lib/env_ctx.mk, add "$(LDLIBFLAG)dl" to the "INSO_LINK =" line. The updated line should with the added "$(LDLIBFLAG)dl" flag, should look like this:
INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m $(LDLIBFLAG)dl $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)
INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m $(LDLIBFLAG)dl $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)
After that hit in the error pop-up.
If this did not fix the problem, try the following solution:
Edit the file
$ORACLE_HOME/ctx/lib/env_ctx.mk again, go to "INSO_LINK =", remove the above entry you made and add "`cat $(LIBHOME)/sysliblist`" to the line and save it. This is what the updated line, with the added "`cat $(LIBHOME)/sysliblist`" string, look like:
INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m `cat $(LIBHOME)/sysliblist` $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)
INSO_LINK = -L$(CTXLIB) $(LDLIBFLAG)m `cat $(LIBHOME)/sysliblist` $(LDLIBFLAG)sc_ca $(LDLIBFLAG)sc_fa $(LDLIBFLAG)sc_ex $(LDLIBFLAG)sc_da $(LDLIBFLAG)sc_ut $(LDLIBFLAG)sc_ch $(LDLIBFLAG)sc_fi $(LLIBCTXHX) $(LDLIBFLAG)c -Wl,-rpath,$(CTXHOME)lib $(CORELIBS) $(COMPEOBJS)
After that hit in the error pop-up.
ORA-27123: unable to attach to shared memory segment
This error, "ORA-27123: unable to attach to shared memory segment", message may came up when the Oracle Database Configuration Assistant was running. Execute the following command to temporarily increase the maximum shared memory size:
Then click for the Oracle Database Configuration Assistant.
It is recommended to increase the shmmax setting permanently for Oracle9i. So if you want to increase the maximum shared memory size permanently, add the following line to the
/etc/sysctl.conf file:
kernel.shmmax=1073741824
kernel.shmmax=1073741824
For more information on setting shared memory parameters for Oracle, see Chapter 7, Setting Shared Memory.
ORA-03113: end-of-file on communication channel
You may see this error, ORA-03113: end-of-file on communication channel, when you run the "Database Configuration Assistant" and "sqlplus". It can be caused by shmmax parameter being too small. Make sure to increase shmmax permanently. Read Chapter 7, Setting Shared Memory for information on how to increase the shmmax parameter.
Error in invoking target install of make file /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk
If you see the error, Error in invoking target install of make file /u01/app/oracle/product/9.2.0/network/lib/ins_oemagent.mk, on Red Hat Enterprise Linux 3, follow the guide lines at Chapter 35, Installing Oracle9i R2 (9.2.0.4.0) on Red Hat Enterprise Linux 3.
An error when executing "
agentctl start"
The error below may have occurred when "agentctl start" is executed.
You are probably trying to start the agent on Red Hat Enterprise Linux 3. See Section 35.3, “Patching Oracle Intelligent Agent on Red Hat Enterprise Linux 3”for how to resolve it.
Errors in
dbcaIf you receive the error:
or
/u01/app/oracle/product/9.2.0/bin/dbca: line 124: 26649 Segmentation fault $JRE_DIR/bin/jre -DORACLE_HOME=$OH -DJDBC_PROTOCOL=thin -mx64m -classpath $CLASSPATH oracle.sysman.assistants.dbca.Dbca $ARGUMENTS
/u01/app/oracle/product/9.2.0/bin/dbca: line 124: 26649 Segmentation fault
$JRE_DIR/bin/jre -DORACLE_HOME=$OH -DJDBC_PROTOCOL=thin -mx64m -classpath
$CLASSPATH oracle.sysman.assistants.dbca.Dbca $ARGUMENTS
If this happens, try the following:
su - root
$ su - root
touch /etc/rac_on
Now try to restart
dbca.
Another option is to edit
$ORACLE_HOME/bin/dbca and to put the following lines under comment except the line not preceded by a hash:
Now try to restart dbca.
gcc errors in Red Hat Enterprise Linux 3When installing or running Oracle on Red Hat Enterprise Linux 3 you may encounter this gcc error.
To fix the linking problem, execute the following commands:
mv /usr/bin/gcc /usr/bin/gcc323 mv /usr/bin/g++ /usr/bin/g++323 ln -s /usr/bin/gcc296 /usr/bin/gcc ln -s /usr/bin/g++296 /usr/bin/g++
# mv /usr/bin/gcc /usr/bin/gcc323
# mv /usr/bin/g++ /usr/bin/g++323
# ln -s /usr/bin/gcc296 /usr/bin/gcc
# ln -s /usr/bin/g++296 /usr/bin/g++
Now you should be able to relink the oracle binary again.
Once you are done, you may want to undo the changes you have performed above:
mv /usr/bin/gcc323 /usr/bin/gcc mv /usr/bin/g++323 /usr/bin/g++
# mv /usr/bin/gcc323 /usr/bin/gcc
# mv /usr/bin/g++323 /usr/bin/g++./runInstaller: line 58: ./runInstaller: cannot execute binary file
You are probably trying to run a 64 bit Oracle version on a 32 bit Linux system. Make sure you downloaded the right Oracle version for your Linux system.
To check if runInstaller is a 32 bit binary or a 64 bit binary, run the following command:
cd /mnt/cdrom file install/linux/runInstaller
$ cd /mnt/cdrom
$ file install/linux/runInstaller
install/linux/runInstaller: ELF 32 bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.0.0, dynamically linked (uses shared libs), not stripped
To check if your Linux system is 32 bit system or a 64 bit system, run e.g. the following command:
file /sbin/init
$ file /sbin/init
/sbin/init: ELF 32 bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), not strippedThe Oracle installer runInstaller Hangs
The Oracle installer runInstaller hangs at:
Installing Java Runtime Environment... Link pending... Copying README...
Installing Java Runtime Environment... Link pending... Copying README...
You may encounter this problem on Red Hat Enterprise Linux 3. You probably forgot to set the environment variable
LD_ASSUME_KERNEL to 2.4.1.
To rectify this problem, run the following command and then restart
runInstaller:
oracle$ export LD_ASSUME_KERNEL=2.4.1
oracle$ export LD_ASSUME_KERNEL=2.4.1Recovery Manager(rman) Hangs
You are probably running the wrong rman binary from the XFree86-devel RPM:
which rman
$ which rman
/usr/X11R6/bin/rmanCan't find init file for Database "SID"
You may see this error when you start the database with dbstart.
Copy the init file for your SID (in this example “test”) from from
/u01/app/oracle/admin/test/pfile to $ORACLE_HOME/dbs to get dbstart and dbshut working:
cp /u01/app/oracle/admin/test/pfile/inittest.ora.642002224936 $ORACLE_HOME/dbs/inittest.ora
cp /u01/app/oracle/admin/test/pfile/inittest.ora.642002224936 $ORACLE_HOME/dbs/inittest.oraError in setting permissions of file/directory /u01/app/oracle/jre/1.1.8/bin/i686/native_threads/.extract_args
This may happen if the CD was not burned correctly. The solution is to check the image checksums and then burn the cd again or download the image again.
Various Oracle SID Errors
If you get the error ORA-01034: ORACLE not available, ORA-27101: shared memory realm does not exist, Linux Error: 2: No such file or directory or ORA-01034: ORACLE not available then check if ORACLE_SID is set correctly.
If
ORACLE_SID is set correctly, then you probably have a trailing slash "/" on the ORACLE_HOME environment variable. Remove it by changing ORACLE_HOME=/u01/app/oracle/product/9.2.0/ to ORACLE_HOME=/u01/app/oracle/product/9.2.0 and try again to connect to sys. Remember the ORACLE_HOME parameter may be slightly different on your machine.
jre was not found in /tmp/OraInstall/jre/bin/i586/green_threads/jre
You are probably running runInstaller on a 586 machine, or your AMD CPU is falsely recognized as 586 (the case for a AMD K6-III-400). You can check your machine (hardware) type by executing "uname -m". If you are not running on a 586 or on a AMD machine, try to link jre to java and see if this solves your problem.
To rectify the problem with the 586 machine or with the AMD CPU, create a link for lib and bin from i586 to i686 and make the i686 directories read only. For example:
ln -s /tmp/OraInstall/jre/bin/i686 /tmp/OraInstall/jre/bin/i586 ln -s /tmp/OraInstall/jre/lib/i686 /tmp/OraInstall/jre/lib/i586 chmod u-w /tmp/OraInstall/jre/bin/i686/tmp/OraInstall/jre/lib/i686
ln -s /tmp/OraInstall/jre/bin/i686 /tmp/OraInstall/jre/bin/i586
ln -s /tmp/OraInstall/jre/lib/i686 /tmp/OraInstall/jre/lib/i586
chmod u-w /tmp/OraInstall/jre/bin/i686/tmp/OraInstall/jre/lib/i686
Now restart
runInstaller.
./jre/bin/i386/native_threads/java: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory
You probably forgot to install the compat-libstdc++ RPM, the package for "Standard C++ libraries for Red Hat Linux 6.2 backwards compatibility". To rectify this problem, install the compat-libstdc++ RPM. Read Chapter 31, Verifying Required Packages(RPMs) for more information.
/u01/app/oracle/jre/1.1.8/bin/../lib/i686/green_threads/libzip.so: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference (libzip.so) Unable to initialize threads: cannot find class java/lang/Thread Could not create Java VM
You may experience this problem when running the Database Configuration Assistant dbca on Red Hat Enterprise Linux 3 but forgot to set the LD_ASSUME_KERNEL environment variable.
To rectify this problem, run the following command as the
oracle user on Red Hat Enterprise Linux 3 and restart dbca:
oracle$ export LD_ASSUME_KERNEL=2.4.1
oracle$ export LD_ASSUME_KERNEL=2.4.1lsnrctl status or lsnrctl start Errors
When lsnrctl status or lsnrctl start are executed you may get the following output:
One of the possibilities are that the
/var/tmp/.oracle directory does not exist. If that is the case, run the following commands:
su - root # mkdir /var/tmp/.oracle # chown oracle:dba /var/tmp/.oracle
su - root
# mkdir /var/tmp/.oracle
# chown oracle:dba /var/tmp/.oracle
Now try to run
lsnrctl start as oracle again.
Java Cannot Connect to X11
First ensure you followed the instructions in Chapter 33, Starting runInstaller very closely.
If you get this error:
Note
If you use newer Red Hat Enterprise Linux versions as your desktop and you want to install the database on another machine, then you need to set the
DisallowTCP entry in /etc/X11/gdm/gdm.conf for the GNOME Display Manager to read:
DisallowTCP=false
After that you need to restart your X server. You can do this runnning the init command as root:
# init 3# init 5
Other Errors
For other errors, issues and problems your best bet is to search the Oracle on Linux Discussion Forum.
Chapter 39. Reference List
링크 복사링크가 클립보드에 복사되었습니다!
To read the Oracle MetaLink links refer to http://metalink.oracle.com and input the numbers. Note that registration is required.
Oracle MetaLink Note:200266.1
Oracle MetaLink Note:225751.1
Oracle MetaLink Note:249213.1
Oracle MetaLink Note:260152.1
Oracle MetaLink Note:262004.1
Oracle MetaLink Note:265194.1
Oracle MetaLink Note:270382.1
Oracle MetaLink Note:280463.1
Oracle MetaLink Note:329378.1
Oracle MetaLink Note:344320.1
Appendix A. Revision History
링크 복사링크가 클립보드에 복사되었습니다!
| Revision History | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Revision 1.5-11 | Mon Jun 30 2014 | |||||||||
| ||||||||||
| Revision 1.5-9 | Wed Apr 16 2014 | |||||||||
| ||||||||||
| Revision 1.5-5 | Thursday July 18 2013 | |||||||||
| ||||||||||
| Revision 1.4-1 | September 1 2008 | |||||||||
| ||||||||||
| Revision 1.1-1 | November 1 2007 | |||||||||
| ||||||||||
| Revision 1.01-1 | July 2 2007 | |||||||||
| ||||||||||
| Revision 1.00-1 | July 2 2007 | |||||||||
| ||||||||||
Legal Notice
링크 복사링크가 클립보드에 복사되었습니다!
Copyright © 2007, 2008, 2012 Red Hat, Inc..
Red Hat owns the copyright to this and all other subsequent derivative works. Werner Puschitz retains the copyright to the original at www.puschitz.com
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
All other trademarks are the property of their respective owners.
1801 Varsity Drive
Raleigh, NC 27606-2072 USA
Phone: +1 919 754 3700
Phone: 888 733 4281
Fax: +1 919 754 3701
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}