Saminnet-Search Article Wiki Forum Piwigo SNS Cloud vtiger Sugar
Install 12c ASM

  • Data-Articles
    • Baja iwf (107) Sun09,20:21pm

      sesuai post saya yang terakhirツdisini, rumah dua pohon sedang dalam pembangunan tahap 2 dengan material utama menggunakan baja. baja adalah material konstruksi yang paling padat apabila dibandingkan dengan beton dan kayu karena memiliki berat satuan yang cukup besar. karena baja bisa difabrikasi di pabrik, pemasangan di site bisa lebih cepat dibandingkan dengan beton yang mesti dicetak dan ditun…

      Read More...

Install 12c ASM

Background & Overview

The following documentation provides instructions for building an Oracle 12c database with ASM residing on RedHat (Version 6.7, Kernel version 2.6.32). Use the commandツcat /etc/*release*ツto check the Oracle Linux OS version andツuname -rツto check the Kernel level.

Further reference documentation about Oracle 12c and Oracle Linux is detailed in theツOther Referencesツsection below.

Assumptions

This document expects and assumes the following:

  • The instructions are carried out by a qualified DBA.
  • All necessary client software, e.g. Telnet and X-Server is available.
  • All references toツSIDツshould be replaced with correct database name as derived using a suitable database naming standard.
  • Allツ$variableツreferences assume theツ.profileツas described in theツFile Listingsツsection has been implemented and run.

Useful Information

  • Read theツKnown Issuesツsection below.

Software

File Name Description Byte Count MD5 Hash
linuxamd64_12102_database_1of2.zip Database Binaries File 1 1673544724 080435a40bd4c8dff6399b231a808e9a
linuxamd64_12102_database_2of2.zip Database Binaries File 2 1014530602 30f20ef9437442b8282ce3984546c982
linuxamd64_12102_grid_1of2.zip Grid Infrastructure Binaries File 1 1747043545 d793c2ba5db9008b79077bff8d27a219
linuxamd64_12102_grid_2of2.zip Grid Infrastructure Binaries File 2 646972897 0e18a9abb80427baf18f85865b1ecd5d
p20996835_121020_Linux-x86-64 Grid Infrastructure and DB PSU 1031691784 F32C00880F4311A20D6D2174ABE95C38
p6880880_121010_Linux-x86-64 OPatch Version 12.1.0.1.8 52853599 f3978f9d719f8f345ca8cca386683a59

Step-By-Step Guide - Pre-Requisites

1. Ensure theツOracle Linuxツversion isツ6ツor higher.

  • cat /etc/*release*

2. Ensure theツOracle LinuxツKernel version for both nodes isツ2.6.18ツor higher.

  • uname -r

3. As a minimum ensureツRedHatツhas the following packages installed on both nodes.

unzip (x86_64)
xorg-x11-utils-7.5-6.el6.x86_64
binutils-2.20.51.0.2-5.11.el6 (x86_64)
compat-libcap1-1.10-1 (x86_64)
compat-libstdc++-33-3.2.3-69.el6 (x86_64)
compat-libstdc++-33-3.2.3-69.el6 (i686)
gcc-4.4.4-13.el6 (x86_64)
gcc-c++-4.4.4-13.el6 (x86_64)
glibc-2.12-1.7.el6 (i686)
glibc-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6 (i686)
ksh
libgcc-4.4.4-13.el6 (i686)
libgcc-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6 (i686)
libstdc++-devel-4.4.4-13.el6 (x86_64)
libstdc++-devel-4.4.4-13.el6 (i686)
libaio-0.3.107-10.el6 (x86_64)
libaio-0.3.107-10.el6 (i686)
libaio-devel-0.3.107-10.el6 (x86_64)
libaio-devel-0.3.107-10.el6 (i686)
libXext-1.1 (x86_64)
libXext-1.1 (i686)
libXtst-1.0.99.2 (x86_64)
libXtst-1.0.99.2 (i686)
libX11-1.3 (x86_64)
libX11-1.3 (i686)
libXau-1.0.5 (x86_64)
libXau-1.0.5 (i686)
libxcb-1.5 (x86_64)
libxcb-1.5 (i686)
libXi-1.3 (x86_64)
libXi-1.3 (i686)
make-3.81-19.el6
sysstat-9.0.4-11.el6 (x86_64)

4. Set the kernel parameters inツ/etc/sysctl.confツfor both nodes as follows.ツNOTEツIf the current value for any parameter is higher than the value listed below, do not change the value of that parameter.

shmmax - Half the server memory
shmmni - 4096 (or greater)
fs.file-max - 6815744 (or greater)
fs.aio-max-nr - 1048576 (or greater)
net.core.rmem_default - 262144 (or greater)
net.core.rmem_max - 4194304 or greater)
net.core.wmem_default - 262144 (or greater)
net.core.wmem_max - 1048576 (or greater)
sem - 250ツ32000ツ100ツ128 (or greater)
net.ipv4.ip_local_port_range - 9000ツ65535

5. Ensureツoracleツaccount andツdbaツgroup exists on both nodes.

6. Update the following fileツ/etc/security/limits.confツon both nodes.

oracle soft nproc 16384
oracle hard nproc 16384
oracle soft nofile 20480
oracle hard nofile 65536
oracle soft stack 10240
oracle hard stack 32768

7. Ensure the following line in theツ/etc/pam.d/loginツfile existis on both nodes.

session required pam_limits.so

8. Create theツ.profileツ- seeツFile Listingsツsection below.

9. InstallツASMLIB.

10. Create a single partition on each device to be used byツASM.

11. Create theツASMツdisks. For this installation the following disks will need to be created.

  • asm-data01
  • asm-fra01
  • asm-redo01
  • asm-redo02

12. Check to confirm the disk are set-up correctly

  • /usr/sbin/oracleasm listdisks

13. Unzip the files

  • Log on as Oracle
  • cd /u01/app/oracle/SOFTWARE
  • unzip linuxamd64_12102_database_1of2.zip
  • unzip linuxamd64_12102_database_2of2.zip
  • unzip linuxamd64_12102_grid_1of2.zip
  • unzip linuxamd64_12102_grid_2of2.zip
  • unzip p6880880_121010_Linux-x86-64
  • unzip p20996835_121020_Linux-x86-64

Step-By-Step Guide - ASM Binary Installs

1. Log on to Oracle.

2. Unset ORACLE_HOME and GRID_HOME

  • unset ORACLE_HOME
  • unset GRID_HOME
  • unset ORACLE_SID
  • unset TNS_ADMIN

3. Install Grid Infrastructure Using the GUI

  • cd /u01/app/oracle/SOFTWARE/grid
  • ./runInstaller

4. Follow the instructions as detailed in theツscreenshots here

5. When prompted run the root scripts in the order specified

  • Log on as root
  • /u01/app/oraInventory/orainstRoot.sh
  • /u01/app/oracle/product/12.1.0/grid/root.sh

Step-By-Step Guide - Configure ASM

1. Create the extra Disk Groups

  • . oraenv
  • ORACLE_SID = [oracle] ? +ASM
  • sqlplus / as sysasm
  • SQL>ツCREATE DISKGROUP FRA01 EXTERNAL REDUNDANCY DISK 窶/dev/asm-fra001窶イ ATTRIBUTE 窶呂OMPATIBLE.ASM窶=窶12.1.0.0.0窶イ,窶僂OMPATIBLE.RDBMS窶=窶12.1.0.0.0窶イ,窶僊U_SIZE窶=窶4M';
  • SQL>ツCREATE DISKGROUP REDO01 EXTERNAL REDUNDANCY DISK 窶/dev/asm-redo001窶イ ATTRIBUTE 窶呂OMPATIBLE.ASM窶=窶12.1.0.0.0窶イ,窶僂OMPATIBLE.RDBMS窶=窶12.1.0.0.0窶イ,窶僊U_SIZE窶=窶4M';
  • SQL>ツCREATE DISKGROUP REDO02 EXTERNAL REDUNDANCY DISK 窶/dev/asm-redo002窶イ ATTRIBUTE 窶呂OMPATIBLE.ASM窶=窶12.1.0.0.0窶イ,窶僂OMPATIBLE.RDBMS窶=窶12.1.0.0.0窶イ,窶僊U_SIZE窶=窶4M';

2. Update parameter file with new Diskgroups

  • SQL>ツALTER SYSTEM SET ASM_DISKGROUPS=窶僥RA01窶イ, 窶漏EDO01窶イ, 窶漏EDO02窶イ SCOPE=BOTH SID=窶+ASM窶

3. Configure ASM to use huge pages

  • . oraenv
  • ORACLE_SID = [oracle] ? MYDB001
  • SQL>ツsqlplus / as sysdba
  • SQL>ツshutdown immediate;
  • SQL>ツquit
  • . oraenv
  • ORACLE_SID = [oracle] ? +ASM
  • SQL>ツsqlplus / as sysasm
  • SQL>ツalter system set memory_max_target=0 scope=spfile sid=窶*窶;
  • SQL>ツalter system set memory_target=0 scope=spfile sid=窶*窶;
  • SQL>ツalter system set sga_target=1088M scope=spfile sid=窶*窶;
  • SQL>ツalter system set use_large_pages=窶儖NLY窶 scope=spfile sid=窶*窶;
  • SQL>ツshutdown immediate;
  • SQL>ツstartup;
  • SQL>ツquit
  • . oraenv
  • ORACLE_SID = [oracle] ? MYDB001
  • SQL>ツsqlplus / as sysdba
  • SQL>ツstartup

Step-By-Step 窶 Oracle Database Binary Install

1. Log on to Oracle

2. Unset variables

  • unset ORACLE_BASE
  • unset ORACLE_HOME
  • unset GRID_HOME
  • unset ORACLE_SID
  • unset TNS_ADMIN

3. Install Database Software

  • cd /u01/app/oracle/SOFTWARE/database
  • ./runInstaller

4. Follow the instructions as detailed in theツscreenshots hereツand when prompted run root.sh.

  • cd /u01/app/oracle/product/12.1.0/dbhome_1
  • ./root.sh

5. Create a symbolic link for TNS directory entries to stop dbca from failing on DB creation and on crsct startup.

  • cd /u01/app/oracle/product/12.1.0/dbhome_1/network/admin
  • ln -s /u01/app/oracle/product/12.1.0/grid/network/admin/tnsnames.ora
  • ln -s /u01/app/oracle/product/12.1.0/grid/network/admin/sqlnet.ora
  • ln -s /u01/app/oracle/product/12.1.0/grid/network/admin/listener.ora

Step-By-Step 窶 Oracle Database Creation

1. Log on to Oracle

2. Create the database using dbca

  • cd /u01/app/oracle/product/12.1.0/dbhome_1/bin
  • ./dbca

3. Follow the instructions as detailed in theツscreenshots here


Step-By-Step 窶 Grid and Database Patching

1. Log on as Oracle

2. Install the latest version of OPatch in the GI home and DB home

  • unzip p6880880_121010_Linux-x86-64.zip -d /u01/app/oracle/product/12.1.0/grid
  • unzip p6880880_121010_Linux-x86-64.zip -d /u01/app/oracle/product/12.1.0/dbhome_1

3. Check the version of OPatch

  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/grid
  • $ORACLE_HOME/OPatch/opatch version
  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
  • $ORACLE_HOME/OPatch/opatch version

4. Validate the oraInventory

  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/grid
  • $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh /u01/app/oracle/product/12.1.0/grid
  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
  • $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh /u01/app/oracle/product/12.1.0/dbhome_1

5. Log on as root

6. Create a Grid OCM response file

  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/grid
  • $ORACLE_HOME/OPatch/ocm/bin/emocmrsp -no_banner -output /tmp/GI_ocm.rsp
    • Press return when prompted for an email
    • Answer 窶弸es窶 to remain uninformed of updates

7. Analyze the patch for conflicts with other patches already installed

  • $ORACLE_HOME/OPatch/opatchauto apply /u01/app/oracle/SOFTWARE/20996835 -analyze -ocmrf /tmp/GI_ocm.rsp

8. Patch the Grid Infrastructure home and the Database Home

  • $ORACLE_HOME/OPatch/opatchauto apply /u01/app/oracle/SOFTWARE/20996835 -ocmrf /tmp/GI_ocm.rsp

Step-By-Step 窶 Database Configuration (Optional and Site Specific)

1. Log on as Oracle

2. Set some database options and rename the spfile in ASM

  • . oraenv
  • ORACLE_SID = [oracle] ? MYDB001
  • SQL>ツsqlplus / as sysdba
  • SQL>ツalter database flashback on;
  • SQL>ツalter database force logging;
  • SQL>ツalter system set cursor_sharing=force scope=spfile sid=窶*';
  • SQL>ツalter system set control_file_record_keep_time =14 scope=spfile sid=窶*窶;
  • SQL>ツalter system set use_large_pages =窶儖NLY窶 scope=spfile sid=窶*窶;
  • SQL>ツBEGIN;
  • SQL>ツexec dbms_auto_task_admin.disable(
  • SQL>ツclient_name => 窶和uto optimizer stats collection窶, operation => NULL, window_name => NULL);
  • SQL>ツEND;
  • SQL>ツ/
  • SQL>ツcreate pfile=窶/tmp/temporary.ora窶 from spfile;
  • SQL>ツshutdown immediate;
  • SQL>ツstartup pfile=窶/tmp/temporary.ora窶
  • SQL>ツcreate spfile=窶+DATA01/MYDB001/spfileMYDB001.ora窶 from pfile=窶/tmp/temporary.ora窶
  • SQL>ツshutdown immediate
  • SQL>ツquit
  • rm /tmp/temporary.ora
  • cd $ORACLE_HOME/dbs
  • echo 窶+DATA01/MYDB001/spfileMYDB001.ora窶 > initMYDB001.ora
  • sqlplus / as sysdba
  • SQL>ツstartup
  • SQL>ツshow parameter spfile
  • Check the new spfile has been picked up
  • SQL>ツquit
  • rman
  • RMAN>ツconnect target /
  • RMAN>ツconfigure controlfile autobackup on;
  • RMAN>ツquit

3. Implement DCD on the databases.

  • cd $TNS_ADMIN
  • vi sqlnet.ora
  • Add the following line to the sqlnet.ora file.
  • SQLNET.EXPIRE_TIME = 10

Security Compliance (Recommended, but optional)

The following steps should be performed once the database has been built to ensure that the environment conforms to Oracle's Best Practices and also ensures that it doesn't fall foul of Internal Audit.

1. Remove theツGRANT EXECUTE TO PUBLICツprivilege from potentially harmful packages.

  • sqlplus '/ as sysdba'
  • SQL>ツrevoke execute on utl_file from public;
  • SQL>ツrevoke execute on dbms_random from public;
  • SQL>ツrevoke execute on utl_http from public;
  • SQL>ツrevoke execute on utl_smtp from public;
  • SQL>ツrevoke execute on utl_tcp from public;
  • SQL>ツexit

2. Ensure the following user-ids' passwords, where applicable, have been changed:

  • SYS
  • SYSTEM
  • DBSNMP
  • OUTLN
  • CTXSYS
  • PERFSTAT

3. Adjust the databaseツDEFAULT TABLESPACEツsettings so that theツSYSTEMツtablespace is not used inappropriately.

  • sqlplus '/ as sysdba'
  • SQL>ツalter database default tablespace users;
  • SQL>ツalter user sys default tablespace system;
  • SQL>ツalter user system default tablespace system;

4. Correct any users that already haveツSYSTEMツas theirツDEFAULT TABLESPACE

  • sqlplus '/ as sysdba'
  • SQL>ツselect username, default_tablespace from dba_users where default_tablespace = 'SYSTEM';
  • SQL>ツalter user <user name> default tablespace <non-SYSTEM tablespace>;
  • SQL>ツexit

5. Lock and expire potentially harmful built-in user-ids.

  • sqlplus '/ as sysdba'
  • SQL>ツalter user &user_idpassword expire account lock;
    • Repeat for each user as required.
  • SQL>ツexit

Regression

To restore the environment back to its initial state, perform the following

1. Shutdown the environment

2. Remove all database files, binaries, trace files and administration logs using theツdeinstallツtool - seeDeinstall Sectionツbelow.


File Listings

oracle .profile

#----------------------------------------------------------------------
# Configure Terminal Settings.
#----------------------------------------------------------------------

stty susp ^Z
stty quit ^C
stty erase ^?
export ORACLE_TERM=vt100

#----------------------------------------------------------------------
# Configure Shell Settings.
#----------------------------------------------------------------------

set -o vi
export PATH=/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/ccs/bin:$PATH
export EDITOR=vi
export HOSTNAME=`hostname`
export PS1='$LOGNAME@$HOSTNAME:$ORACLE_SID> '
export TMPDIR=/tmp
export TEMP=/tmp
export TMOUT=7200
umask 022

#----------------------------------------------------------------------
# Configure Aliases.
#----------------------------------------------------------------------

alias ll="ls -la"
alias lt="ls -lrt|tail"
alias bdf="df -h"

#----------------------------------------------------------------------
# Configure Oracle Settings.
#----------------------------------------------------------------------

export ORACLE_BASE=/u01/app/oracle
export SQLPATH=$ORACLE_BASE/DBA/SQL
export ORACLE_HOME=$ORACLE_BASE/product/12.1.0/dbhome_1
export OPATCH_LIB=/u01/app/oracle/SOFTWARE/OPATCH/OPatch
export PATH=$ORACLE_HOME/bin:$PATH:$OPATCH_LIB
export GRID_HOME==$ORACLE_BASE/product/12.1.0/grid
export TNS_ADMIN=$GRID_HOME/network/admin

oratab

MYDB001:/u01/app/oracle/product/12.1.0/dbhome_1:Y
+ASM1:/u01/app/oracle/product/12.1.0/grid:N

File Systems

--- /u01 --- /app --- /oraInventory
|aaaaaaaaaaaaaa|
|aaaaaaaaaaaaaa--- /oracle --- /software
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /dba --- /scripts
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa|aaaaaaa--- /sql
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /diag
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /product ---/12.1.0 ---/dbhome_1
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /product ---/12.1.0 ---/grid
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /admin --- /SID --- /adump
|aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa--- /pfile


Example GRID Infrastructure Install

12c_GridInfra_001.jpg

  • SelectツInstall and Configure Grid Infrastructure for a Standalone Server
  • ClickツNext

12c_GridInfra_002a.jpg

  • Select the languages you require. In this instance all languages have been chosen.
  • ClickツNext

12c_GridInfra_003.jpg

  • SetツDisk group nameツtoツDATA01
  • SetツAllocation Unit Sizeツtoツ4MB
  • ClickツChange Discovery Path

12c_GridInfra_004.jpg

  • SetツDisk Discovery Pathツtoツ/dev/asmツ(or to the path of your ASM LUNs)
  • ClickツOK

12c_GridInfra_005.jpg

  • Ensure the radial buttonツCandidate Disksツis selected.
  • Select the disks you want added to disk groupツDATA01ツby ticking the box.
  • ClickツNext

12c_GridInfra_006.jpg

  • Select the radial buttonツUse same passwords for these accounts
  • The passwords can be changed to something more suitable later.
  • ClickツNext

12c_GridInfra_007.jpg

  • If presented with this screen clickツYes
  • As mentioned above, the passwords can be changed to something more suitable later

12c_GridInfra_008.jpg

  • For this installation no Grid Agent is going to be configured.
  • ClickツNEXT

12c_GridInfra_009.jpg

  • In this installation the same OS group is going to be used. This may not be suitable for all environments.
  • SetツOracle ASM Administrator (OSASM) Groupツtoツdba
  • SetツOracle ASM DBA (OSDBA for ASM) Groupツtoツdba
  • SetツOracle ASM Operator (OSOPER for ASM) Group (Optional)ツtoツdba
  • ClickツNext

12c_GridInfra_010.jpg

  • If this is okay for the environment being built, clickツYES

12c_GridInfra_011.jpg

  • EnsureツOracle baseツis set toツ/u01/app/oracle
  • EnsureツSoftware locationツis set toツ/u01/app/oracle/product/12.1.0/grid
  • The fields should already be populated with the above values.
  • They can be changed, but it is recommended to keep the defaults.
  • ClickツNext

12c_GridInfra_012.jpg

  • EnsureツInventory Directoryツis set toツ/u01/app/oraInventory
  • The field should already be populated with the value above.
  • TheツInventory Directoryツcan be changed, but it is recommended to keep the defaults.
  • ClickツFinish

12c_GridInfra_013.jpg

  • In this environment theツrootツpassword is known, so configuration scripts will be run automatically.
  • TickツAutomatically run configuration scripts
  • Select the radial buttonツUse "root" user credential
  • Ensure theツPasswordツis set
  • ClickツNext

12c_GridInfra_014.jpg

  • Wait for the verification process to complete.
  • This screen will move on automatically.

12c_GridInfra_015.jpg

  • For demonstration purposes, this installation has some issues.
  • TheツFix & Check Againツbutton can be used to fix any issues.
  • Note that not all issues can be fixed and it may be necessary to refer the issues to a Unix Administrator
  • ClickツCheck Againツwhen all issues have been resolved.

12c_GridInfra_016.jpg

  • Review this screen and clickツInstall
  • At this point aツResponse Fileツcan be saved by clickingツSave Response File窶ヲ
  • A response file can be used for automated deployments.

12c_GridInfra_017.jpg

  • Wait for the installation to complete.
  • This screen will move on automatically.

12c_GridInfra_018.jpg

  • ClickツClose

Example Database Binary Install

12c_DBInstall_001.jpg

  • Un-tick theツI wish to receive security updates via My Oracle Supportツbox.
    • NBツThis is site specific and should be reviewed.
  • ClickツNext.

12c_DBInstall_002.jpg

  • ClickツYesツto remain uninformed.

12c_DBInstall_003.jpg

  • SelectツInstall database software only
  • ClickツNext.

12c_DBInstall_004.jpg

  • EnsureツSingle instance database installationツis selected.
  • ClickツNext.

12c_DBInstall_005.jpg

  • Select the languages you require. In this instance all languages have been chosen.
  • ClickツNext

12c_DBInstall_006.jpg

  • SetツDatabase editionツtoツEnterprise Edition (6.4GB)
  • ClickツNext

12c_DBInstall_007.jpg

  • EnsureツOracle baseツis set toツ/u01/app/oracle
  • EnsureツSoftware locationツis set toツ/u01/app/oracle/product/12.1.0/dbhome_1
  • The fields should already be populated with the above values.
  • They can be changed, but it is recommended to keep the defaults.
  • ClickツNext

12c_DBInstall_008.jpg

  • In this installation different OS groups will be used. Optional groups will be left blank.
  • This may not be suitable for all environments.
  • SetツDatabase Administrator (OSDBA) Groupツtoツdba
  • LeaveツDatabase Operator (OSOPER) Group (Optional)ツblank.
  • SetツDatabase Backup and Recovery (OSBACKUPDBA) Groupツtoツbckpdba
  • SetツData Guard administrative (OSDGDBA) Groupツtoツdgdba
  • SetツEncryption Key Management administrative (OSKMDBA) Groupツtoツkmdba
  • ClickツNext

12c_DBInstall_009.jpg

  • Wait for the verification process to complete.
  • This screen moves on automatically when complete.

12c_DBInstall_010.jpg

  • For demonstration purposes, this installation has some issues.
  • TheツFix & Check Againツbutton can be used to fix any issues.
  • Note that not all issues can be fixed and it may be necessary to refer the issues to a Unix Administrator
  • ClickツCheck Againツwhen all issues have been resolved.

12c_DBInstall_011.jpg

  • Review this screen and clickツInstall
  • At this point aツResponse Fileツcan be saved by clickingツSave Response File窶ヲ
  • A response file can be used for automated deployments.

12c_DBInstall_012.jpg

  • Wait for the installation process to complete.
  • This screen will move on automatically.

12c_DBInstall_013.jpg

  • Get a UNIX administrator to run theツConfiguration Scriptsツas theツrootツuser.
  • ClickツOKツwhen theツConfiguration Scriptsツhave completed successfully.

12c_DBInstall_014.jpg

  • ClickツClose

Example Database Creation

12c_Create_001.jpg

  • SelectツCreate Database
  • ClickツNext.

12c_Create_002.jpg

  • SelectツAdvanced Mode.
  • ClickツNext.

12c_Create_003.jpg

  • SelectツGeneral Purpose or Transaction Processing.
  • ClickツNext.

12c_Create_004.jpg

  • SetツGlobal Database NameツtoツMYDB001.MYDOMAIN.COM
  • EnsureツSIDツhas been populated withツMYDB001
  • ClickツNext.

12c_Create_005.jpg

  • For this installation no Grid Agent is going to be configured.
  • ClickツNext

12c_Create_006.jpg

Set and confirm the passwords for theツSYSツandツSYSTEMツuser.
ClickツNext


12c_Create_007.jpg

  • For this database, theツGRIDツlistener will be used. This may not be suitable for all environments.
  • Tick the box alongsideツLISTENER
  • ClickツNext

12c_Create_008.jpg

  • EnsureツDatabase files Storage Typeツis set toツAutomatic Storage Management (ASM)
  • SelectツUse Common Location for All Database Files
  • SetツFile Locationツtoツ+DATA01
  • TickツUse Oracle-Managed Files
  • EnsureツRecovery files Storage Typeツis set toツAutomatic Storage Management (ASM)
  • TickツSpecify Fast Recovery Area
  • SetツFast Recovery Areaツtoツ+FRA01
  • Set theツFast Recovery Area Sizeツto a suitable value
  • TickツEnable Archiving
  • ClickツMultiplex Redo Logs and Control Files窶ヲ

12c_Create_009.jpg

  • SetツLocation 1ツtoツ+REDO01
  • SetツLocation 2ツtoツ+REDO02
  • ClickツOK

12c_Create_010.jpg

  • ClickツNext

12c_Create_011.jpg

  • In this installationツSample SchemasツandツDatabase Vault & Label Securityツwill be left as default.
  • ClickツNext.

12c_Create_012.jpg

  • For this installationツAutomatic Shared Memory Managementツwill be used.
  • SetツSGA SizeツandツPGA Sizeツto suitable values.
  • Click theツSizingツtab.

12c_Create_013.jpg

  • Set theツProcessesツvalue to a suitable number for the environment.
  • Click theツCharacter Setsツtab.

12c_Create_014a.jpg

  • These settings are dependent on the environment being built.
  • SelectツUse Unicode (AL32UTF8)ツ- Most systems would use this value.
  • SetツNational Character SetツtoツUTF8 - Unicode 3.0 UTF-8 Universal character set, CESU-8 compliantツ- Most systems would use this value.
  • Set aツDefault Language
  • Set aツDefault Territory
  • Click theツConnection Modeツtab.

12c_Create_015.jpg

  • SelectツDedicated Server Mode
  • ClickツAll Initialization Parameters...

12c_Create_016.jpg

  • ClickツShow Advanced Parameters

12c_Create_017.jpg

  • Set theツInitialization Parametersツappropriately.
  • In this installation the following parameters have been set in the DBCA GUI
  • control_filesツhave been set to useツ+DATA01ツandツ+FRA01
  • db_create_online_log_dest_1ツhas be set to useツ+REDO01
  • db_create_online_log_dest_2ツhas be set to useツ+REDO02
  • ClickツClose

12c_Create_018.jpg

  • ClickツNext.

12c_Create_019.jpg

  • ClickツCustomize Storage Locations窶ヲ

12c_Create_019b.jpg

  • Add additionalツREDOツlogs if required.
  • ClickツOk

12c_Create_019c.jpg

  • TickツCreate Database
  • If required at this point, aツDatabase Templateツcan be created by tickingツSave as Database Template
  • Set aツNameツfor theツDatabase Templateツif theツSave as Database Templateツbox has been ticked.
  • The database creation scripts can be created by tickingツGenerate Database Creation Scripts
  • ClickツNext

12c_Create_020.jpg

  • Review the summary page
  • ClickツFinish

12c_Create_021.jpg

  • This screen will move on automatically.

12c_Create_022.jpg

  • Set-up the passwords by clicking onツPassword Managementツif required.
  • ClickツClose.

Other References

  • None Currently

Known Issues

  • None Currently

Deinstalling Oracle 12g Binaries and Database

Withツ12.1ツthe deinstallation tool is located in the Oracle home directory after installation.

Step-by-Step

1. Run this tool fromツORACLE_HOMEツfirst.

  • cd $ORACLE_HOME/deinstall
  • ./deinstall
  • When prompted for the database name enter theツSIDツyou want to remove.
    • NBツThis will remove the database binaries too.
  • When askedツDo you still want to modify the details of SID database(s)? [n]:AnswerツN
    • NBツYou would answerツYツif you wanted to amend the database configuration.
  • The tool should now complete okay after performing several tasks.

2. Now run the tool from theツGRID_HOME.

Background & Overview

The following documentation provides instructions for building an Oracle 12c database with ASM residing on RedHat (Version 6.7, Kernel version 2.6.32). Use the commandツcat /etc/*release*ツto check the Oracle Linux OS version andツuname -rツto check the Kernel level.

Further reference documentation about Oracle 12c and Oracle Linux is detailed in theOther Referencesツsection below.

Assumptions

This document expects and assumes the following:

  • The instructions are carried out by a qualified DBA.
  • All necessary client software, e.g. Telnet and X-Server is available.
  • All references toツSIDツshould be replaced with correct database name as derived using a suitable database naming standard.
  • Allツ$variableツreferences assume theツ.profileツas described in theツFile Listingsツsection has been implemented and run.

Useful Information

Software

File Name Description Byte Count MD5 Hash
linuxamd64_12102_database_1of2.zip Database Binaries File 1 1673544724 080435a40bd4c8dff6399b231a808e9a
linuxamd64_12102_database_2of2.zip Database Binaries File 2 1014530602 30f20ef9437442b8282ce3984546c982
linuxamd64_12102_grid_1of2.zip Grid Infrastructure Binaries File 1 1747043545 d793c2ba5db9008b79077bff8d27a219
linuxamd64_12102_grid_2of2.zip Grid Infrastructure Binaries File 2 646972897 0e18a9abb80427baf18f85865b1ecd5d
p20996835_121020_Linux-x86-64 Grid Infrastructure and DB PSU 1031691784 F32C00880F4311A20D6D2174ABE95C38
p6880880_121010_Linux-x86-64 OPatch Version 12.1.0.1.8 52853599 f3978f9d719f8f345ca8cca386683a59

Step-By-Step Guide - Pre-Requisites

1. Ensure theツOracle Linuxツversion isツ6ツor higher.

  • cat /etc/*release*

2. Ensure theツOracle LinuxツKernel version for both nodes isツ2.6.18ツor higher.

  • uname -r

3. As a minimum ensureツRedHatツhas the following packages installed on both nodes.

unzip (x86_64)
xorg-x11-utils-7.5-6.el6.x86_64
binutils-2.20.51.0.2-5.11.el6 (x86_64)
compat-libcap1-1.10-1 (x86_64)
compat-libstdc++-33-3.2.3-69.el6 (x86_64)
compat-libstdc++-33-3.2.3-69.el6 (i686)
gcc-4.4.4-13.el6 (x86_64)
gcc-c++-4.4.4-13.el6 (x86_64)
glibc-2.12-1.7.el6 (i686)
glibc-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6 (x86_64)
glibc-devel-2.12-1.7.el6 (i686)
ksh
libgcc-4.4.4-13.el6 (i686)
libgcc-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6 (x86_64)
libstdc++-4.4.4-13.el6 (i686)
libstdc++-devel-4.4.4-13.el6 (x86_64)
libstdc++-devel-4.4.4-13.el6 (i686)
libaio-0.3.107-10.el6 (x86_64)
libaio-0.3.107-10.el6 (i686)
libaio-devel-0.3.107-10.el6 (x86_64)
libaio-devel-0.3.107-10.el6 (i686)
libXext-1.1 (x86_64)
libXext-1.1 (i686)
libXtst-1.0.99.2 (x86_64)
libXtst-1.0.99.2 (i686)
libX11-1.3 (x86_64)
libX11-1.3 (i686)
libXau-1.0.5 (x86_64)
libXau-1.0.5 (i686)
libxcb-1.5 (x86_64)
libxcb-1.5 (i686)
libXi-1.3 (x86_64)
libXi-1.3 (i686)
make-3.81-19.el6
sysstat-9.0.4-11.el6 (x86_64)

4. Set the kernel parameters inツ/etc/sysctl.confツfor both nodes as follows.ツNOTEツIf the current value for any parameter is higher than the value listed below, do not change the value of that parameter.

shmmax - Half the server memory
shmmni - 4096 (or greater)
fs.file-max - 6815744 (or greater)
fs.aio-max-nr - 1048576 (or greater)
net.core.rmem_default - 262144 (or greater)
net.core.rmem_max - 4194304 or greater)
net.core.wmem_default - 262144 (or greater)
net.core.wmem_max - 1048576 (or greater)
sem - 250ツ32000ツ100ツ128 (or greater)
net.ipv4.ip_local_port_range - 9000ツ65535

5. Ensureツoracleツaccount andツdbaツgroup exists on both nodes.

6. Update the following fileツ/etc/security/limits.confツon both nodes.

oracle soft nproc 16384
oracle hard nproc 16384
oracle soft nofile 20480
oracle hard nofile 65536
oracle soft stack 10240
oracle hard stack 32768

7. Ensure the following line in theツ/etc/pam.d/loginツfile existis on both nodes.

session required pam_limits.so

8. Create theツ.profileツ- seeツFile Listingsツsection below.

9. InstallツASMLIB.

10. Create a single partition on each device to be used byツASM.

11. Create theツASMツdisks. For this installation the following disks will need to be created.

  • asm-data01
  • asm-fra01
  • asm-redo01
  • asm-redo02

12. Check to confirm the disk are set-up correctly

  • /usr/sbin/oracleasm listdisks

13. Unzip the files

  • Log on as Oracle
  • cd /u01/app/oracle/SOFTWARE
  • unzip linuxamd64_12102_database_1of2.zip
  • unzip linuxamd64_12102_database_2of2.zip
  • unzip linuxamd64_12102_grid_1of2.zip
  • unzip linuxamd64_12102_grid_2of2.zip
  • unzip p6880880_121010_Linux-x86-64
  • unzip p20996835_121020_Linux-x86-64

Step-By-Step Guide - ASM Binary Installs

1. Log on to Oracle.

2. Unset ORACLE_HOME and GRID_HOME

  • unset ORACLE_HOME
  • unset GRID_HOME
  • unset ORACLE_SID
  • unset TNS_ADMIN

3. Install Grid Infrastructure Using the GUI

  • cd /u01/app/oracle/SOFTWARE/grid
  • ./runInstaller

4. Follow the instructions as detailed in theツscreenshots here

5. When prompted run the root scripts in the order specified

  • Log on as root
  • /u01/app/oraInventory/orainstRoot.sh
  • /u01/app/oracle/product/12.1.0/grid/root.sh

Step-By-Step Guide - Configure ASM

1. Create the extra Disk Groups

  • . oraenv
  • ORACLE_SID = [oracle] ? +ASM
  • sqlplus / as sysasm
  • SQL>ツCREATE DISKGROUP FRA01 EXTERNAL REDUNDANCY DISK 窶/dev/asm-fra001窶イ ATTRIBUTE 窶呂OMPATIBLE.ASM窶=窶12.1.0.0.0窶イ,窶僂OMPATIBLE.RDBMS窶=窶12.1.0.0.0窶イ,窶僊U_SIZE窶=窶4M';
  • SQL>ツCREATE DISKGROUP REDO01 EXTERNAL REDUNDANCY DISK 窶/dev/asm-redo001窶イ ATTRIBUTE 窶呂OMPATIBLE.ASM窶=窶12.1.0.0.0窶イ,窶僂OMPATIBLE.RDBMS窶=窶12.1.0.0.0窶イ,窶僊U_SIZE窶=窶4M';
  • SQL>ツCREATE DISKGROUP REDO02 EXTERNAL REDUNDANCY DISK 窶/dev/asm-redo002窶イ ATTRIBUTE 窶呂OMPATIBLE.ASM窶=窶12.1.0.0.0窶イ,窶僂OMPATIBLE.RDBMS窶=窶12.1.0.0.0窶イ,窶僊U_SIZE窶=窶4M';

2. Update parameter file with new Diskgroups

  • SQL>ツALTER SYSTEM SET ASM_DISKGROUPS=窶僥RA01窶イ, 窶漏EDO01窶イ, 窶漏EDO02窶イ SCOPE=BOTH SID=窶+ASM窶

3. Configure ASM to use huge pages

  • . oraenv
  • ORACLE_SID = [oracle] ? MYDB001
  • SQL>ツsqlplus / as sysdba
  • SQL>ツshutdown immediate;
  • SQL>ツquit
  • . oraenv
  • ORACLE_SID = [oracle] ? +ASM
  • SQL>ツsqlplus / as sysasm
  • SQL>ツalter system set memory_max_target=0 scope=spfile sid=窶*窶;
  • SQL>ツalter system set memory_target=0 scope=spfile sid=窶*窶;
  • SQL>ツalter system set sga_target=1088M scope=spfile sid=窶*窶;
  • SQL>ツalter system set use_large_pages=窶儖NLY窶 scope=spfile sid=窶*窶;
  • SQL>ツshutdown immediate;
  • SQL>ツstartup;
  • SQL>ツquit
  • . oraenv
  • ORACLE_SID = [oracle] ? MYDB001
  • SQL>ツsqlplus / as sysdba
  • SQL>ツstartup

Step-By-Step 窶 Oracle Database Binary Install

1. Log on to Oracle

2. Unset variables

  • unset ORACLE_BASE
  • unset ORACLE_HOME
  • unset GRID_HOME
  • unset ORACLE_SID
  • unset TNS_ADMIN

3. Install Database Software

  • cd /u01/app/oracle/SOFTWARE/database
  • ./runInstaller

4. Follow the instructions as detailed in theツscreenshots hereツand when prompted run root.sh.

  • cd /u01/app/oracle/product/12.1.0/dbhome_1
  • ./root.sh

5. Create a symbolic link for TNS directory entries to stop dbca from failing on DB creation and on crsct startup.

  • cd /u01/app/oracle/product/12.1.0/dbhome_1/network/admin
  • ln -s /u01/app/oracle/product/12.1.0/grid/network/admin/tnsnames.ora
  • ln -s /u01/app/oracle/product/12.1.0/grid/network/admin/sqlnet.ora
  • ln -s /u01/app/oracle/product/12.1.0/grid/network/admin/listener.ora

Step-By-Step 窶 Oracle Database Creation

1. Log on to Oracle

2. Create the database using dbca

  • cd /u01/app/oracle/product/12.1.0/dbhome_1/bin
  • ./dbca

3. Follow the instructions as detailed in theツscreenshots here


Step-By-Step 窶 Grid and Database Patching

1. Log on as Oracle

2. Install the latest version of OPatch in the GI home and DB home

  • unzip p6880880_121010_Linux-x86-64.zip -d /u01/app/oracle/product/12.1.0/grid
  • unzip p6880880_121010_Linux-x86-64.zip -d /u01/app/oracle/product/12.1.0/dbhome_1

3. Check the version of OPatch

  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/grid
  • $ORACLE_HOME/OPatch/opatch version
  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
  • $ORACLE_HOME/OPatch/opatch version

4. Validate the oraInventory

  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/grid
  • $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh /u01/app/oracle/product/12.1.0/grid
  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/dbhome_1
  • $ORACLE_HOME/OPatch/opatch lsinventory -detail -oh /u01/app/oracle/product/12.1.0/dbhome_1

5. Log on as root

6. Create a Grid OCM response file

  • export ORACLE_HOME=/u01/app/oracle/product/12.1.0/grid
  • $ORACLE_HOME/OPatch/ocm/bin/emocmrsp -no_banner -output /tmp/GI_ocm.rsp
    • Press return when prompted for an email
    • Answer 窶弸es窶 to remain uninformed of updates

7. Analyze the patch for conflicts with other patches already installed

  • $ORACLE_HOME/OPatch/opatchauto apply /u01/app/oracle/SOFTWARE/20996835 -analyze -ocmrf /tmp/GI_ocm.rsp

8. Patch the Grid Infrastructure home and the Database Home

  • $ORACLE_HOME/OPatch/opatchauto apply /u01/app/oracle/SOFTWARE/20996835 -ocmrf /tmp/GI_ocm.rsp

Step-By-Step 窶 Database Configuration (Optional and Site Specific)

1. Log on as Oracle

2. Set some database options and rename the spfile in ASM

  • . oraenv
  • ORACLE_SID = [oracle] ? MYDB001
  • SQL>ツsqlplus / as sysdba
  • SQL>ツalter database flashback on;
  • SQL>ツalter database force logging;
  • SQL>ツalter system set cursor_sharing=force scope=spfile sid=窶*';
  • SQL>ツalter system set control_file_record_keep_time =14 scope=spfile sid=窶*窶;
  • SQL>ツalter system set use_large_pages =窶儖NLY窶 scope=spfile sid=窶*窶;
  • SQL>ツBEGIN;
  • SQL>ツexec dbms_auto_task_admin.disable(
  • SQL>ツclient_name => 窶和uto optimizer stats collection窶, operation => NULL, window_name => NULL);
  • SQL>ツEND;
  • SQL>ツ/
  • SQL>ツcreate pfile=窶/tmp/temporary.ora窶 from spfile;
  • SQL>ツshutdown immediate;
  • SQL>ツstartup pfile=窶/tmp/temporary.ora窶
  • SQL>ツcreate spfile=窶+DATA01/MYDB001/spfileMYDB001.ora窶 from pfile=窶/tmp/temporary.ora窶
  • SQL>ツshutdown immediate
  • SQL>ツquit
  • rm /tmp/temporary.ora
  • cd $ORACLE_HOME/dbs
  • echo 窶+DATA01/MYDB001/spfileMYDB001.ora窶 > initMYDB001.ora
  • sqlplus / as sysdba
  • SQL>ツstartup
  • SQL>ツshow parameter spfile
  • Check the new spfile has been picked up
  • SQL>ツquit
  • rman
  • RMAN>ツconnect target /
  • RMAN>ツconfigure controlfile autobackup on;
  • RMAN>ツquit

3. Implement DCD on the databases.

  • cd $TNS_ADMIN
  • vi sqlnet.ora
  • Add the following line to the sqlnet.ora file.
  • SQLNET.EXPIRE_TIME = 10

Security Compliance (Recommended, but optional)

The following steps should be performed once the database has been built to ensure that the environment conforms to Oracle's Best Practices and also ensures that it doesn't fall foul of Internal Audit.

1. Remove theツGRANT EXECUTE TO PUBLICツprivilege from potentially harmful packages.

  • sqlplus '/ as sysdba'
  • SQL>ツrevoke execute on utl_file from public;
  • SQL>ツrevoke execute on dbms_random from public;
  • SQL>ツrevoke execute on utl_http from public;
  • SQL>ツrevoke execute on utl_smtp from public;
  • SQL>ツrevoke execute on utl_tcp from public;
  • SQL>ツexit

2. Ensure the following user-ids' passwords, where applicable, have been changed:

  • SYS
  • SYSTEM
  • DBSNMP
  • OUTLN
  • CTXSYS
  • PERFSTAT

3. Adjust the databaseツDEFAULT TABLESPACEツsettings so that theツSYSTEMツtablespace is not used inappropriately.

  • sqlplus '/ as sysdba'
  • SQL>ツalter database default tablespace users;
  • SQL>ツalter user sys default tablespace system;
  • SQL>ツalter user system default tablespace system;

4. Correct any users that already haveツSYSTEMツas theirツDEFAULT TABLESPACE

  • sqlplus '/ as sysdba'
  • SQL>ツselect username, default_tablespace from dba_users where default_tablespace = 'SYSTEM';
  • SQL>ツalter user <user name> default tablespace <non-SYSTEM tablespace>;
  • SQL>ツexit

5. Lock and expire potentially harmful built-in user-ids.

  • sqlplus '/ as sysdba'
  • SQL>ツalter user &user_idpassword expire account lock;
    • Repeat for each user as required.
  • SQL>ツexit

Regression

To restore the environment back to its initial state, perform the following

1. Shutdown the environment

2. Remove all database files, binaries, trace files and administration logs using theツdeinstallツtool - seeDeinstall Sectionツbelow.


File Listings

oracle .profile

#----------------------------------------------------------------------
# Configure Terminal Settings.
#----------------------------------------------------------------------

stty susp ^Z
stty quit ^C
stty erase ^?
export ORACLE_TERM=vt100

#----------------------------------------------------------------------
# Configure Shell Settings.
#----------------------------------------------------------------------

set -o vi
export PATH=/bin:/usr/sbin:/usr/bin:/usr/local/bin:/usr/ccs/bin:$PATH
export EDITOR=vi
export HOSTNAME=`hostname`
export PS1='$LOGNAME@$HOSTNAME:$ORACLE_SID> '
export TMPDIR=/tmp
export TEMP=/tmp
export TMOUT=7200
umask 022

#----------------------------------------------------------------------
# Configure Aliases.
#----------------------------------------------------------------------

alias ll="ls -la"
alias lt="ls -lrt|tail"
alias bdf="df -h"

#----------------------------------------------------------------------
# Configure Oracle Settings.
#----------------------------------------------------------------------

export ORACLE_BASE=/u01/app/oracle
export SQLPATH=$ORACLE_BASE/DBA/SQL
export ORACLE_HOME=$ORACLE_BASE/product/12.1.0/dbhome_1
export OPATCH_LIB=/u01/app/oracle/SOFTWARE/OPATCH/OPatch
export PATH=$ORACLE_HOME/bin:$PATH:$OPATCH_LIB
export GRID_HOME==$ORACLE_BASE/product/12.1.0/grid
export TNS_ADMIN=$GRID_HOME/network/admin

oratab

MYDB001:/u01/app/oracle/product/12.1.0/dbhome_1:Y
+ASM1:/u01/app/oracle/product/12.1.0/grid:N

File Systems

--- /u01 --- /app --- /oraInventory
|aaaaaaaaaaaaaa|
|aaaaaaaaaaaaaa--- /oracle --- /software
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /dba --- /scripts
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa|aaaaaaa--- /sql
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /diag
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /product ---/12.1.0 ---/dbhome_1
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /product ---/12.1.0 ---/grid
|aaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaa--- /admin --- /SID --- /adump
|aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa|
|aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa--- /pfile


Example GRID Infrastructure Install

12c_GridInfra_001.jpg

  • SelectツInstall and Configure Grid Infrastructure for a Standalone Server
  • ClickツNext

12c_GridInfra_002a.jpg

  • Select the languages you require. In this instance all languages have been chosen.
  • ClickツNext

12c_GridInfra_003.jpg

  • SetツDisk group nameツtoツDATA01
  • SetツAllocation Unit Sizeツtoツ4MB
  • ClickツChange Discovery Path

12c_GridInfra_004.jpg

  • SetツDisk Discovery Pathツtoツ/dev/asmツ(or to the path of your ASM LUNs)
  • ClickツOK

12c_GridInfra_005.jpg

  • Ensure the radial buttonツCandidate Disksツis selected.
  • Select the disks you want added to disk groupツDATA01ツby ticking the box.
  • ClickツNext

12c_GridInfra_006.jpg

  • Select the radial buttonツUse same passwords for these accounts
  • The passwords can be changed to something more suitable later.
  • ClickツNext

12c_GridInfra_007.jpg

  • If presented with this screen clickツYes
  • As mentioned above, the passwords can be changed to something more suitable later

12c_GridInfra_008.jpg

  • For this installation no Grid Agent is going to be configured.
  • ClickツNEXT

12c_GridInfra_009.jpg

  • In this installation the same OS group is going to be used. This may not be suitable for all environments.
  • SetツOracle ASM Administrator (OSASM) Groupツtoツdba
  • SetツOracle ASM DBA (OSDBA for ASM) Groupツtoツdba
  • SetツOracle ASM Operator (OSOPER for ASM) Group (Optional)ツtoツdba
  • ClickツNext

12c_GridInfra_010.jpg

  • If this is okay for the environment being built, clickツYES

12c_GridInfra_011.jpg

  • EnsureツOracle baseツis set toツ/u01/app/oracle
  • EnsureツSoftware locationツis set toツ/u01/app/oracle/product/12.1.0/grid
  • The fields should already be populated with the above values.
  • They can be changed, but it is recommended to keep the defaults.
  • ClickツNext

12c_GridInfra_012.jpg

  • EnsureツInventory Directoryツis set toツ/u01/app/oraInventory
  • The field should already be populated with the value above.
  • TheツInventory Directoryツcan be changed, but it is recommended to keep the defaults.
  • ClickツFinish

12c_GridInfra_013.jpg

  • In this environment theツrootツpassword is known, so configuration scripts will be run automatically.
  • TickツAutomatically run configuration scripts
  • Select the radial buttonツUse "root" user credential
  • Ensure theツPasswordツis set
  • ClickツNext

12c_GridInfra_014.jpg

  • Wait for the verification process to complete.
  • This screen will move on automatically.

12c_GridInfra_015.jpg

  • For demonstration purposes, this installation has some issues.
  • TheツFix & Check Againツbutton can be used to fix any issues.
  • Note that not all issues can be fixed and it may be necessary to refer the issues to a Unix Administrator
  • ClickツCheck Againツwhen all issues have been resolved.

12c_GridInfra_016.jpg

  • Review this screen and clickツInstall
  • At this point aツResponse Fileツcan be saved by clickingツSave Response File窶ヲ
  • A response file can be used for automated deployments.

12c_GridInfra_017.jpg

  • Wait for the installation to complete.
  • This screen will move on automatically.

12c_GridInfra_018.jpg

  • ClickツClose

Example Database Binary Install

12c_DBInstall_001.jpg

  • Un-tick theツI wish to receive security updates via My Oracle Supportツbox.
    • NBツThis is site specific and should be reviewed.
  • ClickツNext.

12c_DBInstall_002.jpg

  • ClickツYesツto remain uninformed.

12c_DBInstall_003.jpg

  • SelectツInstall database software only
  • ClickツNext.

12c_DBInstall_004.jpg

  • EnsureツSingle instance database installationツis selected.
  • ClickツNext.

12c_DBInstall_005.jpg

  • Select the languages you require. In this instance all languages have been chosen.
  • ClickツNext

12c_DBInstall_006.jpg

  • SetツDatabase editionツtoツEnterprise Edition (6.4GB)
  • ClickツNext

12c_DBInstall_007.jpg

  • EnsureツOracle baseツis set toツ/u01/app/oracle
  • EnsureツSoftware locationツis set toツ/u01/app/oracle/product/12.1.0/dbhome_1
  • The fields should already be populated with the above values.
  • They can be changed, but it is recommended to keep the defaults.
  • ClickツNext

12c_DBInstall_008.jpg

  • In this installation different OS groups will be used. Optional groups will be left blank.
  • This may not be suitable for all environments.
  • SetツDatabase Administrator (OSDBA) Groupツtoツdba
  • LeaveツDatabase Operator (OSOPER) Group (Optional)ツblank.
  • SetツDatabase Backup and Recovery (OSBACKUPDBA) Groupツtoツbckpdba
  • SetツData Guard administrative (OSDGDBA) Groupツtoツdgdba
  • SetツEncryption Key Management administrative (OSKMDBA) Groupツtoツkmdba
  • ClickツNext

12c_DBInstall_009.jpg

  • Wait for the verification process to complete.
  • This screen moves on automatically when complete.

12c_DBInstall_010.jpg

  • For demonstration purposes, this installation has some issues.
  • TheツFix & Check Againツbutton can be used to fix any issues.
  • Note that not all issues can be fixed and it may be necessary to refer the issues to a Unix Administrator
  • ClickツCheck Againツwhen all issues have been resolved.

12c_DBInstall_011.jpg

  • Review this screen and clickツInstall
  • At this point aツResponse Fileツcan be saved by clickingツSave Response File窶ヲ
  • A response file can be used for automated deployments.

12c_DBInstall_012.jpg

  • Wait for the installation process to complete.
  • This screen will move on automatically.

12c_DBInstall_013.jpg

  • Get a UNIX administrator to run theツConfiguration Scriptsツas theツrootツuser.
  • ClickツOKツwhen theツConfiguration Scriptsツhave completed successfully.

12c_DBInstall_014.jpg

  • ClickツClose

Example Database Creation

12c_Create_001.jpg

  • SelectツCreate Database
  • ClickツNext.

12c_Create_002.jpg

  • SelectツAdvanced Mode.
  • ClickツNext.

12c_Create_003.jpg

  • SelectツGeneral Purpose or Transaction Processing.
  • ClickツNext.

12c_Create_004.jpg

  • SetツGlobal Database NameツtoツMYDB001.MYDOMAIN.COM
  • EnsureツSIDツhas been populated withツMYDB001
  • ClickツNext.

12c_Create_005.jpg

  • For this installation no Grid Agent is going to be configured.
  • ClickツNext

12c_Create_006.jpg

Set and confirm the passwords for theツSYSツandツSYSTEMツuser.
ClickツNext


12c_Create_007.jpg

  • For this database, theツGRIDツlistener will be used. This may not be suitable for all environments.
  • Tick the box alongsideツLISTENER
  • ClickツNext

12c_Create_008.jpg

  • EnsureツDatabase files Storage Typeツis set toツAutomatic Storage Management (ASM)
  • SelectツUse Common Location for All Database Files
  • SetツFile Locationツtoツ+DATA01
  • TickツUse Oracle-Managed Files
  • EnsureツRecovery files Storage Typeツis set toツAutomatic Storage Management (ASM)
  • TickツSpecify Fast Recovery Area
  • SetツFast Recovery Areaツtoツ+FRA01
  • Set theツFast Recovery Area Sizeツto a suitable value
  • TickツEnable Archiving
  • ClickツMultiplex Redo Logs and Control Files窶ヲ

12c_Create_009.jpg

  • SetツLocation 1ツtoツ+REDO01
  • SetツLocation 2ツtoツ+REDO02
  • ClickツOK

12c_Create_010.jpg

  • ClickツNext

12c_Create_011.jpg

  • In this installationツSample SchemasツandツDatabase Vault & Label Securityツwill be left as default.
  • ClickツNext.

12c_Create_012.jpg

  • For this installationツAutomatic Shared Memory Managementツwill be used.
  • SetツSGA SizeツandツPGA Sizeツto suitable values.
  • Click theツSizingツtab.

12c_Create_013.jpg

  • Set theツProcessesツvalue to a suitable number for the environment.
  • Click theツCharacter Setsツtab.

12c_Create_014a.jpg

  • These settings are dependent on the environment being built.
  • SelectツUse Unicode (AL32UTF8)ツ- Most systems would use this value.
  • SetツNational Character SetツtoツUTF8 - Unicode 3.0 UTF-8 Universal character set, CESU-8 compliantツ- Most systems would use this value.
  • Set aツDefault Language
  • Set aツDefault Territory
  • Click theツConnection Modeツtab.

12c_Create_015.jpg

  • SelectツDedicated Server Mode
  • ClickツAll Initialization Parameters...

12c_Create_016.jpg

  • ClickツShow Advanced Parameters

12c_Create_017.jpg

  • Set theツInitialization Parametersツappropriately.
  • In this installation the following parameters have been set in the DBCA GUI
  • control_filesツhave been set to useツ+DATA01ツandツ+FRA01
  • db_create_online_log_dest_1ツhas be set to useツ+REDO01
  • db_create_online_log_dest_2ツhas be set to useツ+REDO02
  • ClickツClose

12c_Create_018.jpg

  • ClickツNext.

12c_Create_019.jpg

  • ClickツCustomize Storage Locations窶ヲ

12c_Create_019b.jpg

  • Add additionalツREDOツlogs if required.
  • ClickツOk

12c_Create_019c.jpg

  • TickツCreate Database
  • If required at this point, aツDatabase Templateツcan be created by tickingツSave as Database Template
  • Set aツNameツfor theツDatabase Templateツif theツSave as Database Templateツbox has been ticked.
  • The database creation scripts can be created by tickingツGenerate Database Creation Scripts
  • ClickツNext

12c_Create_020.jpg

  • Review the summary page
  • ClickツFinish

12c_Create_021.jpg

  • This screen will move on automatically.

12c_Create_022.jpg

  • Set-up the passwords by clicking onツPassword Managementツif required.
  • ClickツClose.

Other References

  • None Currently

Known Issues

  • None Currently

Deinstalling Oracle 12g Binaries and Database

Withツ12.1ツthe deinstallation tool is located in the Oracle home directory after installation.

Step-by-Step

1. Run this tool fromツORACLE_HOMEツfirst.

  • cd $ORACLE_HOME/deinstall
  • ./deinstall
  • When prompted for the database name enter theツSIDツyou want to remove.
    • NBツThis will remove the database binaries too.
  • When askedツDo you still want to modify the details of SID database(s)? [n]:AnswerツN
    • NBツYou would answerツYツif you wanted to amend the database configuration.
  • The tool should now complete okay after performing several tasks.

2. Now run the tool from theツGRID_HOME.


Category Database

TweetTweet Share on LinkedInShare on LinkedIn Share on Google+Google+ Submit to RedditReddit Publish on WordPress WordPress Send emailSend email