Oracle 1Z0-058 Online Practice Questions and Exam Preparation

Oracle 1Z0-058 Online Questions & Answers

• Question 101:

  You are managing a policy-managed database called RACDB. Examine the output given below:

  

  You used these commands to add the service erp:

  

  Which statement is true regarding the srvctl stop instance command?

  A. It will shut down the racdb_1 instance and the ERP service running on node gr7597.
  B. It will shut down the racdb_1 instance, and the ERP service will fail over to an available In- stance.
  C. It will shut down the racdb_1 instance, but the ERP service will keep running on node gr7597
  D. It will shut down the racdb_1 instance and the ERP service running on ih.il Instance However Oracle Clusterware can restart the ERP service running on node gr7597.
  E. It will shut down the racdb_1 instance and stop the ERP service on all the nodes
  A. It will shut down the racdb_1 instance and the ERP service running on node gr7597.

  ---

  Stops instances and stops any services running on specified instances, unless you specify the -f option. If you specify -f, then the services fail over to an available instance when the instance stops.

  Syntax and Options

  Use the srvctl stop instance command with the following syntax:

  srvctl stop instance -d db_unique_name {[-n node_name]|[-i "instance_name_list"]} [-o stop_op- tions] [-f] Oracle Real Application Clusters Administration and Deployment Guide

• Question 102:

  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?

  A. one
  B. two
  C. five
  D. ten
  D. ten

  ---

  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's Guide

• Question 103:

  Your network administrator informs you that the Internet service provider is being changed in a month's time in conjunction with a data center move. You are asked to plan for the changes required in the Oracle Grid Infrastructure, which is set up to use GNS.

  The IP addresses and subnets of the public network are to change. Which two must be done in the Oracle Grid Infrastructure network setup to accommodate this change using the command-line Interfaces available?

  A. The SCAN VIPs and node VIPs must be reconfigured using srvctl.
  B. The SCAN VIPs and SCAN listener resources must be removed and added to obtain the new SCAN IP addresses from DHCP.
  C. The interconnect must be reconfigured by using oifcfg, crsctl, and ifconfig.
  D. The SCAN VIPs and node VIPs must be reconfigured by using oifcfg.
  E. The Interconnect must be reconfigured by using srvctl.
  C. The interconnect must be reconfigured by using oifcfg, crsctl, and ifconfig.
  D. The SCAN VIPs and node VIPs must be reconfigured by using oifcfg.

  ---

  How to Modify Public or Private Network Information in Oracle Clusterware [ID 283684.1] Modified 14-MAR-2012 Type HOWTO Status PUBLISHED

  Applies to:

  Oracle Server - Enterprise Edition - Version: 10.1.0.2 to 11.2.0.3 - Release: 10.1 to 11.2 Information in this document applies to any platform.

  Goal

  The purpose of this note is to describe how to change or update the cluster_interconnect and/or public interface information that is stored in OCR.

  It may be necessary to change or update interface names, or subnet associated with an interface if there is a network change affecting the servers, or if the original information that was input during the installation was incorrect. It may also be

  the case that for some reason, the Oracle Interface Configuration Assistant ('oifcfg') did not succeed during the installation. This note is not intended as a means to change the Public or Private Hostname themselves. Public hostname or

  Private hostname can only be changed by removing/ adding nodes, or reinstalling Oracle Clusterware.

  However, node VIP name/IP can be changed, refer to Note 276434.1 for details. Refer to note 1386709.1 for basics of IPv4 subnet and Oracle Clusterware

  Instructions for Changing Interfaces/Subnet

  1. Public Network Change

  If the change is only public IP address and the new ones are still in the same subnet, nothing needs to be done on clusterware level (all changes needs to be done on OS level to reflect the change).

  If the change involves different subnet or interface, as there is not a 'modify' option - you will need to delete the interface and add it back with the correct information. So, in the example here, the subnet is being changed from 10.2.156.0 to

  10.2.166.0 via two separate commands - first a 'delif' followed by a 'setif':

  % $ORA_CRS_HOME/bin/oifcfg delif -global eth0

  % $ORA_CRS_HOME/bin/oifcfg setif -global eth0/10.2.166.0:public syntax: oifcfg setif / :

  Note: If public network is changed, it may be necessary to change VIP as well, refer to Note 276434.1 for details; for 11gR2, it may be necessary to change SCAN as well, refer to note 972500.1 for details (This procedure does not apply when GNS is being used).

  2.

  Private Network Change 2A. For pre-11gR2, if you wish to change the cluster_interconnect information and/or private IP address, hosts file needs to be modified on each node to reflect the change while the Oracle Clusterware Stack is down on all nodes. After the stack has restarted, to change the cluster_interconnect used by RDBMS and ASM instances, run oifcfg. In this example: % $ORA_CRS_HOME/bin/oifcfg delif -global eth1 % $ORA_CRS_HOME/bin/oifcfg setif -global eth1/192.168.1.0:cluster_interconnect 2B. For 11gR2 and higher, refer to note 1073502.1

  Note: For 11gR2, as clusterware also uses cluster_interconnect, intended private network must be added by "oifcfg setif" before stopping clusterware for any change. Note: If you are running OCFS2 on Linux and are changing the private IP address for your cluster, you may also need to change the private IP address that OCFS2 is using to communicate with other nodes. For more information on this, please refer to

  3.

  Verify the correct interface subnet is in use by re-running oifcfg with the 'getif' option: % $ORA_CRS_HOME/bin/oifcfg getif eth0 10.2.166.0 global public eth1 192.168.1.0 global cluster_interconnect How to Modify Private Network Interface in 11.2 Grid Infrastructure [ID 1073502.1] Modified 08-FEB-2012 Type HOWTO Status PUBLISHED

  Applies to:

  Oracle Server - Enterprise Edition - Version: 11.2.0.1.0 and later [Release: 11.2 and later ] Information in this document applies to any platform.

  Goal

  The purpose of this document is to demonstrate how to change the private network interface configuration stored in the OCR. This may be required if the name of the interface for the private network (cluster interconnect) needs to be changed

  at the OS level, for example, the private network is configured on a single network interface eth0, now you want to replace it with a bond interface bond0 and eth0 will be part of the bond0 interface. It also includes command for adding/deleting

  a private network interface.

  Solution

  As of 11.2 Grid Infrastructure, the CRS daemon (crsd.bin) now has a dependency on the private network configuration stored in the gpnp profile and OCR. If the private network is not available or its definition is incorrect, the CRSD process

  will not start and any subsequent changes to the OCR will be impossible. Therefore care needs to be taken when making modifications to the configuration of the private network. It is important to perform the changes in the correct order.

  Note: If only private network IP is going to be changed, the subnet and network interface remain same (for examples changing private IP from 192.168.0.1 to 192.168.0.10), simply shutdown GI stack, make IP modification at OS level (like /

  etc/hosts, network config etc) for private network, then restart GI stack will complete the task. The following procedures apply when subnet or network interface name also requires change. Please take a backup of profile.xml on all cluster

  nodes before proceeding, as grid user: $ cd $GRID_HOME/gpnp//profiles/peer/ $ cp -p profile.xml profile.xml.bk

  To modify the private network (cluster_interconnect):

  1.

  Ensure CRS is running on ALL cluster nodes in the cluster

  2.

  As grid user, add new interface:

  Find the interface which needs to be removed. For example:

  $ oifcfg getif

  eth1 100.17.10.0 global public

  eth0 192.168.0.0 global cluster_interconnect

  Here the eth0 interface will be replaced by bond0 interface.

  Add new interface bond0:

  $ oifcfg setif -global /:cluster_interconnect

  For example:

  $ oifcfg setif -global bond0/192.168.0.0:cluster_interconnect This can be done with -global option even if the interface is not available yet, but this can not be done with - node option if the interface is not available, it will lead to node eviction.

  If the interface is available on the server, subnet address can be identified by command:

  $ oifcfg iflist

  It lists the network interface and its subnet address. This command can be run even if CRS is not up and running. Please note, subnet address might not be in the format of x.y.z.0. For example, it can be:

  $ oifcfg iflist

  lan1 18.1.2.0

  lan2 10.2.3.64 << this is the private network subnet address associated with privet network IP:

  If the scenario is just to add a 2nd private network, for example: new interface is eth3 with subnet address:

  192.168.1.96, then issue:

  $ oifcfg setif -global eth3/192.168.1.96:cluster_interconnect Verify the change:

  $ oifcfg getif

  3.

  Shutdown CRS on all nodes and disable the CRS as root user:

  # crsctl stop crs

  # crsctl disable crs

  4.

  Make the network configuration change at OS level as required, ensure the new interface is available on all nodes after the change.

  $ ifconfig -a

  $ ping

  5.

  Enable CRS and restart CRS on all nodes as root user:

  # crsctl enable crs

  # crsctl start crs

  6.

  Remove the old interface:

  $ oifcfg delif -global eth0

  Note #1. This step is not required for adding 2nd interface scenario. #2. If the new interface is added without removing the old interface, eg: old interface still available when CRS restart, then after step 6, CRS needs to be stop and start again

  to ensure the old interface is no longer in use.

  

  Workaround: restore the OS network configuration back to the original status, start CRS. Then follow above steps to make the changes again. Please consult with Oracle Support Service if after restoring OS network configuration, CRS still could not start.

  2.

  If any one node is down in the cluster, oifcfg command will fail with error:

  $ oifcfg setif -global bond0/192.168.0.0:cluster_interconnect PRIF-26: Error in update the profiles in the cluster Workaround: start CRS on the node where it is not running. Ensure CRS is up on all cluster nodes.

  3.

  If a user other than Grid Infrastructure owner issues above command, it will fail with same error: $ oifcfg setif -global bond0/192.168.0.0:cluster_interconnect PRIF-26: Error in update the profiles in the cluster Workaround: ensure to login as

  Grid Infrastructure owner to perform such command.

  4.

  From 11.2.0.2 onwards, if attempt to delete the last private interface (cluster_interconnect) without adding a new one first, following error will occur:

  PRIF-31: Failed to delete the specified network interface because it is the last private interface Workaround: Add new private interface first before deleting the old private interface.

  5.

  If CRS is down on the node, the following error is expected:

  $ oifcfg getif

  PRIF-10: failed to initialize the cluster registry

  Workaround: Start the CRS on the node

  My Oracle Support

• Question 104:

  The DBA has executed the command:

  srvctl add service -d PROD -s BATCH -g SP2 -c singleton -y manual What is the result of this command?

  A. Creates a singleton service named batch using the server pool sp2 with a manual service management policy.
  B. Creates a singleton service named batch for the prod database by using only server pool SP2 with a manual service management policy.
  C. Creates a singleton service named batch, which runs by default in the prod database by using the server pool SP2 with a manual service management policy, but can fail over to other databases.
  D. Creates a singleton service, which is only used for batch workloads for the prod database by using only server pool sp2 with a manual service management policy.
  B. Creates a singleton service named batch for the prod database by using only server pool SP2 with a manual service management policy.

  ---

  srvctl add service

  Adds services to a database and assigns them to instances. If you have multiple instances of a cluster database on the same node, then always use only one instance on that node for all of the services that node manages.

  

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

• Question 105:

  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.
  C. Set the rebalance power limit (or allow it to default). Add the disks to the diskgroup.

  ---

  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

• Question 106:

  What is the recommended procedure to shut down an ASM instance with a mounted ACFS file system at / u01/app/oracle/acfsmounts/vol1, where the volume name is VOL1 and the disk group name is DATA?

  A. Issue the synchronize command for the file system twice. Then stop the ASM Instance with the SQL*Plus SHUTDOWN ABORT command.
  B. Use the advmutil dismount /all /DATA command. Then stop the ASM instance with the SQL*Plus SHUTDOWN IMMEDIATE command.
  C. Use the /bin/umount /u01/app/oracle/acfsmounts/vol1 command. Then shut down the ASM instance with the SQL*PIus SHUTDOWN IMMEDIATE command.
  D. Use the SQL ALTER DISKGROUP VOLULE VOL1 DISMOUNT command. Then stop the ASM instance with the SQL*Plus SHUTDOWN IMMEDIATE command.
  E. Stop the ASM instance with the SQL*Plus SHUTDOWN IMMEDIATE command.
  C. Use the /bin/umount /u01/app/oracle/acfsmounts/vol1 command. Then shut down the ASM instance with the SQL*PIus SHUTDOWN IMMEDIATE command.

  ---

  Oracle ACFS and Dismount or Shutdown Operations It is important to dismount any active file system configured with an Oracle ADVM volume device file before an Oracle ASM instance is shutdown or a disk group is dismounted. After the file systems are dismounted, all open references to Oracle ASM files are removed and associated disk groups can be dismounted or the instance shut down. Oracle?Automatic Storage Management Administrator's Guide 11g Release 2 (11.2)

• Question 107:

  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
  C. SMON

  ---

  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

• Question 108:

  Which three steps must be completed to configure Fast Connection Failover for the CRM service with an Oracle Call Interface client?

  A. Ensure that the CRM service has Advanced Queuing notifications enabled by setting the services values of AQ_HA_NOTIFICATIONS to TRUE. For example: $ srvctl modify service -d crm -s gl.us.oracle. com \ -q TRUE -P BASIC -e SELECT -z 180 -w 5 -j LONG
  B. Enable OCI_EVEINTS on the client at environment creation time by using the OCIEnvCreate(...) function.
  C. Use Oracle Call Interface to configure UP events for the service.
  D. Client applications must be linked with the client thread or operating system library.
  A. Ensure that the CRM service has Advanced Queuing notifications enabled by setting the services values of AQ_HA_NOTIFICATIONS to TRUE. For example: $ srvctl modify service -d crm -s gl.us.oracle. com \ -q TRUE -P BASIC -e SELECT -z 180 -w 5 -j LONG
  B. Enable OCI_EVEINTS on the client at environment creation time by using the OCIEnvCreate(...) function.
  D. Client applications must be linked with the client thread or operating system library.

  ---

  Configuring FCF for OCI Clients

  OCI applications must connect to an Oracle RAC instance to enable HA event notification. Furthermore, these applications must perform the following steps to configure FCF for an OCI client:

  Configure the service for your OCI connection pool to enable connection load balancing and runtime connection load balancing. Also configure the service to have Advanced Queuing notifications enabled, as shown in the following example:

  $ srvctl modify service -d crm -s ociapp.example.com -q TRUE -B THROUGHPUT -j LONG Set the context of the environment for OCI calls on the client to enable subscriptions by using the OCIEnvCreate() call, setting the MODE parameter

  value to OCI_EVENTS, as follows:

  (void) OCIEnvCreate(andmyenvhp, OCI_EVENTS|OCI_OBJECT, ...); Link the application with a thread library.

  After linking with the thread library, the applications can register a callback that is invoked whenever a FAN event occurs.

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

• Question 109:

  Your cluster Is subject to a service-level agreement that allows for little scheduled down time You want to use patching and maintenance methods that permit the Oracle Grid Infrastructure and Oracle RAT Databases to be available as much as possible. Which two techniques will work some or all of the time to provide you with minimum down time?

  A. rolling upgradeable and in place patch sets
  B. idling upgradeable and out of place patch bundles
  C. rolling upgradeable and out of place patch sets
  D. rolling upgradeable and in place patch bundles
  E. rolling upgradeable and out of place one-off patches
  C. rolling upgradeable and out of place patch sets
  D. rolling upgradeable and in place patch bundles

  ---

  A rolling upgrade process allows one or more nodes in the cluster to have a different soft- ware version than the other nodes in the cluster for a short period of time. During the time period where cluster nodes have different software versions, the cluster is fully func- tional, but some administrative functions are disabled until the upgrade has completed, for example, adding new cluster resources. An out-of-place patch set installation with cloning has the following advantages: Applications remain available while software is upgraded in the new ORACLE_HOME. The configuration inside the ORACLE_HOME is retained because the cloning procedure involves physically copying the software In-place upgrade You install the patch set into an existing Oracle home location. Oracle recommends that you select this option only if you do not have sufficient free disk space to perform an out-of-place upgrade, as the upgrade removes the existing Oracle installation. This patch option requires less disk space, but requires more time, and is riskier, because if you encounter an installation failure, then you must recover the entire existing Oracle home from a backup

• Question 110:

  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. a new log file in the +DATA disk group, or a log file in the + FRA disk group, if +DATA is not available
  B. a new log file in the +DATA disk group and a log file in the + FRA disk group
  C. a new log file in the +LOGS disk group and a log file in the + FRA disk group
  D. a new log file in the +LOGS disk group, or a log file in the +FRA dls* available
  E. 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
  F. a new log file in the +LOGS disk group, or a log file in the +FRA disk group, if +LOGS is not available
  C. a new log file in the +LOGS disk group and a log file in the + FRA disk group

  ---

  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.

  DB_CREATE_ONLINE_LOG_DEST_n 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. DB_RECOVERY_FILE_DEST 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's Guide