Oracle Real Application Clusters 11g Release 2 and Grid Infrastructure Administration
Question No: 1
Which two Cluster ware stack administration actions must be performed as the root user?
checking the health of the Clusterware on one node
starting the Clusterware manually on one node
disabling the Clusterware from automatic start at node reboot
checking the health and viability of the Clusterware on all nodes
listing the location of the voting disks
Answer: B,C Explanation:
Controlling Oracle Clusterware
The crsctl utility can be used to control Oracle Clusterware. To start or stop Oracle Clusterware on a specific node:
# crsctl start crs
# crsctl stop crs
To enable or disable Oracle Clusterware on a specific node:
# crsctl enable crs
# crsctl disable crs
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 3 – 5
Question No: 2
You plan to remove a node called RACNODE4 from a four-node cluster.
The cluster is running Oracle Grid Infrastructure 11g Release 2 and there is also a database home with cluster databases running Oracle Database version 11g Release 1. This older home supports different applications that have not been certified to run on the latest release.
The cluster databases for Oracle Database 11g Release 1 each had four Instances at one time, but currently only the first two nodes, RACNODE1 and RACNODE2, are running instances of those databases.
Which two additional steps are required when deleting a node from a cluster in this situation?
Run crsctl pin css -n RACNODE1, RACNODE2 as root if the nodes are unpinned.
Run crsctl pin css -n RACNODE4 as the Grid Infrastructure owner if RACNODE4 is unpinned.
Run olsnodes -t -n to list all cluster nodes that are pinned.
Run crsctl unpin css – RACNODE4 as the Grid Infrastructure owner if RACNODE4 is pinned.
Run crsctl unpin css – RACNODE4 as root if RACNODE 4 is pinned.
Run crsctl nodelist -t -n to list all cluster nodes that are pinned.
Answer: C,E Explanation:
Deleting a Cluster Node on Linux and UNIX Systems
Ensure that Grid_home correctly specifies the full directory path for the Oracle Clusterware home on each node, where Grid_home is the location of the installed Oracle Clusterware software.
Run the following command as either root or the user that installed Oracle Clusterware to determine whether the node you want to delete is active and whether it is pinned:
$ olsnodes -s -t
If the node is pinned, then run the crsctl unpin css command. Otherwise, proceed to the next step.
Oracle庐 Clusterware Administration and Deployment Guide 11g Release 2 (11.2)
Question No: 3
Examine the Exhibit.
*** Exhibit is Missing ***
Which three statements are correct?
Global Cache Block Access Latency indicates how many block transfers incurred a delay (busy) or an unexpected longer delay (congested).
Global Cache Block Access Latency indicates how many block transfers received blocks cached by other instances as well as blocks read from disk.
Global Cache Block Transfer Rate shows the total aggregated number of blocks received by all instances in the cluster over the interconnect.
Global Cache Block Transfer Rate is essentially a profile of how much work is performed
in the local buffer cache, rather than the portion of remote references and physical reads, which both have higher latencies.
Global Cache Block Transfers and Physical Reads shows the percentage of read operations that retrieved blocks from disk, and the buffer cache of other instances using Cache Fusion.
Global Cache Block Transfers and Physical Reads shows the aggregated number of data blocks received by all instances in the cluster over the interconnect.
Answer: A,C,E Explanation:
Global Cache Block Access Latency
The global cache access latency represents the end-to-end elapsed time for a block request. The request is timed from when the request is initiated until it completes. Cache transfer indicates how many current and CR blocks per block class were received from remote instances, including how many transfers incurred a delay (busy) or an unexpected longer delay (congested).
If accessing a database block of any class does not locate a buffered copy in the local cache, a global cache operation is initiated. Before reading a block from disk, an attempt is made to find the block in the buffer cache of another instance. If the block is present in another instance, a version of the block may be shipped. Two different kinds of blocks are distinguished: current and consistent read blocks. The average block receive time represents the end-to-end elapsed time or latency for a block request.
Global Cache Block Transfer Rate
The global cache block transfer rate shows the total aggregated number of data blocks received by all instances in the cluster by way of an interconnect. If a logical read fails to find a copy of the buffer in the local cache, it attempts to find the buffer in the database cache of a remote instance. If the block is present in another database, it is sent to the current instance.
Global Cache Block Transfers and Physical Reads
The chart represents the percentage of logical reads that read data from the buffer cache of other instances via Direct Memory Access and from disk. It is essentially a profile of how much work is performed in the local buffer cache, rather than the portion of non-local references that incur some latency overhead.
Active Sessions for Cluster Wait Class
The chart represents the active sessions for the cluster wait class. You can view the top modules and top SQL for a time period by selecting the time period in the active sessions chart.
Oracle Enterprise Manager Online Help
Question No: 4
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 new log file in the DATA disk group, or a log file in the FRA disk group, if DATA is not available
a new log file in the DATA disk group and a log file in the FRA disk group
a new log file in the LOGS disk group and a log file in the FRA disk group
a new log file in the LOGS disk group, or a log file in the FRA dls* available
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
a new log file in the LOGS disk group, or a log file in the FRA disk group, if LOGS is not available
Explanation: The following table lists the initialization parameters that enable the use of Oracle Managed Files.
Initialization Parameter DB_CREATE_FILE_DEST
Defines the location of the default file system directory or Oracle ASM disk group where the database creates datafiles or tempfiles when no file specification is given in the create operation. Also used as the default location for redo log and control files if DB_CREATE_ONLINE_LOG_DEST_n are not specified.
Defines the location of the default file system directory or Oracle ASM disk group for redo
log files and control file creation when no file specification is given in the create operation. By changing n, you can use this initialization parameter multiple times, where n specifies a multiplexed copy of the redo log or control file. You can specify up to five multiplexed copies.
Defines the location of the Fast Recovery Area, which is the default file system directory or Oracle ASM disk group where the database creates RMAN backups when no format option is used, archived logs when no other local destination is configured, and flashback logs.
Also used as the default location for redo log and control files or multiplexed copies of redo log and control files if DB_CREATE_ONLINE_LOG_DEST_n are not specified.
Oracle庐 Database Administrator#39;s Guide
Question No: 5
Which three describe how often OCR backups are taken and how many are retained, according to the default backup schedule?
every 12 hours and the Clusterware keeps the last four copies
every 4 hours and the Clusterware keeps the last three copies
every day and the Clusterware keeps the last two copies
every day and the Clusterware keeps the last three copies
every week and the Clusterware keeps the last two copies
Answer: B,C,E Explanation:
Locating the OCR Automatic Backups The OCR is backed up automatically. Only one node performs the backup.
To determine the node and location of the backup:
$ ocrconfig -showbackup auto
host02 2009/07/28 12:20:42 /u01/app/…/cdata/cluster01/backup00.ocr host02 2009/07/28 08:20:41 /u01/app/…/cdata/cluster01/backup01.ocr host02 2009/07/28 04:20:40 /u01/app/…/cdata/cluster01/backup02.ocr host02 2009/07/27 16:20:37 /u01/app/…/cdata/cluster01/day.ocr host02 2009/07/28 00:20:39 /u01/app/…/cdata/cluster01/week.ocr
Files could be spread across nodes due to outages. The backup frequency and retention policies are:
Every four hours: CRS keeps the last three copies.
At the end of every day: CRS keeps the last two copies.
At the end of every week: CRS keeps the last two copies.
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 3 – 11
Question No: 6
Which two conditions are required by the ASM fast mirror resynchronization to track block changes for a set period of time before dropping the disk from the disk group?
Redundancy is normal or high.
compatibility. rdbms is set to a value of at least 11. l.
disk_repair_time is set to a nondefault value.
block_change_tracking IS enabled.
db_block_checking is enabled.
resumable_timeout is set to a nondefault value.
Answer: A,B Explanation:
ASM Fast Mirror Resync
Enabled when COMPATIBLE.RDBMS gt;= 11.1
Whenever ASM is unable to write an extent, ASM takes the associated disk offline. If the corresponding disk group uses ASM mirroring (NORMAL or HIGH redundancy), at least one mirror copy of the same extent exists on another disk in the disk group.
Before Oracle Database 11g, ASM assumed that an offline disk contains only stale data and no longer reads from such disks. Shortly after a disk is put offline, ASM drops it from the disk group by re-creating the extents allocated to the disk on the remaining disks in the disk group using mirrored extent copies. This process is quite resource intensive and can take hours to complete. If the disk is replaced or the failure is repaired, the disk must be added again and another rebalance operation must take place.
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 8 – 32
Question No: 7
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?
Explanation: There are always failure groups even if they are not explicitly created. If you do not specify a failure group for a disk, then Oracle automatically creates a new failure group containing just that disk, except for disk groups containing disks on Oracle Exadata cells.
Oracle庐 Automatic Storage Management Administrator#39;s Guide
Question No: 8
Examine the following output:
[oracIe@gr5153 ~]$ sudo crsctl config crs
CRS-4622: Oracle High Availability Services autostart is enabled. [oracIe@gr5153 ~]$ srvctl config database -d RACDB -a Database unique name: RACDB
Database name: RACDB
Oracle home : /u01/app/oracle/product/l11.2.0/dbhome_1 Oracle user: oracle
Spfile: DATA/ RACDB /spfileRACDB.ora Domain:
Start options: open Stop options: immediate
Database role: PRIMARY Management policy: AUTOMATIC Server pools: POOL1
Database instances: Disk Groups: DATA, FRA Services:
Database is enabled Database is policy managed
Oracle Clusterware is started automatically after the system boot. Which two statements are true regarding the attributes of RACDB?
Oracle Clusterware automatically starts RACDB.
You must manually start RACDB.
Database resource is managed by crsd for high availability and may be automatically restarted in place if it fails.
Database resource Is not managed by crsd for high availability and needs to be restarted manually if it fails.
Answer: A,C Explanation:
Switch Between the Automatic and Manual Policies
By default, Oracle Clusterware is configured to start the VIP, listener, instance, ASM, database services, and other resources during system boot. It is possible to modify some resources to have their profile parameter AUTO_START set to the value 2. This means that after node reboot, or when Oracle Clusterware is started, resources with
AUTO_START=2 need to be started manually via srvctl. This is designed to assist in troubleshooting and system maintenance. When changing resource profiles through srvctl, the command tool automatically modifies the profile attributes of other dependent resources given the current prebuilt dependencies. The command to accomplish this is: srvctl modify database -d lt;dbnamegt; -y AUTOMATIC|MANUAL
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 15 – 3
3.4.1 Benefits of Using Oracle Clusterware
Oracle Clusterware provides the following benefits:
Tolerates and quickly recovers from computer and instance failures.
Simplifies management and support by means of using Oracle Clusterware together with Oracle Database.
By using fewer vendors and an all Oracle stack you gain better integration compared to using third-party clusterware.
Performs rolling upgrades for system and hardware changes. For example, you can apply Oracle
Clusterware upgrades, patch sets, and interim patches in a rolling fashion, as follows: Upgrade Oracle Clusterware from Oracle Database 10g to Oracle Database 11g Upgrade Oracle Clusterware from Oracle Database release 11.1 to release 11.2 Patch Oracle Clusterware from Oracle Database 184.108.40.206 to 220.127.116.11
Patch Oracle Clusterware from Oracle Database 10.2.0.2 Bundle 1 to Oracle Database
10.2.0.2 Bundle 2
Automatically restarts failed Oracle processes.
Automatically manages the virtual IP (VIP) address so when a node fails then the node#39;s VIP address fails over to another node on which the VIP address can accept connections. Automatically restarts resources from failed nodes on surviving nodes.
Controls Oracle processes as follows:
For Oracle RAC databases, Oracle Clusterware controls all Oracle processes by default. For Oracle single-instance databases, Oracle Clusterware allows you to configure the Oracle processes into a resource group that is under the control of Oracle Clusterware. Provides an application programming interface (API) for Oracle and non-Oracle applications that enables you to control other Oracle processes with Oracle Clusterware, such as restart or react to failures and certain rules.
Manages node membership and prevents split-brain syndrome in which two or more instances attempt to control the database.
Provides the ability to perform rolling release upgrades of Oracle Clusterware, with no downtime for applications.
Oracle庐 Database High Availability Overview 11g Release 2 (11.2)
Question No: 9
The disk groups on the current ASM instance at version 11.2 were configured to support a version 10.2 database instance. The 10.2 instance has the COMPATIBLE parameter defined as 10.2.0. The compatible.asm attribute is set to 11.2 for each disk group. The database has been upgraded to 11.2. Which statement indicates the proper time to change the compatible.rdbms disk group attribute to 11.2?
Change the disk group attribute after the database instance COMPATIBLE parameter is upgraded to 11.2.
Change the disk group attribute after the database instance is started with the 11.2 software.
Change the disk group attribute after the database instance optimizer_features_enabled parameter is set to 11.2.
Change each disk group after the 11.2 features are required for use on the disk group.
Never, upgrading the attribute is not reversible.
Answer: A Explanation: COMPATIBLE.RDBMS
The value for the disk group COMPATIBLE.RDBMS attribute determines the minimum COMPATIBLE database initialization parameter setting for any database instance that is allowed to use the disk group.
Before advancing the COMPATIBLE.RDBMS attribute, ensure that the values for the COMPATIBLE initialization parameter for all of the databases that access the disk group are set to at least the value of the new setting for COMPATIBLE.RDBMS.
Oracle庐 Automatic Storage Management Administrator#39;s Guide 11g Release 2 (11.2)
Question No: 10
You plan to use Enterprise Manager to locate and stage patches to your Oracle Home.
The software library has been configured to be downloaded to /u01/app/oracle and your quot;My Oracle Supportquot; credentials have been entered.
You want to start the provisioning daemon in order to use the deployment procedure manager to view, edit, monitor, and run deployment procedures.
How would you start the provisioning daemon?
using pafctl start
using crsctl start paf
using srvctl start paf
using emctl start paf
Answer: A Explanation:
Starting the Provisioning Daemon
The provisioning daemon is started with:
$ pafctl start
Enter repository user password : Enter interval [default 3]:
Provisioning Daemon is Up, Interval = 3 D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 4 – 26
|Lowest Price Guarantee||Yes||No||No|
|Free VCE Simulator||Yes||No||No|