LGWR Is Generating Trace file with 'Warning Log Write Time 540ms, Size 5444kb' In 10.2.0.4 Database
2011-10-10 09:56
573 查看
he customer is reporting trace files being generated with the following message:
Warning: log write time 540ms, size 5444KB
*** 2008-05-14 10:19:02.686
Warning: log write time 1470ms, size 5533KB
*** 2008-05-14 10:19:03.546
Warning: log write time 860ms, size 2230KB
*** 2008-05-14 10:23:04.183
Warning: log write time 2940ms, size 5701KB
*** 2008-05-14 10:23:05.758
Warning: log write time 1580ms, size 4234KB
*** 2008-05-14 10:23:07.559
Warning: log write time 1800ms, size 5701KB
Changes
The problem surfaced after upgrading to 10.2.0.4.
Cause
The above warning messages has been introduced in 10.2.0.4 patchset. This warning message will be generated only if the log write time is more than 500 ms and it will be written to the lgwr trace file .
Solution
These messages are very much expected in 10.2.0.4 database in case the log write is more than 500 ms.
This is a warning which means that the write process is not as fast as it intented to be . So probably you need to check if the disk is slow or not or for any potential OS causes. If everything looks fine at the hardware level or OS level then you
can safely ignore these messages. The trace file can easily be deleted or truncated.
Warning: log write time 540ms, size 5444KB
*** 2008-05-14 10:19:02.686
Warning: log write time 1470ms, size 5533KB
*** 2008-05-14 10:19:03.546
Warning: log write time 860ms, size 2230KB
*** 2008-05-14 10:23:04.183
Warning: log write time 2940ms, size 5701KB
*** 2008-05-14 10:23:05.758
Warning: log write time 1580ms, size 4234KB
*** 2008-05-14 10:23:07.559
Warning: log write time 1800ms, size 5701KB
Changes
The problem surfaced after upgrading to 10.2.0.4.
Cause
The above warning messages has been introduced in 10.2.0.4 patchset. This warning message will be generated only if the log write time is more than 500 ms and it will be written to the lgwr trace file .
Solution
These messages are very much expected in 10.2.0.4 database in case the log write is more than 500 ms.
This is a warning which means that the write process is not as fast as it intented to be . So probably you need to check if the disk is slow or not or for any potential OS causes. If everything looks fine at the hardware level or OS level then you
can safely ignore these messages. The trace file can easily be deleted or truncated.
相关文章推荐
- LGWR Is Generating Trace file with 'Warning Log Write Time 540ms, Size 5444kb' In 10.2.0.4 Database
- 【每日一摩斯】-LGWR Is Generating Trace file with "Warning: Log Write Time 540ms, Size 5444kb" In 10.2.0.4
- ubuntu make[1]: Warning: File `scripts/Makefile.host' has modification time 3.4e+08 s in the future
- 错误:Warning: File `../table/table.pro' has modification time 3.9e+08 s in the future
- LGWR TRACE Warning: log write time
- The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods install
- The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods install
- Can't allocate space for object 'syslogs' in database 'ge' because 'logsegment' segment is full/has no free extents. If you ran
- ORA-01103: database name 'LCRO' in control file is not 'DUMMY'
- Warning: File `src/core/nginx.h' has modification time 1.2e+07 s in the future
- LGWR TRACE Warning: log write time
- LGWR Trace Warning: Log Write Time ? Maybe not an issue
- Warning: File `src/core/nginx.h' has modification time 1.2e+07 s in the future
- The transaction log for database 'NJ_Address' is full. To find out why space in the log cannot be
- ASE Can't allocate space for object 'syslogs' in database 'WEN' because 'logsegment' segment is full
- make[1]: Warning: File `libbb/Makefile.in' has modification time 3.2e+04 s in the future 错误
- RMAN恢复报错: ORA-01103: database name 'POWERDES' in control file is not 'PDUNQ'
- The sandbox is not in sync with the Podfile.lock. Run 'pod install' or update your CocoaPods install
- make: Warning: File `Makefile' has modification time 2.4e 08 s in the future
- ld: i386 architecture of input file `exit.o' is incompatible with i386:x86-64 output