Re: "Thread 1 cannot allocate" msgs showing up after 10gR2 Upgrade

From: GeoPappas <PappasG_at_gmail.com>
Date: 6 Jan 2006 05:56:07 -0800
Message-ID: <1136555767.090882.259090@g49g2000cwa.googlegroups.com>

<< Is there an actual Oracle error message number? >>

No, there is no ORA error message or number. The warnings show up in the alert log and a snippet from the log is as follows:

Thread 1 advanced to log sequence 1165
  Current log# 6 seq# 1165 mem# 0:
+DISK_GROUP_1/esclrd1/onlinelog/group_6.262.1
Thu Jan 5 02:00:04 2006
Thread 1 cannot allocate new log, sequence 1166 Private strand flush not complete
  Current log# 6 seq# 1165 mem# 0:
+DISK_GROUP_1/esclrd1/onlinelog/group_6.262.1
Thread 1 advanced to log sequence 1166
  Current log# 2 seq# 1166 mem# 0:
+DISK_GROUP_1/esclrd1/onlinelog/group_2.258.1

I have researched the issue and understand why it is happening, I just don't understand why it IS happening under 10gR2 and why it WASN'T happening under 10gR1! It seems like something changed in the new release that is causing this to happen. Received on Fri Jan 06 2006 - 07:56:07 CST