1Z0-083 · Question #153
You execute this command successfully: SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; What is the outcome?
The correct answer is C. It creates a file that contains SQL statements to re-create the control file. ALTER DATABASE BACKUP CONTROLFILE TO TRACE writes a text-based SQL script to a trace file in the diagnostic destination - that script contains CREATE CONTROLFILE statements you can run to manually rebuild the control file if it's lost, making C correct. Option A describes ALTER…
Question
You execute this command successfully:
SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE; What is the outcome?
Options
- AIt creates a binary backup of the control file.
- BIt updates the alert log with the location and contents of the control file
- CIt creates a file that contains SQL statements to re-create the control file.
- DIt creates a file that contains RMAN scripts to create a duplicate database.
- EIt creates a copy of the control file in the fast recovery area (FRA).
How the community answered
(13 responses)- A8% (1)
- C92% (12)
Explanation
ALTER DATABASE BACKUP CONTROLFILE TO TRACE writes a text-based SQL script to a trace file in the diagnostic destination - that script contains CREATE CONTROLFILE statements you can run to manually rebuild the control file if it's lost, making C correct. Option A describes ALTER DATABASE BACKUP CONTROLFILE TO '<filename>', which produces a binary copy, not a trace file. Option B is wrong because the alert log records database events, not control file contents. Option D is wrong because RMAN duplicate scripts are generated through RMAN, not this SQL command. Option E is wrong because nothing is written to the FRA - the output goes to the ADR trace directory ($ORACLE_BASE/diag/.../trace/).
Memory tip: The keyword TRACE = text - think "trace files are always human-readable text," so this command gives you readable SQL, not a binary file or an RMAN script.
Topics
Community Discussion
No community discussion yet for this question.