I went to a client yesterday to install the 11g database, and made a record of the entire installation process and encountered problems. Because the customer cannot remotely connect to the server using his own machine or copy any files through a USB flash drive or a mobile hard disk, some records cannot be detailed and can only be roughly written by memory.
HOST: Sun Netra T4-1 m4000cpu: 8 core 2.85ghz memory: 32g system: Solaris 10
I. Check hardware requirements
-- View memory
#/Usr/sbin/prtconf | grep "memory size" memory size: 32768 megabytes
#/Usr/sbin/swap-lswapfile Dev swaplo blocks free/dev/DSK/c0t0d0s1 8405360, 9 16 8405360 512 -- a block is K, so here is 4G
-- View System Architecture#/Bin/isainfo-kv64-bit sparcv9 Kernel Modules
Note: If you have downloaded the Solaris x86 media, it cannot be installed on the iSCSI host, and the iSCSI media can only be installed on the real machine, and the virtual machine cannot simulate
-- View available disk space# DF-k/tmp must be at least 1 GB, currently 30 GB
# DF-K requires 4.68g space to install Oracle Enterprise Edition. Currently, 197g
2. check software requirements
-- View the Solaris kernel version# Uname-r5.10
$ CAT/etc/releasesolaris 10 5/09 s10s_u7wos_08 iSCSI
-- List of packages to be installedSunwarcsunwbtoolsunwheasunwlibcsunwlibmsunwlibmssunwsprotsunwtoosunwi1ofsunwi1cs (ISO8859-1) sunwi15cs (ISO8859-15) sunwxwfntsunwcsl
-- Check the package# Pkginfo-I sunwarc sunwbtool sunwhea sunwlibc sunwlibm sunwlibms sunwsprot sunwtoo sunwi1of sunwi1cs sunwi15cs sunwxwfnt sunwcsl
If an unmounted installation is found, mount the installation disk and run the pkgadd command.
-- Installation PackagePkgadd-D/path sunwarc sunwbtool sunwhea sunwlibc sunwlibm sunwlibms sunwsprot sunwtoo sunwi1of sunwi1cs sunwi15cs sunwxwfnt sunwcsl
/Path indicates the path to attach the disk.
3. Create users and user groups
Oracle software installation requires the following groups of users: the Oracle Inventory Group (typically, oinstall) The osdba group (typically, DBA) the Oracle software owner (typically, Oracle) the osoper group (optional. typically, logical) -- the logical group is optional.
-- View oinstall group information# More/var/opt/Oracle/orainst. locinventory_loc =/Oracle/orainventoryinst_group = oinstall
-- View DBA group information# Grep DBAs/etc/groupdba: 100: wcadmin, Oracle
-- Add Group#/Usr/sbin/groupadd oinstall #/usr/sbin/groupadd DBA
-- View the permission group of an Oracle user# ID-A oracleuid = 103 (Oracle) gid = 102 (oinstall) groups = 100 (DBA)
Note that the last item cannot be seen without the-a parameter, for example, # ID Oracle
Uid = 103 (Oracle) gid = 102 (oinstall)
-- Add oracle users to the oinstall and DBA groups#/Usr/sbin/useradd-G oinstall-g dba Oracle
-- Add a password file# Passwd-r files Oracle requires a password and confirmation
4. Configure OS Kernel Parameters
-- Modify/etc/System
Set noexec_user_stack = 1 Set semsys: seminfo_semmni = 100 Set semsys: seminfo_semmns = 1024 set semsys: seminfo_semmsl = 256 set semsys: runtime = 32767 set shmsys: shminfo_shmmax = 4294967296 -- the actual value must be greater than the SGA value set shmsys: shminfo_shmmni = 100
Note that Vim is not installed on Solaris 10 by default. You can use VI or gedit to modify the parameter values to meet the minimum requirements for installation. The actual value of/etc/system already exists more than above, only the listed items can be modified.
-- View the Project ID# Su-Oracle
$ Id-puid = 103 (Oracle) gid = 102 (oinstall) projid = 3 (default)
The value here is different from the value in the official document. It is default rather than group. dBA, but it does not affect the smooth installation.
-- View Project # Cat/etc/Project
System: 0 ::: user. root: 1: noproject: 2: Default: 3: group. staff: 10 ::: group. DBA: 100: Oracle default -- if the last row does not exist, manually add
5. Create related paths and grant Oracle Read and Write Permissions
# Mkdir-P/Oracle # chown-r ORACLE: oinstall/Oracle
# Chmod-r 775/Oracle
6. Configure Environment Variables
-- View shell types$ Echo $ Shell
/Bin/sh
-- Modify Environment VariablesThe Solaris environment variable file is. /. profile, with the Linux bash shell. bash_profile is different. For example, the Oracle user's environment variable is/home/Oracle /. profile # Su-Oracle $ TMP =/tmp $ tmpdir =/tmp $ export TMP tmpdir $ oracle_sid = orcl
$ Oracle_base =/Oracle $ export oracle_sid Oracle base $ display = 192.168.1.181: 0.0 -- note that the IP address here is a host with a graphic interface, not a DB Server $ export display $ umask 022
-- Make sure that the ORACLE_HOME and tns_admin environment variables are not set (recommended for Oracle)$ Unset ORACLE_HOME
$ Unset tns_admin
-- After setting the preceding variables, run the Env command to check the variables.$ ENV | more
Note that this is only valid in the current session and is not written. in the profile file. profile file, and finally use .. /. make the change take effect. Note that the source command is unavailable on Solaris.
7. Copy the installation media
#/Usr/sbin/Mount-r-F hsfs/dev/DSK/c0t0d0s1/DVD
8. Install database software
#/Mount_point/database/runinstaller -- if you are prompted that the command cannot be found, Add./And run the command. The Oracle user must have the read permission on the Mount directory; otherwise, the operation fails.
I personally think it is easier to configure the above steps than Linux, but it may be difficult for many people to install Oracle databases on Solaris for the first time, try it and you will have experience.
Problems encountered during database installation:
1. Insufficient swapBecause the physical memory is 32 GB, but currently only 4 GB is assigned to swap, the swap-l command can view the swap size currently configured. Add and solidify the swap file and run runinstaller again.
2. OS-related patches missing: 124861-15This package is mainly used for Oracle XML developer's kit (xdk), SunOS 5.10 compiler common patch for Sun C ++ (Optional). Note that this package is optional, therefore, you can select ignore.
After resolving the swap deficiency and ignoring the patch-missing error, the database software is successfully installed, followed by dbca, which is consistent with the steps on other platforms and is not described in detail.
Appendix: Solaris solution to swap deficiency:
1. Add swap
1. Become a Super User $ su-Root
2. Create a swap file # mkfile NN [klblm]/path/filename for example: # mkfile 100 m swapfile
3. Activate the swap file #/usr/sbin/swap-A/path/filename
The swap file must be specified with an absolute path. filename indicates the file created in the previous step.
4. Fixed the swap and recorded the file name and swap type in the/etc/vfstab file, for example,/path/filename--Swap-no-
5. Verify whether/usr/sbin/swap-L is added to the swap file
Ii. Delete swap
1. Become a Super User $ su-Root
2. Use the swap-D command to reclaim swap space #/usr/sbin/swap-D/path/filename
3. Edit the/etc/vfstab file and remove the entity of the swap file.
4. reclaim this file from the file system # rm swap filename
5. Of course, if the swap space is not a file but a partition, you need to create a new file system and then mount it to the original file system.
Install mirror E 11g on Solaris 10 iSCSI 64 bit
