Exam Code: 1Z0-058 (Practice Exam Latest Test Questions VCE PDF)
Exam Name: Oracle Real Application Clusters 11g Release 2 and Grid Infrastructure
Certification Provider: Oracle
Free Today! Guaranteed Training- Pass 1Z0-058 Exam.
2021 May 1Z0-058 Study Guide Questions:
Q51. 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
Explanation:
How to update the IP address of the SCAN VIP resources (ora.scan.vip) [ID 952903.1]
Modified 03-JAN-2012 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.1 to 11.2.0.1 - Release: 11.2 to 11.2
Information in this document applies to any platform.
Goal
The purpose of this document is to explain how to change the IP addresses associated with the SCAN VIPs in a 11gR2 Grid (CRS) environment.
The IP addresses associated with the SCAN VIP resources are initially set when the SCAN resources are created.
Any changes to the DNS entry for the SCAN are not automatically propagated to the clusterware and need to be done manually.
This applies only to installations that are not using GNS.
The information in this note can also be helpful in cases where SCAN was originally configured with just one address and is now being expanded to accommodate three IP addresses.
Solution
Before the SCAN VIPs can be changed, the entry for the SCAN name on the Domain
Name Server (DNS) needs to be updated with the new IP addresses. This usually will be done by a network administrator. To check the current setting, the following command can be used:
nslookup <scan_name>
To check the current IP address(es) of the SCAN VIPs, run the following commands as the root user:
$GRID_HOME/bin/srvctl config scan
Next refresh the SCAN VIPs with the new IP addresses from the DNS entry:
$GRID_HOME/bin/srvctl modify scan -n <scan_name>
To check if the SCAN VIPs have been changed, run the following command, it should now show the new IP addresses.
$GRID_HOME/bin/srvctl config scan
Below is an example using the following configuration:
The name of the SCAN is sales-scan.example.com
subnet of the public network is 10.100.10.0
netmask for the public network is 255.255.255.0
name of the public interface is eth1
old IP addresses: 10.100.10.81, 10.100.10.82 & 10.100.10.83
new IP addresses: 10.100.10.121, 10.100.10.122 & 10.100.10.123
A lookup of the SCAN on the DNS server shows that the entry has already been updated
with the new IP addresses:
$ nslookup sales-scan.example.com Server: dns1.example.com Address: 10.100.10.70#53 Name: sales-scan.example.com Address: 10.100.10.123 Name: sales-scan.example.com Address: 10.100.10.122 Name: sales-scan.example.com Address: 10.100.10.121
Stop the SCAN listener and the SCAN VIP resources: # $GRID_HOME/bin/srvctl stop scan_listener # $GRID_HOME/bin/srvctl stop scan # $GRID_HOME/bin/srvctl status scan SCAN VIP scan1 is enabled SCAN VIP scan1 is not running SCAN VIP scan2 is enabled SCAN VIP scan2 is not running SCAN VIP scan3 is enabled SCAN VIP scan3 is not running # $GRID_HOME/bin/srvctl status scan_listener SCAN Listener LISTENER_SCAN1 is enabled SCAN listener LISTENER_SCAN1 is not running SCAN Listener LISTENER_SCAN2 is enabled SCAN listener LISTENER_SCAN2 is not running SCAN Listener LISTENER_SCAN3 is enabled SCAN listener LISTENER_SCAN3 is not running
The SCAN VIP resources still show the old IP addresses: # $GRID_HOME/bin/srvctl config scan SCAN name: sales-scan, Network: 1/10.100.10.0/255.255.255.0/eth1 SCAN VIP name: scan1, IP: /sales-scan.example.com/10.100.10.81 SCAN VIP name: scan2, IP: /sales-scan.example.com/10.100.10.82 SCAN VIP name: scan3, IP: /sales-scan.example.com/10.100.10.83
Now tell CRS to update the SCAN VIP resources: # $GRID_HOME/bin/srvctl modify scan -n sales-scan.example.com
To verify that the change was successful, check the SCAN configuration again: # $GRID_HOME/bin/srvctl config scan SCAN name: sales-scan, Network: 1/10.100.10.0/255.255.255.0/eth1 SCAN VIP name: scan1, IP: /sales-scan.example.com/10.100.10.121 SCAN VIP name: scan2, IP: /sales-scan.example.com/10.100.10.122 SCAN VIP name: scan3, IP: /sales-scan.example.com/10.100.10.123
Start SCAN and the SCAN listener: # $GRID_HOME/bin/srvctl start scan # $GRID_HOME/bin/srvctl start scan_listener
Please note that if the SCAN VIPs are being changed because of a change of the subnet of the public network additional changes may be required , e.g. the node VIPs and the network resource (ora.net1.network). For more information please refer to Document 276434.1 and the 11.2 documentation. My Oracle Support
Q52. Examine the Exhibit.
*** Exhibit is Missing ***
Which three statements are correct?
A. Global Cache Block Access Latency indicates how many block transfers incurred a delay (busy) or an unexpected longer delay (congested).
B. Global Cache Block Access Latency indicates how many block transfers received blocks cached by other instances as well as blocks read from disk.
C. Global Cache Block Transfer Rate shows the total aggregated number of blocks received by all instances in the cluster over the interconnect.
D. 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.
E. 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.
F. 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
Q53. Your Apache-based application resource called MyApp has a VIP application resource definition and an application resource definition.
The application is administrator managed and is currently active on nodeRACNODE3.
You want to move it to host RACNODE4, which is one of the HOSTING_MEMBERS in the resource definition.
What is the most efficient method to move the application and the VIP?
A. Run crsctl relocate resource MyApp - n RACNODE4 - f.
B. Run crsctl stop resource MyApp -n RACNODE3 -f followed by crsctl start MyApp -n RACNODE4 -f.
C. Run crsctl stop resource MyApp -n RACNODE3 -f followed by crsctl relocate resource MyApp –n RACNODE4.
D. Run crsctl relocate resource MyApp -n RACNODE4.
Answer: A
Explanation:
Relocating Applications and Application Resources
Use the crsctl relocate resource command to relocate applications and application resources. For example, to relocate the Apache Web server application to a server named rac2, run the following command: # crsctl relocate resource myApache -n rac2 Each time that the action program is called, the crsctl relocate resource command waits for the duration specified by the value of the SCRIPT_TIMEOUT resource attribute to receive notification of success or failure from the action program. A relocation attempt fails if: The application has required resources that run on the initial server Applications that require the specified resource run on the initial server To relocate an application and its required resources, use the -f option with the crsctl relocate resource command. Oracle Clusterware relocates or starts all resources that are required by the application regardless of their state. Oracle. Clusterware Administration and Deployment Guide 11g Release 2 (11.2)
Most recent 1Z0-058 exam guide:
Q54. 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
Explanation:
. Run the following CVU command to check cluster integrity. This command verifies that any number of specified nodes has been successfully added to the cluster at the network, shared storage, and clusterware levels: $ cluvfy stage -post nodeadd -n node3 [-verbose]
. cluvfy comp peer Use the cluvfy comp peer component verification command to check the compatibility and properties of the specified nodes against a reference node. You can check compatibility for non-default user group names and for different releases of the Oracle software. This command compares physical attributes, such as memory and swap space, as well as user and group values, kernel settings, and installed operating system packages. Syntax cluvfy comp peer -n node_list [-refnode node] [-r {10gR1 | 10gR2 | 11gR1 | 11gR2}] [-orainv orainventory_group][-osdba osdba_group] [-verbose] Usage Notes Peer comparison with the -refnode option compares the system properties of other nodes against the reference node. If the value does not match (the value is not equal to reference node value), then CVU flags that comparison as a deviation from the reference node. If a group or user does not exist on reference node as well as on the other node, CVU reports this comparison as 'passed' because there is no deviation from the reference node. Similarly, CVU reports as 'failed' a comparison with a node that has more total memory than the reference node.
. Verify the integrity of the cluster and node3: $ cluvfy stage -pre nodeadd -n node3 [-fixup [-fixupdir fixup_dir]] [-verbose] You can specify the -fixup option and a directory into which CVU prints instructions to fix the cluster or node if the verification fails. Oracle. Clusterware Administration and Deployment Guide
Q55. 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 up time 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
Explanation: Determining Which Process Caused Reboot
untitled First, determine the time of the node reboot by using the uptime command and subtracting the up time from the current system time. The reboot time will be used when examining log files. When the OCSSD daemon is responsible for rebooting a node, a message similar to “Oracle CSSD failure. Rebooting for cluster integrity” is written into the system messages log at /var/log/messages. The cssd daemon log file that is located at <Grid_Home>/log/<hostname>/cssd/ocssd.log may also contain messages similar to "Begin Dump" or "End Dump" just before the reboot. If hangcheck-timer is being used, it will provide message logging to the system messages log when a node restart is initiated by the module. To verify whether this process was responsible for the node reboot, examine the /var/log/messages file and look for an error message similar to: "Hangcheck: hangcheck is restarting the machine." Other useful log files include the Clusterware alert log in <Grid_home>/log/<hostname> and the lastgasp log in /etc/oracle/lastgasp or /var/opt/oracle/lastgasp.
If no indication of which process caused the reboot can be determined from these files, additional debugging and tracing may need to be enabled.
Note: The oclsomon and the oprocd background processes have been eliminated in Oracle
Database 11g Release 2.
D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 6 - 21
Q56. Choose three correct statements about ASM disk group attributes set from the ASMCA Create Disk Group
A. The field labeled ASM Compatibility sets the compatible.asm attribute.
B. When creating a disk group with ASMCA, the default setting for the ASM Compatibility field (compatible.asm) is 10.1.
C. The Database Compatibility field (compatible.rdbms) sets the minimum version level for any database instance that is allowed to mount the disk group.
D. To use ADVM volumes, ADVM Compatibility (compatible.advm) must be set to 11.2.0 or later and ASM Compatibility must be 11.2.0 or later.
E. Advancing the values for disk group compatibility attributes can be reversed if desired.
Answer: A,C,D
Explanation: COMPATIBLE.ASM
The value for the disk group COMPATIBLE.ASM attribute determines the minimum software version for an Oracle ASM instance that can use the disk group.
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.
COMPATIBLE.ADVM
The value for the disk group COMPATIBLE.ADVM attribute determines whether the disk group can contain Oracle ASM volumes. The value must be set to 11.2 or higher. Before setting this attribute, the COMPATIBLE.ASM value must be 11.2 or higher The default disk group compatibility settings are 11.2 for Oracle ASM compatibility, 10.1 for database compatibility, and no value for Oracle ADVM compatibility. The disk group compatibility settings can only be advanced; you cannot revert to a lower compatibility setting.
Oracle Database Storage Administrator's Guide
Download 1Z0-058 vce:
Q57. Which interconnect design is NOT supported for Oracle Clusterware?
A. crossover cable design
B. single switch design
C. multiple switch design
D. redundant interconnect design
Answer: A
Explanation:
2.7.1 Network Hardware Requirements For the private network, the interface must support the user datagram protocol (UDP) using high-speed network adapters and switches that support TCP/IP (minimum requirement 1 Gigabit Ethernet). Note: UDP is the default interface protocol for Oracle RAC, and TCP is the interconnect protocol for Oracle Clusterware. You must use a switch for the interconnect. Oracle recommends that you use a dedicated switch. Oracle does not support token-rings or crossover cables for the interconnect. Oracle. Grid Infrastructure Installation Guide 11g Release 2 (11.2)
Q58. An ASM diskgroup that contains database tablespaces with six disks and normal redundancy is nearing 90% capacity. You want to add additional capacity to the diskgroup. A set of six additional disks has been made available, and appears as CANDIDATE disks in the V$ASM_DISK view.
What steps are required to increase the diskgroup capacity?
A. Export the database objects.
Drop the diskgroup.
Create a new diskgroup.
Import the database objects.
B. Shut down the database instances using the diskgroup.
Add the disks to the diskgroup.
Start the database instances using the diskgroup.
C. Set the rebalance power limit (or allow it to default).
Add the disks to the diskgroup.
D. Shut down all database instances and ASM instances.
Back up the ASM diskgroup.
Start the ASM instances.
Add the disks to the diskgroup.
Issue a rebalance command.
Start the database instances.
Answer: C
Explanation:
You can use the ADD clause of the ALTER DISKGROUP statement to add a disk or a failure group to a disk group. The same syntax that you use to add a disk or failure group with the CREATE DISKGROUP statement can be used with the ALTER DISKGROUP statement. ASM automatically rebalances the disk group when disks are added. By default, the ALTER DISKGROUP statement returns immediately after the disks have been added while the rebalance operation continues to run asynchronously. You can query the V$ASM_OPERATION view to monitor the status of the rebalance operation. D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 8 - 21
Q59. In an ASM instance, there are several parameters that have meanings specific to the ASM. Which parameter is mandatory?
A. ASM_DISKGROUP
B. ASM_DISKSTRING
C. INSTANCE_TYPE
D. CLUSTER_DATABASE
E. MEMORY_TARGET
F. ASM_POWER_LIMIT
Answer: C
Explanation: Oracle ASM Parameter Setting Recommendations
This section contains information about the following parameters for Oracle ASM: ASM_DISKGROUPS ASM_DISKSTRING ASM_POWER_LIMIT ASM_PREFERRED_READ_FAILURE_GROUPS DB_CACHE_SIZE DIAGNOSTIC_DEST INSTANCE_TYPE uk.co.certification.simulator.questionpool.PList@9387e00 LARGE_POOL_SIZE PROCESSES REMOTE_LOGIN_PASSWORDFILE SHARED_POOL_SIZE
Oracle. Automatic Storage Management Administrator's Guide
Q60. 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
Explanation:
. RMAN is also critical to Automatic Storage Management (ASM)..Since ASM is critical to GRID operations, RMAN is then critical for GRID based systems. In ASM, RMAN is responsible for tracking the ASM filenames and for performing the deletion of obsolete ASM files. ASM files cannot, however, be accessed through normal operating system interfaces; therefore, RMAN is the preferred means of copying ASM files. It is also possible to use FTP through XDB, but generally, RMAN will be less complex. It is important to learn to use RMAN first because RMAN is the only method for performing backups of a database containing ASM files.
. Setting Initialization Parameters for ASM The procedure for creating a duplicate database to an ASM location is similar to the procedure described in "Settings and Restrictions for OMF Initialization Parameters" on page 25-4. The difference is that you must identify the initialization parameters that control the location where files are created and set these parameters to an ASM disk group. For example, set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_DEST_n,and CONTROL_FILES to +DISK1.
. To take advantage of Automatic Storage Management (ASM) with an existing database you must migrate that database into ASM. This migration is performed using Recovery Manager (RMAN) even if you are not using RMAN for your primary backup and recovery strategy.
Oracle. Database Backup and Recovery Advanced User's Guide