log file switch (archiving needed)
- From: "Xu, Roger" <Roger.Xu@xxxxxxxx>
- To: "Oracle-L Group" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 6 Mar 2009 11:10:41 -0700
Environment: 2 node Data Guard (10.2.0.4.0 - 64bit )
Is this normal or there is an issue? So far, nobody complaints
performance problem.
SQL> select time_waited from v$system_event where event = 'log file
switch (archiving needed)';
TIME_WAITED
-----------
715859487
Thu Mar 5 23:05:26 2009
LGWR: Standby redo logfile selected to archive thread 1 sequence 433
LGWR: Standby redo logfile selected for thread 1 sequence 433 for
destination LOG_ARCHIVE_DEST_2
Thu Mar 5 23:05:26 2009
Thread 1 advanced to log sequence 433 (LGWR switch)
Current log# 1 seq# 433 mem# 0:
/SRV_ACE/server/database/logs/redo01.log
Fri Mar 6 03:39:02 2009
LGWR: Standby redo logfile selected to archive thread 1 sequence 434
LGWR: Standby redo logfile selected for thread 1 sequence 434 for
destination LOG_ARCHIVE_DEST_2
Fri Mar 6 03:39:02 2009
Thread 1 advanced to log sequence 434 (LGWR switch)
Current log# 2 seq# 434 mem# 0:
/SRV_ACE/server/database/logs/redo02.log
Fri Mar 6 04:39:02 2009
LGWR: Standby redo logfile selected to archive thread 1 sequence 435
LGWR: Standby redo logfile selected for thread 1 sequence 435 for
destination LOG_ARCHIVE_DEST_2
Fri Mar 6 04:39:02 2009
Thread 1 advanced to log sequence 435 (LGWR switch)
Current log# 3 seq# 435 mem# 0:
/SRV_ACE/server/database/logs/redo03.log
Fri Mar 6 04:49:01 2009
LGWR: Standby redo logfile selected to archive thread 1 sequence 436
LGWR: Standby redo logfile selected for thread 1 sequence 436 for
destination LOG_ARCHIVE_DEST_2
Fri Mar 6 04:49:01 2009
Thread 1 advanced to log sequence 436 (LGWR switch)
Current log# 1 seq# 436 mem# 0:
/SRV_ACE/server/database/logs/redo01.log
Waiting for a log switch because the log that the LGWR will be switching
into has not been archived yet. Check the alert file to make sure that
archiving has not stopped due to a failed archive write. To speed
archiving, consider adding more archive processes or putting the archive
files on striped disks.
http://www.drpeppersnapplegroup.com/about/corporate to learn more about Dr
Pepper Snapple Group’s commitment to corporate social responsibility.
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:
- » log file switch (archiving needed) - Xu, Roger
