How To Install Oracle 11gR2 Software and Database in Silent Mode Using Response File

How To Install Oracle 11gR2 Software and Database in Silent Mode Using Response File

1. Create Groups & Oracle User
2. Create profile for Oracle User
3. Set Security limits
4. Set Kernel Parameters
5. Copy "<11gR2 Disk>/database/response/db_install.rsp" to "<path>/db_install.rsp"
   Edit "<path>/db_install.rsp" and modify the values that suits your environment

6. Do the required changes in below file based on your environment:


####################################################################
## Copyright(c) Oracle Corporation 1998,2011. All rights reserved.##
##                                                                ##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
##                                                                ##
## Each variable is associated with a comment. The comment        ##
## can help to populate the variables with the appropriate        ##
## values.                              ##
##                                                                ##
## IMPORTANT NOTE: This file contains plain text passwords and    ##
## should be secured to have read permission only by oracle user  ##
## or db administrator who owns this installation.                ##
##                                                                ##
####################################################################

#------------------------------------------------------------------------------
# Do not change the following system generated value.
#------------------------------------------------------------------------------
oracle.install.responseFileVersion=/oracle/install/rspfmt_dbinstall_response_schema_v11_2_0

#------------------------------------------------------------------------------
# Specify the installation option.
# It can be one of the following:
# 1. INSTALL_DB_SWONLY
# 2. INSTALL_DB_AND_CONFIG
# 3. UPGRADE_DB
#-------------------------------------------------------------------------------
oracle.install.option=INSTALL_DB_AND_CONFIG

#-------------------------------------------------------------------------------
# Specify the hostname of the system as set during the install. It can be used
# to force the installation to use an alternative hostname rather than using the
# first hostname found on the system. (e.g., for systems with multiple hostnames
# and network interfaces)
#-------------------------------------------------------------------------------
ORACLE_HOSTNAME=localhost

#-------------------------------------------------------------------------------
# Specify the Unix group to be set for the inventory directory. 
#-------------------------------------------------------------------------------
UNIX_GROUP_NAME=oinstall

#-------------------------------------------------------------------------------
# Specify the location which holds the inventory files.
# This is an optional parameter if installing on
# Windows based Operating System.
#-------------------------------------------------------------------------------
INVENTORY_LOCATION=/vol1/app/oraInventory

#-------------------------------------------------------------------------------
# Specify the languages in which the components will be installed.            
#
# en   : English                  ja   : Japanese                 
# fr   : French                   ko   : Korean                   
# ar   : Arabic                   es   : Latin American Spanish   
# bn   : Bengali                  lv   : Latvian                  
# pt_BR: Brazilian Portuguese     lt   : Lithuanian               
# bg   : Bulgarian                ms   : Malay                    
# fr_CA: Canadian French          es_MX: Mexican Spanish          
# ca   : Catalan                  no   : Norwegian                
# hr   : Croatian                 pl   : Polish                   
# cs   : Czech                    pt   : Portuguese               
# da   : Danish                   ro   : Romanian                 
# nl   : Dutch                    ru   : Russian                  
# ar_EG: Egyptian                 zh_CN: Simplified Chinese       
# en_GB: English (Great Britain)  sk   : Slovak                   
# et   : Estonian                 sl   : Slovenian                
# fi   : Finnish                  es_ES: Spanish                  
# de   : German                   sv   : Swedish                  
# el   : Greek                    th   : Thai                     
# iw   : Hebrew                   zh_TW: Traditional Chinese      
# hu   : Hungarian                tr   : Turkish                  
# is   : Icelandic                uk   : Ukrainian                
# in   : Indonesian               vi   : Vietnamese               
# it   : Italian                                                  
#
# all_langs   : All languages
#
# Specify value as the following to select any of the languages.
# Example : SELECTED_LANGUAGES=en,fr,ja
#
# Specify value as the following to select all the languages.
# Example : SELECTED_LANGUAGES=all_langs 
#------------------------------------------------------------------------------
SELECTED_LANGUAGES=en

#------------------------------------------------------------------------------
# Specify the complete path of the Oracle Home.
#------------------------------------------------------------------------------
ORACLE_HOME=/vol1/app/oracle/product/11.2.0/db_1

#------------------------------------------------------------------------------
# Specify the complete path of the Oracle Base.
#------------------------------------------------------------------------------
ORACLE_BASE=/vol1/app/oracle

#------------------------------------------------------------------------------
# Specify the installation edition of the component.                       
#                                                            
# The value should contain only one of these choices.       
# EE     : Enterprise Edition                               
# SE     : Standard Edition                                 
# SEONE  : Standard Edition One
# PE     : Personal Edition (WINDOWS ONLY)
#------------------------------------------------------------------------------
oracle.install.db.InstallEdition=EE

#------------------------------------------------------------------------------
# This variable is used to enable or disable custom install and is considered
# only if InstallEdition is EE.
#
# true  : Components mentioned as part of 'optionalComponents' property
#         are considered for install.
# false : Value for 'optionalComponents' is not considered.
#------------------------------------------------------------------------------
oracle.install.db.EEOptionsSelection=false

#------------------------------------------------------------------------------
# This variable is considered only if 'EEOptionsSelection' is set to true.
#
# Description: List of Enterprise Edition Options you would like to enable.
#
#              The following choices are available. You may specify any
#              combination of these choices.  The components you choose should
#              be specified in the form "internal-component-name:version"
#              Below is a list of components you may specify to enable.
#       
#              oracle.oraolap:11.2.0.3.0 - Oracle OLAP
#              oracle.rdbms.dm:11.2.0.3.0 - Oracle Data Mining
#              oracle.rdbms.dv:11.2.0.3.0 - Oracle Database Vault
#              oracle.rdbms.lbac:11.2.0.3.0 - Oracle Label Security
#              oracle.rdbms.partitioning:11.2.0.3.0 - Oracle Partitioning
#              oracle.rdbms.rat:11.2.0.3.0 - Oracle Real Application Testing
#------------------------------------------------------------------------------
oracle.install.db.optionalComponents=oracle.rdbms.partitioning:11.2.0.3.0,oracle.oraolap:11.2.0.3.0,
oracle.rdbms.dm:11.2.0.3.0,oracle.rdbms.dv:11.2.0.3.0,oracle.rdbms.lbac:11.2.0.3.0,oracle.rdbms.rat:11.2.0.3.0

###############################################################################
#                                                                             #
# PRIVILEGED OPERATING SYSTEM GROUPS                                            #
# ------------------------------------------                                  #
# Provide values for the OS groups to which OSDBA and OSOPER privileges       #
# needs to be granted. If the install is being performed as a member of the   #       
# group "dba", then that will be used unless specified otherwise below.          #
#                                                                             #
# The value to be specified for OSDBA and OSOPER group is only for UNIX based #
# Operating System.                                                           #
#                                                                             #
###############################################################################

#------------------------------------------------------------------------------
# The DBA_GROUP is the OS group which is to be granted OSDBA privileges.
#------------------------------------------------------------------------------
oracle.install.db.DBA_GROUP=dba

#------------------------------------------------------------------------------
# The OPER_GROUP is the OS group which is to be granted OSOPER privileges.
# The value to be specified for OSOPER group is optional.
#------------------------------------------------------------------------------
oracle.install.db.OPER_GROUP=oper

#------------------------------------------------------------------------------
# Specify the cluster node names selected during the installation.
# Example : oracle.install.db.CLUSTER_NODES=node1,node2
#------------------------------------------------------------------------------
oracle.install.db.CLUSTER_NODES=

#------------------------------------------------------------------------------
# This variable is used to enable or disable RAC One Node install.
#
# true  : Value of RAC One Node service name is used.
# false : Value of RAC One Node service name is not used.
#
# If left blank, it will be assumed to be false
#------------------------------------------------------------------------------
oracle.install.db.isRACOneInstall=

#------------------------------------------------------------------------------
# Specify the name for RAC One Node Service.
#------------------------------------------------------------------------------
oracle.install.db.racOneServiceName=

#------------------------------------------------------------------------------
# Specify the type of database to create.
# It can be one of the following:
# - GENERAL_PURPOSE/TRANSACTION_PROCESSING            
# - DATA_WAREHOUSE                               
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.type=GENERAL_PURPOSE

#------------------------------------------------------------------------------
# Specify the Starter Database Global Database Name.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.globalDBName=orcl

#------------------------------------------------------------------------------
# Specify the Starter Database SID.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.SID=orcl

#------------------------------------------------------------------------------
# Specify the Starter Database character set.
#                                             
# It can be one of the following:
# AL32UTF8, WE8ISO8859P15, WE8MSWIN1252, EE8ISO8859P2,
# EE8MSWIN1250, NE8ISO8859P10, NEE8ISO8859P4, BLT8MSWIN1257,
# BLT8ISO8859P13, CL8ISO8859P5, CL8MSWIN1251, AR8ISO8859P6,
# AR8MSWIN1256, EL8ISO8859P7, EL8MSWIN1253, IW8ISO8859P8,
# IW8MSWIN1255, JA16EUC, JA16EUCTILDE, JA16SJIS, JA16SJISTILDE,
# KO16MSWIN949, ZHS16GBK, TH8TISASCII, ZHT32EUC, ZHT16MSWIN950,
# ZHT16HKSCS, WE8ISO8859P9, TR8MSWIN1254, VN8MSWIN1258
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.characterSet=AL32UTF8

#------------------------------------------------------------------------------
# This variable should be set to true if Automatic Memory Management
# in Database is desired.
# If Automatic Memory Management is not desired, and memory allocation
# is to be done manually, then set it to false.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.memoryOption=true

#------------------------------------------------------------------------------
# Specify the total memory allocation for the database. Value(in MB) should be
# at least 256 MB, and should not exceed the total physical memory available
# on the system.
# Example: oracle.install.db.config.starterdb.memoryLimit=512
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.memoryLimit=1024

#------------------------------------------------------------------------------
# This variable controls whether to load Example Schemas onto
# the starter database or not.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.installExampleSchemas=true

#------------------------------------------------------------------------------
# This variable includes enabling audit settings, configuring password profiles
# and revoking some grants to public. These settings are provided by default.
# These settings may also be disabled.   
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.enableSecuritySettings=true

###############################################################################
#                                                                             #
# Passwords can be supplied for the following four schemas in the          #
# starter database:                                    #
#   SYS                                                                       #
#   SYSTEM                                                                    #
#   SYSMAN (used by Enterprise Manager)                                       #
#   DBSNMP (used by Enterprise Manager)                                       #
#                                                                             #
# Same password can be used for all accounts (not recommended)               #
# or different passwords for each account can be provided (recommended)       #
#                                                                             #
###############################################################################

#------------------------------------------------------------------------------
# This variable holds the password that is to be used for all schemas in the
# starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.ALL=oracle123

#-------------------------------------------------------------------------------
# Specify the SYS password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.SYS=oracle123

#-------------------------------------------------------------------------------
# Specify the SYSTEM password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.SYSTEM=oracle123

#-------------------------------------------------------------------------------
# Specify the SYSMAN password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.SYSMAN=oracle123

#-------------------------------------------------------------------------------
# Specify the DBSNMP password for the starter database.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.password.DBSNMP=oracle123

#-------------------------------------------------------------------------------
# Specify the management option to be selected for the starter database.
# It can be one of the following:
# 1. GRID_CONTROL
# 2. DB_CONTROL
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.control=DB_CONTROL

#-------------------------------------------------------------------------------
# Specify the Management Service to use if Grid Control is selected to manage
# the database.     
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.gridcontrol.gridControlServiceURL=

###############################################################################
#                                                                             #
# SPECIFY BACKUP AND RECOVERY OPTIONS                                           #
# ------------------------------------                                      #
# Out-of-box backup and recovery options for the database can be mentioned    #
# using the entries below.                              #   
#                                                                             #
###############################################################################

#------------------------------------------------------------------------------
# This variable is to be set to false if automated backup is not required. Else
# this can be set to true.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.automatedBackup.enable=false

#------------------------------------------------------------------------------
# Regardless of the type of storage that is chosen for backup and recovery, if
# automated backups are enabled, a job will be scheduled to run daily to backup
# the database. This job will run as the operating system user that is
# specified in this variable.
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.automatedBackup.osuid=

#-------------------------------------------------------------------------------
# Regardless of the type of storage that is chosen for backup and recovery, if
# automated backups are enabled, a job will be scheduled to run daily to backup
# the database. This job will run as the operating system user specified by the
# above entry. The following entry stores the password for the above operating
# system user.
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.automatedBackup.ospwd=

#-------------------------------------------------------------------------------
# Specify the type of storage to use for the database.
# It can be one of the following:
# - FILE_SYSTEM_STORAGE
# - ASM_STORAGE
#------------------------------------------------------------------------------
oracle.install.db.config.starterdb.storageType=FILE_SYSTEM_STORAGE

#-------------------------------------------------------------------------------
# Specify the database file location which is a directory for datafiles, control
# files, redo logs.        
#
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.fileSystemStorage.dataLocation=/vol1/app/oracle/oradata

#-------------------------------------------------------------------------------
# Specify the backup and recovery location.
#
# Applicable only when oracle.install.db.config.starterdb.storage=FILE_SYSTEM_STORAGE
#-------------------------------------------------------------------------------
oracle.install.db.config.starterdb.fileSystemStorage.recoveryLocation=/vol1/app/oracle/flash_recovery_area

#-------------------------------------------------------------------------------
# Specify the existing ASM disk groups to be used for storage.
#
# Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
#-------------------------------------------------------------------------------
oracle.install.db.config.asm.diskGroup=

#-------------------------------------------------------------------------------
# Specify the password for ASMSNMP user of the ASM instance.                 
#
# Applicable only when oracle.install.db.config.starterdb.storage=ASM_STORAGE
#-------------------------------------------------------------------------------
oracle.install.db.config.asm.ASMSNMPPassword=

#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username.
#
#  Example   : MYORACLESUPPORT_USERNAME=abc@oracle.com
#------------------------------------------------------------------------------
MYORACLESUPPORT_USERNAME=

#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username password.
#
# Example    : MYORACLESUPPORT_PASSWORD=password
#------------------------------------------------------------------------------
MYORACLESUPPORT_PASSWORD=

#------------------------------------------------------------------------------
# Specify whether to enable the user to set the password for
# My Oracle Support credentials. The value can be either true or false.
# If left blank it will be assumed to be false.
#
# Example    : SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
#------------------------------------------------------------------------------
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false

#------------------------------------------------------------------------------
# Specify whether user doesn't want to configure Security Updates.
# The value for this variable should be true if you don't want to configure
# Security Updates, false otherwise.
#
# The value can be either true or false. If left blank it will be assumed
# to be false.
#
# Example    : DECLINE_SECURITY_UPDATES=false
#------------------------------------------------------------------------------
DECLINE_SECURITY_UPDATES=false

#------------------------------------------------------------------------------
# Specify the Proxy server name. Length should be greater than zero.
#
# Example    : PROXY_HOST=proxy.domain.com
#------------------------------------------------------------------------------
PROXY_HOST=

#------------------------------------------------------------------------------
# Specify the proxy port number. Should be Numeric and atleast 2 chars.
#
# Example    : PROXY_PORT=25
#------------------------------------------------------------------------------
PROXY_PORT=

#------------------------------------------------------------------------------
# Specify the proxy user name. Leave PROXY_USER and PROXY_PWD
# blank if your proxy server requires no authentication.
#
# Example    : PROXY_USER=username
#------------------------------------------------------------------------------
PROXY_USER=

#------------------------------------------------------------------------------
# Specify the proxy password. Leave PROXY_USER and PROXY_PWD 
# blank if your proxy server requires no authentication.
#
# Example    : PROXY_PWD=password
#------------------------------------------------------------------------------
PROXY_PWD=

#------------------------------------------------------------------------------
# Specify the proxy realm. This value is used if auto-updates option is selected.
#
# Example    : PROXY_REALM=metalink
#------------------------------------------------------------------------------
PROXY_REALM=

#------------------------------------------------------------------------------
# Specify the Oracle Support Hub URL.
#
# Example    : COLLECTOR_SUPPORTHUB_URL=https://orasupporthub.company.com:8080/
#------------------------------------------------------------------------------
COLLECTOR_SUPPORTHUB_URL=

#------------------------------------------------------------------------------
# Specify the auto-updates option. It can be one of the following:
# a.MYORACLESUPPORT_DOWNLOAD
# b.OFFLINE_UPDATES
# c.SKIP_UPDATES
#------------------------------------------------------------------------------
oracle.installer.autoupdates.option=SKIP_UPDATES
#------------------------------------------------------------------------------
# In case MYORACLESUPPORT_DOWNLOAD option is chosen, specify the location where
# the updates are to be downloaded.
# In case OFFLINE_UPDATES option is chosen, specify the location where the updates
# are present.
oracle.installer.autoupdates.downloadUpdatesLoc=
#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username which has the patches download privileges 
# to be used for software updates.
#  Example   : AUTOUPDATES_MYORACLESUPPORT_USERNAME=abc@oracle.com
#------------------------------------------------------------------------------
AUTOUPDATES_MYORACLESUPPORT_USERNAME=

#------------------------------------------------------------------------------
# Specify the My Oracle Support Account Username password which has the patches download privileges 
# to be used for software updates.
#
# Example    : AUTOUPDATES_MYORACLESUPPORT_PASSWORD=password
#------------------------------------------------------------------------------
AUTOUPDATES_MYORACLESUPPORT_PASSWORD=


7. Execute the file with the following command

[oracle@localhost database]$ ./runInstaller -silent DECLINE_SECURITY_UPDATES=true SECURITY_UPDATES_VIA_MYORACLESUPPORT=false -responseFile "/vol1/database/response/db_orcl_install.rsp"


output:

Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 3474 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 4094 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-04-30_11                                                                                    

password entered does not conform to the Oracle recommended standards.
CAUSE: Oracle recommends that the password entered should be at least 8 charait [0-9].
   ACTION: Provide a password that conforms to the Oracle recommended standards.
[WARNING] [INS-13014] Target environment do not meet some optional requirements.
   CAUSE: Some of the optional prerequisites are not met. See logs for details.
   ACTION: Identify the list of failed prerequisite checks from the log: /tmp/Or the log file or from installation manual find the appropriate configuration
You can find the log of this install session at:
 /vol1/app/oraInventory/logs/installActions2013-04-30_11-57-29AM.log

[oracle@localhost database]$ The installation of Oracle Database 11g was successful.
Please check '/vol1/app/oraInventory/logs/silentInstall2013-04-30_11-57-29AM.log' for more details.
[oracle@localhost database]$

As a root user, execute the following script(s):

        1. /vol1/app/oraInventory/orainstRoot.sh
        2. /vol1/app/oracle/product/11.2.0/db_1/root.sh


Successfully Setup Software.

8. Open one terminal and execute the follwing scripts

[root@localhost ~]# sh  /vol1/app/oraInventory/orainstRoot.sh
Changing permissions of /vol1/app/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.

Changing groupname of /vol1/app/oraInventory to oinstall.
The execution of the script is complete.

[root@localhost ~]# sh /vol1/app/oracle/product/11.2.0/db_1/root.sh
Check /vol1/app/oracle/product/11.2.0/db_1/install/root_localhost.localdomain_2013-04-30_12-16-52.log for the output of root script
[root@localhost ~]

9. Check the log file

[oracle@localhost orcl]$ cat /vol1/app/oraInventory/logs/silentInstall2013-04-30_11-57-29AM.log

The installation of Oracle Database 11g was successful.

10. Check the Database status

[oracle@localhost orcl]$ ps -ef | grep pmon
oracle   28091     1  0 12:11 ?        00:00:00 ora_pmon_orcl
oracle   32497 24152  0 12:30 pts/3    00:00:00 grep pmon
[oracle@localhost orcl]$

Oracle Database Patch Set Update (PSU) 11.2.0.3.6 (INCLUDES CPUAPR2013) - Patch 16056266

Oracle Database Patch Set Update (PSU) 11.2.0.3.6

Patch Set Update (PSU) patches are cumulative. That is, the content of all previous PSUs is included in the latest PSU patch.

To install the PSU 11.2.0.3.6 patch, the Oracle home must have the 11.2.0.3.0 Database installed. Subsequent PSU patches can be installed on Oracle Database 11.2.0.3.0 or any PSU with a lower 5th numeral version than the one being installed.

This patch is Oracle RAC Rolling Installable. This patch is Data Guard Standby-First Installable.

OPatch Utility

You must use the OPatch utility version 11.2.0.3.0 or later to apply this patch. Oracle recommends that you use the latest released OPatch 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release.


PSU 11.2.0.3.6 contains the following new fixes:

Automatic Storage Management

	16231699 - ADDING A NEW DISK ON ODA APPLIANCE HITS ORA-00600 [KFGPSET3] ASSERT
	16299830 - CREATE DISKGROUP RECO/REDO ONLY DISCOVER 2 FAILGROUPS
	13098318 - CTRL-C OR A SESSION KILL DURING DML INVOLVING TEMP BLOCKS LEADS TO ORA-600[6856]

Buffer Cache Management

13098318 - CTRL-C OR A SESSION KILL DURING DML INVOLVING TEMP BLOCKS LEADS TO ORA-600[6856]

Enterprise Manager Database Control

	14273397 - Fix for bug 14273397
	14459552 - Fix for bug 14459552

Generic

	8547978 - DROP USER GIVES ORA-00600[KQD-OBJERROR$] AFTER ONLINE REDEFINITION OF TABLE
	10242202 - ORA-22992 WHEN CREATING MATERIALIZED VIEW WITH REMOTE LOB COLUMN
	13496884 - MERGE STMT CONTAINING BIND VARIABLES SOMETIMES FAILS DUE TO ORA-600 [QCSFBDNP:1]
	13582702 - ORA-600 [KKMMCTBF:BAD INTCOLN] MAY BE SEEN WHILE EXECUTING DELETE
	13584130 - ORA-7445 COMPILING LIBRARY UNIT WITH _LOAD_WITHOUT_COMPILE IN NON-BASE EDITION
	13616375 - SQL TUNING FOR SELECT QUERY WITH FUNC-INDEX MAY FAIL DUE TO ORA-600 QKAFFSINDEX5
	13786142 - DROP TRIGGER IN EDITIONING ENVIRONMENT COULD FAIL WITH ORA-4045/ORA-4098
	13810393 - HANGING DUE TO 'LIBRARY CACHE: MUTEX X' DURING SHARED CURSOR STRESS TEST
	13812031 - POSSIBLE WRONG RESULTS FROM QUERIES ON PARTITIONED TABLES
	13860201 - INTERMITTENT COREDUMP IN KKSPBD0() DUE TO OBSOLETE CURSOR REFERENCED FROM PLSQL
	13911821 - INSTANCE TERMINATION DUE A CRASH HIT BY PMON IN SHARED CURSORS CODE
	14110275 - PARSE OF QUERY WITH TABLE THAT HAD UNDERGONE ADD COLUMN MAY RAISE INTERNAL ERROR
	14226599 - 'LATCH: ROW CACHE OBJECTS' CONTENTION FOR DC_ROLLBACK_SEGS : ADD HASH BUCKETS
	14644185 - DISABLE DEADLOCK DETECTION FOR CURSOR BUILD LOCKS
	16175381 - PROCESS HUNG SPINNING IN KKSCSSEARCHCHILDLIST() -> KKSHGETNEXTCHILD()
	16344871 - MISMATCH IN CURSOR SHAREABILITY (KKS LAYER) WITH VPD/RLS POLICY
	14841812 - Fix for bug 14841812

High Availability

	9706792 - ORA-600 [KCRPDV_NOENT] IN CRASH RECOVERY WITH PARALLELISM
	11715084 - ACTIVE DUPLICATE SHOULD WORK WHEN CONNECTED TO STANDBY AS SOURCE DB
	12983611 - RARELY ASYNC PROCESS CAN READ THE LOG ENTRY WHILE LGWR IS MODIFYING IT
	13632809 - RMAN BZ2 COMPRESSION BACKUP HANGS
	13680405 - PGA CONSUMPTION KEEP GROWING BY DIA0
	14088346 - LMS DIED BECAUSE OF ORA-600 [KJBRWRDONE:SC3]

Oracle Security

13596521 - Fix for bug 13596521

Oracle Space Management

	13910420 - ORA-8103 DURING UPDATE OF BASICFILE CLOB IN ASSM SEGMENT USING SPACE SEARCH CACH
	13913630 - COMPRESSION OLTP: INSERT ... SELECT DOESN'T COMPRESS SOME ROWS
	13958038 - EXCESS SPACE USAGE DURING UPDATE
	14176879 - EXTENSIVE GROWTH OF SECUREFILES SEGMENTS UNDERGOING UPDATES
	14207163 - FAILED TO CREATE EHCC TBS ON ZFS POOL STORAGE
	14472647 - WRONG RESULTS ON IOT SECONDARY INDEX
	14589750 - TRUNCATE TABLE HANG IN RAC AFTER APPLICATION OF PATCH OF 14144283

Oracle Spatial

13561951 - Fix for bug 13561951

Oracle Virtual Operating System Services

13914613 - DATABASE CRASHED DUE TO ORA-240 AND ORA-15064

SQL*Net

14841558 - Fix for bug 14841558

Workspace Manager

	16368108 - RUNNING OWMV1120.PLB IN PSU 112036 GIVING ORA-00955
	14220725 - Fix for bug 14220725

New Format - Oracle Database 11g Certified Master Exam

Hi Friends,

Previous Environment :

1. Oracle Linux Release 5.4 (64-bit)
2. Oracle Database Enterprise Edition Release 11.2.0.1.0 (64-bit)
3. Oracle Enterprise Management Grid Control 10g version 10.2.0.5 (64-bit) with repository database 11.1.0.6

New Environment (From 13^th May 2013 onwards)

1. Oracle Linux Release 5.4 (32-bit)
2. Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 (32-bit)
3. Oracle Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0)  (32-bit)

Note: The topic "Configure and manage Streams for capture, propagation and apply" will be retired in the new release of this exam from 13th May 2013.
 

Oracle Database Patch Set Update 11.2.0.3.5 - Patch 14727310

OPatch Utility

You must use the OPatch utility version 11.2.0.3.0 or later to apply this patch.

Oracle recommends that you use the latest released OPatch 11.2, which is available for download from My Oracle Support patch 6880880 by selecting the 11.2.0.0.0 release

Bugs Fixed by This Patch

This patch includes the following bug fixes.

1 CPU Molecules

CPU molecules in PSU 11.2.0.3.5:

PSU 11.2.0.3.5 contains all molecules previously released in PSU 11.2.0.3.4 and the following new PSU 11.2.0.3.5 molecules:

	15862016 - DB-11.2.0.3-MOLECULE-024-CPUJAN2013
	15862017 - DB-11.2.0.3-MOLECULE-025-CPUJAN2013
	15862018 - DB-11.2.0.3-MOLECULE-026-CPUJAN2013
	15862019 - DB-11.2.0.3-MOLECULE-027-CPUJAN2013
	15862020 - DB-11.2.0.3-MOLECULE-028-CPUJAN2013
	15862021 - DB-11.2.0.3-MOLECULE-029-CPUJAN2013
	15862022 - DB-11.2.0.3-MOLECULE-030-CPUJAN2013
	15862023 - DB-11.2.0.3-MOLECULE-031-CPUJAN2013
	15862024 - DB-11.2.0.3-MOLECULE-032-CPUJAN2013

2 Bug Fixes

See My Oracle Support Document 1449750.1 that documents all the non-security bugs fixed in each 11.2.0.3 Patch Set Update (PSU).

PSU 11.2.0.3.5 contains the following new fixes:

Enterprise Manager Database Control

	14023636 - Fix for bug 14023636
	14205448 - Fix for bug 14205448
	14258925 - Fix for bug 14258925
	14262913 - Fix for bug 14262913
	14263036 - Fix for bug 14263036
	14263073 - Fix for bug 14263073
	14469008 - Fix for bug 14469008
	14546575 - Fix for bug 14546575
	14546638 - Fix for bug 14546638
	14546673 - Fix for bug 14546673

Oracle Spatial

14035825 - Fix for bug 14035825

Automatic Storage Management

	12857027 - ORA-600[KFADELTREE00] RAISED WHILE DELETING SYSTEM DIRECTORY WITH ONLY ONE FILE
	13448206 - TOO MANY OCCURRENCES OF NOTE: ATTEMPTING VOTING FILE REFRESH ON DISKGROUP
	13559697 - INTEGRATE ASM WITH OAK LIB

Buffer Cache Management

	13038684 - PER PROCESS ASYNC IO MAX LIMIT IS REACHED VERY QUICKLY FOR DIRECT I/O
	13534412 - ORA-600 [KCLCHKBLKDMA_3] : LOCK ELEMENT BLOCK SCN UPDATED WITH NEWED BLOCK SCN
	13807411 - ORA-00600[KCBCHG1_38] DURING CURRENT CLEANOUT

Generic

	10263668 - SELECTING CLOB SOMETIMES FAIL WITH ORA-600 [KOKEGPINLOB1]
	12345082 - ORA-600[KKZGBTCOLS] DURING CREATE MV ON TABLE HAVING OBJECT TYPES + UROWID/BFILE
	12791981 - MEM LEAK DUE TO OBSOLETED CURSORS PRESENT AS THEY HAVE REFERENCE TO CURSOR STATS
	12873183 - QUERY WITH ROWNUM IN SELECT LIST AND IN STOP PREDICATE MAY RETURN WRONG RESULTS
	12964067 - DBMS_REDEFINITION FAILS WITH ORA-600 [KKZUCMVL_CHKMVLOG: KKZLGLNM]
	13011409 - ORA-600:[KGLLOCK-BAD-BYD] HIT DURING CURSOR SHARING CHECKS
	13026410 - ORA-4029 MAY BE HIT WHEN EXECUTING QUERY AGAINST VIEWS THAT REFERENCE X$KGLLK
	13454210 - BUILD LOCK IS NOT RELEASED IN SOME ERROR CASE CAN CAUSE HANG
	13524899 - CREATION OF IN MEMORY TEMPORARY TABLE PRODUCES TOO MUCH RECURSIVE SQL
	13645875 - UPDATE STATEMENT ON AN IOT TABLE WITH SECONDARY INDEX RUNS INTO ORA-7445
	13719081 - UPGRADE INVALIDATE VIEWS IS SLOW
	13936424 - SELECT FOR UPDATE NOT RETURNING VALUES FOR COL ADDED WITH DEF VALUE & NOT NULL
	14040433 - CURSORS NOT SHARED DUE TO DIFFERENT CALL DURATION
	14052474 - QUERY INVOLVING NULLIF'S WITH CONSTANT OPERANDS IN JOIN MAY RETURN WRONG RESULTS

High Availability

	12959852 - LMS PROCESS HITS ORA-600[KJBRSCPING:SLSEND] AND LEADS TO INSTANCE CRASH
	13399435 - KJFCDRMRCFG WAITED 249 SECS FOR LMD TO RECEIVE ALL FTDONES, REQUESTING KILL
	13593999 - INSTANCE EVICTED SINCE TIMEOUT FOR RECEIVER SYNC DURING DRM
	13645917 - PMON ONLINE BLOCK RECOVERY IN LOOP COULD LEAD TO INSTANCE HANG
	13685544 - DB INSTANCE NOT STARTING UP AFTER KERNEL UPDATES ON THE BOX
	13732226 - NODE GETS EVICTED WITH REASON CODE 0X2

Oracle Space Management

	9659614 - HUGE ORA-8103 TRACE FILES GENERATED AFTER PATCH 7519406 APPLIED
	13544396 - TABLES PER_ADDRESSES THROWS ORA-00600 ON ANY DML, DDL

Oracle Streams

13787482 - CDC PURGE ROUTINE INVALIDATING CUSTOM INDEXES

Oracle Transaction Management

	14138130 - CORE DUMP WHEN MODIFYING UNCOMPRESSED BLOCKS OF A HCC-COMPRESSED SEGMENT
	15853081 - DMLS HANG WHEN HCC HAS INITRANS=255

OPN Certified Specialist , Oracle Certified Expert, Oracle Exadata Database Machine X3 Administrator (1Z0-027)

Exadata Database Machine Overview

• Identify the benefits of using Database Machine for different application classes
• Describe the integration of the Database Machine with Oracle Database Clusterware and ASM
• Describe Exadata Storage Server and the different Database Machine configurations
• Describe the key capacity and performance specifications for Database Machine
• Describe the key benefits associated with Database Machine

Exadata Database Machine Architecture

• Describe the Database Machine network architecture
• Describe the Database Machine software architecture
• Describe the Exadata Storage Server storage entities and their relationships
• Describe how multiple Database Machines can be interconnected
• Describe site planning requirements for Database Machine
• Describe network requirements for Database Machine

Key Capabilities of Exadata Database Machine

• Describe the key capabilities of Exadata Database Machine
• Describe the Exadata Smart Scan capabilities
• Describe the capabilities of hybrid columnar compression
• Describe the capabilities and uses of the Smart Flash Cache
• Describe the capabilities of the Smart Flash Log
• Describe the purpose and benefits of Storage Indexes
• Describe the capabilities and uses of Exadata Secure Erase

Exadata Database Machine Initial Configuration

• Describe the installation and configuration process for Database Machine
• Describe the default configuration for Database Machine
• Describe supported and unsupported customizations for Database Machine
• Describe database machine operating system options and configurations

Configure Exadata Storage Server

• Configure Exadata software
• Create and configure ASM disk groups using Exadata
• Use the CellCLI Exadata administration tool
• Describe Exadata Storage Server security

I/O Resource Management

• Use Exadata Storage Server I/O Resource Management to manage workloads within a database and across multiple databases
• Configure database resource management plans
• Configure category plans
• Configure inter-database plans
• Describe and configure the I/O resource manager objectives
• Monitor I/O using I/O Metrics

Recommendations for Optimizing Database Performance

• Optimize database performance in conjunction with Exadata Database Machine
• Monitor and configure table indexes, accounting for the presence of Exadata

Using Smart Scan

• Describe Smart Scan and the query processing that can be offloaded to Exadata Storage Server
• Describe the requirements for Smart Scan
• Describe the circumstances that prevent using Smart Scan
• Identify Smart Scan in SQL execution plan
• Use database statistics and wait events to confirm how queries are processed

Consolidation Options and Recommendations

• Describe the options for consolidating multiple databases on Database Machine
• Describe the benefits and costs associated with different options
• Identify the most appropriate approach for consolidation in different circumstances

Migrating Databases to Exadata Database Machine

• Describe the steps to migrate your database to Database Machine
• Explain the main approaches for migrating your database to  Database Machine
• Identify the most appropriate approach for migration in different circumstances
• Identify the most appropriate storage configuration for different circumstances

Bulk Data Loading using Oracle DBFS

• Use Oracle DBFS for bulk data loading into Database Machine
• Configure the Database File System (DBFS) feature for staging input data files
• Use external tables based on input data files stored in DBFS to perform high-performance data loads

Exadata Database Machine Platform Monitoring

• Describe the purpose and uses of SNMP for the Database Machine
• Describe the purpose and uses of IPMI for the Database Machine
• Describe the purpose and uses of ILOM for the Database Machine

Configuring Enterprise Manager Grid Control 11g to Monitor Exadata Database Machine

• Describe the Enterprise Manager Grid Control architecture as it specifically applies to Exadata Database Machine
• Describe the placement of agents, plug-ins and targets
• Describe the recommended configuration for high availability
• Describe the plug-ins associated with Exadata Database Machine and how they are configured
• Use setupem.sh
• Configure a dashboard for Exadata Database Machine

Monitoring Exadata Storage Servers

• Describe Exadata Storage Server metrics, alerts and active requests
• Identify the recommended focus areas for Exadata Storage Server monitoring
• Monitor the recommended Exadata Storage Server focus areas

Monitoring Exadata Database Machine Database Servers

• Describe the monitoring recommendations for Exadata Database Machine database servers

Monitoring the InfiniBand Network

• Monitor InfiniBand switches
• Monitor InfiniBand switch ports
• Monitor InfiniBand ports on the database servers
• Monitor the InfiniBand subnet master location
• Monitor the InfiniBand network topology

Monitoring other Exadata Database Machine Components

• Monitor Exadata Database Machine components: Cisco Catalyst Ethernet Switch, Sun Power Distribution Units, Avocent MergePoint Unity KVM Switch

Monitoring Tools

• Use monitoring tools: Exachk, DiagTools, ADRCI, Imageinfo and Imagehistory, OSWatcher

Backup and Recovery 

• Describe how RMAN backups are optimized using Exadata Storage Server
• Describe the recommended approaches for disk-based and tape-based backups of databases on Database Machine
• Describe the recommended best practices for backup and recovery on Database Machine
• Perform backup and recovery
• Connect a media server to the Database Machine InfiniBand network

Database Machine Maintenance tasks

• Power Database Machine on and off
• Safely shut down a single Exadata Storage Server
• Replace a damaged physical disk on a cell
• Replace a damaged flash card on a cell
• Move all disks from one cell to another
• Use the Exadata  cell software rescue procedure

Patching Exadata Database Machine

• Describe how software is maintained on different Database Machine components
• Locate recommended patches for Database Machine
• Describe the recommended patching process for Database Machine
• Describe the  characteristics of an effective test system

Database Machine Automated Support Ecosystem

• Describe the Auto Service Request (ASR) function and how it relates to Exadata Database Machine
• Describe the implementation requirements for ASR
• Describe the ASR configuration process
• Describe Oracle Configuration Manager (OCM) and how it relates to Exadata Database Machine

Quality of Service Management

• Describe the purpose of Oracle Database Quality of Service (QoS) Management
• Describe the benefits of using Oracle Database QoS Management
• Describe the components of Oracle Database QoS Management
• Describe the operations of Oracle Database QoS Management

Oracle RAC 11g R2 and Grid Infrastructure Administration (1z0-058)

1
Which three actions would be helpful in determining the cause of a node reboot?
A. determining the time of the node reboot by using the uptime command and subtracting the uptime from the current system time
B. looking for messages such as "Oracle CSSD failure. Rebooting for cluster integrity" in /var/log/messages
C. using the crsctl command to view tracing information
D. inspecting the ocssd log for "Begin Dump" or "End Dump" messages
E. inspecting the database alert log for reboot messages

Answer: A,B,D

2
After Oracle Grid Infrastructure has been installed, you should take a few moments to verify the
installation. Which two actions would be useful in verifying the installation?
A. Run the crsctl status resource –t command to confirm that all necessary cluster resources are online.
B. Use the operating system utilities to verify that your SCAN addresses are being properly resolved.
C. Start Oracle Enterprise Manager and check all monitored targets.
D. Run the cluvfy comp nodecon –n all –verbose command to verify the entire Grid Infrastructure installation.

Answer: A,B

3
Which two network addresses are required to be static, non-dhcp addresses when using the Grid Naming?
A. GNS VIP Address
B. SCAN VIP Address
C. Node VIP Address
D. Node Public Address
E. Node Private Address

Answer: A,D

4
You are in the planning stages for upgrading your Oracle RAC database from Oracle Database
10g Release 2 to Oracle Database 11g Release 2 to run under the Oracle Grid Infrastructure.
You decide to use an administrator-managed configuration because the cluster is fairly small.
Which statement is correct about this configuration?
A. A parent pool of the GENERIC server pool will be used.
B. You must define a new server pool called MANUAL.
C. A subpool of the GENERIC server pool will be used.
D. A subpool of the FREE server pool will be used.

Answer: C

5
The Instance Initialization parameters are set to:

DB_CREATE_FILE_DEST = +DATA
DB_CREATE_ONLlNE_LOG_DEST_l = +LOGS
DB_CREATE_ONLlNE_LOG_DEST_2 = + FRA
The SQL* Plus command “ALTER DATABASE ADD LOGFILE;” will create:

A. a new log file in the +DATA disk group, or a log file in the + FRA disk group, if +DATA is not available
B. a new log file in the +DATA disk group and a log file in the + FRA disk group
C. a new log file in the +LOGS disk group and a log file in the + FRA disk group
D. a new log file in the +LOGS disk group, or a log file in the +FRA dls* available
E. a new log file in the +DATA disk group, a log file in the +LOGS disk group, and a log file in the +FRA disk group
F. a new log file in the +LOGS disk group, or a log file in the +FRA disk group, if +LOGS is not available

Answer: C


6
Which three statements define a cluster?
A. is a group of independent, but interconnected computers that act as a single system
B. can be deployed to increase availability and performance
C. can be deployed to balance a dynamically changing workload
D. should appear to an application as multiple servers
Answer: A,B,C


7
You want to create an ACFS on an ADVM volume using a shell script and the appropriate command-line utilities.
These are the requirements:
1. The dynamic volume file must use space in the VOLFILE disk group with a size of 500 M and be called prodvol.
2. The mount point called /acfs already exists. Which four steps must be performed to achieve this?
A. As the Grid Infrastructure owner, run mount -t acfs /dev/asm/prodvol-417 /acfs to mount the file system.
B. As the Grid Infrastructure owner, run asmcmd volinfo -d volfile prodvol to determine the volume information.
C. As the Grid Infrastructure owner, run asmcmd volcreate -d volfile -s 500M prodvol to create the volume file.
D. As the Grid Infrastructure owner, run mkfs -t acfs /dev/asm/prodvol-417 to create the filesystem.
E. As root, run mount -t acfs /dev/asm/prodvol-417 /acfs to mount the file system.
F. As root, run mkfs -t acfs /dev/asm/prodvol-417 to create the file system.

Answer: B,C,E,F

8
Some new non-ASM shared storage has been made available by the storage administrator, and
the Oracle Grid Infrastructure administrator decides to move the voting disks, which do not reside
in ASM, to this new non-ASM location. How can this be done?
A. by running crsctl add css votedisk <path_to_new_location> followed by crsctl delete css –votedisk <path_to_old_location>
B. by running crsctl replace css votedisk <path_to_old_location,path_to_new_location>
C. by running srvctl replace css votedisk <path_to_old_location, path_to_new_location>
D. by running srvctl add css votedisk <path_to_new_location> followed by srvctl delete css votedisk <path_to_old_location>

Answer: A


9
Which three statements are true about using RMAN with ASM?
A. RMAN is the only supported method to back up database files stored in ASM.
B. RMAN is the only supported method to back up ACFS files.
C. RMAN can use ASM storage for backups.
D. RMAN cannot use ASM storage for backups.
E. Using RMAN, database files can be migrated to ASM from a file system.
F. Using RMAN, database files cannot be moved from ASM to a file system

Answer: A,C,E


10
Which two statements are true about ACFS snapshots?
A. They can be created for ACFS file systems only if the ASM disk group hosting the ADVM
volume file used by the file system has free space available.
B. They can be created for ACFS file systems only if the ADVM volume file used by the file system
has free space available.
C. They can be created only if the ASM disk group hosting the ADVM volume used by the file
system has no other ASM files contained in the disk group.
D. They can be created when ACFS is used both on clusters and on stand-alone servers.
E. They are accessible only on the cluster node that was used when creating the snapshot

Answer: B,D


11
Your cluster Is subject to a service-level agreement that allows for little scheduled down time You
want to use patching and maintenance methods that permit the Oracle Grid Infrastructure and
Oracle RAT Databases to be available as much as possible.
Which two techniques will work some or all of the time to provide you with minimum down time?
A. rolling upgradeable and in place patch sets
B. idling upgradeable and out of place patch bundles
C. rolling upgradeable and out of place patch sets
D. rolling upgradeable and in place patch bundles
E. rolling upgradeable and out of place one-off patches

Answer: C,D


12
Which two types of files can be stored In an ASM clustered file system?
A. OCR and Voting Disk files
B. data files for external tables
C. Oracle database executable
D. Grid Infrastructure executables
E. data files for tablespaces
F. archive log files

Answer: B,C

13
You want to reorganize the DATA diskgroup while continuing database operations. The DATA
diskgroup was created using normal redundancy having one disk per failure group. The two disks
used are /dev/sdal and /dev/sda2.
You plan to drop the existing disks and add the /dev/sdb1 and /dev/sdb2 disks to failure group
FG_C and the /dev/sdcl and /dev/sdc2 disks to failure group FG_D.
Which procedure would you use to minimize the effect of the I/Os of this reorganization on
ongoing database operations?
A.
Set rebalance power to 0 for diskgroup DATA.
Add failure group FG_C with all the /dev/sdb disks.
Add failure group FG_D with all the /dev/sdc disks.
Drop disks/dev/sda1 and /dev/sda2.
Set rebalance power to 1 for diskgroup DATA.
B.
Set rebalance power to 0 for diskgroup DATA.
Add failure group FG_C with all the /dev/sdb disks.
Add failure group FG_D with all the /dev/sdb disks.
Drop disks/dev/sda1 and /dev/sda2.
Set rebalance power to 9 for diskgroup DATA.
C.
Set rebalance power to 9 for diskgroup DATA.
Add failure group FG_C with all the /dev/sdb disks.
Add failure group FG_D with all the /dev/sdc disks.
Drop disks /dev/sda1 and /dev/sda2.
Set rebalance power to 0 for diskgroup DATA.
D.
Set rebalance power to 0 for diskgroup DATA
Drop disks /dev/sdal and /dev/sdb disks.
Add failure group FG_C with all the /dev/sdb disks.
Add failure group FG_D with all the /dev/sdc disks
Set rebalance power to 1 for diskgroup DATA.

Answer: A

14
Which two Cluster ware stack administration actions must be performed as the root user?
A. checking the health of the Clusterware on one node
B. starting the Clusterware manually on one node
C. disabling the Clusterware from automatic start at node reboot
D. checking the health and viability of the Clusterware on all nodes
E. listing the location of the voting disks

Answer: B,C

15
Which four statements are true about ADVM interoperability?
A. Using fdisk or similar disk utilities to partition ADVM-managed volumes is not supported
B. On Linux platforms, the raw utility can be used to map ADVM volume block devices to raw volume devices.
C. The creation of multipath devices over ADVM devices is not supported.
D. You may create ASMLIB devices over ADVM devices to simplify volume management.
E. ADVM does not support ASM storage contained in Exadata.
F. F. ADVM volumes cannot be used as a boot device or a root file system.

Answer: A,C,E,F


16
Your four-node cluster was originally purchased, installed, and configured three years ago. You
recently added another four nodes to the cluster.
Now you want to remove two of the older nodes that are still accessible to be redeployed
elsewhere in the data center. Which two are true regarding the procedure for removing one or
more cluster nodes?
A. The procedure requires that all commands be invoked from one of the surviving cluster nodes.
B. All commands are run as root regardless of which nodes are used to invoke them.
C. The procedure requires that some commands be invoked on the node or nodes to be removed
and that some be invoked from all surviving cluster nodes.
D. The procedure requires that some commands be invoked on the node or nodes to be removed
and that some be invoked from one surviving cluster node.
E. Some commands require that the name of the node or nodes to be removed are passed as
arguments, and some commands require the name of existing nodes to be passed.

Answer: D,E


17
Your production environment cluster is running Oracle Enterprise Linux and currently has four
nodes. You are asked to plan for extending the cluster to six nodes. Which three methods are
available to add the new nodes?
A. silent cloning using crsctl clone cluster and ssh
B. a GUI interface from Enterprise Manager
C. with the Oracle Universal Installer using runInstaller –clone <nodename>
D. silent cloning using perl clone.pl–silent either with parameters in a file or in line
E. using addNode.sh

Answer: B,D,E


18
The Oracle 11g Release 2 (version 11.2.0.1) ASM instance has a new diskgroup named DATA
that is currently not mounted. You log in to a cluster node as the Grid Infrastructure software
owner and set the environment variables to point to the ASM instance on that node. Using
SQL*Plus, you issue the commands:
CONNECT / AS SYSDBA
ALTER DISKGROUP DATA MOUNT;
The system response is:
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15260: permission denied on ASM disk group
How do you diagnose this error?
A. Check v$asm_operation for operations halted by the error.
B. Check v$asm_attributes to determine the asm.compatible setting.
C. Check v$asm_usergroup to determine the owning user group for this diskgroup.
D. Check v$xs_session_role to determine the role privileges of the current user.
E. Check the connect string for the privileged role.

Answer: E

19
You enter the following command:
crsctl status resource MyApp
You get this output:
NAME=MyApp
TYPE=cluster_resource TARGET=ONLINE STATE=ONLINE on RACNODE4
MyApp is a policy-managed resource using a server pool with two nodes called RACNODE3 and
RACNODE4 and has a cardinality of 1.
What are the meanings of the target and state status values?
A. MyApp is currently active on RACNODE4 and is meant to be active only on RACNODE4.
B. MyApp is meant to be active, is currently active on RACNODE4, but the Grid Infrastructure may
start MyApp on RACNODE3 due to failovers.
C. MyApp is active on RACNODE4 and was manually started.
D. MyApp should also be online on RACNODE3 because it is a cluster_resources type that must
be active on at least two nodes in the cluster, thereby overriding the CARDINALITY attribute.

Answer: B


20
After evaluating the various methods for extending a cluster, you decide to use addNode.sh.
The cluster originally consisted of four nodes: RACNODE1, RACNODE2, RACNODE3, and
RACNODE4. Now two nodes called RACNODES and RACNODE6 have been installed and
connected to the cluster by OS administrations.
Which three actions should be performed to check whether the new nodes are ready for running
addNode.sh and to help correct any problems?
A. cluvfy stage -pre crsinst -n RACNODE5/ RACNODE6 -C + DATA -q +VOTE -orainv
B. <oinstall group> -fixup -verbose
C. cluvfy stage -post hwos -n RACNODE5, RACNODE6 -verbose
D. cluvfy comp peer -refnode RACNODE1 -n RACNODE5, RACNODE6 -orainv <oinstall group> -osdba <asmdba group> -verbose
E. cluvfy stage -post hwos -n all -verbose
F. cluvfy stage -pre nodeadd -n RACNODE5, RACNODE6 -fixup
G. cluvfy comp peer -refnode RACNODES -n RACNODE6 -orainv <oinstall group> -osdba<asmdba group> -verbose

Answer: C,D,F


21
What are the default connect strings used by SQL*Plus and ASMCMD when connecting to ASM
instances?
A. operating system authentication for ASMCMD;
none for SQL*Plus
B. "/ AS SYSASM" for ASMCMD;
"/" for SQL*Plus
C. "SYS/ AS SYSASM" for ASMCMD;
"/ AS SYSDBA" for SQL*Pius
D. operating system authentication for ASMCMD;
operating system authentication for SQL*Plus
E. "/ AS SYSASM" for ASMCMD;
operating system authentication for SQL*Plus

Answer: B


22
You want to install a database patch on your eight-node cluster by using Opatch with, the
minimum amount of down time to your cluster nodes.
You have already been prompted for the first set of nodes and you replied with node names
RACNODE1 RACNODE2, and RACNODE3.
Which two statements are true about the procedure for minimizing down time?
A. The patch must be propagated to, applied, and the inventory updated on all the remaining
nodes before restarting the instances on the first set of nodes.
B. When the first set of nodes has been patched, the instances on the remaining nodes are shut
down automatically by opatch.
C. The instances must be started on the first set of nodes and then stopped on the remaining set
to make certain that some nodes are always available.
D. When the first set of nodes has been patched, the administrator is prompted to shut down the
instances on the remaining nodes.
E. The patch must be propagated to and the inventory updated on all the remaining nodes before
restarting the instances on the first set of nodes.

Answer: D,E


23
You are ready to add two new nodes called RACNODE5 and RACNODE6 to your existing fournode
cluster using addNode.sh
You have run cluvfy -peer to check the new nodes against a reference node.
When you originally created the cluster, the network administrators chose to statically define the
scan vip addresses in the corporate DNS server, and you installed the Oracle Grid Infrastructure
without using GNS.
What is the correct way to silently add the nodes? r
A. addNode . sh -silent "CLUSTER_NEW_nodes={ RACNODE5, RACNODEg > "
B. addNode . sh -silent "CLUSTER_NEW_VIRTUAL_HOSTNAMES=<(RACNODES -VI P,
RACNODE6-VIP) "
C. addNode. sh -silent "CLUSTER_NEW_NODES= { RACNODES, RACNODE6 } "
"CLUSTER_NEW_VlRTUAL_HOSTNAMES= RACNODE5-VIP, RACNODE6-VI P > "
D. addNode.sh -silent -responseFile mynewnodea . txt With the response file containing only
E. CLUSTER_NEW_NODES= {“RACNODE5, RACNODE6”)
F. addNode.sh -silent -responseFile mynewnodes . txt With the response file containing only
CLUSTER NEW VIRTUAL HOSTNAMES= { " RACNODE3-VI P , RACNODE4 -VI P >

Answer: C

24
Which four statements about mounting ASM cluster file systems are true?
A. An ACFS volume can be mounted by using ASMCA.
B. The standard Linux/UNIX mount command can be used to mount an ACFS volume, provided the ACFS type is specified; (mount -t acfs).
C. ACFS volumes can be mounted by using the ASMCMD utility.
D. The acfsmountvol command can be used to mount ACFS volumes on Windows platforms.
E. Oracle Enterprise Manager can be used to mount ACFS volumes.

Answer: A,B,D,E


25
You are allocating space from the ASM disk group for an ADVM volume. What will be the volume
extent and Volume Allocation Unit (VAU) if the stripe column is 4 and AU is 1 MB? Which are the
default values?
A. The volume extent is 64 MB and the VAU will be 512 MB.
B. The volume extent is 64 MB and the VAU will be 256 MB.
C. The volume extent is 32 MB and the VAU will be 256 MB.
D. It is not possible to calculate these values with the given information.

Answer: B

26
You are creating a resource definition called WEBAPP for a web-based application that requires
an application called WEBVIP.
Both WEBVIP and WEBAPP are normally active on a single node, but may fail over if required to
another cluster node in your eight-node cluster.
A second VIP application resource called appsvip exists, used by a second application resource
called secapp. webvip and webapp must start In the correct sequence.
Which two start dependencies would you use for the WEBAPP application resource definition?
A. hard(SECAPP)
B. pullup(SECAPP)
C. pullup (WEBVIP)
D. hard(WEBVlP)
E. dispersion(WEBVIP)
F. weak (WEBVIP)

Answer: C,D


27
The database administrator is tasked with creating an ASM disk group. Exadata is not being used.
If failure groups are not specified when creating an ASM disk group containing 10 disks, how
many failure groups are automatically created?
A. one
B. two
C. five
D. ten

Answer: D


28
The Oracle Grid Infrastructure administrator runs ocrconfig -backupioc <new_location> after
completing the installation of the Grid Infrastructure. What are the two reasons for doing this
A. The master node may change if the node running the master CRS daemon shuts down causing
another node to become the master. Because the default location is a nonshared storage, and
only the master node performs backups, the backups could be spread around on many nodes
making management or recovery more difficult.
B. The cluster node currently acting as the master node for CRS is the only node that backs up
the OCR to the default location, and by changing the location, all cluster nodes will then take
backups.
C. This is done to move the backup location into an ASM Cluster File System directory so that the
backups benefit from ASM striping and mirroring.
D. If for any reason CRS must be stopped on all nodes for a time spanning a scheduled backup,
then on restart, the backup timer will be reset. This could result in longer time duration between
automatic backups than the standard four-hour interval.

Answer: A,D

29
From a command line, you can create an ASM volume with the same properties by using either
SQL or ASMCMD. Which two commands will create a 500 MB volume called TESTVOL in the
ACFSDG ACFS diskgroup by storing only one copy of the volume file extents in the diskgroup
A. SQL> alter diskgroup ACFSDG add volume TESTVOL size 500M unprotected;
B. ASMCMD> volcreate -G ASMFS -s 500M
C. SQL> alter diskgroup ACFS add volume TESTVOL size 500M;
D. ASMCMD> volcreate -G ACFSDG -s 500M --redundancy unprotected TESTVOL
E. SQL> create volume TESTVOL diskgroup ACFSDG size 500M unprotected;

Answer: A,D

You installed the Oracle Grid Infrastructure on a four-node cluster before discussing the network
requirements with the network administrator who was on holiday.
You created a single scan named mydb-scan.myclust.example.com by adding this name to the
/etc/hosts file. As a result, the Grid Infrastructure has four node listeners and node VIP but only a
single SCAN listener and SCAN VIP.
The network administrator has returned and modified the corporate DNS server to associate three
IP addresses with the mydb-scan.myclust.example.com scan name. The SCAN VIPs are on the
same network as the node VIPs.
You now must replace the single SCAN VIP and listener with three of each for high availability
purposes and make certain that the SCANs and listeners are active. Which procedure will do this
properly if run as the root user?

A. srvctl stop scan_listener
srvctl stop scan
srvctl start scan
srvctl start scan_listener

B. srvctl stop scan_listener
srvctl stop scan
srvctl remove scan
srvctl add scan -n MYDB-SCAN.MYCLUST.EXAMPLE.COM
srvctl start scan
srvctl start scan_listener

C. srvctl add scan -n MYDB-SCAN.MYCLUST.EXAMPLE.COM
srvctl start scan
srvctl start scan_listener

D. srvctl stop scan_listener
srvctl stop scan
srvctl remove scan
srvctl add scan
srvctl start scan
srvctl start scan listener

Answer: B

31
Which three statements are true about the logging or tracing of Java-based Oracle tools?
A. By default, Oracle logs actions for DBCA and DBUA.
B. For tools such as SRVCTL and CLUVFY, tracing can be enabled by setting srvm trace = true
your shell environment before executing the commands.
C. The srvm_trace environment variable can be set only in the user's shell environment file.
D. To disable tracing for Java-based tools, unset the srvm_trace variable: export srvm_trace=

Answer: A,B,D