Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback, please email oracle-forums_moderators_us@oracle.com

cannot allocate new log, sequence # Private strand flush not complete

A. UyanikApr 25 2014 — edited Apr 29 2014

Dear Oracle fanatics ,

Since some time now we have been facing the following message after an backup :

Completed:       alter tablespace SYSTEM begin backup

Thu Apr 24 04:42:21 2014

      alter tablespace SYSTEM end backup

Thu Apr 24 04:42:21 2014

Completed:       alter tablespace SYSTEM end backup

Thu Apr 24 04:42:21 2014

      alter tablespace TOOLS begin backup

Completed:       alter tablespace TOOLS begin backup

Thu Apr 24 04:42:38 2014

      alter tablespace TOOLS end backup

Thu Apr 24 04:42:38 2014

Completed:       alter tablespace TOOLS end backup

Thu Apr 24 04:42:38 2014

      alter tablespace UNDO begin backup

Completed:       alter tablespace UNDO begin backup

Thu Apr 24 04:46:01 2014

Thread 1 advanced to log sequence 346923 (LGWR switch)

  Current log# 1 seq# 346923 mem# 0: /usr/mvf/data/dbase/redo/redo01.log

Thu Apr 24 04:52:18 2014

alter tablespace UNDO end backup

Thu Apr 24 04:52:20 2014

Completed:  alter tablespace UNDO end backup

Thu Apr 24 04:52:27 2014

  alter database backup controlfile to '/usr/mvf/data/dbase/arch/MVFcontrolfile.0424010014'

Thu Apr 24 04:52:29 2014

Completed:   alter database backup controlfile to '/usr/mvf/data/dbase/arch/MVFcontrolfile.0424010014'

Thu Apr 24 04:52:29 2014

  1. ALTER SYSTEM ARCHIVE LOG
  2. Thu Apr 24 04:52:29 2014
  3. Thread 1 cannot allocate new log, sequence 346924
  4. Private strand flush not complete
  5. Current log# 1 seq# 346923 mem# 0: /usr/mvf/data/dbase/redo/redo01.log

Thu Apr 24 04:52:30 2014

Thread 1 advanced to log sequence 346924 (LGWR switch)

  Current log# 2 seq# 346924 mem# 0: /usr/mvf/data/dbase/redo/redo02.log

Thu Apr 24 05:02:04 2014

Thread 1 advanced to log sequence 346925 (LGWR switch)

  Current log# 3 seq# 346925 mem# 0: /usr/mvf/data/dbase/redo/redo03.log

I dont think it should be because of the size of the redo , but to be sure i will post info about those as well :

    GROUP#    THREAD#  SEQUENCE# ARC STATUS           REDOLOG_FILE_NAME                                     SIZE_MB

---------- ---------- ---------- --- ---------------- -------------------------------------------------- ----------

         1          1     347040 YES INACTIVE         /usr/mvf/data/dbase/redo/redo01.log                                      200

         2          1     347041 YES INACTIVE         /usr/mvf/data/dbase/redo/redo02.log                                      200

         3          1     347042 YES INACTIVE         /usr/mvf/data/dbase/redo/redo03.log                                      200

         4          1     347043 YES INACTIVE         /usr/mvf/data/dbase/redo/redo04.log                                      200

         5          1     347044 YES INACTIVE         /usr/mvf/data/dbase/redo/redo05.log                                      200

         6          1     347045 NO  CURRENT          /usr/mvf/data/dbase/redo/redo06.log                                     200

         7          1     347037 YES INACTIVE         /usr/mvf/data/dbase/redo/redo07.log                                      200

         8          1     347038 YES INACTIVE         /usr/mvf/data/dbase/redo/redo08.log                                      200

         9          1     347039 YES INACTIVE         /usr/mvf/data/dbase/redo/redo09.log                                      200

                       Number

                           of

Date                 Switches Redo Size

-------------------- -------- ---------

14-04-11                  110    22,000

14-04-19                   96    19,200

14-04-06                   55    11,000

14-04-17                  139    27,800

14-04-18                  116    23,200

14-04-21                  102    20,400

14-04-23                  122    24,400

14-04-16                  124    24,800

14-04-25                   36     7,200

                       Number

                           of

Date                 Switches Redo Size

-------------------- -------- ---------

14-04-09                  119    23,800

14-04-10                  116    23,200

14-04-14                  114    22,800

14-04-15                  110    22,000

14-04-13                   72    14,400

14-04-07                  104    20,800

14-04-12                   98    19,600

14-04-20                   61    12,200

14-04-24                  117    23,400

                       Number

                           of

Date                 Switches Redo Size

-------------------- -------- ---------

14-04-08                  116    23,200

14-04-22                  115    23,000

                     -------- ---------

sum                      2042   408,400

20 rows selected.

I hope some bright mind out there may shed some light on the fact why this message keeps pestering our Alert system

Many Thanks in advance ,

Ahmet Uyanik

This post has been answered by Dude! on Apr 26 2014
Jump to Answer
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on May 27 2014
Added on Apr 25 2014
13 comments
8,625 views