Multiple choice technology databases

You have performed the first step in placing your database into ARCHIVELOG mode. The second step is deciding whether the online redo log files are to be archived automatically or manually. which action should you take to enable archiving an instance startup?

  1. Set the LOG_ARCHIVE_START parameter to TRUE in the initialization parameter file.

  2. Automatic archive is the default when ARCHIVELOG mode is set. No further actions are required.

  3. Set the LOG_ARCHIVE_MAX_PROCESSES parameter to n (where n is the number of Archiver process) in the initialization parameter file.

  4. Immediately after setting the database in ARCHIVELOG mode, in SQL*Plus select automatic archiving using the syntax : ALTER DATABASE SET LOG_ARCHIVE_START=TRUE
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

The LOG_ARCHIVE_START parameter controls automatic archiving at instance startup. Setting it to TRUE in the initialization parameter file enables automatic archiving when the instance starts. Option B is incorrect because automatic archiving is not the default - you must explicitly enable it. Option C sets the number of archiver processes but doesn't enable automatic archiving. Option D is incorrect because LOG_ARCHIVE_START is an initialization parameter, not set dynamically with ALTER DATABASE.

AI explanation

On classic Oracle (8i/9i-era) databases, once a database is placed into ARCHIVELOG mode you separately control whether the archiver actually kicks in automatically at instance startup. Setting LOG_ARCHIVE_START=TRUE in the initialization parameter file (init.ora) tells the instance to start the ARCn background process(es) automatically whenever the instance starts, so filled redo logs get archived without manual intervention. Automatic archiving is not the default (option B is false) — without this parameter, archiving must be started manually with ARCHIVE LOG START. LOG_ARCHIVE_MAX_PROCESSES only tunes how many archiver processes run, not whether archiving is enabled. LOG_ARCHIVE_START cannot be set with ALTER DATABASE — it's a static parameter requiring an init.ora edit and instance restart, so option D is invalid syntax/approach. (Later Oracle versions deprecated this parameter since archiving is automatic in ARCHIVELOG mode, but this question reflects the older behavior.)

Keep practicing — related questions