Oracle 11gR2 ASM single instance installation steps

Oracle 11gR2 ASM single instance installation steps
Environment: Platform: VisualBox 4.3.12OS: Oracle Linux 5.8 Grid Infrastructure: 11.2.0.3Database: 11.2.0.3 1. Install the Operating System (omitted) 2. Configure the software installation environment-configure a local yum cd/etc/yum after installation. repos. d/touch yum_oel5.repovi yum_oel5.repo Add the following content: [oel5] name = Oracle Linux 5.8 x86_64 DVD baseurl = file: /// media/Servergpgcheck = 0 enabled = 1 detailed usage of repo settings can refer to: http://docs.oracle.com/cd/E37670_01/E37355/html/ol_create_repo.html -- install necessary packages for Oracle software and Kernel Parameter settings yum install oracle-validated note, in Oracle Linux 6. the yum install oracle-rdbms-server-11gR2-preinstall-1.0-6.el6 is used in x with some related yum commands: yum clean allyum repolistyum list in OEL6 use yum to install "Desktop", "X Window System", "Chinese Support" yum -- disablerepo = * -- enablerepo = oel6 groupinstall "Desktop" yum -- disablerepo = * -- enablerepo = oel6 groupinstall "X Window System" yum -- disablerepo = * -- enablerepo = oel6 groupinstall "Chinese Support" If Oracle Linux is used, this package will automatically configure the kernel parameters, users, user groups, and software packages required for installing the Oracle software after installation. Therefore, we strongly recommend that you use Oracle Linux to build a test environment-mount the disk mount-t iso9660/dev/cdrom/media-add users and groups (non-Oracle Linux environment configuration) groupadd-g 501 oinstallgroupadd-g 502 dbagroupadd-g 503 opergroupadd-g 504 asmadmingroupadd-g 505 asmdbagroupadd-g 506 asmoper useradd-u 500-g oinstall-G dba, asmdba, asmadmin, revoke oracleuseradd-u 507-g oinstall-G asmadmin, asmdba, asmoper, daily, and dba grid. Note that the quota group is not required. dba, asmdba, asmadmin must have -- modify the grid and oracle user password passwd oraclepasswd grid -- configure the Environment Variable grid: export ORACLE_SID = + ASMexport ORACLE_BASE =/u01/app/gridexport ORACLE_HOME =/u01/app/11.2.0/gridexport PATH = $ ORACLE_HOME/bin: $ PATH: /usr/local/bin /:. export TEMP =/tmpexport TMP =/tmp export TMPDIR =/tmpumask 022 oracle: ORACLE_SID = zlm; export ORACLE_SIDORACLE_BASE =/u01/app/oracle; export ORACLE_BASE
ORACLE_HOME = $ ORACLE_BASE/product/11.2.0/db_1; export ORACLE_HOMEGRID_HOME =/u01/app/11.2.0/grid; export GRID_HOMENLS_DATE_FORMAT = "YYYY: MM: DD HH24: MI: SS "; export NLS_DATE_FORMATNLS_LANG = american_america.ZHS16GBK; export NLS_LANGPATH =. :$ {PATH }:$ HOME/bin: $ ORACLE_HOME/bin: $ GRID_HOME/bin export PATHexport TEMP =/tmpexport TMPDIR =/tmpumask 022 environment variables used to configure the red font (required) -- add a shared disk VBoxManage createhd -- filename asm01.vdi -- size 3072 -- format VDI -- variant FixedVBoxManage createhd -- filename plugin -- size 3072 -- format VDI -- variant FixedVBoxManage createhd -- filename plugin -- size 3072 -- format VDI -- variant Fixed -- set the disk as a shared disk VBoxManage storageattach asm11g -- storagectl "SATA" -- port 1 -- device 0 -- type hdd -- medium attachment -- mtype implements ablevboxmanage storageattach asm11 -- storagectl "SATA" -- port 2 -- device 0 -- type hdd -- medium asm02.vdi -- mtype unzip ablevboxmanage storageattach asm11g -- storagectl "SATA" -- port 3 -- device 0 -- type hdd -- medium restart -- mtype retriable note: VBoxManage.exe is executed in the cmd command line of the local window (first to the root directory of the installation of the vbox software). You can also add a shared disk by clicking the mouse, the principle is the same-use udev to bind a disk for Linux 6. xfor I in B c d; doecho "KERNEL = \" sd * \ ", BUS = \" scsi \", PROGRAM = \ "/sbin/scsi_id-g-u/dev/\ $ name \", RESULT = \ "'/sbin/scsi_id-g-u/dev/sd $ I' \", NAME = \ "asm-disk $ I \", OWNER = \ "grid \", GROUP = \ "asmadmin \", MODE = \ "0660 \" "done for Linux 5. xfor I in B c d; doecho "KERNEL = \" sd * \ ", BUS = \" scsi \", PROGRAM = \ "/sbin/scsi_id-g-u-s % p \", RESULT = \ "'scsi _ id-g-u-s/block/sd $ I '\", NAME = \ "asm-disk $ I \", OWNER = \ "grid \", GROUP = \ "asmadmin \", MODE = \ "0660 \" "done, pay attention to the differences of scripts in different versions, otherwise, the scsi_id of the disk cannot be obtained. -- create the rule file touch/etc/udev/rules. d/99-oracle-asmdevices.rules -- restart udev to make the configuration take effect./sbin/start_udev -- disable the firewall. (If you have already disabled the firewall when installing the OS, skip this step.) temporarily disable the Firewall: service iptables statusservice iptables stop permanent close: chkconfig -- list iptables chkconfig [-- level 35] iptables off PS: You can also permanently disable sendmail, otherwise, the system will take a long time to start-create the required directories (directories configured in environment variables) mkdir-p/u01/app/gridmkdir-p/u01/app/11.2.0/gridchown-R grid: oinstall/u01 mkdir-p/u01/app/oracle/product/11.2.0/db_1chown-R oracle: oinstall/u01/app/oraclechmod-R 775/u01 -- disable selinux (you can disable selinux when installing OS) cat>/etc/selinux/config <EOFSELINUX = DISABLEDEOF -- set Logon Restrictions cat>/etc/pam. d/login <EOFsession required pam_limits.soEOF -- set profile (optional) cat>/etc/profile <EOFif [/$ USER = "oracle"] | [/$ USER = "grid"]; thenif [/$ SHELL = "/bin/ksh"]; thenulimit-p 16384 ulimit-n 65536 elseulimit-u 16384-n 65536 fiumask 022 fiEOF -- modify the hosts file cat/etc/hosts127.0.0.1 localhost asm11g III. Install GI software (omitted) here we may encounter several problems: given that root permissions for the CRS directory may be modified, Oracle does not recommend setting GRID_HOME (GI software installation directory) to GRID_BASE, if this is the case, an INS-32033 warning will be given: but with this modification, you can run the pre-Installation check: in this way, the/g01/app/11.2.0/grid is no longer in the/g01/app/grid directory. In addition, if the Fixable status is "Yes" after an error is found during the installation pre-Check, you can click "Fix & Check again" to enable Oracle to automatically Fix the error. The repair script is automatically provided, for example, run/tmp/CVU_11.2.0.3.0_grid/runfixup as the root user. sh this script and then check to meet the installation requirements about NTP error, you can directly ignore, or modify/etc/ntp. solve the conf name [root @ zlm etc] # ls-l | grep ntp
Drwxr-xr-x 2 root 4096 Jan 5 ntp
-Rw-r -- 1 root 1833 Nov 17 2011 ntp. conf [root @ zlm etc] # mv ntp. conf ntp. conf_bak -- after GI software is installed, the root user executes the single-node script/u01/app/11.2.0/grid/perl/bin/perl-I/u01/app/11.2.0/grid/perl/lib-I/u01/app/ 11.2.0/grid/crs/install/u01/app/11.2.0/grid/crs/install/roothas. pl must be implemented in this step. Otherwise, the crs resources will not be started, and crsctl and other related GI commands will not be executed. 4. Install the ORACLE database software. After the database software is installed, the grid user will execute asmca, add a disk group (Omitted) -- before creating a database, the oracle user executes netmgr and creates a listener (omitted). 5. An error occurred when selecting a database disk during dbca database creation, unable to identify the previously created disk group
If you enter one manually, an error is returned:
The solution is very simple. Just give the oracle binfile A 6751 permission, and the root user can execute the commands separately under the bin in the Software Directory: chmod 6751/u01/app/11.2.0/grid/bin/oraclechmod 6751/u01/app/oracle/product/11.2.0/db_1/bin/oracle about 6751 permissions: 6751 specify the ugoa permissions respectively: the first six represents that u (owner) has read and write permissions, and the second seven represents g (group) the third digit has the read, write, and execution permissions. The third digit 5 represents o (other users). The fourth digit 1 represents a (owner, group, and other users) four-digit 6751 with execution permission. If three digits indicate 675, the fourth digit inherits the umask value. oracle users belong to the dba group and the oinstall executable code require a minimum permission of 110, that is, the owner and the group have the execution permission, for maintenance convenience, 775 is generally granted to the owner and the group with the read, write, and execution permissions. Other users have the execution permission.

Install Oracle 10g xe on CentOS 5.5 i386

Installation notes for Oracle 11g xe in Linux

Install Oracle 11gR2 (x64) in CentOS 6.4)

Steps for installing Oracle 11gR2 in vmwarevm

Install Oracle 11g XE R2 In Debian