the location of archive logs arriving from a primary database
- From: "Xu, Roger" <Roger.Xu@xxxxxxxx>
- To: <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 21 Jan 2009 16:36:29 -0700
All,
I am a bit confused by the location of archive logs arriving from a
primary database in a standby database.
Oracle 10g Version - 10.2.0.4.0
Primary Settings: (MAXIMUM AVAILABILITY mode)
log_archive_dest_1: LOCATION=/upslt/server/database/archlogs
VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=ups60p0
log_archive_dest_2: SERVICE=ups60p1 LGWR SYNC AFFIRM
VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=ups60p1
standby_archive_dest: ?/dbs/arch
Standby Settings:
log_archive_dest_1: LOCATION=/upslt/server/database/archlogs
VALID_FOR=(ALL_LOGFILES, ALL_ROLES) DB_UNIQUE_NAME=ups60p1
log_archive_dest_2: SERVICE=ups60p0 LGWR SYNC AFFIRM
VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=ups60p0
standby_archive_dest: ?/dbs/arch
Why the archive log arriving from the primary ends up in
log_archive_dest_1 (/upslt/server/database/archlogs in my case), not
standby_archive_dest?
I believe in 9i, it lands on standby_archive_dest.
Thanks,
Roger Xu
IMPORTANT: As of December 31st, 2008, emails sent to cs-americas.com will no
longer be forwarded to dpsg.com. Please make sure to update your contacts to
reflect this change or mail will be undeliverable after that date.
Please be conscious of the environment and print this email only if absolutely
necessary.
This e-mail (including any attachments) is confidential and may contain
privileged information of Dr Pepper Snapple Group, Inc. and/or its subsidiaries
("Dr Pepper Snapple Group"). If you are not the intended recipient or receive
it in error, you may not use, distribute, disclose or copy any of the
information contained within it and it may be unlawful to do so. If you are not
the intended recipient, please notify us immediately by returning this e-mail
to us at mailto:mailerror@xxxxxxxx and destroy all copies. Any views expressed
by individuals within this e-mail do not necessarily reflect the views of Dr
Pepper Snapple Group. This e-mail does not constitute a binding offer,
acceptance, amendment, waiver or other agreement, unless the intent that an
e-mail will constitute such is clearly stated in the body of the email.
Recipients are advised to subject this e-mail and attachments to their own
virus checking, in keeping with good computing practice. Please note that
e-mail received by Dr Pepper Snapple Group may be monitored in accordance with
applicable law.
Other related posts:
