Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Thread 1 cannot allocate new log, sequence in Alert log

Kevin HondeJul 11 2012 — edited Jul 11 2012
Could someone help, I am getting the below message in my alert log

System: AIX6.1 - Oracle 11r2
GROUP#	THREAD#	MEMBER                                  ARCHIVED	STATUS	        MB
1	1	+DATA01/mydb/redolog_group1_member1	NO	    INACTIVE	        1536
1	1	+DATA01/mydb/redolog_group1_member2	NO	    INACTIVE	        1536
2	1	+DATA01/mydb/redolog_group2_member2	NO	    CURRENT		1536
2	1	+DATA01/mydb/redolog_group2_member1	NO	    CURRENT		1536
3	1	+DATA01/mydb/redolog_group3_member2	NO	    INACTIVE	        1536
3	1	+DATA01/mydb/redolog_group3_member1	NO	    INACTIVE	        1536
Tue Jul 10 18:37:48 2012
Thread 1 advanced to log sequence 28831 (LGWR switch)
  Current log# 1 seq# 28831 mem# 0: +DATA01/mydb/redolog_group1_member1
  Current log# 1 seq# 28831 mem# 1: +DATA01/mydb/redolog_group1_member2
Tue Jul 10 19:12:01 2012
Thread 1 advanced to log sequence 28832 (LGWR switch)
  Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
  Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
Tue Jul 10 19:39:00 2012
Thread 1 cannot allocate new log, sequence 28833
Private strand flush not complete
Tue Jul 10 19:39:18 2012
  Current log# 2 seq# 28832 mem# 0: +DATA01/mydb/redolog_group2_member1
  Current log# 2 seq# 28832 mem# 1: +DATA01/mydb/redolog_group2_member2
Tue Jul 10 19:41:21 2012
Thread 1 advanced to log sequence 28833 (LGWR switch)
  Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
  Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
Tue Jul 10 20:15:28 2012
Thread 1 cannot allocate new log, sequence 28834
Private strand flush not complete
  Current log# 3 seq# 28833 mem# 0: +DATA01/mydb/redolog_group3_member1
  Current log# 3 seq# 28833 mem# 1: +DATA01/mydb/redolog_group3_member2
Tue Jul 10 20:16:21 2012
Could an increase on the redo log file sizes solve this problem? Unfortunately I do not have a test platform, where I could have tested this.
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Aug 8 2012
Added on Jul 11 2012
14 comments
3,015 views