Correct ans : d: 4 : rman target=sys/robert@orcl catalog=rcat_own/pw_racat_own@rcat

RMAN> configure controlfile autobackup on; new RMAN configuration parameters:CONFIGURE CONTROLFILE AUTOBACKUP ON;new RMAN configuration parameters are successfully stored

1mb,ASM AU Size and Extents ASM files are stored in disk groups. In each disk group, space is allocated in extents, and an extent consists of one or more units of space called allocation units (AUs). Allocation units default to a size of 10MB and can be configured from 1 to 64MB at the time the disk group is created. Once the AU size has been determined for a given disk group, it cannot be changed. To enable support for larger ASM datafiles, to reduce the memory overhead of large databases, and to improve file open and close operations, ASM uses a variable-extent sizing policy. Extents will be initially sized at the size of the AU (for the first 20,000 extents) of the ASM diskgroup in which the extent is created. The extent size will be increased to 8 times the AU size for the next 20,000 extents and then will increment to 64 times the AU size for subsequent extent allocations.

Ans B. If the DROP DISK operation has not yet completed, you can cancel and roll back the entire DROP DISK operation by using ALTER DISKGROUP ... UNDROP DISKS, with the disk group still being continuously available to all users.

A. The ADD DIRECTORY command is not likely to use V$ASM_OPERATION to track its prog- ress, because this operation adds only a small amount of metadata—a directory object—to the disk group and takes a minimal amount of time to complete. The V$ASM_OPERATION view provides the status of long-running ASM operations.

Ans : A

When you put a tablespace in hot backup mode, you are really putting the underlying datafiles of the that tablespace in hot backup mode. You can determine if a datafile is in hot backup mode by querying the V$BACKUP view. The STATUS column will indicate ACTIVE if the given datafile is in hot backup mode. Here is an example of such a query where our users tablespace is in hot backup mode, as indicated by the ACTIVE status. SQL> 2 select a.tablespace_name, b.status from dba_data_files a, v$backup b

Ans : 4 : check point the database.

Dealing with the Loss of an Inactive Online Redo Log Group When the Database Is Running If you lose an inactive online redo log group (or it becomes corrupted) while the database is running, the database will sometimes keep operating. It will sometimes skip the online redo log group that went missing and continue to operate normally. In this case, you can issue an alter system checkpoint command and then clear the log-file group with the alter database clear logfile group command as shown here: SQL>alter system checkpoint; SQL>alter database clear logfile group 1;

12. D. Since the online redo logs are intact, you will be able to use the noresetlogs version of the create controlfile command.

Use the alter database enable block change tracking using file command, followed by the path and filename in single quotes, to create the block change tracking file. For more information