CHAPTER – 1

Installing Oracle Database Software

Oracle Database Installation Notes

1. Installation Process:

• Oracle Universal Installer (OUI): Used for installing and maintaining Oracle products.
• Standardization: Installation processes are standardized but may vary by platform and
product.
• Pre-installation: Read release notes for the specific platform before installing.

2. Planning the Installation:

• Prerequisites: Ensure software availability and a suitable machine.

• Installation Time: Typically takes about 15 minutes, depending on hardware.
• Practice Environment: Recommended for students to have personal installations for
practice.

3. Supported Platforms:

• Historical Support: Originally supported a wide range of platforms.

• Current Support: Reduced to commercially viable platforms; Linux is prioritized for
release.
• Common Platforms for Students: Linux and Microsoft Windows.

4. Obtaining the Software:

• Public Download: Available for development and self-tuition; restricted license.

• Restrictions: Legal restrictions on downloading in certain countries; base release only
for public.
• Patches: Require a support agreement.
• Download Sources:
o Oracle Technology Network (OTN): Navigate to www.oracle.com, go to
Downloads, select Oracle Database.
o Oracle Software Delivery Cloud: Go to http://edelivery.oracle.com, select
Oracle Database product pack.
• Files Needed: Four ZIP files (two for Oracle Database, two for Grid Infrastructure);
unzip into separate directories.

5. User Accounts:

• Unix/Linux:
o Accounts Needed: Separate accounts for database and Grid Infrastructure
software.
 oRecommended Account: Typically named oracle with groups oinstall
(primary) and dba (secondary).
• Windows:
o Installation Account: Often uses Administrator privileges (not recommended for
production).
o Installer Actions: Creates necessary operating groups (ORA_DBA).

6. Disk Space and Directories:

• Required Space: Approximately 5GB for the Oracle Home.

• File Systems: Must be a “cooked” file system, not ASM disk group or raw device.
• Directory Structure:
o Optimal Flexible Architecture (OFA): Each product installed into its own
Oracle Home, beneath an Oracle Base.
o Oracle Base: Contains Oracle Homes and other directories for administration and
databases.
o OUI Inventory: Located outside the Oracle Base.

7. Recommended Naming Conventions:

• Oracle Base Path Example: D:\app\oracle.

• Oracle Home Path Example: /u01/app/oracle/product/12.1.0/dbhome_1.
• Database Files Path Example: D:\app\oracle\oradata\orcl.
• OUI Inventory Path Example: /u01/app/oraInventory.

8. OFA Directory Structure Benefits:

• Ease of Organization: Helps manage multiple software installations.

• Common Assumptions: Some DBAs and products expect OFA compliance, deviation
may cause confusion.

Prerequisite Checks for Oracle Installation

1. Prerequisites:

• Installation Release Notes: List hardware requirements (disk space, RAM), OS

versions, utilities, security settings, kernel limits, and patch levels.
• Platform Differences:
o Windows: Generally simpler due to a tightly controlled environment; OUI can
make more assumptions.
o Linux: Requirements can vary based on the distribution. Oracle Enterprise Linux
is likely to meet prerequisites; other distributions (Red Hat, SUSE, CentOS) may
require additional setup.
2. OUI Prerequisites:

• File: oraparam.ini (found in unzipped software).

• Basic Requirements (Example for 64-bit Linux, release 12.1.0.1.0):
o TEMP_SPACE=500
o SWAP_SPACE=150
o MIN_DISPLAY_COLORS=256
• Product-Specific Prerequisites: Defined in cvu_prereq.xml, checked by OUI. Ignoring
these may lead to issues, though the installation might still proceed.

3. Handling Prerequisite Failures:

• Common Issues: May include kernel settings or missing packages, especially on non-
Oracle validated Linux versions.
• Support Considerations: Support might be denied if prerequisites are not met. Fix
issues as soon as possible if they occur.

Installing Oracle Database Software

4. OUI Options:

• Standard Installation: Suitable up to Oracle Certified Professional level. RAC

installation not covered in this guide.
• Installation vs. Database Creation: The option to create a database during installation is
not discussed here.

5. OUI Inventory:

• Purpose: Records installed Oracle products and Oracle Home locations.

• Locking Mechanism: Prevents concurrent OUI or Opatch sessions to avoid corruption.
• Pointer File Locations:
o Linux: /etc/oracle/oraInst.loc
o Solaris/AIX: /var/opt/oracle
o Windows: Registry key HKEY_LOCAL_MACHINE/SOFTWARE/ORACLE/inst_loc

6. OUI Details:

• Platform Compatibility: Written in Java (JDK 1.5 included); consistent across

platforms with minor UI differences.
• Installation: Typically shipped with Oracle products; install from product CD/DVD. Use
the latest version to avoid issues.

7. Interactive Install (OUI Dialog):

• Launch Commands:
o Linux: runInstaller.sh
o Windows: setup.exe
 • Requirements: Graphical terminal needed (X Window for Linux, graphical interface for
Windows).
• Steps in OUI Dialog:
1. Configure Security Updates (optional).
2. Download Software Updates (optional).
3. Select Installation Option (chain install or separate database creation).
4. Grid Installation Options (single instance, RAC, RAC One Node).
5. Select Product Languages (default is English).
6. Select Database Edition (Enterprise, Standard, Standard Edition 1).
7. Specify Installation Location (Oracle Base and Oracle Home directories).
8. Privileged OS Groups (nominate groups managing Oracle Home).
9. Perform Prerequisite Checks (validate environment).
10. Summary (review dialog summary).
11. Install Product (view progress).
12. Finish (complete installation).

8. Handling Installation Issues:

• Linux: Step 9 may fail if not using an Oracle-validated Linux version. Fixable issues can
be addressed with a script, but unfixable issues must be resolved before proceeding.
• Root Script: Run root.sh as root to perform privileged tasks. Windows does not require
this step.

Silent Install and Response Files

9. Response Files:

• Purpose: Automate installations without graphical output, suitable for multiple machines
or automated setups.
• Template: db_install.rsp file provided in /response/ directory; well-documented.
• Generating a Response File: Run OUI interactively, check "Generate response file," and
cancel installation.
• Running Silent Install: Edit the response file for the environment and use the command:
o Windows: setup.exe -silent -responseFile db_install.rsp
o Linux: Use ./runInstaller -help for command-line switches; -
ignoreSysPrereqs allows bypassing prerequisite checks.

Platform Variations

10. User ID Differences:

• Linux: User must be pre-created with necessary groups (oinstall and dba). OUI cannot
be run as root.
• Windows: OUI run as an administrator; prompts for Oracle Home owner user.
11. OS Groups:

• Linux: OSDBA group (dba) must be pre-created. oinstall should be the primary group
for the OUI user.
• Windows: Groups are hard-coded and created by OUI.

12. Root Scripts:

• Linux: Requires running root.sh at the end of installation for root privileges tasks.
• Windows: Does not require this step since OUI runs with administration rights.

(Pg-10) Exercise 1-1: Install the Oracle Database Software

 CHAPTER 2
Creating an Oracle Database Using DBCA

Database Creation Overview

**1. Introduction to Database Creation:

• Objective: Understand both GUI and command line methods for creating a database.
• Key Concept: Creating a database is straightforward. While initial design and structure
are important, most aspects can be adjusted later. Keep the process simple at the
beginning.

Key Concepts

**2. Instance and Database:

• Instance:
o Definition: Consists of memory structures and processes.
o Characteristics: Transient; can be started and stopped.
• Database:
o Definition: Composed of files on disk.
o Characteristics: Persistent until deleted.
• Interaction:
o The instance creates the database once and can then open or close it multiple
times.
o Database requires an instance to be accessible.

**3. Data Dictionary:

• Description: Contains logical and physical structures, including segments for user data.
• Creation:
o Initial database creation sets up basic physical structures and the data dictionary.
o Data dictionary is built by running SQL scripts in ORACLE_HOME/rdbms/admin.

Steps in Database Creation

**4. Core Steps:

• 1. Create the instance.

• 2. Create the database.
• 3. Create the data dictionary.
• 4. Make the database usable.
o Data dictionary needs additional views and PL/SQL packages for usability.
**5. Scripts for Database Creation:

• Initial Scripts:
o sql.bsq for data dictionary creation.
• Additional Scripts:
o catalog.sql, catproc.sql for generating views and functionality.
o Optional “cat” scripts for additional features.

Using the Database Configuration Assistant (DBCA)

**6. DBCA Steps:

• 1. Create a parameter file and optional password file.

• 2. Build an instance in memory using the parameter file.
• 3. Issue CREATE DATABASE command to generate controlfile, redo log files, datafiles
for SYSTEM and SYSAUX tablespaces, and data dictionary.
• 4. Run SQL scripts to generate data dictionary views and PL/SQL packages.
• 5. Run SQL scripts for Enterprise Manager Database Express and other required
options.
• 6. On Windows, use oradim.exe to create the Oracle Windows service.

**7. DBCA Usage:

• Interactive Creation:
o Easier to use DBCA for creating the database; it handles parameter file creation
and script execution.
• Combination Approach:
o Some DBAs use DBCA to generate files and scripts, then manually review and
execute them using SQL*Plus.

**8. Launching DBCA:

• Windows:
o Navigate through Start menu or run dbca.bat from CMD prompt.
• Linux:
o Set environment variables: DISPLAY, ORACLE_BASE, ORACLE_HOME, and PATH.
o Run dbca shell script from $ORACLE_HOME/bin.

**9. Environment Variables for Linux:

• Example Script:

export DISPLAY=myhost:0.0
export ORACLE_BASE=/u01/app/oracle
export ORACLE_HOME=$ORACLE_BASE/product/12.1.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH
 • Note: Ensure $ORACLE_HOME/bin is at the start of the search path to avoid conflicts with
similarly named executables.

**10. Final Tip:

• Database Choices: Most decisions during creation can be modified later, though some
changes might require downtime. Aim to make the best choices possible initially, but
know adjustments can be made.

DBCA Dialog Overview

1. Database Operation:

• Create Database: Launches dialog to create an instance and database.

• Configure Database Options: Adjust existing database settings, e.g., install additional
capabilities.
• Delete Database: Remove existing instances and databases.
• Manage Templates: Handle stored, preconfigured databases; create from existing
databases or use supplied templates.
• Manage Pluggable Databases: Specific to Oracle 12c and not covered in the OCA
curriculum.

2. Creation Mode:

• Create A Database With Default Configuration: Limited subset of DBCA capabilities.

• Advanced Mode: Access to all DBCA capabilities.

3. Database Template:

• Template: Preconfigured database used to create new databases quickly.

• Oracle Templates: General-purpose and data warehouse templates.
• Custom Database: Allows full configuration freedom without predefined limits.

4. Database Identification:

• Global Database Name: Combines database name and optional domain (up to 128
characters).
o DB_NAME: Unique, up to 8 characters, including alphanumeric, underscores,
number signs, and dollar signs.
o DB_DOMAIN: Optional, used for DB_DOMAIN instance parameter.
• System Identifier (SID): Oracle instance name, used for ORACLE_SID parameter.
Usually kept the same as DB_NAME for simplicity.

5. Management Options:

• Oracle Enterprise Manager (OEM): Optional management tools.

 o Enterprise Manager Database Express: Configured within a single managed
database.
o Enterprise Manager Cloud Control: Universal management system for multiple
databases.

6. Database Credentials:

• SYS and SYSTEM Passwords: Required for database administration; follow best
practices for complexity.
• Windows Variation: Prompt for operating system account password owning the Oracle
Home.

7. Storage Locations:

• Storage Types: Automatic Storage Management (ASM) disk group or file system
directory.
• Oracle Managed Files (OMF): Allows Oracle to control file naming and directory
structure.
• Recovery Related Files: Nominate a Fast Recovery Area for backups and enable archive
log mode.

8. Database Options:

• License-Specific Options: Select or deselect options based on licensing.

• Sample Schemas: Install demonstration schemas if desired.

9. Initialization Parameters:

• Memory Parameters: Set values for SGA (System Global Area) and PGA (Program
Global Area).
• DB_BLOCK_SIZE: Critical parameter; defaults to 8KB and cannot be changed post-
creation.
• Character Sets: Choose database and national character sets; Unicode (AL32UTF8) is
recommended.
• Connection Mode: Configure shared server settings.

10. Creation Options:

• Create Database: Initiates database creation.

• Save As A Database Template: Generates a template for future use.
• Generate Database Creation Scripts: Creates scripts for manual database creation.

11. Prerequisite Checks:

• Sanity Checks: Verifies that the creation process can proceed; errors should be
addressed if detected.
12. Summary:

• Review: Displays DBCA’s actions before finalizing. Make changes if needed.

13. Progress Page:

• Creation Progress: Shows stages of database creation; duration varies based on options
and hardware.

Notes on Generating Database Creation Scripts Using DBCA

Purpose: Generating database creation scripts is useful for situations such as:

• Servers without graphical capabilities.

• Change control procedures needing tested scripts.
• Creating multiple identical databases.
• Avoiding manual interactions with prompts.

Generating the Scripts:

1. Launch DBCA: Follow the dialog and options as needed.

2. Step 10: Select the option to generate scripts and specify a directory.
o Default Locations:
§ Windows: c:\app\oracle\admin\orcl121\scripts
§ Linux: /u01/app/oracle/admin/orcl121/scripts
3. Script Structure:
o Shell Script (Linux): E.g., orcl121.sh
§ Creates directories.
§ Sets environment variables.
§ Executes SQL*Plus to run a SQL script (orcl121.sql).
o Batch File (Windows): E.g., orcl121.bat
§ Similar function, uses ORADIM utility for Windows services.

Creation Scripts:

1. Shell Script Example (Linux):

#!/bin/sh
OLD_UMASK='umask'
umask 0027
mkdir -p /u01/app/oracle/admin/orcl121/{adump,dpdump,pfile}
umask ${OLD_UMASK}
ORACLE_SID=orcl121; export ORACLE_SID
PATH=$ORACLE_HOME/bin:$PATH; export PATH
echo You should Add this entry in the /etc/oratab:
orcl121:/u01/app/oracle/product/12.1.0/dbhome_1:Y
/u01/app/oracle/product/12.1.0/dbhome_1/bin/sqlplus /nolog
@/u01/app/oracle/admin/orcl121/scripts/orcl121.sql
 2. SQL Script Example:

set verify off

ACCEPT sysPassword CHAR PROMPT 'Enter new password for SYS: ' HIDE
ACCEPT systemPassword CHAR PROMPT 'Enter new password for SYSTEM: '
HIDE
host /u01/app/oracle/product/12.1.0/dbhome_1/bin/orapwd
file=/u01/app/oracle/product/12.1.0/dbhome_1/dbs/orapworcl121
force=y extended=y
@/u01/app/oracle/admin/orcl121/scripts/CreateDB.sql
@/u01/app/oracle/admin/orcl121/scripts/CreateDBFiles.sql
@/u01/app/oracle/admin/orcl121/scripts/CreateDBCatalog.sql
@/u01/app/oracle/admin/orcl121/scripts/sampleSchema.sql
@/u01/app/oracle/admin/orcl121/scripts/apex.sql
@/u01/app/oracle/admin/orcl121/scripts/postDBCreation.sql
@/u01/app/oracle/admin/orcl121/scripts/lockAccount.sql

3. Key Commands and Settings:

o CREATE DATABASE "orcl121": Defines database structure and tablespaces.
§ SYSTEM: Data dictionary, 700MB.
§ SYSAUX: Related objects, 550MB.
§ TEMP: Temporary tablespace, 20MB.
§ UNDO: Undo tablespace, 200MB.
o Character Sets: AL32UTF8 (database), AL16UTF16 (national).
o LOGFILE: Defines online log file groups.
o Passwords: For SYS and SYSTEM users.

Post-Creation Scripts:

1. CreateDBFiles.sql: Creates default tablespaces.

2. CreateDBCatalog.sql: Generates data dictionary views and PL/SQL packages.
3. Sample Schema and Other Scripts: Install various options and features.
4. postDBCreation.sql: Applies patches, converts pfile to spfile.
5. lockAccount.sql: Locks pre-seeded accounts and restarts the database.

Initialization Parameter File:

• Generated for starting the database instance.

• Example content:

plaintext
Copy code
db_block_size=8192
open_cursors=300
db_domain=""
db_name="orcl121"
control_files=("/u01/app/oracle/oradata/orcl121/control01.ctl",
"/u01/app/oracle/fast_recovery_area/orcl121/control02.ctl")
db_recovery_file_dest="/u01/app/oracle/fast_recovery_area"
db_recovery_file_dest_size=5061476352
compatible=12.0.0.0.0
 diagnostic_dest=/u01/app/oracle
processes=300
sga_target=503316480
audit_file_dest="/u01/app/oracle/admin/orcl121/adump"
audit_trail=db
remote_login_passwordfile=EXCLUSIVE
dispatchers="(PROTOCOL=TCP) (SERVICE=orcl121XDB)"
pga_aggregate_target=167772160
undo_tablespace=UNDOTBS1

Notes on Managing Database Design Templates and Options Using DBCA

Database Design Templates

Overview:

• Templates: Stored defini+ons of a database used to create new databases; portable

across pla6orms.

Types of Templates:

1. Structure Only:
o Contains structural informa+on (op+ons, storage details, ini+aliza+on
parameters).
o Excludes: Actual datafiles.
o Outcome: Database created from scratch with no user-defined data.
2. Structure and Data:
o Includes both structural informa+on and datafiles.
o Outcome: Database is an exact replica of the source database at the +me of
template crea+on.

Managing Templates with DBCA:

• DBCA Dialog:
o Step 1: Choose "Manage Templates" radio buHon.
o Op:ons:
§ Delete a template.
§ Create a template from:
§ An exis+ng template.
§ An exis+ng database (structure only or structure and data).
o Requirements: Template or database must exist on the machine running DBCA.
o Restart Requirement:
§ If crea+ng a template with datafiles, the source database must be
restarted.
§ No restart required for structure-only templates.
o Process:
 § Specify source and type of template.
§ For templates with datafiles, provide loca+on for storing the compressed
database.
§ Created templates are available for selec+on in step 3 of the DBCA dialog.

Storage Location:

• Templates are stored in ORACLE_HOME/assistants/dbca/templates.

• Copying these files to another Oracle Home will make the template available there.

Configuring Database Op5ons with DBCA

Concept:

• Database Op:ons: Combina+on of executable code (in Oracle Home) and necessary
objects (in the database).
• Installa:on: DBCA prompts during crea+on determine which op+ons are installed, based
on the scripts it runs.
• Limita:ons: Op+ons cannot be uninstalled via DBCA. Templates with datafiles do not
allow control over installed op+ons.

Configuring Options:

• DBCA Func:onality:
o Generates and runs scripts to install op+ons.
o Does not support uninstalla+on of op+ons.

Viewing Installed Options:

• Query the DBA_REGISTRY view to see installed op+ons.

Example Query:

select comp_name, version, status from dba_registry order by 1;

Sample Output:

COMP_NAME VERSION STATUS

----------------------------------- --------------- ------
OLAP Catalog 12.1.0.0.2 VALID
Oracle Application Express 4.1.1.00.23 VALID
Oracle Database Catalog Views 12.1.0.0.2 VALID
Oracle Database Packages and Types 12.1.0.0.2 VALID
Oracle Expression Filter 12.1.0.0.2 VALID

Note: DBA_REGISTRY: Provides information on installed components and their statuses

 CHAPTER 3

Installing Oracle Grid Infrastructure for a Stand-Alone Server

Notes on Grid Infrastructure (GI) and Automatic Storage Management (ASM)

Grid Infrastructure (GI)

Overview:

• Purpose: Provides clustering, networking, storage, and high-availability services for

Oracle databases. Required for Real Applica+on Clusters (RAC) and can be used with
single-instance databases.
• Single-Instance Use: Typically used for Automa+c Storage Management (ASM) and
automa+c restart capabili+es.

Configuration and Components:

• ASM Management:
o From Oracle 11.2.x onward, ASM is part of GI.
o Earlier releases had ASM integrated with the database so\ware.
• GI Processes:
o Windows: Services running with Administrator privileges.
o Linux: Daemons running with root privileges.
o Core Process: High Availability Services daemon (OHASD), protected by the OS.
• Resource Management:
o Managed Resources Include:
§ Database listeners
§ Virtual IP addresses
§ ASM instance
§ ASM disk groups
§ Database instances
§ Third-party products
o Registry: Oracle Local Registry (OLR) stores details about resources.
§ Linux Loca:on: /etc/oracle/olr.loc
§ Windows Loca:on: Registry key
HKEY_LOCAL_MACHINE/SOFTWARE/Oracle/olr/olrconfig_loc
• Administration Tools:
o crsctl U:lity: Used for managing GI processes and resources, including
star+ng/stopping OHASD.
o srvctl U:lity: Manages Oracle resources only, not third-party resources.

Exam Tip:

• crsctl can manage both GI and third-party resources.

 • srvctl manages only Oracle resources.

Automa5c Storage Management (ASM)

Overview:

• Func:on: Logical Volume Manager (LVM) that configures striped and mirrored volumes
for Oracle database files.
• Storage Units: Uses disk groups (not visible to the OS) for Oracle database files.

Architecture:

• ASM Files and Disks:

o Files are stored in disk groups, which consist of one or more ASM disks.
o Disks are formaHed into Alloca+on Units (AUs) grouped into file extents.
o Files can span mul+ple disks and vice versa.
• ASM Instance:
o Manages the ASM environment with memory components and background
processes.
o Only operates in nomount mode, lacks a data dic+onary.
o Authen+ca+on via OS or password file.

Bootstrap Process:

1. OS starts GI processes.
2. GI starts the ASM instance.
3. ASM instance locates and mounts disk groups, registers with GI.
4. RDBMS instance starts and requests ASM instance address from GI.
5. RDBMS instance logs on to ASM and accesses file extent map.
6. RDBMS instance opens the file.

Important Points:

• Data Flow: No data passes through ASM instance; all I/O is between RDBMS instance
and the file.
• File Types Stored in ASM Disk Groups:
o Controlfiles
o Datafiles
o Tempfiles
o Online logfiles
o Archive logfiles
o Server parameter file (spfile)
o Password file
o RMAN backups
o Data Pump dump files
 • File Types Not Stored in ASM Disk Groups:
o Oracle Home
o Trace files or alert log
o pfile ini+aliza+on file
o User-managed backups

Exam Tip:

• ASM instance controls storage, with all data I/O managed directly between RDBMS and
the file.

Notes on ASM Disks

Overview

Definition:

• ASM Disks: The term "ASM disk" is somewhat misleading as these are not physical disks
but can be various types of storage devices.

Types of ASM Disks:

1. Directly Attached Storage (DAS):

o Descrip:on: Physical disks aHached directly to the server, typically SCSI or similar.
o Current Requirement: Disks must have a par++on table (even if it covers the
en+re disk) to be presented to ASM.
2. Storage Area Network (SAN):
o Descrip:on: Volumes managed by a storage array, o\en striped and/or mirrored,
connected via fiber-op+c channels.
o Presenta:on: Presented to ASM as logical unit numbers (LUNs).
o Performance: Striping and RAID algorithms are used for performance; mirroring
can be handled by SAN or ASM.
3. Network-Attached Storage (NAS):
o Descrip:on: Typically iSCSI volumes or NFS files.
o iSCSI Devices: Exported by an iSCSI target machine and mounted on the database
server by an iSCSI ini+ator.
o NFS Files: Large zero-filled files on an NFS volume, exported from an NFS server.
o Network Requirements: High-speed, dedicated local area network connec+on
with mul+pathing recommended.

Identification:

• DAS, SAN, or iSCSI Devices: Iden+fied by their device drivers.

• NFS Files: Iden+fied by their fully qualified filename.
ASM Configuration:

• Parameter File: ASM instance is controlled by a parameter file similar to an RDBMS

instance.
• Cri:cal Parameter: ASM_DISKSTRING iden+fies ASM disks with a comma-separated list
of values and wildcards.
o Default Values by OS:
§ AIX: /dev/rhdisk*
§ HP-UX: /dev/rdisk/*
§ Solaris: /dev/rdsk/*
§ Windows: \\.\ORCLDISK*
§ Linux: /dev/raw/* or ORCL:* if using ASMLib Kernel Driver
• Note: Default values may need adjustment to ensure only intended devices are found.

Crea5ng ASM Disks

General Process:

• Disk Crea:on: Done by the system administrator; each device accessed via a device
driver created during system boot.
• Persistence Issue: Device names must be persistent and drivers readable/writeable by
Oracle processes.

Techniques for Linux:

1. ASMLib Kernel Library:

o Descrip:on: Available for some Linux distribu+ons; manages ASM disks.
2. ASM Filter Driver:
o Descrip:on: Introduced in release 12.1.0.2; can replace ASMLib, preven+ng non-
Oracle processes from wri+ng to ASM disks.
3. udev Facility:
o Descrip:on: Uses scripts wriHen by the system administrator to iden+fy devices
and set ownership and permissions.

Windows Configuration:

• U:lity: asmtool.exe is used for managing devices and ensuring persistence.

NFS Files Creation:

• Commands Example:

dd if=/dev/zero of=/asm/disk1 bs=1048576 count=1048576

chown oracle:dba /asm/disk1
chmod 660 /asm/disk1
Note: Creating ASM disks involves platform-specific techniques and details beyond the OCA
examination scope.

Notes on Installing Oracle Grid Infrastructure (GI) for a Stand-Alone Server

General Requirements

• Dedicated Oracle Home: GI should be installed into its own Oracle Home.
• Version Compa:bility: GI must be the same version or higher than any databases using
its services. For example, GI 12.1.x can support a database of version 11.2.x, but not vice
versa.
• Node Compa:bility: GI must run on the same nodes as the database instances. In
clustered environments, Flex ASM allows only a few nodes (default is three) to run ASM
instances.

Installa5on Process

1. Media and Installer:

o Executable:
§ Unix: runInstaller.sh
§ Windows: setup.exe
2. Major Installation Choices:
o Download SoRware Updates: Op+on to register with My Oracle Support for
updates and patches.
o Select Installa:on Op:on:
§ Install and Configure GI for a Cluster
§ Install and Configure GI for a Standalone Server
§ Upgrade GI or Automa+c Storage Management (ASM)
§ Install GI So\ware Only
o Create ASM Disk Group:
§ Set ASM_DISKSTRING discovery path
§ Select disks for the disk group
3. Disk Group Configuration:
o Redundancy Op:ons:
§ Normal: Mirrors each extent (requires at least two disks).
§ High: Creates three copies of each extent (requires at least three disks).
§ External: No ASM mirroring; relies on storage medium’s fault tolerance.
o Alloca:on Unit (AU) Size:
§ Defaults to 1MB; affects file extent size.
§ Sizes available: 1, 2, 4, 8, 16, 32, or 64MB.
§ Recommenda:on: 4MB is op+mal for large systems, especially for
Exadata. 1MB is suitable for most installa+ons.
4. Discovery Path:
o Ini:al State: No disks shown if default path does not detect any.
 o Ac:on: Click “Change Discovery Path” to set the loca+on of prepared ASM disks.
5. Upgrading GI:
o OUI Upgrade Process: Detects exis+ng installa+on and transfers configura+on to
the new GI home.
o Concurrent Instances: Only one GI instance can run per machine; the installer
will disable the previous version.
6. Best Practices:
o OS User Separa:on:
§ Install GI under a different OS user than the database so\ware to
separate responsibili+es.
§ This is par+cularly useful in larger environments where different
administrators manage GI and database roles.
o OS Group:
§ GI Administrator Group:
§ Windows: Hard-coded as ORA_ASMDBA.
§ Unix: Can be named anything, but must be created before running
OUI.
§ The GI administrator must be a member of the OSASM group.

This summary captures the key points about installing Oracle Grid Infrastructure, including
version requirements, installation options, disk group configuration, and best practices for user
and group management.