This content has been marked as final. Show 17 replies
Are you seeing some issues other than this message in the db ? If yes then post them here, else just ignore because these messages are not a cause for concern unless there is a significant gap in seq# between the "cannot allocate new log" message and the "advanced to log sequence" message.
our dataware house database is too slow to responce. Private strand flush not complete is coming after 1 or 2 minutes
i have add and resize redo logs, and now current size is 1.7gb.
log_buffer size is 33M, while in our another 10g database log_buffer size 4M. And its working.
RAM is 32g and server has one physical processor has 64 virtual processors (0-63) UltraSPARC-T2 (chipid 0, clock 1165 MHz)
i am confused about the cpu speed, i think the problem is due to cpu, becuase we have one physical processor.
below are system statistics:
SNAME PNAME PVAL1 PVAL2
SYSSTATS_INFO STATUS COMPLETED
SYSSTATS_INFO DSTART 07-08-2012 13:00
SYSSTATS_INFO DSTOP 07-09-2012 05:41
SYSSTATS_INFO FLAGS 1
SYSSTATS_MAIN CPUSPEEDNW 714
SYSSTATS_MAIN IOSEEKTIM 10
SYSSTATS_MAIN IOTFRSPEED 4,096
SYSSTATS_MAIN SREADTIM 0
SYSSTATS_MAIN MREADTIM 3,248
SYSSTATS_MAIN CPUSPEED 312
SYSSTATS_MAIN MBRC 16
SYSSTATS_MAIN MAXTHR 368,645,120
SYSSTATS_MAIN SLAVETHR 83,968
No, I don't think that there is any considerable issue with CPU statistics which you provided for this message. If you still feel that its something with CPU then please check below link :
1.Post the output of select * from v$version;
3.select l.group#, lf.member, l.bytes/1024/1024 mb, l.status, l.archived
from v$logfile lf, v$log l
where l.group# = lf.group#
order by 1, 2;
4.Are there some datafile which are not autoextended ? Because since its a message only, not a warning or a bug or an error, whose sense is user sessions trying to generate redo, wait on this event when LGWR waits for DBWR to complete flushing redo from IMU buffers into the log buffer; when DBWR is complete LGWR can then finish writing the current log, and then switch log files.
As this message means that we haven't completed writing all the redo information to the log when we are trying to switch, you can tell us how many redo log groups are the there and whats the size of the member? Are the redo log files on slower disk? You need to check disk performance too where redo logfiles and datafiles are stored. What are the top-5 wait events from AWR?
1. select * from v$version;
Oracle Database 11g Enterprise Edition Release 18.104.22.168.0 - 64bit
2. os version = 5.10 Generic_144488-09 sun4v sparc SUNW,Sun-Blade-T6320
3. select l.group#, lf.member, l.bytes/1024/1024 mb, l.status, l.archived from v$logfile lf, v$log l
where l.group# = lf.group# order by 1, 2;
GROUP# MEMBER MB STATUS ARCHIVED
1 +DATA1/finc/onlinelog/group_1.258.787920895 200 INACTIVE NO
1 +DATA1/finc/onlinelog/group_1.261.787920953 200 INACTIVE NO
2 +DATA2/finc/onlinelog/group_2.272.788019709 200 INACTIVE NO
2 +DATA2/finc/onlinelog/group_2.274.788019729 200 INACTIVE NO
3 +DATA2/finc/onlinelog/group_3.275.788019737 200 INACTIVE NO
3 +DATA2/finc/onlinelog/group_3.276.788019743 200 INACTIVE NO
4 +DATA1/finc/onlinelog/group_4.273.787921255 200 INACTIVE NO
4 +DATA1/finc/onlinelog/group_4.274.787921265 200 INACTIVE NO
5 +DATA2/finc/onlinelog/group_5.268.788018911 200 INACTIVE NO
5 +DATA2/finc/onlinelog/group_5.269.788018927 200 INACTIVE NO
6 +DATA2/finc/onlinelog/group_6.270.788018935 200 CURRENT NO
6 +DATA2/finc/onlinelog/group_6.271.788018943 200 CURRENT NO
6 +DATA2/finc/onlinelog/group_6.273.788019717 200 CURRENT NO
7 +DATA2/finc/onlinelog/group_7.277.788023645 500 INACTIVE NO
7 +DATA2/finc/onlinelog/group_7.278.788023657 500 INACTIVE NO
4. datafiles are autoextend
*all datafiles, tem and undo data files are big files.