Log_Archive_Dest_1 Set To Default Even When DB_Recovery_File_Dest Is Set (Doc ID 553286.1)

Last updated on OCTOBER 31, 2016

Applies to:

Oracle Server - Enterprise Edition - Version 11.1.0.6 to 11.1.0.7 [Release 11.1]
Information in this document applies to any platform.
***Checked for relevance on 21-Nov-2012***


Symptoms

Archive logs are being written to a default location, even when the following conditions are met:
.
- LOG_ARCHIVE_DEST is not set
- LOG_ARCHIVE_DEST_n is not set
- DB_RECOVERY_FILE_DEST is set
.
This is contrary to the documentation:
.
"If you do not set any value for LOG_ARCHIVE_DEST, LOG_ARCHIVE_DEST_n, or DB_RECOVERY_FILE_DEST, then the redo logs are archived to a default location that is platform-specific."

This is causing higher disk space utilitization by archive logs than desired.

Test Case
----------

- Create 11.1.0.6 database using DBCA
- Click "enable archiving" in DBCA
- After DBCA completes, connect to the database and issue the following queries:
.

SQL> show parameter log_archive_dest
-- There should be no values for log_archive_dest or log_archive_dest_n.

SQL> show parameter db_recover
-- There should be values for the Flashback Recovery Area and its size, from DBCA.

SQL> select dest_name, destination from v$archive_dest;
-- There should be values in LOG_ARCHIVE_DEST_1 (default location), and
LOG_ARCHIVE_DEST_10 (USE_DB_RECOVERY_FILE_DEST).

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms