Installing Oracle Database 10g on Linux x86
*Updated for RHEL4 and SLES9*
Contents
Overview
Part
I: Installing Linux
RHEL4
RHEL3
RHEL2.1
SLES9
SLES8
Part
II: Configuring Linux for Oracle
Verify
System Requirements
Create
Directories
Create
the Oracle Groups and User Account
Configure
Linux Kernel Parameters
Set
Shell Limits for the oracle User
Avoid
the Bug! (SLES8 Only)
Environment
Variables for the oracle User
Part
III: Installing Oracle
Install
the Software
Part
IV: Configuring Storage
Filesystems
Automatic
Storage Management
Conclusion
Appendix
Tips and Hints
Oracle
Errors and Problems (External)
Part V: Tuning Linux for Oracle (Async I/O, SGA over
2.7GB, Using Large Memory Pages)
The five Linux distributions certified for Oracle Database 10g covered are:
This guide assumes a server with the following hardware:
The disks are configured so that each SCSI host adapter is connected to one 9GB disk and three 36GB disks.
Note that although this is far from a "beefy" setup, much of what this guide covers can be accomplished with even less horsepower. All that is necessary for a basic database install is a single CPU, 512MB of RAM, and one disk drive (IDE, SCSI, or FireWire) with at least 6.5GB of free space.
Oracle Database 10g is certified to run the base release of RHEL4 (Advanced Server and Enterprise Server) without updates. (Free evaluation copies of RHEL4 are available for download.) If you have update CDs, you can use the boot CD from the update instead of the boot CD from the base release to automatically apply all updates during the installation. All updates from Red Hat are supported by Oracle.
The easiest and fastest way to apply the updates for a fresh install of Linux is to perform the install by using the update CDs. If Linux is already installed or you don't have the updates on CDs, they can be applied through RHN. Because this guide is designed for a fresh Linux install, you'll use the update CDs.
This guide uses the following partitioning scheme, with ext3
for each filesystem:
The 9GB disk on the first controller (/dev/sda) will hold all Linux and
Oracle software and contains the following partitions:
- 100MB /boot partition
-1,500MB swap partition—Set
this to at least twice the amount of RAM in
the system but to no more than 2GB. (Thirty-two-bit systems do not
support swap files larger than 2GB.) If you need more than 2GB of swap
space, create multiple swap partitions.
-7,150MB root partition—This partition will be used for everything,
including /usr, /tmp, /var, /opt, /home, and more. This approach is
purely to simplify installation for the purposes of this guide. A more
robust partitioning scheme would separate these directories onto
separate filesystems.
Verifying Your Installation
If you've completed the steps above, you should have all the
packages and updates required for Oracle Database 10g .
However, you can take the steps below to verify your installation.
Required kernel version: 2.6.9-5.EL (This is the kernel version shipped
with the base release of RHEL4. This kernel, or any of the kernels
supplied in updates, works with Oracle Database 10g .)
Check your kernel version by running the following command:
uname -rOther required package versions
Ex:
# uname -r
2.6.9-5.ELsmp
rpm -q gcc make binutils openmotif setarch compat-db
Ex:
# rpm -q gcc make binutils openmotif setarch compat-db
gcc-3.4.3-9.EL4
make-3.80-5
binutils-2.15.92.0.2-10.EL4
setarch-1.6-1
compat-db-4.1.25-9
Install the following packages:
# From RedHat AS4 Disk 2
cd /media/cdrom/RedHat/RPMS
rpm -Uvh setarch-1.6-1.i386.rpm
rpm -Uvh compat-libstdc++-33-3.2.3-47.3.i386.rpm
# From RedHat AS4 Disk 3
cd /media/cdrom/RedHat/RPMS
rpm -Uvh openmotif-2.2.3-6.RHEL4.2.i386.rpm
rpm -Uvh compat-db-4.1.25-9.i386.rpm
# From RedHat AS4 Disk 4
cd /media/cdrom/RedHat/RPMS
rpm -Uvh compat-gcc-32-3.2.3-47.3.i386.rpm
rpm -Uvh compat-gcc-32-c++-3.2.3-47.3.i386.rpm
Oracle Database 10g is certified to run the base release of Red Hat Enterprise Linux 3 (Advanced Server and Enterprise Server) without updates. If you have update CDs, you can use the boot CD from the update instead of the boot CD from the base release to automatically apply all updates during the installation. All updates from Red Hat are supported by Oracle.
(WARNING: Improperly partitioning a disk is one of the
surest and fastest ways to wipe out everything on your hard
disk. If you are unsure how to proceed, stop and get help, or
you will risk losing data!)
This guide uses the following partitioning scheme, with ext3
for each filesystem:
The 9GB disk on the first
controller (/dev/sda) will hold all Linux and
Oracle software and contains the following partitions:
- 100MB /boot partition
-1,500MB swap partition—Set
this to at least twice the amount of RAM in
the system but to no more than 2GB (32-bit systems do not support swap
files larger than 2GB). If you need more than 2GB of swap space, create
multiple swap partitions.
-7,150MB root partition— This
partition will be used for everything,
including /usr, /tmp, /var, /opt, /home, and more. This was done purely
to simplify installation for the purposes of this guide. A more robust
partitioning scheme would separate these directories onto separate
filesystems.
If you've completed the steps above, you should have all the packages and updates required for Oracle Database 10g. However, you can take the steps below to verify your installation.
Required kernel version: 2.4.21-4.EL (This is the kernel version shipped with the base release of RHEL3. This kernel, or any of the kernels supplied in updates, works with Oracle Database 10g.)
Check your kernel version by running the following command:
uname -rOther required package versions (or later):
Ex:
# uname -r
2.4.21-4.0.1.ELsmp
rpm -q gcc make binutils openmotif setarch compat-db compat-gcc \
compat-gcc-c++ compat-libstdc++ compat-libstdc++-devel
Ex:
# rpm -q gcc make binutils openmotif setarch compat-db compat-gcc \
> openmotif compat-gcc-c++ compat-libstdc++ compat-libstdc++-devel
gcc-3.2.3-20
make-3.79.1-17
binutils-2.14.90.0.4-26
openmotif-2.2.2-16
setarch-1.3-1
package compat-db is not installed
compat-gcc-7.3-2.96.122
compat-gcc-c++-7.3-2.96.122
compat-libstdc++-7.3-2.96.122
compat-libstdc++-devel-7.3-2.96.122
Installing compat-db
Insert CD2 of the original Red Hat Enterprise Linux media. (This
package has not been updated as of Update 2 and is found only on the
original media.)
The CD mounts automatically.
Run the following command as root:
rpm -ivh /mnt/cdrom/RedHat/RPMS/compat-db-4.0.14-5.i386.rpm
Ex:
# rpm -ivh /mnt/cdrom/RedHat/RPMS/compat-db-4.0.14-5.i386.rpm
Preparing... ########################################### [100%]
1:compat-db ########################################### [100%]
Oracle Database 10g is certified to run on Red Hat Enterprise Linux 2.1 (Advanced Server and Enterprise Server) with Update 3 or higher. Updates are available from the Red Hat Network (RHN) and can be downloaded as ISO files for creating CDs or as individual package updates.
The easiest and fastest way to apply the updates for a fresh install of Linux is to perform the install by using the update CDs. If Linux is already installed or you don't have the updates on CDs, they can be applied through RHN. Because this guide is designed for a fresh Linux install, you'll use the update CDs.
(WARNING: Improperly partitioning a disk is one of the
surest and fastest ways to wipe out everything on your hard
disk. If you are unsure how to proceed, stop and get help, or
you will risk losing data!)
This guide uses the following partitioning scheme, with ext3
for each filesystem:
The 9GB disk on the first
controller (/dev/sda) will hold all Linux and
Oracle software and contains the following partitions:
- 100MB /boot partition (50MB
is the minimum for RHEL 2.1)
-1,500MB swap partition—Set
this to at least twice the amount of RAM in
the system but to no more than 2GB (32-bit systems do not support swap
files larger than 2GB). If you need more than 2GB of swap space, create
multiple swap partitions.
-7,150MB root partition—This
partition will be used for everything,
including /usr, /tmp, /var, /opt, /home, and more. This was done purely
to simplify installation for the purposes of this guide. A more robust
partitioning scheme would separate these directories onto separate
filesystems.
Verifying Your Installation
If you've completed the steps above, you should have all the packages and updates required for Oracle Database 10g. However, you can take the steps below to verify your installation.
Required kernel version: 2.4.9-e.25 (or later)
Check your kernel version by running the following command:
uname -rOther required package versions (or later):
Ex:
# uname -r
2.4.9-e.27smp
rpm -q gcc make binutils openmotif glibcIf any of the package versions on your system are missing or the versions are earlier than those specified above, you can download and install the updates from the Red Hat Network.
Ex:
# rpm -q gcc make binutils openmotif glibc
gcc-2.96-118.7.2
make-3.79.1-8
binutils-2.11.90.0.8-12
openmotif-2.1.30-11
glibc-2.2.4-32.8
Oracle Database 10g is certified to run on the base release of SLES9. Service Packs and package updates are available from Novell, either on CDs or online via its support portal. In this guide, we will install on the SLES9 base release.
(WARNING: Improperly partitioning a disk is one of the surest and fastest ways to wipe out everything on your hard disk. If you are unsure how to proceed, stop and get help, or you will risk losing data!)
This guide uses the following partitioning scheme, with ext3
for each filesystem:
The 9GB disk on the first controller (/dev/sda) will hold all Linux and
Oracle software and contains the following partitions:
- 100MB /boot partition
-1,500MB swap partition—Set this to at least twice the amount of RAM in
the system but to no more than 2GB. (Thirty-two-bit systems do not
support swap files larger than 2GB.) If you need more than 2GB of swap
space, create multiple swap partitions.
-7,150MB root partition—this partition will be used for everything,
including /usr, /tmp, /var, /opt, /home, and more. This approach is
purely to simplify installation for the purposes of this guide. A more
robust partitioning scheme would separate these directories onto
separate filesystems.
If you've completed the steps above, you should have all the packages and updates required for Oracle Database 10g. However, you can take the steps below to verify your installation.
Required kernel version: 2.6.5-7.5 (or later)
Check your kernel version by running the following command:
uname -rOther required package versions (or later):
Ex:
# uname -r
2.6.5-7.97-smp
If any of the package versions on your system are missing or the versions are earlier than those specified above, you can download and install the updates from the Novell SUSE Linux Portal.
rpm -q gcc gcc-c++ glibc libaio libaio-devel make openmotif-libs
Ex:
# rpm -q gcc gcc-c++ glibc libaio libaio-devel make openmotif-libs
gcc-3.3.3-43.24
gcc-c++-3.3.3-43.24
glibc-2.3.3-98.28
libaio-0.3.98-18.3
libaio-devel-0.3.98-18.3
make-3.80-184.1
openmotif-libs-2.2.2-519.1
Oracle Database 10g is certified to run on Novell SUSE Linux Enterprise Server (SLES) 8 and SLES-9. Service Packs and package updates are available from Novell, either on CDs or online via its support portal. In this guide, we will install on SLES8 with Service Pack 3 from CDs.
(WARNING: Improperly partitioning a disk is one of the surest and fastest ways to wipe out everything on your hard disk. If you are unsure how to proceed, stop and get help, or you will risk losing data!)
This guide uses the following partitioning scheme, with ext3
for each filesystem:
The 9GB disk on the first controller (/dev/sda) will hold all Linux and
Oracle software and contains the following partitions:
- 100MB /boot partition
-1,500MB swap partition—Set this to at least twice the amount of RAM in
the system but to no more than 2GB (32-bit systems do not support swap
files larger than 2GB). If you need more than 2GB of swap space, create
multiple swap partitions.
-7,150MB root partition—this partition will be used for everything,
including /usr, /tmp, /var, /opt, /home, and more. This was done purely
to simplify installation for the purposes of this guide. A more robust
partitioning scheme would separate these directories onto separate
filesystems.
If you've completed the steps above, you should have all the packages and updates required for Oracle Database 10g. However, you can take the steps below to verify your installation.
Required kernel version: 2.4.21-138 (or later)
Check your kernel version by running the following command:
uname -rOther required package versions (or later):
Ex:
# uname -r
k_smp-2.4.21-138
rpm -q gcc make binutils openmotifIf any of the package versions on your system are missing or the versions are earlier than those specified above, you can download and install the updates from the SUSE Linux Portal.
Ex:
# rpm rpm -q gcc make binutils openmotif
gcc-3.2.2-38
make-3.79.1-407
binutils-2.12.90.0.15-50
openmotif-2.2.2-124
Part II: Configuring Linux for Oracle
To verify that your system meets the minimum requirements for an Oracle 10g database, log in as root and run the commands below.
To check the size of physical memory, execute:grep MemTotal /proc/meminfoTo check the size of swap space, execute:
grep SwapTotal /proc/meminfoYou also can add temporary swap space to your system by creating a temporary swap file instead of using a raw device. Here is the procedure:
su - rootTo disable the temporary swap space execute the following commands:
dd if=/dev/zero of=tmpswap bs=1k count=900000
chmod 600 tmpswap
mkswap tmpswap
swapon tmpswap
su - root
swapoff tmpswap
rm tmpswap
$ df /tmpIf you do not have enough space in the /tmp filesystem, you can temporarily create a tmp directory in another filesystem. Here is how you can do this:
su - rootWhen you are done with the Oracle installation, shutdown Oracle and remove the temporary /tmp directory:
mkdir /<AnotherFilesystem>/tmp
chown root.root /<AnotherFilesystem>/tmp
chmod 1777 /<AnotherFilesystem>/tmp
export TEMP=/<AnotherFilesystem> # used by Oracle
export TMPDIR=/<AnotherFilesystem> # used by Linux programs like the linker "ld"
su - root
rmdir /<AnotherFilesystem>/tmp
unset TEMP
unset TMPDIR
Create the Oracle Groups and User Account
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
Now create directories to store the Oracle 10g software and the database files. This guide adheres to the Optimal Flexible Architecture (OFA) for the naming conventions used in creating the directory structure. For more information on OFA standards, see Appendix D of the Oracle Database 10g Installation Guide for UNIX Systems.
The following assumes that the directories are being created in the root filesystem. This is done for the sake of simplicity and is not recommended as a general practice. These directories would normally be created as separate filesystems.
Issue the following commands as root:
mkdir -p /u01/app/oracle
mkdir -p /u02/oradata
chown -R oracle:oinstall /u01/app/oracle /u02/oradata
chmod -R 775 /u01/app/oracle /u02/oradata
Configuring the Linux Kernel Parameters
The Linux kernel is a wonderful thing. Unlike most other *NIX systems, Linux allows modification of most kernel parameters while the system is up and running. There's no need to reboot the system after making kernel parameter changes. Oracle Database 10g requires the kernel parameter settings shown below. The values given are minimums, so if your system uses a larger value, don't change it.
shmmax = 2147483648 (To verify, execute: cat /proc/sys/kernel/shmmax)
shmmni = 4096 (To verify, execute: cat /proc/sys/kernel/shmmni)
shmall = 2097152 (To verify, execute: cat /proc/sys/kernel/shmall) (for 10g R1)
shmmin = 1 (To verify, execute: ipcs -lm |grep "min seg size")
shmseg = 10 (It's hardcoded in the kernel - the default is much higher)
semmsl = 250 (To verify, execute: cat /proc/sys/kernel/sem | awk '{print $1}')
semmns = 32000 (To verify, execute: cat /proc/sys/kernel/sem | awk '{print $2}')
semopm = 100 (To verify, execute: cat /proc/sys/kernel/sem | awk '{print $3}')
semmni = 128 (To verify, execute: cat /proc/sys/kernel/sem | awk '{print $4}')
file-max = 65536 (To verify, execute: cat /proc/sys/fs/file-max)
ip_local_port_range = 1024 65000 (To verify, execute: cat /proc/sys/net/ipv4/ip_local_port_range)
If you're following along and have just installed Linux, the kernel parameters will all be at their default values and you can just cut and paste the following commands while logged in as root.
cat >> /etc/sysctl.conf <<EOF
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
EOF
sysctl -p
su - rootTo make the change permanent, add the following lines to the /etc/sysctl.conf file, which is used during the boot process:
sysctl -w net.core.rmem_default=262144 # Default setting in bytes of the socket receive buffer
sysctl -w net.core.wmem_default=262144 # Default setting in bytes of the socket send buffer
sysctl -w net.core.rmem_max=262144 # Maximum socket receive buffer size which may be set by using the SO_RCVBUF socket option
sysctl -w net.core.wmem_max=262144 # Maximum socket send buffer size which may be set by using the SO_SNDBUF socket option
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=262144
net.core.wmem_max=262144
Verify your settings!!!
If any of the parameters on your system are set lower than those shown, edit the /etc/sysctl.conf file and add or change the parameters. When you're finished, run the following command to activate the changes:
sysctl -p
For all Novell SUSE Linux releases, use the following:
/sbin/chkconfig boot.sysctl on
Setting Shell Limits for the oracle User
Oracle recommends setting limits on the number of processes and open files each Linux account may use. To make these changes, cut and paste the following commands as root:
cat >> /etc/security/limits.conf <<EOF
oracle soft nproc 2047
oracle hard nproc 16384
oracle soft nofile 4096
oracle hard nofile 65536
EOF
cat >> /etc/pam.d/login <<EOF
session required /lib/security/pam_limits.so
EOF
For RHEL 2.1 and 3, use the following:
cat >> /etc/profile <<EOF
if [ \$USER = "oracle" ]; then
if [ \$SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
umask 022
fi
EOF
cat >> /etc/csh.login <<EOF
if ( \$USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
umask 022
endif
EOF
For SLES8, use the following:
cat >> /etc/profile.local <<EOF
if [ \$USER = "oracle" ]; then
if [ \$SHELL = "/bin/ksh" ]; then
ulimit -p 16384
ulimit -n 65536
else
ulimit -u 16384 -n 65536
fi
umask 022
fi
EOF
cat >> /etc/csh.login.local <<EOF
if ( \$USER == "oracle" ) then
limit maxproc 16384
limit descriptors 65536
umask 022
endif
EOF
Avoid the Bug! (Novell SUSE Linux releases only)
There is a bug in the installation of Oracle Enterprise Manager 10g on SLES8 and SLES9 that causes it to fail due to required ports that are reserved in /etc/services. The OEM DBConsole needs port 1830, and in SUSE environments this port is already reserved in /etc/services. This bug is documented in MetaLink as bug# 3513603.
To avoid problems during the installation, log in as root and
comment out the lines for ports 1830 through 1849 in the /etc/services
file prior to installing the Oracle Database 10g software.
(Note: It's probably a good idea to reboot the server at this point, to
ensure that the above changes are in effect.)
Environment Variables for the oracle User
If you have more than one Oracle product or database on the same server, the ORACLE_HOME, ORACLE_SID, and PATH variables may change. The ORACLE_BASE variable should not change and can be set in your login profile if you want. Oracle provides a utility, called oraenv, for setting the remaining variables.
Log in as oracle and add ORACLE_BASE to your login profile by adding the following line to your .bash_profile or .profile (bash or ksh):
# Oracle SettingsThis change will take effect the next time you log in to the oracle account. To make the changes active for the current session, simply run the command from the command line.
export ORACLE_BASE=/u01/app/oracle
export ORACLE_SID=XXXXXX
Oracle Database 10g can be downloaded from OTN. Oracle offers a development and testing license free of charge. However, no support is provided and the license does not permit production use. A full description of the license agreement is available on OTN. The easiest way to make the Oracle Database 10g distribution media available on your server is to download them directly to the server.
Installing Oracle10g on a
Remote Linux Server
If you don't install Oracle on your local system but 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 don't have to run xhost and set the DISPLAY
environment variable.
Here is an example how to make use of the "X11 forward" feature of ssh.
Simply run the following command from your local desktop:
$ ssh -X oracle@oracle_remote_server_nameNow when you try to run any GUI tool on the remote server, it will 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 the remote server:
su - root
# grep ForwardX11 /etc/ssh/ssh_config | grep -v "^#"
ForwardX11 yes
#
Working with the Installed FilesAs the oracle user, Change directory to Disk1.
Compute a cyclic redundancy check (CRC) checksum for the downloaded files and
compare the checksum numbers against the numbers posted on OTN's website. For example:
cksum ship.db.lnx32.cpio.gz
Uncompress the downloaded file(s):
gunzip ship.db.lnx32.cpio.gz
Unpack ship.db.lnx32.cpio:
$ cpio -idmv < ship.db.lnx32.cpio
$ cd Disk1
Start the Oracle Universal Installer.
$ ./runInstaller
The database we created in Part III used a single filesystem
(/u02/oradata) for disk storage. However, there are several ways to
configure storage for an Oracle database.
Part IV explores other methods of configuring disk storage for this
database. In particular, it describes creating additional filesystems
and using Automatic Storage Management (ASM).
Filesystems are the most widely used means of storing data file, redo logs, and control files for Oracle databases. Filesystems are easy to implement and require no third-party software to administer. In most cases, filesystems are created during the initial installation of Linux. However, there are times when a new filesystem must be created after the initial installation, such as when a new disk drive is being installed. This section describes building a new filesystem and using it in an Oracle database. Unless otherwise noted, all commands must be run as root.
Partition the Disk
You must have an empty disk partition to create the filesystem. If
you already have an empty disk partition available, skip to the next
step. The following shows an example of creating a new partition for a
Linux filesystem. (WARNING: Improperly partitioning a disk is one of
the surest and fastest ways to wipe out everything on your
hard disk. If you are unsure how to proceed, stop and get
help, or you will risk losing data.)
This example uses /dev/sdb (an empty SCSI disk with no existing
partitions) to create a single partition for the entire disk (36 GB).
# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 4427.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 255 heads, 63 sectors, 4427 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-4427, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-4427, default 4427):
Using default value 4427
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: If you have created or modified any DOS 6.x
partitions, please see the fdisk manual page for additional
information.
Syncing disks.
Now verify the new partition:
Ex:
# fdisk /dev/sdb
The number of cylinders for this disk is set to 4427.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/sdb: 255 heads, 63 sectors, 4427 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 1 4427 35559846 83 Linux
Command (m for help): q
Create the Filesystem
Use ext3 to create this new filesystem. Other filesystems work just as well, but ext3 offers the fastest recovery time in the event of a system crash.
Ex:
# mke2fs -j /dev/sdb1
mke2fs 1.26 (3-Feb-2002)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
4447744 inodes, 8889961 blocks
444498 blocks (5.00%) reserved for the super user
First data block=0
272 block groups
32768 blocks per group, 32768 fragments per group
16352 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
2654208, 4096000, 7962624
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 23 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
Create the Mount Point
A filesystem must have a mount point, which is
simply an empty directory where the new filesystem "attaches" to the
system's directory tree. Mount points should be given names consistent
with the Oracle Flexible Architecture (OFA) standard. For more
information on OFA standards, see Appendix D of the Oracle 10g Database Installation Guide.
Because you have already used the /u01 and /u02 directory names in Part
I, use /u03 for this example.
Ex:
# mkdir /u03
Add the New Filesystem to /etc/fstab
So that the new filesystem will be mounted automatically when the system boots, you need to add a line to the /etc/fstab file that describes the new filesystem and where to mount it. Add a line similar to the one below to /etc/fstab, using a text editor.
/dev/sdb1 /u03 ext3 defaults 1 1
Mount the New Filesystem
Mounting the filesystem makes it available for use. Until the filesystem is mounted, files cannot be stored in it. Use the following commands to mount the filesystem and verify that it is available.
mount /u03
df -h /u03
Ex:
# mount /u03
# df -h /u03
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 33G 33M 31G 1% /u03
Create Oracle Directories and Set Permissions
Now you create a directory to store your Oracle files. The directory name used in the example follows the OFA standard naming convention for a database with ORACLE_SID=demo1.
mkdir -p /u03/oradata/demo1
chown -R oracle:oinstall /u03/oradata
chmod -R 775 /u03/oradata
Create a New Tablespace in the New Filesystem
The new filesystem is ready for use. Next you create a new tablespace in the filesystem to store your database objects. Connect to the database as the SYSTEM user, and execute the CREATE TABLESPACE statement, specifying the data file in the new filesystem.
Ex:
create tablespace data1 datafile '/u03/oradata/demo1/data1_01.dbf' size 100M
extent management local
segment space management auto;
I've saved the best for last.
ASM is a fantastic new feature in Oracle Database 10g that
provides the services of a filesystem, logical volume manager, and
software RAID in a platform-independent manner. ASM can stripe and
mirror your disks, allow disks to be added or removed while the
database is under load, and automatically balance I/O to remove "hot
spots." It also supports direct and asynchronous I/O and implements the
Oracle Data Manager API (simplified I/O system call interface)
introduced in Oracle9i.
ASM is not a general-purpose filesystem and can be used only for Oracle
data files, redo logs, and control files. Files in ASM can be created
and named automatically by the database (by use of the Oracle Managed
Files feature) or manually by the DBA. Because the files stored in ASM
are not accessible to the operating system, the only way to perform
backup and recovery operations on databases that use ASM files is
through Recovery Manager (RMAN).
ASM is implemented as a separate Oracle instance that must be up if
other databases are to be able to access it. On Linux the OCSSD service
(installed by default by the Oracle Universal Installer) must be
running to allow use of ASM. Memory requirements for ASM are light:
only 64 MB for most systems.
More information HERE
Installing ASM
On Linux platforms, ASM can use raw devices or devices managed via the
ASMLib interface. Oracle recommends ASMLib over raw devices, for
ease-of-use and performance reasons. ASMLib is available for free
download from OTN. This section walks through the process of
configuring a simple ASM instance by using ASMLib and building a
database that uses ASM for disk storage.
Determine Which Version of ASMLib You Need
ASMLib is delivered as a set of three Linux packages:
First, determine which kernel you are using by logging in as root and running the following command:
uname -rm
Ex:
# uname -rm
2.4.9-e.27smp i686
The example shows that this is a 2.4.9 kernel for an SMP (multiprocessor) box using Intel i686 CPUs.
Use this information to find the correct ASMLib packages on OTN:
Next, install the packages by executing the following command as root:
rpm -Uvh oracleasm-kernel_version-asmlib_version.cpu_type.rpm \
oracleasmlib-asmlib_version.cpu_type.rpm \
oracleasm-support-asmlib_version.cpu_type.rpm
Ex:
# rpm -Uvh \
> oracleasm-2.4.9-e-smp-1.0.0-1.i686.rpm \
> oracleasmlib-1.0.0-1.i386.rpm \
> oracleasm-support-1.0.0-1.i386.rpm
Preparing... #################################### [100%]
1:oracleasm-support #################################### [ 33%]
2:oracleasm-2.4.9-e-smp #################################### [ 66%]
Linking module oracleasm.o into the module path [ OK ]
3:oracleasmlib #################################### [100%]
Configuring ASMLib
Before using ASMLib, you must run a configuration script to prepare the
driver. Run the following command as root, and answer the prompts as
shown in the example below.
# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration [ OK ]
Creating /dev/oracleasm mount point [ OK ]
Loading module "oracleasm" [ OK ]
Mounting ASMlib driver filesystem [ OK ]
Scanning system for ASM disks [ OK ]
Now enable the ASMLib driver as shown below.
# /etc/init.d/oracleasm enable
Writing Oracle ASM library driver configuration [ OK ]
Scanning system for ASM disks [ OK ]
Configuring Disks for ASM
Next you tell the ASM driver which disks you want it to use. Note that
these are bare disks with nothing on them (not even a partition). It is
possible to use disk partitions with ASM, but it isn't recommended.
You mark disks for use by ASMLib by running the following command as root:
/etc/init.d/oracleasm createdisk DISK_NAME device_name
(Tip: Enter the DISK_NAME in UPPERCASE letters. There is a bug in the current release that prevents the disks from being visible to the ASM instance if lowercase is used.)
Ex:
# /etc/init.d/oracleasm createdisk VOL1 /dev/sdb
Marking disk "/dev/sdb" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL2 /dev/sdc
Marking disk "/dev/sdc" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL3 /dev/sdd
Marking disk "/dev/sdd" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL4 /dev/sdf
Marking disk "/dev/sdf" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL5 /dev/sdg
Marking disk "/dev/sdg" as an ASM disk [ OK ]
# /etc/init.d/oracleasm createdisk VOL6 /dev/sdh
Marking disk "/dev/sdh" as an ASM disk [ OK ]
The following example shows how to list all the disks marked for use by ASMLib.
# /etc/init.d/oracleasm listdisks
VOL1
VOL2
VOL3
VOL4
VOL5
VOL6
Now that ASMLib is installed and the disks are marked for use, you can create an ASM instance and build a database that uses ASM for disk storage. This is easiest to accomplish with the Data Base Configuration Assistant (DBCA).
Log in as oracle and start DBCA:
$ dbca
Now that your database is up and running, you can begin exploring the many new features offered in Oracle Database 10g. A great place to start is Oracle Enterprise Manager, which has been completely re-written with a crisp new Web-based interface. If you're unsure where to begin, the Oracle Database 10g Concepts Guide and the 2-Day DBA Guide will help familiarize you with your new database. OTN also has a number of guides designed to help you get the most out of 10g. One of my favorites is the series by Arup Nanda, "Oracle Database 10g: The Top 20 Features for DBAs."
Using Oracle Enterprise Manager 10g Database Control
In a Web browser, connect to the URL
provided during the installation.
http://IPADDRESS:5500/em (You can use the host name if your database
server is in your DNS.)
User Name: SYS
Password: <The password you chose during installation>
Connect As: SYSDBA
Click on <Login>
Starting and Stopping Oracle Enterprise Manager Database Control:
$ emctl start dbconsole
$ emctl stop dbconsole
Accessing the Database Using iSQL*Plus
iSQL*Plus is a Web-based version of the
venerable SQL*Plus interactive tool for accessing databases. To use
iSQL*Plus, click on the iSQL*Plus link in the Related Links section of
the OEM console or point your browser to the iSQL*Plus URL provided
during installation.
Ex:
http://ds1.orademo.org:5560/isqlplus (You may have to use the IP
address instead of the host name if your database server isn’t in your
DNS.)
User Name: SYSTEM
Password: <The password you chose during installation>
Click on <Login>.
Enter SQL commands in the Workspace box, and click on Execute.
Starting and Stopping iSQL*Plus:
$ isqlplusctl start
$ isqlplusctl stop
List the Oracle Processes:
$ ps –fuoracle
su - rootMake also sure to unset and uncomment ORACLE_HOME from ~oracle/.bash_profile.
export ORACLE_HOME=/u01/app/oracle/product/10.1.0/db_1
. $ORACLE_HOME/bin/localconfig delete # stops the Oracle CSS daemon and deletes configuration rm -rf /u01/app/oracle/* rm -f /etc/oraInst.loc /etc/oratab rm -rf /etc/oracle rm -f /etc/inittab.cssd rm -f /usr/local/bin/coraenv /usr/local/bin/dbhome /usr/local/bin/oraenv
# shutdown OracleIf asynchronous I/O needs to be disabled for any reason, run the following commands:
SQL> shutdown
su - oracle
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk async_on
make -f ins_rdbms.mk ioracle
# The last step creates a new "oracle" executable "$ORACLE_HOME/bin/oracle".
# It backs up the old oracle executable to $ORACLE_HOME/bin/oracleO,
# it sets the correct privileges for the new Oracle executable "oracle",
# and moves the new executable "oracle" into the $ORACLE_HOME/bin directory.
# shutdown OracleEnabling Asynchronous I/O in init.ora for Raw Devices
SQL> shutdown
su - oracle
cd $ORACLE_HOME/rdbms/lib
make -f ins_rdbms.mk async_off
make -f ins_rdbms.mk ioracle
disk_asynch_io=trueNote that this init.ora parameter is already set to true by default:
SQL> select value, isdefault from v$parameter where name = 'disk_asynch_io';Enabling Asynchronous I/O in init.ora for Filesystem Files
VALUE ISDEFAULT
------------------------------ ---------
TRUE TRUE
disk_asynch_io=trueNote that this init.ora parameter is already set to true by default:
SQL> select value, isdefault from v$parameter where name = 'filesystemio_options';The filesystemio_options init.ora parameter needs to be set to asynch:
VALUE ISDEFAULT
------------------------------ ---------
none TRUE
SQL>
filesystemio_options=asynchThis init.ora parameter is platform-specific. By default, this parameter is set to none for Linux and thus needs to be changed.
SQL> select value, isdefault from v$parameter where name = 'filesystemio_options';The filesystemio_options can have the following values with Oracle9iR2:
VALUE ISDEFAULT
------------------------------ ---------
none TRUE
SQL>
su - rootThe maximum number of bytes can be changed for e.g. DSS systems in the proc file system without reboot:
# cat /proc/sys/fs/aio-max-size
131072
echo "2147483648" > /proc/sys/fs/aio-max-sizeAlternatively, you can use sysctl(8) to change it:
sysctl -w fs.aio-max-size=2147483648To 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.aio-max-size=2147483648" >> /etc/sysctl.conf
su - root
rpm -e slocate
init 3To switch back to runlevel 5 that X comes up again, run:
init 5To set the default runlevel permanently to 3 so that X doesn't come up with the next reboot, change the following line in /etc/inittab:
id:5:initdefault:so that it reads:
id:3:initdefault:
/sbin/chkconfig --listTo temporarely disable e.g. ypbind, run:
su - rootTo permanently disable ypbind, run:
service ypbind stop
chkconfig ypbind off