Oracle 1Z0-058 Online Practice Questions and Exam Preparation

Oracle 1Z0-058 Online Questions & Answers

• Question 71:

  As part of the preinstatlation process for adding two new nodes to your four-node UNIX cluster, you are in discussions with the OS administrators about the operating system Installation and setup for the two new nodes called RACNODE5 and RACNODE6. The nodes have already been connected to the network infrastructure and the administrators are ready for the OS installation. Which two methods fulfill the installation requirements?

  A. Install a new image of the OS, then configure SSH for the root user.
  B. Install a cloned image of the OS that at least matches the existing node images for drivers, patches, and updates.
  C. Install a new image of the OS, that at least matches an existing node for drivers, patches, and updates, and create the necessary OS users and groups with user and group IDs matching those on the existing nodes.
  D. Install a new image of the OS that at least matches the existing node Images for drivers.
  E. Install a new image of the OS, and create the necessary OS users and groups with any user and group IDs.
  B. Install a cloned image of the OS that at least matches the existing node images for drivers, patches, and updates.
  C. Install a new image of the OS, that at least matches an existing node for drivers, patches, and updates, and create the necessary OS users and groups with user and group IDs matching those on the existing nodes.

  ---

  Prerequisite Steps for Adding Cluster Nodes

  1.

  Make physical connections.

  Connect the nodes' hardware to the network infrastructure of your cluster. This includes establishing electrical connections, configuring network interconnects, configuring shared disk subsystem connections, and so on. See your hardware

  vendor documentation for details about this step.

  2.

  Install the operating system.

  Install a cloned image of the operating system that matches the operating system on the other nodes in your cluster. This includes installing required service patches, updates, and drivers. See your operating system vendor documentation for

  details about this process. Note: Oracle recommends that you use a cloned image. However, if the installation fulfills the installation requirements, then install the operating system according to the vendor documentation.

  3.

  Create Oracle users.

  You must create all Oracle users on the new node that exist on the existing nodes. For example, if you are adding a node to a cluster that has two nodes, and those two nodes have different owners for the Grid Infrastructure home and the

  Oracle home, then you must create those owners on the new node, even if you do not plan to install an Oracle home on the new node.

  Oracle?Clusterware Administration and Deployment Guide 11g Release 2 (11.2)

• Question 72:

  You are managing a three-Instance RAC database. In the AWR report, you notice a gc current block busy wait event on one of the database Instances, in the cluster top timed events section. What are two possible reasons for this wait event?

  A. Access to blocks was delayed as the blocks were pinned In exclusive mode for updates by some sessions.
  B. Access to blocks was delayed by log writes on remote Instance.
  C. Frequently used select statements are causing high disk Input/output contention.
  D. CPU shortages.
  A. Access to blocks was delayed as the blocks were pinned In exclusive mode for updates by some sessions.
  B. Access to blocks was delayed by log writes on remote Instance.

  ---

  Analyzing Performance Using GCS and GES Statistics

  The gc current block busy wait event indicates that the access to cached data blocks was delayed because they were busy either in the remote or the local cache. This could be caused by any of the following:

  The blocks were pinned

  The blocks were held up by sessions

  The blocks were delayed by a log write on a remote instance

  A session on the same instance was already accessing a block which was in transition between instances and the current session needed to wait behind it (for example, gc current block busy) Contention-Related Wait Events

  The main wait events for contention-related waits are:

  gc current block busy

  gc cr block busy

  gc buffer busy acquire/release

  The contention-related wait event statistics indicate that a block was received which was pinned by a session on another node, was deferred because a change had not yet been flushed to disk or because of high concurrency, and therefore

  could not be shipped immediately. A buffer may also be busy locally when a session has already initiated a cache fusion operation and is waiting for its completion when another session on the same node is trying to read or modify the same

  data. High service times for blocks exchanged in the global cache may exacerbate the contention, which can be caused by frequent concurrent read and write accesses to the same data. The gc current block busy and gc cr block busy wait

  events indicate that the local instance that is making the request did not immediately receive a current or consistent read block. The term busy in these events' names indicates that the sending of the block was delayed on a remote instance.

  For example, a block cannot be shipped immediately if Oracle Database has not yet written the redo for the block's changes to a log file.

  Oracle?Real Application Clusters Administration and Deployment Guide 11g Release 2 (11.2)

• Question 73:

  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?

  A. Run crsctl pin css -n RACNODE1, RACNODE2 as root if the nodes are unpinned.
  B. Run crsctl pin css -n RACNODE4 as the Grid Infrastructure owner if RACNODE4 is unpinned.
  C. Run olsnodes -t -n to list all cluster nodes that are pinned.
  D. Run crsctl unpin css - RACNODE4 as the Grid Infrastructure owner if RACNODE4 is pinned.
  E. Run crsctl unpin css - RACNODE4 as root if RACNODE 4 is pinned.
  F. Run crsctl nodelist -t -n to list all cluster nodes that are pinned.
  C. Run olsnodes -t -n to list all cluster nodes that are pinned.
  E. Run crsctl unpin css - RACNODE4 as root if RACNODE 4 is pinned.

  ---

  Deleting a Cluster Node on Linux and UNIX Systems

  1.

  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.

  2.

  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 74:

  Which three predefined database-type templates already include the data files when creating an Oracle Cluster database?

  A. General Purpose
  B. Transaction Processing
  C. Custom Database
  D. Data Warehouse
  E. OLAP Database
  A. General Purpose
  B. Transaction Processing
  D. Data Warehouse

  ---

  Creating an Oracle RAC Database with DBCA Oracle ships templates for the following two workload types: General purpose or transaction processing Data warehouse For more complex environments, you can select the Custom Database option. This option does not use templates and results in a more extensive interview, which means that it takes longer to create your database.

  Oracle?Real Application Clusters Installation Guide 11g Release 2 (11.2) for Linux and UNIX

• Question 75:

  You notice that there is a very high percentage of wait time for the gc current split event in your RAC database that has frequent insert operations. Which two recommendation would you make to reduce this problem?

  A. shorter transactions
  B. using hash partitioned global indexes
  C. uniform and large extent sizes
  D. automatic segment space management
  E. smaller extent sizes
  F. increasing sequence cache sizes
  D. automatic segment space management
  F. increasing sequence cache sizes

• Question 76:

  You are managing a policy-managed Real Application Cluster (RAC) database, RACDB with Oracle Managed Files (OMF) enabled. Examine the following outputs:

  

  You added a new server to the server pool using the following command: [oracle@gr5153 ~]$ srvctl modify srvpool -g POOL1 -i 0 -l 2 -u 4 -n gr5119

  The instance on the newly added node is started by the Oracle Clusterware. Automatic Storage Management (ASM) is used as the storage option.

  Which statement is true regarding the redo log files for the instance?

  A. Oracle Clusterware automatically creates and enables a new thread of red
  B. You must create redo log groups for the newly added service.
  C. Redo log members will not be created automatically because storage option used is ASM.
  D. The newly added instance must save full online log groups tracked in the control file.
  A. Oracle Clusterware automatically creates and enables a new thread of red

  ---

  For a policy-managed database, when you add a new node to the cluster, it is placed in the Free pool by default. If you increase the cardinality of the database server pool, then an Oracle RAC instance is added to the new node, racnode3, and it is moved to the database server pool. No fur- ther action is necessary. Add shared storage for the undo tablespace and redo log files. If OMF is not enabled for your database, then you must manually add an undo tablespace and redo logs. You should create redo log groups only if you are using administrator-managed databases. For policy- managed databases, if an instance starts due to a change in server pool cardinality, then Oracle Database automatically creates redo log files, enables a redo thread for the instance if there is not a redo thread allocated to that instance, and creates the undo tablespace if there is not an undo tablespace allocated to that instance. The database must be using Oracle Managed Files and Oracle ASM in this situation. Oracle Database 2 Day + Real Application Clusters Guide

• Question 77:

  Choose the two correct commands that will successfully create an ASM cluster file system (ACFS) and register the mount point on a Linux/UNIX system.

  A. mkfs -t asm /dev/asm/testvol-461 -n "testvol"
  B. mkfs -t acfs /dev/asm/testvol-461 "testvol"
  C. crsctl -r mountpoint /dev/asm/testvol-461 /u01/app/grid/acfsmounts/acfs_testvol
  D. acfsutil registry -a -f /dev/asm/testvol-461 /u01/app/grid/acfsmounts/acfs_testvol
  B. mkfs -t acfs /dev/asm/testvol-461 "testvol"
  D. acfsutil registry -a -f /dev/asm/testvol-461 /u01/app/grid/acfsmounts/acfs_testvol

  ---

  mkfs Purpose Creates an Oracle ACFS file system.

  Syntax and Description mkfs -t acfs -h mkfs [-v] [-f]-t acfs [-b blocksize] [-n name ] volume_device [size]

  

  Table 13-3 Options for the Linux mkfs command Option Description

  acfsutil registry Purpose Registers an Oracle ACFS file system with the Oracle ACFS mount registry. Syntax and Description acfsutil registry -h acfsutil registry acfsutil registry -a [-f] [-n { nodes|all } ] [-o moptions] device mount_point acfsutil registry -d {device | mount_point} acfsutil registry -l [device | mount_point] acfsutil registry -m device acfsutil registry -h displays help text and exits. Oracle?Automatic Storage Management Administrator's Guide 11g Release 2 (11.2)

• Question 78:

  You use the following command to create a disk group:

  CREATE DISRGROUP DATA NORMAL REDUNDANCY FAILGROUP fg_f ra_l DISK '/dev/sda6' NAME FRA_DISKl, '/dev/sda7' NAME FRA_DISK2 FAILGROUP fg_fra_2 DISK '/dev/sdb1' NAME FRA_DISK3, '/dev/sdb2' NAME FRA_DISK4 FAILGROUP fg_fra_3 DISK '/dev/sdc1' NAME FRA_DISK5, '/dev/sdc2' NAME FRA_DISK6 ATTRIBUTES 'AU_SIZE' = '4M' 'compatible.rdbms' = '11.1.0';

  Which two statements are true about the data disk group?

  A. Each disk in a failure group is a mirror of the corresponding disk in the other failure groups. For example, FRA_DISK2 is a mirror of FRA_DISK4 and FRA_DISK6.
  B. By default, the files created in this disk group must have, for each extent, one primary copy and two mirror copies; one on each of the failure groups.
  C. Because the size clause is not used, the disk group uses the same amount of space on each disk.
  D. The 'compatible. rdbms' attribute specifies the minimum COMPATIBLE setting for any database using this disk group.
  E. If the FRA_DISK2 disk fails, there are mirrored copies in one of the other failure groups for any primary extents that are on FRA_DISK2.
  F. The allocation unit, AU_SIZE, sets the size of the disk read and write to ASM diskgroups.
  D. The 'compatible. rdbms' attribute specifies the minimum COMPATIBLE setting for any database using this disk group.
  E. If the FRA_DISK2 disk fails, there are mirrored copies in one of the other failure groups for any primary extents that are on FRA_DISK2.

  ---

  About Mirroring and Failure Groups

  Mirroring protects data integrity by storing copies of data on multiple disks. When you create a disk group, you specify an Oracle ASM disk group type based on one of the following three redundancy levels:

  Normal for 2-way mirroring

  High for 3-way mirroring

  External to not use Oracle ASM mirroring, such as when you configure hardware RAID for redundancy

  The redundancy level controls how many disk failures are tolerated without dismounting the disk group or losing data. The disk group type determines the mirroring levels with which Oracle creates files in a disk group.

  For information about disk group types and templates, see "Managing Disk Group Templates". Oracle ASM mirroring is more flexible than traditional RAID mirroring. For a disk group specified as NORMAL redundancy, you can specify the

  redundancy level for each file. For example, two files can share the same disk group with one file being mirrored while the other is not.

  When Oracle ASM allocates an extent for a mirrored file, Oracle ASM allocates a primary copy and a mirror copy. Oracle ASM chooses the disk on which to store the mirror copy in a different failure group than the primary copy. Failure

  groups are used to place mirrored copies of data so that each copy is on a disk in a different failure group. The simultaneous failure of all disks in a failure group does not result in data loss.

  You define the failure groups for a disk group when you create an Oracle ASM disk group. After a disk group is created, you cannot alter the redundancy level of the disk group. If you omit the failure group specification, then Oracle ASM

  automatically places each disk into its own failure group, except for disk groups containing disks on Oracle Exadata cells. Normal redundancy disk groups require at least two failure groups. High redundancy disk groups require at least three

  failure groups. Disk groups with external redundancy do not use failure groups.

  Allocation Units

  Every Oracle ASM disk is divided into allocation units (AU). An allocation unit is the fundamental unit of allocation within a disk group. A file extent consists of one or more allocation units. An Oracle ASM file consists of one or more file

  extents. When you create a disk group, you can set the Oracle ASM allocation unit size with the AU_SIZE disk group attribute. The values can be 1, 2, 4, 8, 16, 32, or 64 MB, depending on the specific disk group compatibility level. Larger AU

  sizes typically provide performance advantages for data warehouse applications that use large sequential reads.

  Oracle?Automatic Storage Management Administrator's Guide 11g Release 2 (11.2)

• Question 79:

  Which three fragments will complete this statement correctly? In a cluster environment, an ACFS volume___________.

  A. Will be automatically mounted by a node on reboot by default
  B. Must be manually mounted after a node reboot
  C. Will be automatically mounted by a node if it is defined as cluster stack startup if it is included in the ACFS mount registry.
  D. Will be automatically mounted to all node if it is defined as cluster resource when dependent cluster resources requires access
  E. Will be automatically mounted to all node in the cluster when the file system is registered
  F. Must be mounted before it can be registered
  A. Will be automatically mounted by a node on reboot by default
  C. Will be automatically mounted by a node if it is defined as cluster stack startup if it is included in the ACFS mount registry.
  E. Will be automatically mounted to all node in the cluster when the file system is registered

  ---

  The Oracle ACFS mount registry supports both Oracle Restart and Oracle Grid Infra- structure cluster configurations. File systems that are to be mounted persistently (across reboots) can be registered with the Oracle ACFS mount registry. In cluster configura- tions, registered Oracle ACFS file systems are automatically mounted by the mount re- gistry, similar to a clusterwide mount table. By default, an Oracle ACFS file system that is inserted into the cluster mount registry is automatically mounted on all cluster members, including cluster members that are added after the registry addition. The Oracle ACFS registry resource actions are designed to automatically mount a file system only one time for each Oracle Grid Infrastructure initialization to avoid potential conflicts with administrative actions to dismount a given file system. Oracle Automatic Storage Management Administrator's Guide

• Question 80:

  You are managing a policy-managed three-instance RAC database. You ran database ADDM for the database and noticed gc current block congested and gc cr block congested waits. What are two possible reasons for these wait events?

  A. The wait events indicate a delay in processing has occurred in the Global Cache Services (GCS), which is usually caused by high load.
  B. The wait times indicate that the blocks must wait after initiating a gc block request, for the round trip from the start of the wait until the blocks arrive.
  C. The wait events indicate that there is block contention resulting in multiple requests for access to local blocks.
  D. The wait events indicate that the local instance making the request for current or consistent read blocks was waiting for logical I/O from its own buffer cache at the same time.
  A. The wait events indicate a delay in processing has occurred in the Global Cache Services (GCS), which is usually caused by high load.
  B. The wait times indicate that the blocks must wait after initiating a gc block request, for the round trip from the start of the wait until the blocks arrive.

  ---

  Load-Related Wait Events The main wait events for load-related waits are: gc current block congested gc cr block congested The load-related wait events indicate that a delay in processing has occurred in the GCS, which is usually caused by high load, CPU saturation and would have to be solved by additional CPUs, load-balancing, off loading processing to different times or a new cluster node. For the events mentioned, the wait time encompasses the entire round trip from the time a session starts to wait after initiating a block request until the block arrives Oracle Real Application Clusters Administration and Deployment Guide