1Z0-058 | 10 Tips For Renew 1Z0-058 practice test
Q21. You have defined two server pools.
One is called OLTP with MIN_SIZE=3, MAX_SIZE =5 and IMPORTANCE=3.
The other is called DSS with MIN_SIZE =2, MAX_SIZE =4 and IMPORTANCE =5.
Your cluster currently has four nodes with two nodes in each of the pools. A fifth node is added to the cluster. What is true about the server pool to which the node will be assigned?
A. The node will have the server assigned to the DSS pool because the current size is less than MAX_SIZE and the DSS pool has a greater importance than the OLTP pool.
B. The node will have the server assigned to the OLTP pool because the OLTP pool's MAX_SIZE is greater than MAX_SIZE of the DSS pool.
C. The node will have the server assigned to the OLTP pool because the OLTP pool's current size is less than its MIN_SIZE and the DSS pool has enough servers to equal its own MIN_SIZE.
D. The node will have the server assigned to the DSS pool on the basis of having a greater IMPORTANCE.
Answer: C
Explanation:
Oracle Clusterware continues to assign servers to server pools until the following conditions are met:
Until all server pools are filled in order of importance to their minimum (MIN_SIZE).
Until all server pools are filled in order of importance to their maximum (MAX_SIZE).
By default, any servers not placed in a server pool go into the Free server pool.
Oracle. Clusterware Administration and Deployment Guide
11g Release 2 (11.2)
Q22. 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 Explanation: Cause
You have logged in with SYSDBA privilege that is not allowed for ASM operations
Solution
Login with SYSASM credentials for ASM operations
MOS [ID 889810.1]
Q23. 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
Explanation: Oracle Real Application Clusters . Oracle Real Application Clusters (Oracle RAC) is a database clustering technology whose shared storage capabilities allow multiple machines to work in parallel on the same data, reducing processing time significantly. Oracle RAC also offers resilience, allowing processing to continue in the event of one or more machines being unavailable because of planned or unplanned downtime.
Computer cluster . A computer cluster consists of a set of loosely connected computers that work together so that in many respects they can be viewed as a single system. . The components of a cluster are usually connected to each other through fast local area networks, each node running its own instance on an operating system.
Computer clusters emerged as a result of convergence of a number of computing trends including the availability of low cost microprocessors, high speed networks, and software for high performance distributed computing.
. Clusters are usually deployed to improve performance and availability over that of a single computer, while typically being much more cost-effective than single computers of comparable speed or availability
Q24. 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.
Answer: A,E
Explanation: FAST_START_MTTR_TARGET
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.
V$INSTANCE_RECOVERY
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)
Q25. 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
Explanation: . To control the speed and resource consumption of the rebalance operation, you can include the REBALANCE POWER clause in statements that add, drop, or resize disks. . The ASM_POWER_LIMIT initialization parameter specifies the default power for disk rebalancing in a disk group. The range of values is 0 to 1024. The default value is 1. A value of 0 disables rebalancing. Higher numeric values enable the rebalancing operation to complete more quickly, but might result in higher I/O overhead and more rebalancing processes. . 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.
Oracle. Automatic Storage Management
Q26. Your two-instance RAC database is running in ARCHVELOG. The instance running on node1., fails and this failure Is ejected by the instance running on node2,which indicates the recovery process for node1.
Which, process will read the redo log of the failed instance to identify the database blocks that need to be recovered during the recovery process, after the configuration of enqueue and cache part of Global resource Directory (GRD)?
A. PMON
B. MMON
C. SMON
D. GES
E. GCS
Answer: C
Explanation:
Instance Recovery and Database Availability The graphic illustrates the degree of database availability during each step of Oracle instance recovery:
1. Real Application Clusters is running on multiple nodes.
2. Node failure is detected.
3. The enqueue part of the GRD is reconfigured; resource management is redistributed to the surviving nodes.
This operation occurs relatively quickly.
4. The cache part of the GRD is reconfigured and SMON reads the redo log of the failed instance to identify the database blocks that it needs to recover.
5. SMON issues the GRD requests to obtain all the database blocks it needs for recovery.
After the requests are complete, all other blocks are accessible.
6. The Oracle server performs roll forward recovery. Redo logs of the failed threads are applied to the database, and blocks are available right after their recovery is completed.
7. The Oracle server performs rollback recovery. Undo blocks are applied to the database for all uncommitted transactions.
8. Instance recovery is complete and all data is accessible.
Note: The dashed line represents the blocks identified in step 2 in the previous slide. Also, the dotted steps represent the ones identified in the previous slide.
D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 14 - 7
Q27. Which command will set full debugging for the communications and resource management components of the CRS module on nodes host01 and host03?
A. srvctl set log -m CRS -c CRSCTI 5, CRSCOMM 5 -m host01,host03
B. ocrconfig set log CRS "CRSRTI, CRSCOMM: 5" -nodelist host01,host03
C. crsctl set log CRS "CRSRTI: 5, CRSCOMM: 5" -nodelist host01,host03
D. crsctl lsmodules crs set log CRSRTX : 5, CRSCOMM: 5 -nodelist host01, host03
Answer: C
Explanation:
Dynamic Debugging
This section includes the following CRSCTL commands that aid in debugging:
crsctl set log
Use the crsctl set log command to set log levels for Oracle Clusterware.
Syntax
crsctl set log {[crs | css | evm "component_name=log_level, [...]"] |
[all=log_level]}
You can also set log levels for the agents of specific resources, as follows:
crsctl set log res "resource_name=log_level, [...]"
untitled
Oracle. Clusterware Administration and Deployment Guide 11g Release 2 (11.2)
Q28. 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
Explanation:
. If you are deleting multiple nodes, then run the rootcrs.pl script on each node that you are deleting. . From any node that you are not deleting, run the following command from the Grid_home/bin directory as root to delete the node from the cluster: # crsctl delete node -n node_to_be_deleted
. On the node you want to delete, run the following command as the user that installed Oracle Clusterware from the Grid_home/oui/bin directory where node_to_be_deleted is the name of the node that you are deleting:
$ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home "CLUSTER_NODES= {node_to_be_deleted}" CRS=TRUE -silent -local
. On the node that you are deleting, depending on whether you have a shared or local Oracle home, complete one of the following procedures as the user that installed Oracle Clusterware:
. For a local home, deinstall the Oracle Clusterware home from the node that you want to delete, as follows, by running the following command, where Grid_home is the path defined for the Oracle Clusterware home:
On any node other than the node you are deleting, run the following command from the Grid_home /oui/bin directory where remaining_nodes_list is a comma-delimited list of the nodes that are going to remain part of your cluster: $ ./runInstaller -updateNodeList ORACLE_HOME=Grid_home "CLUSTER_NODES= {remaining_nodes_list}" CRS=TRUE -silent
. Run the following CVU command to verify that the specified nodes have been
successfully deleted from the cluster: $ cluvfy stage -post nodedel -n node_list [-verbose] Oracle. Clusterware Administration and Deployment Guide
Q29. orcl1, orcl2, and orcl3 are tnsnames that connect to predefined instances of a three-instance RAC database which uses ASM for shared storage.
The database is in archivelog mode.
Examine the Exhibit for the tnsnames.ora entries for orcl1, orcl2, and orcl3.
You plan to execute the following RMAN commands to back up the database:
RUN{
ALLOCATE CHANNEL CH1 DEVICE TYPE DISK CONNECT 'user1/pwd1@orcl1'
ALLOCATE CHANNEL CH2 DEVICE TYPE DISK CONNECT 'user2/pwd2@orcl2'
ALLOCATE CHANNEL CH3 DEVICE TYPE DISK CONNECT 'user3/pwd3@orcl3'
BACKUP DATABASE PLUS ARCHIVELOG; }
What should be the database mode on each of the three instances for this backup to succeed?
A. The database can be either mounted or open on all three instances.
B. The database must be open on all three instances.
C. The database must be open on any one instance and mounted on the other two instances.
D. The database must be mounted on any one of the instances and the other instances will be mounted automatically.
Answer: A
Explanation:
connectStringSpec Purpose Use the connectStringSpec subclause to specify the user name, password, and net service name for connecting to a target, recovery catalog, or auxiliary database. The connection is necessary to authenticate the user and identify the database. Prerequisites You must have SYSDBA privileges to CONNECT to a target or auxiliary database. Do not connect to the recovery catalog database as user SYS. Usage Notes RMAN connections to a database are specified and authenticated in the same way as SQL*Plus connections to a database. The only difference is that RMAN connections to a target or auxiliary database require the SYSDBA privilege. The AS SYSDBA keywords are implied and cannot be explicitly specified. See Oracle Database Administrator's Guide to learn about database connection options when using SQL*Plus.
Oracle. Database Backup and Recovery Reference 11g Release 2 (11.2)
Q30. Identify the three forms of link aggregation that are supported by Oracle Ciusterware for the interconnect.
A. single switch active/standby configuration to increase redundancy for high availability
B. single switch active/active configuration to increase bandwidth for performance
C. multiswitch active/standby configuration to increase redundancy for high availability
D. multiswitch active/active configuration to increase bandwidth for performance
Answer: A,B,C
Explanation:
Interconnect Link Aggregation: Single Switch
. Link aggregation can be used to increase redundancy for higher availability with an Active/Standby configuration. . Link aggregation can be used to increase bandwidth for performance with an Active/Active configuration.
Interconnect Link Aggregation: Multiswitch
. Redundant switches connected with an Inter-Switch Trunk may be used for an enhanced highly available design. . This is the best practice configuration for the interconnect.
With the single switch solutions presented in the previous slide, a failure at the switch level would bring down the entire interconnect. A better highly available (HA) design would be to implement a redundant switch strategy as illustrated in the slide, with an Inter-Switch Trunk connecting the switches. This is the best practice design for the Oracle Clusterware interconnect. Only Active/Standby mode is supported in this configuration.
D60488GC11 Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 1 - 12,13,14