1Z0-058 | how many questions of 1Z0-058 practice test?
Q51. 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
Q52. 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.
Answer: B,D
Explanation:
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
D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 12 - 22, 23
Q53. You are creating a resource definition called WEBAPP for a web-based application that requires an application called WEBVIP.
Both WEBVIP and WEBAPP are normally active on a single node, but may fail over if required to another cluster node in your eight-node cluster.
A second VIP application resource called appsvip exists, used by a second application resource called secapp. webvip and webapp must start In the correct sequence.
Which two start dependencies would you use for the WEBAPP application resource definition?
A. hard(SECAPP)
B. pullup(SECAPP)
C. pullup (WEBVIP)
D. hard(WEBVlP)
E. dispersion(WEBVIP)
F. weak (WEBVIP)
Answer: C,D
Explanation:
Start Dependencies hard Define a hard start dependency for a resource if another resource must be running before the dependent resource can start. For example, if resource A has a hard start dependency on resource B, then resource B must be running before resource A can start. Note: Oracle recommends that resources with hard start dependencies also have pullup start dependencies. weak If resource A has a weak start dependency on resource B, then an attempt to start resource A attempts to start resource B, if resource B is not running. The result of the attempt to start resource B is, however, of no consequence to the result of starting resource A. attraction If resource A has an attraction dependency on resource B, then Oracle Clusterware prefers to place resource A on servers hosting resource B. Dependent resources, such as resource A in this case, are more likely to run on servers on which resources to which they have attraction dependencies are running. Oracle Clusterware places dependent resources on servers with resources to which they are attracted. pullup Use the pullup start dependency if resource A must automatically start whenever resource B starts. This dependency only affects resource A if it is not running. As is the case for other dependencies, pullup may cause the dependent resource to start on any server. Use the pullup dependency whenever there is a hard stop dependency, so that if resource A depends on resource B and resource B fails and then recovers, then resource A is restarted. dispersion If you specify the dispersion start dependency for a resource, then Oracle Clusterware starts this resource on a server that has the fewest number of resources to which this resource has dispersion. Resources with dispersion may still end up running on the same server if there are not enough servers to disperse them to. Oracle. Clusterware Administration and Deployment Guide 11g Release 2 (11.2)
Q54. 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
Q55. 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
Answer: C
Explanation: 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
Q56. Which three statements are true about Oracle Clusterware component log files?
A. Oracle RAC uses a common unified log directory structure to store all Oracle Clusterware component log files.
B. The consolidated directory structure simplifies diagnostic information collection and assists during data retrieval and problem analysis.
C. The Clusterware and Database log files are stored under the same unified directory structure.
D. The location of the log directory structure is <Grid_Home>/log/<hostname>.
E. The log directory structure is the same on UNIX and Linux systems, but different on Windows platforms.
Answer: A,B,D
Explanation:
Oracle Clusterware Main Log Files
Oracle Clusterware uses a unified log directory structure to consolidate the Oracle
Clusterware component log files. This consolidated structure simplifies diagnostic information collection and assists during data retrieval and problem analysis.
The slide shows you the main directories used by Oracle Clusterware to store its log files:
CRS logs are in <Grid_Home>/log/<hostname>/crsd/. The crsd.log file is archived every 10
MB (crsd.l01, crsd.l02, ...).
CSS logs are in Grid_HOME /log/<hostname>/cssd/. The cssd.log file is archived every 20
MB (cssd.l01, cssd.l02, ...).
EVM logs are in <Grid_Home>/log/<hostname>/evmd.
SRVM (srvctl) and OCR (ocrdump, ocrconfig, ocrcheck) logs are in
<Grid_Home>/log/<hostname>/client/ and $ORACLE_HOME/log/<hostname>/client/.
Important Oracle Clusterware alerts can be found in alert<nodename>.log in the
<Grid_Home>/log/<hostname> directory.
D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 2 - 11
Q57. Identify the three valid storage options for Grid Infrastructure voting disk and Install.
A. a certified Cluster File System (CFS)
B. a certified Network File System (NFS)
C. ASM Cluster File System (ACFS)
D. Automatic Storage Management (ASM)
E. shared disk slices (block or raw devices)
Answer: A,B,D
Explanation:
untitled D60488GC11
Oracle 11g: RAC and Grid Infrastructure Administration Accelerated 2 - 4
Q58. 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.
Answer: C
Explanation:
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)
Q59. Examine the following output:
[oracle@gr5153~]$srvctl add service -d RACDB -s erp -g pool1 -c uniform -y manual [oracle0gr5153~]$srvctl start service -d RACDB -s ERP [oracle@gr5153~]$crsctl stat res ora.racdb.erp.svc NAME=ora.racdb.erp.svc
TYPE=ora.service.type
TARGET=ONLINE, ONLINE, ONLINE STATE=ONLINE on gr5118, ONLINE on gr5152,
ONLINE on gr5153
[oracle@gr5153~]$ srvctl config database -d RACDB
Database unique name: RACDB
Database name: RACDB
Oracle home:/u01/app/oracle/product/11.2.0/dbhome_1
Oracle user:oracle
Spfile:+DATA/RACDB/spfileRACDB.ora
Domain:
Start options:open
Stop options:immediate
Database role:PRIMARY
Management policy:AUTOMATIC
Server pools:POOL 1 Database instances:
Disk Groups:DATA, FRA
Services:ERP
Database is policy managed
$srvctl stop database -d RACDB -o immediate
Which two statements are true regarding the srvctl stop command?
A. It will shut down all the instances of the RACDB database.
B. It will shut down only the RACDB instance and the ERP service on the node on which the Command is executed.
C. It will shut down only the database instance on the node on which the command is executed.
D. It will stop the ERP service related to the RACDB database on all the nodes.
Answer: A,D
Explanation: Shut down all Oracle RAC instances on all nodes. To shut down all Oracle RAC instances for a database, enter the following command, where db_name is the name of the database: srvctl stop database -d db_name Stops a database, its instances, and its services. When the database later restarts, services with AUTOMATIC management start automatically but services with MANUAL management policy must be started manually.
Oracle Real Application Clusters Administration and Deployment Guide
Q60. A policy-managed RAC database that hosts the ACCOUNTS service has only three instances running rather than the usual four on a six-node cluster.
Five of the six cluster nodes are active and the sixth (RACNODE6) is down for maintenance.
You decide to check the state of the servers in the server pools to see if there are problems with the OLTP pool to which the ACCOUNTS service has been assigned.
You used the crsctl status server-f command and see that the RACNODE3 node has STATE=VISIBLE.
What is true about this situation?
A. The Cluster Synchronization Services Daemon (cssd) is running and RACNODE3 is considered to be part of the cluster, but the Cluster Ready Services Daemon (crsd) is currently not running.
B. Both the Cluster Ready Services Daemon (crsd) and the Cluster Synchronization Service Daemon (cssd) are running on RACNODE3, but RACNODE3 is currently being moved to another server pool.
C. The Cluster Ready Services Daemon (crsd) is running and RACNODE3 is considered to be a part of the cluster, but the Cluster Synchronization Services Daemon (cssd) is currently not running.
D. Neither the Cluster Ready Services Daemon (crsd) nor the Cluster Synchronization Services Daemon (cssd) is running on RACNODE3.
Answer: A Explanation: Cluster Synchronization Service daemon (CSSD)
An Oracle Clusterware component that discovers and tracks the membership state of each node by providing a common view of membership across the cluster. CSS also monitors process health, specifically the health of the database instance. The Global Enqueue Service Monitor (LMON), a background process that monitors the health of the cluster database environment and registers and de-registers from CSS.
Cluster Ready Services Daemon (CRSD)
The primary Oracle Clusterware process that performs high availability recovery and management operations, such as maintaining OCR. Also manages application resources and runs as root user (or by a user in the admin group on Mac OS X-based systems) and restarts automatically upon failure
STATE=VISIBLE
Servers that have Oracle Clusterware running, but not the Cluster Ready Services daemon (crsd), are put into the VISIBLE state. This usually indicates an intermittent issue or failure and Oracle Clusterware trying to recover (restart) the daemon. Oracle Clusterware cannot manage resources on servers while the servers are in this state.
Oracle Clusterware Administration and Deployment Guide