nerdexam
Oracle

1Z0-052 · Question #66

You are working on an instance started using the SPFILE. You want to move the Flash Recovery Area of your database to a new location. You want the Flashback log files to be stored in the new…

The correct answer is A. 2, 1, 4, 3, 5, 6. Moving the Flash Recovery Area when flashback logging is active requires changing the destination parameter first, then bouncing to mount state to disable and re-enable Flashback Database so new logs are written to the new location.

Performing Backup and Recovery

Question

You are working on an instance started using the SPFILE. You want to move the Flash Recovery Area of your database to a new location. You want the Flashback log files to be stored in the new location. Given below are the steps to accomplish the task in random order: 1) Shut down the instance. 2) Change the value of the DB_RECOVERY_FILE_DEST initialization parameter to a new value. 3) Execute the ALTER DATABASE FLASHBACK OFF command. 4) Start up the instance and mount the database. 5) Execute the ALTER DATABASE FLASHBACK ON command. 6) Open the database. Select the correct order in which these tasks need to be performed.

Options

  • A2, 1, 4, 3, 5, 6
  • B1, 4, 3, 2, 6, 5
  • C1, 4, 2, 6, 3, 5
  • D3, 2, 1, 4, 5, 6

How the community answered

(44 responses)
  • A
    64% (28)
  • B
    9% (4)
  • C
    23% (10)
  • D
    5% (2)

Why each option

Moving the Flash Recovery Area when flashback logging is active requires changing the destination parameter first, then bouncing to mount state to disable and re-enable Flashback Database so new logs are written to the new location.

A2, 1, 4, 3, 5, 6Correct

Because SPFILE is in use, DB_RECOVERY_FILE_DEST can be changed dynamically with ALTER SYSTEM while the instance is running (step 2), persisting the new path to the SPFILE. The instance is then shut down (step 1) and started to mount state (step 4) because ALTER DATABASE FLASHBACK OFF and ON require the database to be mounted but not open. Flashback is disabled (step 3) to discard old log pointers, re-enabled (step 5) so Oracle begins writing flashback logs to the new destination, and finally the database is opened (step 6).

B1, 4, 3, 2, 6, 5

Shutting down before changing the parameter (steps 1, 4, 3, 2, 6, 5) means the ALTER SYSTEM change happens in mount state and step 6 opens the database before Flashback ON (step 5), leaving flashback re-enabled after the database is already open - which is invalid.

C1, 4, 2, 6, 3, 5

This sequence changes the parameter in mount state but opens the database (step 6) before turning flashback off and on (steps 3, 5), which is not allowed because ALTER DATABASE FLASHBACK ON/OFF requires mount-only state.

D3, 2, 1, 4, 5, 6

Turning Flashback OFF (step 3) and changing the parameter (step 2) while the database is open, then cycling the instance, means the SPFILE change occurs while flashback is still active under the old destination, creating an inconsistent state during shutdown.

Concept tested: Relocating Flash Recovery Area with Flashback Database enabled

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/bradv/using-flasback-database-restore-points.html

Topics

#Flash Recovery Area#DB_RECOVERY_FILE_DEST#Flashback logs#FRA relocation

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full 1Z0-052 Practice