OCP-1Z0-053-V13.02-176题

176.Which of the following statements is true when the database is in ARCHIVELOG mode and tablespaces are in hot backup mode?

A. Archive log generation is suspended until the tablespaces are taken out of hot backup mode.

B. Datafiles are not written to during hot backups.

C. Changes to the database are cached during the backup and not written to the datafiles to ensure that the datafiles are consistent when recovered.

D. The datafile headers are not updated during the backup.

E. The way data is written to the online redo logs is unchanged during the backup.

Answer: D

答案解析：

当执行ALTER TABLESPACE ... BEGIN BACKUP是，数据文件的头部就会冻结，不再更新，等执行ALTER TABLESPACE ... END BACKUP后，将更新为目前的SCN号。

backup mode

The database mode (also called hot backup mode) initiated when you issue the ALTER TABLESPACE ... BEGIN BACKUP or ALTER DATABASE BEGIN BACKUP command before taking an online backup. You take a tablespace out of backup mode when you issue the ALTER TABLESPACE ... END BACKUP or ALTER DATABASE END BACKUPcommand.

When making a user-managed backup of data files in an online tablespace, you must place the tablespace in backup mode to protect against the possibility of a fractured block. In backup mode, updates to the database create more than the usual amount of redo. Each time a block in the buffer cache becomes dirty, the database must write an image of the changed block to the redo log file, in addition to recording the changes to the data. RMAN does not require you to put the database in backup mode.

fractured block

A block in which the header and footer are not consistent at a given SCN. In a user-managed backup, an operating system utility can back up a data file at the same time that DBWR is updating the file. It is possible for the operating system utility to read a block in a half-updated state, so that the block that is copied to the backup media is updated in its first half, while the second half contains older data. In this case, the block is fractured.

For non-RMAN backups, the ALTER TABLESPACE ... BEGIN BACKUP or ALTER DATABASE BEGIN BACKUP command is the solution for the fractured block problem. When a tablespace is in backup mode, and a change is made to a data block, the database logs a copy of the entire block image before the change so that the database can reconstruct this block if media recovery finds that this block was fractured.

 

BEGIN BACKUP

Specify BEGIN BACKUP to indicate that an open backup is to be performed on the data files that make up this tablespace. This clause does not prevent users from accessing the tablespace. You must use this clause before beginning an open backup.

Restrictions on Beginning Tablespace Backup Beginning tablespace backup is subject to the following restrictions:

• You cannot specify this clause for a read-only tablespace or for a temporary locally managed tablespace.

• While the backup is in progress, you cannot take the tablespace offline normally, shut down the instance, or begin another backup of the tablespace.

  
  

  Backing Up Tablespaces: Examples The following statement signals to the database that a backup is about to begin:

  ALTER TABLESPACE tbs_01

      BEGIN BACKUP;