My Oracle Support Banner

DGARC1 Set For Primary LOG_ARCHIVE_DEST_1 When Creating DG Configuration (Doc ID 277881.1)

Last updated on APRIL 03, 2020

Applies to:

Oracle Database - Enterprise Edition - Version 9.2.0.1 to 9.2.0.5 [Release 9.2]
Information in this document applies to any platform.

Symptoms

NOTE: In the images and/or the document content below, the user information and environment data used
represents fictitious data from the Oracle sample schema(s),Public Documentation delivered with an
Oracle database product or other training material. Any similarity to actual environments, actual
persons, living or dead, is purely coincidental and not intended in any manner.



For the purposes of this document, the following fictitious environment is used as an example
to describe the procedure:

Service Name  = dgarc1
Directory = c:\dgarc1 and all subdirectories

 

When creating a DataGuard Configuration using the DataGuard Manager tool from Oracle Enterprise Manager and your primary database is set to NOARCHIVELOG mode when you start, DataGuard Manager will set this to ARCHIVELOG mode for you.

Research has found, however, that the LOG_ARCHIVE_DEST_1 for the primary will be set to a bogus value in this case. Namely the following nonsensical value:

log_archive_dest_1 string location=dgarc1 mandatory

This is nonsensical because LOCATION implies a directory on disk, not a service name.

Please note that LOG_ARCHIVE_DEST_1 on the primary SHOULD ALWAYS be set to a location (disk directory) value. Example:


log_archive_dest_1 string location=c:\dgarc1 mandatory

Changes

 

Cause

To view full details, 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 a vibrant support community of peers and Oracle experts.