Oracle Legal Notices
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
License Restrictions Warranty/Consequential Damages Disclaimer
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
Restricted Rights Notice
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.
Hazardous Applications Notice
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Third-Party Content, Products, and Services Disclaimer
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
Alpha and Beta Draft Documentation Notice Disclaimer
If this document is in preproduction status:
This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.
This document contains information on Oracle Linux Release 6 Update 4. This document may be updated after it is released. To check for updates to this document, and to view other Oracle documentation, refer to the Documentation section on the Oracle Technology Network (OTN) Web site:
This document is intended for users and administrators of Oracle Linux. It describes potential issues and the corresponding workarounds you may encounter while using Oracle Linux. Oracle recommends that you read this document before installing or upgrading Oracle Linux.
Document generated on: 2013-07-10 (revision: 1091)
Table of Contents
The Oracle Linux Release Notes provides a summary of the new features, changes, and fixed and known issues in Oracle Linux Release 6 Update 4.
This document is written for system administrators who want to install or update Oracle Linux. It is assumed that readers have a general understanding of the Linux operating system.
The document is organized as follows:
Chapter 1, New Features and Changes contains a summary of the new features and changes in this release.
Chapter 2, Fixed and Known Issues contains details of the fixed and known issues with the software.
Chapter 3, Upgrading to Oracle Linux 6 Update 4 contains information about how to install updates on your system.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.
The latest version of this document and other documentation for this product are available at:
The following text conventions are used in this document:
Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
Table of Contents
This chapter describes the new features that are introduced by Oracle Linux 6 Update 4.
Oracle Linux 6 Update 4 ships with two sets of kernel packages:
Unbreakable Enterprise Kernel Release 2
Red Hat Compatible Kernel (
By default, both the Unbreakable Enterprise Kernel and the Red Hat Compatible Kernel for the specific architecture (i386 or x86_64) are installed and the system boots the Unbreakable Enterprise Kernel.
To make your system use the Red Hat Compatible Kernel by default:
/etc/grub.conf and change the value of the
default parameter to indicate the Red Hat Compatible Kernel. (Each
entry for a bootable kernel in the file starts with a
definition. The entries are effectively numbered from 0 upwards, where 0 corresponds to
the first entry in the file, 1 to the second entry, and so on. To view the GRUB manual,
use the info grub command.)
/etc/sysconfig/kernel and change the setting for the default
kernel package type from
The Unbreakable Enterprise Kernel Release 2 (UEK R2) is based on the upstream kernel 3.0.36 stable source tree.
The Unbreakable Enterprise Kernel supports a wide range of hardware and devices. In close cooperation with hardware and storage vendors, the following device drivers have been updated by Oracle in the 2.6.39-400 kernel.
NetXtreme II iSCSI driver (
bnx2i) updated to 184.108.40.206f.
NetXtreme II Fibre Channel over Ethernet driver (
updated to 2.2.17.
Blade Engine 2 Open-iSCSI driver (
be2iscsi) updated to
Fibre Channel HBA driver (
lpfc) updated to 220.127.116.11.2p.
ConnectX core driver (
mlx4_core) released at 1.0-ofed1.5.5
(x86_64 only). Handles low-level functions such as device initialization and firmware
commands processing, and controls resource allocation so that the InfiniBand and
Ethernet functions can share a device without interfering with each other.
ConnectX Ethernet driver (
mlx4_en) released at 18.104.22.168 (x86_64
only). Handles Ethernet-specific functions and plugs into the netdev mid-layer.
ConnectX InfiniBand driver (
mlx4_ib) released at 1.0-ofed1.5.5
(x86_64 only). Handles InfiniBand-specific functions.
Fibre Channel HBA driver (
qla2xxx) updated to
iSCSI driver (
qla4xxx) updated to 5.03.00.01.06.02-uek2. Now
NetXtreme II network adapter driver (
bnx2) updated to
NetXtreme II 10Gbps network adapter driver (
bnx2x) updated to
Converged Network Interface Card core driver (
cnic) updated to
Tigon3 Ethernet adapter driver (
tg3) updated to 3.125g.
Blade Engine 2 10Gbps adapter driver (
be2net) updated to
PRO/1000 PCI-Express Gigabit network adapter driver (
updated to 2.1.4-NAPI.
Gigabit Ethernet network adapter driver (
igb) updated to
10 Gigabit PCI-Express network adapter driver (
10 Gigabit Server Adapter virtual function driver (
updated to 2.6.2-NAPI. The kernel must support Single Root I/O Virtualization
NetXen Multiport 1/10 Gigabit Network adapter driver
netxen_nic) updated to 4.0.80.
1/10 GbE Converged/Intelligent Ethernet Adapter driver (
updated to 22.214.171.124.
QLE81xx network adapter driver (
qlge) updated to
Reliable Datagram Sockets driver (
rds) updated to 4.1. RDS
provides in-order, non-duplicated, highly-available, low-overhead, reliable delivery
of datagrams between hundreds of thousands of non-connected endpoints.
This release of the Unbreakable Enterprise Kernel includes the following new functionality:
The following InfiniBand hardware is supported with the Unbreakable Enterprise Kernel:
Mellanox ConnectX-2 InfiniBand Host Channel Adapters
Sun InfiniBand QDR Host Channel Adapter PCIe #375-3696
InfiniBand support via the
rdma package. To start the
rdma service, and enable it to load all the required modules
automatically when you reboot the system, run the following commands as
# service rdma start # chkconfig --level 2345 rdma on
To stop or restart the
rdma service, use the following
# service rdma stop # service rdma restart
To configure which upper-layer modules the
rdma service should
The Linux Containers template script for Oracle Linux
lxc-oracle) supports the creation of containers for Oracle
Enterprise Linux 4, Oracle Linux 5, and Oracle Linux 6, downloading and installing the
release RPMs from the Public Yum repository.
Several improvements have been incorporated to support Xen usage with the Unbreakable Enterprise Kernel:
Numerous bug fixes and performance improvements.
Added support for more than 128 GB in a PV guest.
Xen Machine Check Exception (MCE) driver added (allows you to view MCE events that the Xen hypervisor receives).
Xen Physical CPU (PCPU) driver added (allows management tools to online or offline physical CPUs in dom0).
Xen Processor Aggregator Device (PAD) added (enables configuration and control of all processors on a platform).
The following sections detail notable new features in this update for the Red Hat Compatible Kernel.
You can create, resize, and remove RAID10 volumes in LVM, where striping is laid out across an array of mirrors.
To create a RAID 10 logical volume, use the following form of the lvcreate command:
# lvcreate --type raid10 -m
For example, the following command would create a 200 GB RAID10 volume named
myr10vol with four stripes and two mirrors in the
# lvcreate --type raid10 -m 1 -i 4 -L 200G -n myr10vol myvg
The -m option specifies the number of additional copies of the data, not the total number of copies.
The following new boot options are available:
Specifies the bonded network interface, the network connections to be bonded to the interface, and any additional options.
Specifies a network device's numeric 802.1q tag to allow installation over a VLAN.
The following new Kickstart options are available with the
Specifies the network connections to be bonded to the network interface, and any additional options.
Specifies a network device's numeric 802.1q tag to allow installation over a VLAN.
The new Kickstart
fcoe keyword allows you to enable Fibre Channel
over Ethernet (FCoE) devices in addition to Enhanced Disk Drive Services (EDD) discovered
devices. The following options are available with the
Specifies that VLANs should be discovered automatically.
Specifies settings for Data Center Bridging (DCB).
Specifies the name of the FCoE device to activate.
udev maintains persistent device names for devices such as
/dev/sdb by creating symbolic links such as
/dev/disk/by-uuid/e8d40553-43f2-4ae6-8e4b-38e04e7ee41c. The kernel
message log now records each
udev persistent device name mapping in the
The uncore feature of the
perf event subsystem implements Performance
Monitoring Unit (PMU) support for the Intel Xeon Processor X55xx and X56xx processor
families. Multiple processor cores can share physical uncore subsystems, including the L3
cache. Uncore PMU support allows packages to collect performance data, including load
latency at various levels in the cache and memory hierarchy, which ranges from
micro-operation dispatch up to globally observable data. Debugging in
perf is made possible by the implementation of PMU event
The following features included in the Unbreakable Enterprise Kernel Release 2 are still under development, but are made available for testing and evaluation purposes.
Kernel module signing facility
Applies cryptographic signature checking to modules on module load, checking the signature against a ring of public keys compiled into the kernel. GPG is used to do the cryptographic work and determines the format of the signature and key data.
Linux Containers (lxc)
Based on the Linux Cgroups and name spaces functionality, containers allow you to
safely and securely run multiple applications or instances of an operating system on a
single host without risking them interfering with each other. Containers are lightweight
and resource-friendly, which saves both rack space and power. In order to get started with
containers, you need to install the
lxc package, which is included in
the package repository of the Unbreakable Enterprise Kernel.
Transcendent memory (tmem)
Transcendent Memory provides a new approach for improving the utilization of physical memory in a virtualized environment by claiming underutilized memory in a system and making it available where it is most needed. From the perspective of an operating system, tmem is fast pseudo-RAM of indeterminate and varying size that is useful primarily when real RAM is in short supply. To learn more about this technology and its use cases, see the Transcendent Memory project page on oss.oracle.com: http://oss.oracle.com/projects/tmem/
Distributed Replicated Block Device (DRBD)
A shared-nothing, synchronously replicated block device (RAID1 over network), designed to serve as a building block for high availability (HA) clusters. It requires a cluster manager (for example, pacemaker) to implement automatic failover.
The following Technology Preview features are currently not supported under Oracle Linux 6 and may not be functionally complete:
DIF/DIX support for SCSI
IPv6 support in IPVS
LVM RAID support
Open multicast ping (
System Information Gatherer and Reporter (SIGAR)
Trusted Platform Module (TPM)
The following Technology Preview features are only available when running the Red Hat Compatible Kernel (RHCK):
Brocade BFA driver
Diagnostic pulse for the
Error Detection And Correction (EDAC) driver interface
Fibre Channel over Ethernet (FCoE) target mode
Kernel Media support
KVM Live Snapshots
KVM network drivers wire-speed requirement
Remote audit logging
Single Root I/O Virtualization (SR-IOV) on the
System monitoring via SNMP
These features are not suitable for production use, but are included to give them wider exposure.
The following packages have been added to the upstream release:
The following packages have been modified from the upstream release:
Unless otherwise noted, changes relate to distro renaming, trademark usage, or user-interface modifications.
The following packages from the upstream release are not included:
This chapter describes the fixed and known issues for Oracle Linux 6 Update 4.
Run the yum update command regularly to ensure that the latest bug fixes and security errata are installed on your system.
The following issues have been fixed in this update:
The updated automounter package (
autofs) allows NetApp filer
paths to be automounted. (Bug ID 12658280)
The legacy DNS resolver in the UEK R2 kernel now supports the sending of NFSv4
referrals (lists of NFS servers and exported NFS file systems) to Oracle Linux 6
clients. The user-space component is included with the
package. (Bug ID 14769650)
This section describes known issues in this update.
If the SELinux policy packages have not been updated recently, Cluster Ready Services
(CRS) might fail to start with messages such as the following in
SELinux is preventing /usr/lib/oracleasm/oracleasm-instantiate-disk from associate access on the filesystem DATA1.
The solution is to upgrade the
selinux-policy-targeted packages to ensure that you are running a version
no earlier than 126.96.36.199.1.el6_4.5:
# yum update 'selinux-policy*'
After upgrading the packages, reboot the system. (Bug ID 13925445)
Releases of Oracle Linux prior to Oracle Linux 5 supplied a hugemem kernel to allow a system to address up to 64 GB of memory in 32-bit mode. The hugemem kernel is no longer available in Oracle Linux 5 and later releases.
The Unbreakable Enterprise Kernel (UEK) supports a maximum of 16 GB of memory for 32-bit kernels on bare metal and hardware virtualized machine (HVM) systems, and 8 GB for fully paravirtualized machine (PVM) systems. 32-bit PVM guest operating systems must be located in the first 128 GB of physical memory on the host.
The Red Hat Compatible Kernel (RHCK) has the same limitations, except that PVM systems can have up to 16 GB of memory. The limitation of 8 GB for PVM on UEK was chosen for reasons of reliability.
A 32-bit system uses the PAE (physical address extension) memory feature to map physical memory beyond 4 GB into the 32-bit address space that is available to each process. A 64-bit system can address memory beyond 4 GB without requiring an extra layer of memory abstraction.
Oracle Linux on x86_64 includes 32-bit libraries, which allow applications built for both 64-bit and 32-bit Linux to run on the same system. This capability provides scalability to virtually unlimited memory sizes, while retaining the ability to run 32-bit applications. Oracle recommends this configuration for any system with more than 4 GB of memory. (Bug ID 16974301)
The Linux Containers package (
lxc) is not available for the i386
Running with SELinux enabled on the host can cause issues with Linux Containers. The
workaround is to disable SELinux altogether by setting
/etc/selinux/config and rebooting the system. Using the
setenforce Permissive command is not sufficient as the
selinuxfs pseudo file system remains mounted. (Bug ID 15967411)
The default location for a container's configuration has changed from
To start a container that you created with a previous update of Oracle Linux, specify the -f option to lxc-start, for example:
# lxc-start -n ol6u3 -f /etc/lxc/ol6u3/config
To convert an existing container to use the new location:
Move the container's configuration directory to
# mv /etc/lxc/
file and change the values of any
lxc.mount parameters to refer to
/container instead of
For example, if the
config file contained the following
lxc.rootfs = /etc/lxc/example/rootfs lxc.mount.entry=/lib /etc/lxc/example/rootfs/lib none ro,bind 0 0 lxc.mount.entry=/usr/lib /etc/lxc/example/rootfs/usr/lib none ro,bind 0 0 lxc.mount.entry=/lib64 /etc/lxc/example/rootfs/lib64 none ro,bind 0 0 lxc.mount.entry=/usr/lib64 /etc/lxc/example/rootfs/usr/lib64 none ro,bind 0 0
you would change these entries to read:
lxc.rootfs = /container/example/rootfs lxc.mount.entry=/lib /container/example/rootfs/lib none ro,bind 0 0 lxc.mount.entry=/usr/lib /container/example/rootfs/usr/lib none ro,bind 0 0 lxc.mount.entry=/lib64 /container/example/rootfs/lib64 none ro,bind 0 0 lxc.mount.entry=/usr/lib64 /container/example/rootfs/usr/lib64 none ro,bind 0 0
After converting the container, you do not need to specify the -f option to lxc-start. (Bug ID 15967411)
When using the
bnx2x driver in a bridge, disable Transparent Packet
Aggregation (TPA) by including
options bnx2x disable_tpa=1 in
/etc/modprobe.conf. (Bug ID 14626070)
Running btrfs filesystem balance converts a non-RAID or concatenated file system setup to RAID-0 after adding a new device. Do not run this command if you do not intend to convert the profile of the file system after adding the new device. (Bug ID 13715389)
Converting an existing
ext4 root file system to
btrfs does not carry over the
associated security contexts that are stored as part of a file's extended attributes. With
SELinux enabled and set to enforcing mode, you might experience many
denied errors after reboot, and the system might be unbootable. To avoid this
problem, enforce automatic file system relabeling run at bootup time. To trigger automatic
relabeling, create an empty file named
autorelabel (for example, by using
touch) in the file system's root directory before rebooting the system
after the initial conversion. The presence of this file instruct SELinux to recreate the
security attributes for all files on the file system. If you forget to do this and rebooting
fails, either temporarily disable SELinux completely by adding
the kernel boot parameters, or disable enforcing of the SELinux policy by adding
enforcing=0. (Bug ID 13806043)
A failing RAID1 disk might result in a kernel panic with the error
error (device (null)) in btree_writepage_io_failed_hook:3662: IO failure (Error occurred
while writing out btree at offset). (Bug ID 16262571)
The btrfs subvolume get-default command lists all existing subvolumes instead of only the default subvolume. (Bug ID 13815433)
The btrfs filesystem defragment command exits with an exit code of 20 even if it succeeds. (Bug ID 13714531)
Commands such as du might show inconsistent results for file sizes in a btrfs file system when the number of bytes that is under delayed allocation is changing. (Bug ID 13096268)
Btrfs has a limit of 237 hard links to a file. Attempting to create more than this number
of links results in the error
Too many links. (Bug ID 16278563)
You might see a message similar to the following during the first reboot of an HP ProLiant server:
[Firmware Bug]: the BIOS has corrupted hw-PMU resources (MSR 186 is 43003c)
You can safely ignore this message. The functionality and performance of the operating system and the server are not affected.
The Mellanox ConnectX core, Ethernet, and InfiniBand drivers are supported only for the x86_64 architecture.
(Bug ID 16228063)
A message similar to the following might be recorded in
/var/log/messages at boot
pid/oom_adj is deprecated, please use /proc/
udevd process uses the deprecated
interface to prevent it from being killed if the system runs short of memory. You can safely
ignore the message as the action still succeeds. To prevent the message from occurring,
install the package
udev-147-2.42.el6.arch.rpm or higher. (Bug ID 13655071,
Registering an Oracle Linux guest running under Virtual Box with the Unbreakable Linux
Network (ULN) might fail with a server communication error. The workaround is to run the
following command as
root on the
# echo "uuid=`uuidgen -t`" >> /etc/sysconfig/rhn/up2date
and then run uln_register again. (Bug ID 14696776)
xguest package fails to install with a
script error, enable SELinux by setting
/etc/selinux/config, reboot the system, and reinstall the
xguest package. (Bug ID 13495388)
If you install an Oracle Linux 6 Update 4 (x86_64) PVHVM guest with either the Desktop or the Software Development Workstation installation options, the X Window System is not accessible after installation when you boot the guest into run level 5. This problem is seen in OVM 3.0 and later.
Use the following workaround:
Boot the guest into run level 3 by appending 3 to the
command line in GRUB, for example:
kernel /vmlinuz-2.6.39-400.15.0.el6uek.x86_64 ... rd_NO_DM 3
After the guest boots, log in as
root, and uninstall the
xorg-x11-drv-cirrus package, for example:
# rpm -ev --nodeps xorg-x11-drv-cirrus
You can then either reboot the system into run level 5 or use the init 5 command to switch to run level 5. The X Window System will be accessible on subsequent boots to run level 5. (Bug ID 16280196)
PVHVM guests on Oracle VM 3.0 crash during Oracle Database installation if the value of
the maximum memory (
maxmem) parameter set for the guest is greater than the
amount specified at boot time (
memory). To avoid this issue, ensure that
the values of the
memory parameters are the
same. This issue has been resolved in Oracle VM 3.1.1. (Bug ID 13396734)
When booting UEK R2 as a 32-bit PVHVM guest, you can safely ignore the kernel message
register_vcpu_info failed: err=-38, which might be displayed. (Bug ID
In certain cases, after successfully completing installation and rebooting the system, it is possible for errors such as the following to occur:
Error in sys.excepthook: Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/meh/handler.py", line 161, in (lambda) File "/usr/lib/anaconda/exception.py", line 44, in handleException File "/usr/lib/python2.6/site-packages/meh/handler.py", line 106, in handleException File "/usr/lib/anaconda/gui.py", line 1169, in mainExceptionWindow ImportError: No module named ui.gui
These errors can safely be ignored.
The upstream release has added support for FCoE target service. This service is not supported with the previous release of the Unbreakable Enterprise Kernel (2.6.32). To use this service, boot your system into the Unbreakable Enterprise Kernel Release 2 (2.6.39) or the Red Hat Compatible Kernel.
ofa packages contain
mlx4_core. Only one of these packages should be installed. Attempting to
install both packages on a single server results in a package conflict error. If you have a
Mellanox Ethernet Controller, install
mlnx_en. If you have a Mellanox
InfiniBand Controller, install
ofa. If your system has both controllers,
ofa as it supports both the Ethernet and InfiniBand controllers.
When configuring the crash kernel for the UEK, only standard crash kernel settings (for
crashkernel=128M@32M) are supported. The new settings used by the
Red Hat Compatible Kernel (for example,
crashkernel=auto) are not supported
and cause the
kdump service to fail to start. (Bug ID 13495212)
If you see the boot-time
iTCO_wdt: failed to reset
NO_REBOOT flag, device disabled by hardware/BIOS with UEK R2 or
failed to reset NO_REBOOT flag, reboot disabled by hardware with UEK, add the line
blacklist iTCO_wdt to
The Unbreakable Enterprise Kernel adds support for PV drivers in a HVM guest (PVHVM) on
Oracle VM. The default is to present only PV drivers when running in an HVM guest. To run
kernel-uek fully hardware virtualized, including the drivers, add the
xen_emul_unplug=never to the boot parameters in
/etc/grub.conf, for example:
kernel /vmlinuz-2.6.32-300.2.1.el6uek ro root=/dev/VolGroup00/LogVol00 xen_emul_unplug=never
Adding this parameter makes the kernel also present the emulated drivers as previously
(for example, the
8139cp network driver).
Selecting all packages in certain groups during installation might not show the correct package count. (Bug ID 11684244)
Oracle Linux 6 defaults to reverse path filtering in strict mode. Some Oracle products and
network storage devices work more reliably with reverse path filtering in loose mode. To
enable loose mode, issue the following command (where
iface is the
network interface, for example,
# sysctl net.ipv4.conf.
The default setting is 1 for strict mode. (Bug ID 10649976)
Certain network operations that utilize receive packet steering could cause errors on the system. (Bug ID 11071685)
If failed paths are restored in a multipath configuration, you might see
udevd-work error messages in
failed paths are restored despite these messages, which you can ignore. (Bug ID
The default NFS mount option has changed to NFS v4. To mount an NFS v3 volume (the default in Oracle Linux 5), use the following mount options:
To set the serial console a hardware virtualized guest, use following settings in the guest:
Add the following parameters to the kernel boot line in
Add the following line to
On an x86_64 system, if you install the
pam.i386 package either
manually or via a package dependency, and the
oracle-rdbms-server-11gR2-preinstall package is also selected, this
overwrites the settings for Oracle Database in
This is most likely to occur during a Kickstart-automated installation that includes
non-standard packages. To restore the settings, run the
oracle-rdbms-server-11gR2-preinstall-verify script. (Bug ID
Following the first reboot after installing Oracle Linux 6, you are prompted to register
your system with the Unbreakable Linux Network (ULN). If you did not configure your network
during the installation, the registration process to ULN cannot succeed. To register your
system, log in as
root, configure the system's network manually, and run
On some hardware, the console may appear to hang during the boot process after starting
udev. However, the system does boot properly and is accessible. A
workaround to this problem is to add
nomodeset as a kernel boot parameter
/etc/grub.conf. (Bug ID 10094052, 13485328)
For the Unbreakable Enterprise Kernel,
deadline is the default I/O
For the Red Hat Compatible Kernel,
cfq is the default I/O
For the Unbreakable Enterprise Kernel, the default setting is
For the Red Hat Compatible Kernel, the default setting is
Table of Contents
This chapter describes how to upgrade your system to Oracle Linux 6 Update 4.
Upgrading from Oracle Linux 6 GA, Update 1, Update 2, or Update 3 is supported. Upgrading from a beta release is not supported.
In-place upgrading from a major version of Oracle Linux 5 or earlier is not supported. Although Anaconda provides an option to perform an upgrade, fresh installation is strongly recommended.
If you have an Oracle Linux 5.8 system, you can use new features in Unbreakable Enterprise Kernel without upgrading to Oracle Linux 6 as Oracle Linux 5.8 includes the Unbreakable Enterprise Kernel.
You use yum rather than up2date to manage packages with Oracle Linux 6. Using up2date is not supported.
You can download a full Oracle Linux installation media image from the Oracle Software Delivery Cloud at http://edelivery.oracle.com/linux. You can also obtain Oracle Linux packages from the Unbreakable Linux Network (ULN) and the Oracle Public Yum server.
You have the option of registering a system with ULN when you install Oracle Linux 6 on a system. To register with ULN after installation, use the uln_register command.
To obtain Oracle Linux updates from ULN, you must have an Oracle Linux support subscription. For more information about ULN, see http://linux.oracle.com.
During ULN registration, your server is automatically registered with the latest channels for the base repository and the Unbreakable Enterprise Kernel Release 2. If you have upgraded your system from a previous release and do not want to install UEK Release 2, you must manually unsubscribe the server from this channel.
ULN also provides channels for Oracle-specific software packages such as Oracle's
ASMlib userspace package and the Oracle Instant Client. To enable
access to these packages, log in to ULN and subscribe your system to the Oracle Software
Oracle also provides all errata and updates for Oracle Linux via the Public Yum service, which includes updates to the base distribution, but does not include Oracle-specific software. You do not require an Oracle Linux support subscription to use this service. For more information on how to obtain updates from Public Yum, see http://public-yum.oracle.com.
By default, all new installations of Oracle Linux 6 Update 4 are automatically configured to use the public yum update service. If you subsequently register the system with ULN, the public yum service is automatically disabled.
The following entries in the
file enable you to download the latest available packages for Oracle Linux 6 and the
Unbreakable Enterprise Kernel Release
[ol6_latest] name=Oracle Linux $releasever Latest ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=1 [ol6_UEK_latest] name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=1
Oracle Linux 6 Update 4 contains two distinct repository sources on the installation
media for the Red Hat Compatible Kernel and the Unbreakable Enterprise Kernel. To configure
yum to use both repositories from an ISO image of the installation
media, create the file
/etc/yum.repos.d/Media.repo containing entries
similar to the following:
[ol6_base_media] name=Oracle Linux 6 Update 4 Base Media baseurl=file:///media/
ISOimage/RPM-GPG-KEY gpgcheck=1 enabled=1 [ol6_uek_media] name=Oracle Linux 6 Update 4 UEK Media baseurl=file:///media/
ISOimage/RPM-GPG-KEY gpgcheck=1 enabled=1
Adjust the value of the
parameters to match the mount point of the ISO image on your system. If you do not require
one of the repositories, set the value of the corresponding
parameter to 0.
Once you have set up the ULN channels, Public Yum repositories, or installation media repositories that yum should use, you can update all installed packages by running the following command:
# yum update
If your system is currently installed with Oracle Linux 6 GA, Update 1, Update 2, or Update 3, this command upgrades it to Update 4.
You can use the following command to update a specific package:
# yum update
For example, to update the Z-shell package (
zsh), you would
# yum update zsh
For more information, see the
yum(8) manual page.
Oracle Linux 6 Update 4 ships with the latest Unbreakable Enterprise Kernel Release 2. If you upgrade your system from the installation media, there are two upgrade scenarios:
If UEK R2 is not currently installed on the system, only the latest Red Hat Compatible Kernel is installed. The UEK R2 kernel is not installed.
If UEK R2 is currently installed on the system, the latest version of that kernel is installed.
yum uses whatever repositories you have configured on your system to
upgrade it. You can find the latest UEK2 packages in the
repositories. If you want to install the latest UEK R2 kernel, subscribe your system to the
correct channel on ULN, or configure the repository in the
/etc/yum.repos.d/public-yum-ol6.repo file as shown here:
[ol6_UEK_latest] name=Latest Unbreakable Enterprise Kernel for Oracle Linux $releasever ($basearch) baseurl=http://public-yum.oracle.com/repo/OracleLinux/OL6/UEK/latest/$basearch/ gpgkey=http://public-yum.oracle.com/RPM-GPG-KEY-oracle-ol6 gpgcheck=1 enabled=1