Tested of 1Z0-058 practice test materials and prep for Oracle certification for consumer, Real Success Guaranteed with Updated 1Z0-058 pdf dumps vce Materials. 100% PASS Oracle Real Application Clusters 11g Release 2 and Grid Infrastructure exam Today!
2016 May 1Z0-058 Study Guide Questions:
Q31. You need to set up a three-Instance RAC database. The data files and fast recovery area will be stored in ASM diskgroups called +data and +fra, respectively. The ASM disk groups will be mounted on all ASM Instances.
Which are the two best location options for archivelogs so that they can be accessed during recovery without DBA intervention?
A. Cluster File System with each instance writing to a shared location
B. Cluster File System with each instance writing to a separate location as long as all the locations are in directories under the same mount point C. the ASM diskgroup +fra with the db_recovery_file_dest parameter set to the same value on all instances
D. a raw or block device
Explanation: The primary consideration when configuring archiving is to ensure that all archived redo logs can be read from every node during recovery, and if possible during backups. During recovery, because the archived log destinations are visible from the node that performs the recovery, Oracle RAC can successfully recover the archived redo log data. The fast recovery area for an Oracle RAC database must be placed on an Oracle ASM disk group, a cluster file system, or on a shared directory that is configured through a network file system file for each Oracle RAC instance. In other words, the fast recovery area must be shared among all of the instances of an Oracle RAC database. The preferred configuration for Oracle RAC is to use Oracle Automatic Storage Management (Oracle ASM) for storing the fast recovery area, using a different disk group for your recovery set than for your data files. The location and disk quota must be the same on all instances. Oracle recommends that you place the fast recovery area on the shared Oracle ASM disks. In addition, you must set the DB_RECOVERY_FILE_DEST and DB_RECOVERY_FILE_DEST_SIZE parameters to the same values on all instances. Oracle Database 2 Day + Real Application Clusters Guide
Q32. In your two-instance RAC database, you find that FAST_START_MTTR_TARGET is set to
300 on both the nodes. The ESTD_CLUSTER_AVAILABLE_TIME column in the V$INSTANCE_RECOVERY view shows the value 100.
What is the correct interpretation? (Choose 2)
A. In the event of an instance failure, the database will become partially available In 100 seconds.
B. In the event of an instance failure, the database will become fully available in 100 seconds.
C. In the event of an instance failure, the failed instance will become fully available In 300 seconds.
D. In the event of an instance failure, the database will become partially available in 200 seconds.
E. In the event of an instance failure, the failed instance will become available In 300 seconds.
untitled FAST_START_MTTR_TARGET enables you to specify the number of seconds the database takes to perform crash recovery of a single instance. When specified, FAST_START_MTTR_TARGET is overridden by LOG_CHECKPOINT_INTERVAL.
Estimated time (in seconds) that the cluster would become partially available should this instance fail. This column is only meaningful in an Oracle Real Application Clusters (Oracle RAC) environment. In a non-Oracle RAC environment, the value of this column is null.
Oracle. Database Reference 11g Release 2 (11.2)
Q33. Which statement describes the requirements for the network interface names, such as eth0, in Oracle Clusterware?
A. Only the public interface names must be the same for all nodes.
B. Only the private interface names must be the same for all nodes.
C. Both the public interface name and the private interface name must be the same for all nodes.
D. Both the public interface name and the private interface name can vary on different nodes.
E. Only the private interface names can be different on different nodes.
F. Only the public interface names can be different on different nodes.
Checking Network Requirements
Each node must have at least two network interface cards (NICs).
Interface names must be the same on all nodes.
Public NIC must support TCP/IP and Private NIC UDP.
Public IP must be registered in the domain name server (DNS) or the /etc/hosts file.
# cat /etc/hosts
##### Public Interfaces – eth0 (odd numbers)####
xxx.xxx.100.11 host01.example.com host01
xxx.xxx.100.13 host02.example.com host02 IF GNS is used, the Cluster GNS address must be registered in the DNS. Prevent public network failures when using NAS devices or NFS mounts by starting the Name Service Cache Daemon. # /sbin/service nscd start
D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 2 – 18
Up to the immediate present 1Z0-058 free exam questions:
Q34. You are managing RAC database with policy managed services. The database is started by using an SPILE.
Which two statements are true regarding initialization parameters In a RAC environment?
A. All initialization parameters must have identical settings on all instances.
B. All instances in the cluster database use the same SPFILE.
C. To change values for initialization parameters for an instance, you must log in to that instance.
D. All initialization parameters for all instances can be changed from any instance In a RAC database.
RAC Initialization Parameter Files
An SPFILE is created if you use the DBCA.
The SPFILE must be created in an ASM disk group or a cluster file system file.
All instances use the same SPFILE.
If the database is created manually, create an SPFILE from a PFILE.
SPFILE Parameter Values and RAC
You can change parameter settings using the ALTER SYSTEM SET command from any instance
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 12 - 22, 23
Q35. You are managing a three-instance Oracle RAC database which uses a Cluster File System for shared storage.
Which two options can you use to ensure that the redo logs from all the instances are available during RMAN recovery from any instance?
A. Set the LOG_ARCHIVE_DEST_1 parameter to a single location on the Cluster File System for each of the three instances and leave the LOG_ARCHIVE_FORMAT parameter with the default value.
B. Set only the LOG_ARCHIVE_DEST_1 parameter to a single location on the Cluster File System for any one of the three instances and leave the LOG_ARCHIVE_FORMAT parameter with the default value.
C. Set the LOG_ARCHIVE_DEST_1 parameter to a single location on the Cluster File System for each of the three instances, and the LOG_ARCHIVE_FORMAT parameter for each instance, to the same format including the thread number.
D. Set the LOG_ARCHIVE_DEST_1 parameter to a single location on the Cluster File System, and set LOG_ARCHIVE_FORMAT parameter on only one instance.
Initialization Parameter Settings for the Cluster File System Archiving Scheme In the cluster file system scheme, each node archives to a directory that is identified with the same name on all instances within the cluster database (/arc_dest, in the following example). To configure this directory, set values for the LOG_ARCH_DEST_1 parameter, as shown in the following example:
*.LOG_ARCHIVE_DEST_1="LOCATION=/arc_dest" Archived Redo Log File Conventions in Oracle RAC For any archived redo log configuration, uniquely identify the archived redo logs with the LOG_ARCHIVE_FORMAT parameter. The format of this parameter is operating system-specific and it can include text strings, one or more variables, and a filename extension. Use the %R or %r parameters to include the resetlogs identifier to avoid overwriting the logs from a previous incarnation. If you do not specify a log format, then the default is operating system-specific and includes %t, % s, and %r.
Oracle. Real Application Clusters Administration and Deployment Guide 11g Release 2 (11.2)
Q36. When creating an Oracle Cluster database using DBCA the "Memory size (SGA and PGA)” field is supplied on value of 2000 MB. Identify the default block Size used for the database.
A. 2 KB
B. 4 KB
C. 8 KB
D. 16 KB
E. 32 KB
Explanation: Type of LimitLimit Value
Minimum2k.Must be a multiple of operating system physical block size MaximumOperating system dependent, but never more than 32 KB
DBCA tab sizing
In this tab, you specify the smallest block size and the maximum number of operating system user processes that can simultaneously connect to the database. In the Block Size list, enter the size in bytes or accept the default. Oracle Database data is stored in these blocks. One data block corresponds to a specific number of bytes of physical space on disk. While using pre-defined templates, this field is not enabled since the database will be created with the default block size of 8 KB. But while using the custom option, you can change block size. Selecting a block size other than the default 8 KB value requires advanced knowledge and should only be done when absolutely required.
Oracle. Database 2 Day DBA
Precise 1Z0-058 forum:
Q37. Which two statements are true regarding the Average Active Sessions chart on the performance page
A. It shows active aggregate wait class statistics across all the instances In the cluster database.
B. It shows active aggregate wait class per instance for all the instances In the cluster database.
C. If the Average Active Sessions chart displays a large number of sessions waiting, indicating internal contention, but the throughput is high, then the situation may be acceptable.
D. If the Average Active Sessions chart displays a large number of sessions waiting, indicating internal contention, but the throughput is low, then the CPU needs to be upgraded
Explanation: Chart for Average Active Sessions
The Average Active Sessions chart in the Cluster Database Performance page shows potential problems inside the database. Verifying the Interconnect Settings for Oracle RAC Categories, called wait classes, show how much of the database is using a resource, such as CPU or disk I/O. Comparing CPU time to wait time helps to determine how much of the response time is consumed with useful work rather than waiting for resources that are potentially held by other processes. Compare the peaks on the Average Active Sessions chart with those on the Database Throughput charts. If the Average Active Sessions chart displays a large number of sessions waiting, indicating internal contention, but throughput is high, then the situation may be acceptable.
Oracle Database 2 Day + Real Application Clusters Guide
Q38. The Oracle Grid Infrastructure administrator wants to perform daily checks on the integrity of the Clusterware files. Which three steps can be performed to determine the health of the OCR files and voting disks?
A. Run ocrcheck to verify the health of the OCR file only from the master node, which performs all input/output (I/O) operations on the OCR.
B. Run grep voting <grid_home>/log/<hostname>/cssd/ocssd.log from any cluster node.
C. Run cluvfy comp ocr -n all from any cluster node.
D. Run ocrcheck to verify the health of the OCR file from any cluster node.
E. Run votecheck to verify the health of the voting disk from any cluster node.
Checking the Integrity of Oracle Clusterware Configuration Files The following techniques are used to validate the integrity of Oracle Cluster configuration files. Check the ocssd.log for voting disks issues. $ grep voting <grid_home>/log/<hostname>/cssd/ocssd.log Use the cluvfy utility or the ocrcheck command to check the integrity of the OCR. $ cluvfy comp ocr –n all -verbose $ ocrcheck
D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration
Q39. Choose four tools that can be used to create ASM disk groups.
A. Enterprise Manager
Q40. Examine the following details from the AWR report for your three-instance RAC database:
Which inferences is correct?
A. There are a large number of requests for cr blocks or current blocks currently in progress.
B. Global cache access is optimal without any significant delays.
C. The log file sync waits are clue to cluster interconnect latency.
D. To determine the frequency of two-way block requests you must examine other events In the report.
Analyzing Cache Fusion Transfer Impact Using GCS Statistics This section describes how to monitor GCS performance by identifying objects read and modified frequently and the service times imposed by the remote access. Waiting for blocks to arrive may constitute a significant portion of the response time, in the same way that reading from disk could increase the block access delays, only that cache fusion transfers in most cases are faster than disk access latencies. The following wait events indicate that the remotely cached blocks were shipped to the local instance without having been busy, pinned or requiring a log flush:
gc current block 2-way gc current block 3-way gc cr block 2-way gc cr block 3-way
The object statistics for gc current blocks received and gc cr blocks received enable quick identification of the indexes and tables which are shared by the active instances. As mentioned earlier, creating an ADDM analysis will, in most cases, point you to the SQL statements and database objects that could be impacted by interinstance contention. Any increases in the average wait times for the events mentioned in the preceding list could be caused by the following occurrences: High load: CPU shortages, long run queues, scheduling delays Misconfiguration: using public instead of private interconnect for message and block traffic If the average wait times are acceptable and no interconnect or load issues can be diagnosed, then the accumulated time waited can usually be attributed to a few SQL statements which need to be tuned to minimize the number of blocks accessed. Oracle. Real Application Clusters Administration and Deployment Guide 11g Release 2 (11.2)