[email protected]1 | Page Quick Installation Guide 12c Release 1 (12.1) for Oracle Solaris on x86-64 (64-Bit) This guide describes how to quickly install Oracle Database 12c Release 1 (12.1) on Oracle Solaris on x86-64 (64-Bit) systems. It includes information about the following: Table of Contents 1. Reviewing Information About This Guide.......................................................................................... 3 2. Logging Into the system as root ............................................................................................................. 3 3. Configuring Servers for Oracle Database ............................................................................................ 3 3.1 Checking Server Hardware and Memory Configuration ................................................................... 3 1. To determine the available RAM and swap space, enter the following command to obtain the system activity report:............................................................................................................................... 3 2. To determine the size of the configured swap space, enter the following command: .................. 3 3. To determine the amount of space available in the /tmp directory, enter the following command: .................................................................................................................................................. 4 4. To determine the amount of free disk space on the system, enter one of the following commands: ................................................................................................................................................ 4 5. To determine the RAM size, enter the following command: .......................................................... 4 3.2 General Server Minimum Requirements .............................................................................................. 5 3.3 Server Storage Minimum Requirements .............................................................................................. 5 3.4 Server Memory Minimum Requirements ............................................................................................. 6 4. Operating System Requirements for Oracle Solaris onx86-64 (64-Bit)............................................. 6 4.1 Supported Oracle Solaris 10 Releases for x86-64 (64-Bit) .................................................................... 7 5. Checking the Software Requirements ................................................................................................ 26 1. To determine which version of Oracle Solaris is installed, enter the following command: ........... 26 2. To determine the release level enter the following command: ......................................................... 26 3. To determine if the required packages are installed, enter the following command: ..................... 26 6. Verifying Operating System Patches on Oracle Solaris 10 .............................................................. 27
29
Embed
Quick Installation Guide - · PDF file · 2013-10-022013-10-02 · 3.1 Checking Server Hardware and Memory Configuration ... Extend the file system that contains the /tmp...
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
12c Release 1 (12.1) for Oracle Solaris on x86-64 (64-Bit)
This guide describes how to quickly install Oracle Database 12c Release 1 (12.1) on
Oracle Solaris on x86-64 (64-Bit) systems. It includes information about the following:
Table of Contents
1. Reviewing Information About This Guide .......................................................................................... 3
2. Logging Into the system as root ............................................................................................................. 3
3. Configuring Servers for Oracle Database ............................................................................................ 3
3.1 Checking Server Hardware and Memory Configuration ................................................................... 3
1. To determine the available RAM and swap space, enter the following command to obtain the
system activity report: ............................................................................................................................... 3
2. To determine the size of the configured swap space, enter the following command: .................. 3
3. To determine the amount of space available in the /tmp directory, enter the following
Note: You may also require additional font packages for Java, depending on your locale. Refer to the following website for more information: http://www.oracle.com/technetwork/java/javase/sola ris-font-requirements-142758.htm
5. Checking the Software Requirements
To ensure that the system meets these requirements, follow these steps:
1. To determine which version of Oracle Solaris is installed, enter the following command:
# uname -r 5.10
In this example, the version shown is Oracle Solaris 10 (5.10).
2. To determine the release level enter the following command:
# cat /etc/release # cat /etc/release Oracle Solaris 10 1/13 s10x_u11 wos_24a X86 Copyright (c) 1983, 2013, Oracle and/or its affil iates. All rights reserved. Assembled 17 January 20 13
3. To determine if the required packages are installed, enter the following command:
pkginfo -i pkg_name
Where pkg_name is the name of the package to check.
For example, to determine if the required Oracle Solaris 10 packages are installed, enter a
# pkginfo -i SUNWarc SUNWbtool SUNWhea SUNWlibC SUN Wlibm SUNWlibms SUNWsprot \ > SUNWtoo SUNWi1of SUNWi1cs SUNWi15cs SUNWxwfnt SUN Wcsl SUNWdtrc system SUNWarc Lint Libraries (usr) system SUNWbtool CCS tools bundled with SunOS system SUNWcsl Core Solaris, (Shared Libs) system SUNWdtrc DTrace Clients system SUNWhea SunOS Header Files system SUNWi1of ISO-8859-1 (Latin-1) Optional Fonts system SUNWlibC Sun Workshop Compilers Bundle d libC system SUNWlibm Math & Microtasking Library H eaders & Lint Files (Usr) system SUNWlibms Math & Microtasking Libraries (Usr) system SUNWsprot Solaris Bundled tools system SUNWtoo Programming Tools system SUNWxwfnt X Window System platform requ ired fonts ERROR: information for "SUNWi1cs" was not found ERROR: information for "SUNWi15cs" was not found
If a package that is required for your system architecture is not installed, then install it.
Refer to your operating system or software documentation for information about
installing packages.
See Also: "Verifying Operating System Packages on Oracle Solaris
10"
Note: There may be more recent versions of packages listed installed on the
system. If a listed patch is not installed, then determine if a more recent
version is installed before installing the version listed.
6. Verifying Operating System Patches on Oracle Solaris 10
Note: Your system may have more recent versions of the listed patches
installed on it. If a listed patch is not installed, then determine if a more recent
version is installed before installing the version listed.
Verify that you have the required operating system patches. To ensure that the system meets
these requirements, use the following procedure:
1. To determine whether an operating system patch is installed, and whether it is the correct
version of the patch, enter a command similar to the following:
# /usr/sbin/patchadd -p | grep patch_number
For example, to determine if any version of the 119963 patch is installed, use the
following command:
# /usr/sbin/patchadd -p | grep 119963
If an operating system patch is not installed, then download and install it from My
Oracle Support: https://support.oracle.com
7. Creating Required Operating System Groups and User
The following local operating system groups and users are required if you are
installing Oracle Database:
■ The Oracle Inventory group (typically, oinstall )
You must create this group the first time you install Oracle software on the system. The usual name chosen for this group is oinstall . This group owns the Oracle inventory, which is a catalog of all Oracle software installed on the system.
■ The OSDBA group (typically, dba )
You must create this group the first time you install Oracle Database software on the system. It
identifies operating system user accounts that have database administrative privileges (the
SYSDBA privilege). The default name for this group is dba.
If you want to specify a group name other than the default dba group, then you must choose the
Custom installation type to install the software or start Oracle Universal Installer as a user that is
not a member of this group. In this case, Oracle Universal Installer prompts you to specify the
name of this group.
• An unprivileged user
Verify that the unprivileged user nobody exists on the system. The nobody user must own the
external jobs (extjob) executable after the installation.
Verifying that the User nobody Exists
Before installing the software, perform the following procedure to verify that the nobody user
exists on the system:
1. To determine whether the user exists, enter the following command:
# id nobody
uid=60001(nobody) gid=60001(nobody)
#
If this command displays information about the nobody user, then you do not have to
create that user.
2. If the nobody user does not exist, then enter the following command to create it:
# /usr/sbin/useradd nobody
■ The Oracle software owner (typically, oracle)
You must create this user the first time you install Oracle software on the system. This user owns
all of the software installed during the installation. This user must have the Oracle Inventory
group as its primary group. It must also have the OSDBA and OSOPER groups as secondary
groups.
■ The OSOPER group (Optional. Typically, oper)
This is an optional group. Create this group if you want a separate group of operating system
users to have a limited set of database administrative privileges (the SYSOPER privilege). By
default, members of the OSDBA group also have the SYSOPER privilege.
If you want to specify a separate OSOPER group, other than the default dba group, then you must
choose the Custom installation type to install the software or start Oracle Universal Installer as a
user that is not a member of the dba group. In this case, Oracle Universal Installer prompts you to
specify the name of this group. The usual name chosen for this group is oper.
To determine whether these groups and users exist, and if necessary, to create them, follow
these steps:
1. To determine whether the oinstall group exists, enter the following command:
# more /var/opt/oracle/oraInst.loc
If the output of this command shows the oinstall group name, then the group exists.
If the oraInst.loc file exists, then the output from this command is similar to the
5. If necessary, complete one of the following actions:
■ If the oracle user exists, but its primary group is not oinstall or it is not a member
of the dba group, then enter the following command:
# /usr/sbin/usermod -g oinstall -G dba oracle
Oracle does not support modifying an existing installation owner. See Oracle
Database Installation Guide for more information.
■ If the oracle user does not exist, enter the following command to create it:
-bash-3.2$ df -h |egrep 'File|export' Filesystem size used avail capacity Mounted on /dev/dsk/c0t0d0s7 7.1G 7.2M 7.0G 1% /export/home
To delete existing users: ========================== userdel -r oracle � this will remove his home folder as well or userdel oracle � this will keep his home folder and only remove user
# id -a oracle id: invalid user name: "oracle" # pwd /export/home # ls -ltrh total 18 drwx------ 2 root root 8.0K Jul 7 18: 49 lost+found drwxr-xr-x 2 root root 512 Jul 9 16: 49 soft
■ project.max-shm-memory resource control = the cumulative sum of all shared memory allocated on each Oracle database instance started under the corresponding project.
■ The project.max-shm-memory resource control value assumes that no other application is using the shared memory segment from
this project other than the Oracle instances. If applications, other than the Oracle instances are using the shared memory segment, then you must add that shared memory usage to the project.max-shm-memory resource control value.
■ Ensure that memory_target (or max_sga_size ) does not exceed process.max-address-space and project.max-shm-memory . For more information, see My Oracle Support Note 1370537.1 at:
Where default is the project ID obtained by running the id -p command.
For example, to change the setting for project.max-shm-memory to 6 GB for the project
default without a system reboot, enter the following command:
prctl -n project.max-shm-memory -v 6gb -r -i projec t default
See Also: Administering Oracle Solaris 10 at:
http://docs.oracle.com/cd/E23824_01/index.html
9.2 Displaying and Changing Kernel Parameter Values
Use the following procedure to display the current value specified for resource
controls, and to change them if necessary:
1. To display the current values of the resource control, enter the following
commands:
$ id -p // to verify the project id uid=100(oracle) gid=101(oinstall) projid=3(default) $ prctl -n project.max-shm-memory -i project group.oinstall $ prctl -n project.max-sem-ids -i project group.oinstall As seen above projid is showing default which needs to be changed to dba group. $ cat /etc/project system:0:::: user.root:1:::: noproject:2:::: default:3:::: group.staff:10:::: Project file do have dba entry as above. We would a dd one as root user. As below steps:
Login as root user : # id -p uid=0(root) gid=0(root) projid=1(user.root) # cat /etc/project system:0:::: user.root:1:::: noproject:2:::: default:3:::: group.staff:10::::
# projadd -c "For Oracle Group" 'group.oinstall' # cat /etc/project system:0:::: user.root:1:::: noproject:2:::: default:3:::: group.staff:10:::: group.oinstall:100:For Oracle Group::: # su - oracle Oracle Corporation SunOS 5.10 Generic Pat ch January 2005 $ id -p uid=100(oracle) gid=101(oinstall) projid=100( group.oinstall )
2. If you must change any of the current values, then:
Check the current values for shared memory and Semapores
Note: When you use the prctl command (Resource Control) to change system parameters, you do not have to restart the system for these parameter changes to take effect. However, the changed parameters do not persist after a system restart.
4. To verify that the resource control is active, check process ownership, and run the
commands id and prctl :
# su - oracle $ id -p uid=100(oracle) gid=101(oinstall) projid=100( group.oinstall ) $ prctl -n project.max-shm-memory -i process $$ process: 951 : -ksh NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory privileged 2.00GB - deny - system 16.0EB max deny - OR $ prctl -n project.max-shm-memory -i project group. oinstall project: 100: group.oinstall NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-shm-memory
privileged 2.00GB - deny - system 16.0EB max deny - $ prctl -n project.max-sem-ids -i project group.oin stall project: 100: group.oinstall NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT project.max-sem-ids privileged 256 - deny - system 16.8M max deny -
Note: The value for the maximum shared memory depends on the SGA requirements and should be set to a value greater than the SGA size. For more information, see the Oracle Solaris Tunable Parameters Reference Manual.
Setting UDP and TCP Kernel Parameters Manually
=================================================
tcp_smallest_anon_port 9000
tcp_largest_anon_port 65500
udp_smallest_anon_port 9000
udp_largest_anon_port 65500
If you do not use a Fixup script or CVU to set ephemeral ports, then use NDD to ensure
that the kernel TCP/IP ephemeral port range is broad enough to provide enough
ephemeral ports for the anticipated server workload.
Ensure that the lower range is set to at least 9000 or higher, to avoid Well Known ports,
and to avoid ports in the Registered Ports range commonly used by Oracle and other
server ports.
Set the port range high enough to avoid reserved ports for any applications you may
intend to use.
If the lower value of the range you have is greater than 9000, and the range is large
enough for your anticipated workload, then you can ignore OUI warnings regarding the
ephemeral port range.
Use the following command to check your current range for ephemeral ports:
Oracle recommends that you set shell limits and system configuration parameters as
described in this section.
Note: The shell limit values in this section are minimum values only. For production database systems, Oracle recommends that you tune these values to optimize the performance of the sys tem. See your operating system documentation for more information about configuring shell limits.
The ulimit settings determine process memory related resource limits. Verify that the
shell limits displayed in the following table are set to the values shown:
Shell Limit Description Soft Limit (KB) Hard Limit (KB)
STACK Size of the stack segment of the process
at most 10240 at most 32768
NOFILES Open file descriptors at least 1024 at least 65536
MAXUPRC or MAXPROC
Maximum user processes at least 2047 at least 16384
To display the current value specified for these shell limits enter the following
commands:
ulimit -s
ulimit –n
For Standard Project, Task, and Process Resource Controls http://docs.oracle.com/cd/E23824_01/html/821-1460/rmctrls-3.html#rmctrls-4
10.1 To check current soft shell limits, enter the following command: -
See more at: http://www.unixarena.com/2012/07/solaris-10s-resource-management-and.html $ ulimit –a � By default -a shows Soft Limit time(seconds) unlimited file(blocks) unlimited data(kbytes) unlimited stack(kbytes) 10240 coredump(blocks) unlimited nofiles(descriptors) 256 vmemory(kbytes) unlimited OR $ ulimit -Sa time(seconds) unlimited file(blocks) unlimited
10.2 To check maximum hard limits, enter the following command:
Hard Limit can only be modified by Root $ ulimit -Ha time(seconds) unlimited file(blocks) unlimited data(kbytes) unlimited stack(kbytes) unlimited coredump(blocks) unlimited nofiles(descriptors) 65536 vmemory(kbytes) unlimited $ ulimit -Hn 65536 $ id uid=100(oracle) gid=101(oinstall) $ plimit $$ 822: -ksh resource current maximum time(seconds) unlimited unlimited file(blocks) unlimited unlimited data(kbytes) unlimited unlimited stack(kbytes) 10240 unlimited coredump(blocks) unlimited unlimited nofiles(descriptors) 256 65536 vmemory(kbytes) unlimited unlimited Change as Below Temporarily for session Specific =================================================== === The plimit command can be used to set the limit for the maximum number of open files of an already running process. For example, the following command will set the sof t limit to 2048 and the hard limit to 65536 for process $$ (Current Process): $ id -p uid=100(oracle) gid=101(oinstall) projid=100(group. oinstall) $ plimit -n 2048,65536 $$ OR ulimit -Sn 2048 $ plimit -n 2048,65536 $$ $ plimit $$ 822: -ksh resource current maximum time(seconds) unlimited unlimited file(blocks) unlimited unlimited data(kbytes) unlimited unlimited
stack(kbytes) 10240 unlimited coredump(blocks) unlimited unlimited nofiles(descriptors) 2048 65536 vmemory(kbytes) unlimited unlimited # echo $$ 854 # prctl -n process.max-file-descriptor $$ process: 854: -sh NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT process.max-file-descriptor basic 256 - deny 854 privileged 65.5K - deny - system 2.15G max deny -
10.3 To change Soft/hard limits permanently, enter the following command:
NOFILES Open file descriptors at least 2048 at least 65536 As root: ========= # cat /etc/project system:0:::: user.root:1:::: noproject:2:::: default:3:::: group.staff:10:::: group.oinstall:100:For Oracle Group:::project.max-s em-ids=(privileged,256,deny);project.max-sem-nsems=(privileged,256,deny);project.max-shm-ids=(privileged,100,deny);project.max-shm-memory=(privileged,2147483648,deny) # cp -pr /etc/project /etc/project.bkp
export TEMP TMPDIR PATH=/usr/sbin:/usr/bin:/usr/openwin/bin:. export PATH alias c='clear' alias s='sqlplus / as sysdba' alias h='history -30' echo "Profile execution completed"
To verify that the environment has been set correctly, enter the following commands:
$ umask $ env | more
Verify that the umask command displays a value of 22, 022, or 0022 and the
environment variables that you set in this section have the correct values.
VERIFY you can create a file in ORACLE_BASE as ORACLE user