Home » RDBMS Server » Server Administration » Should I pass or keep this alert message? (Oracle 10.2.0.1, Sun Solaris 10 64 bit)
| Should I pass or keep this alert message? [message #385961] |
Thu, 12 February 2009 01:09  |
trantuananh24hg
Messages: 744
Registered: January 2007
Location: Ha Noi, Viet Nam
|
Senior Member |
|
|
Hi all!
I found these messages in alert log file such as
$ tail -500 $ORACLE_BASE/admin/VNP/bdump/alert_VNP.log
Thu Feb 12 12:12:53 2009
Thread 1 cannot allocate new log, sequence 1539
Private strand flush not complete
Current log# 2 seq# 1538 mem# 0: /vnporadataSYSTEM/VNP/redo02.log
Thread 1 advanced to log sequence 1539
Current log# 3 seq# 1539 mem# 0: /vnporadataSYSTEM/VNP/redo03.log
Thu Feb 12 13:25:13 2009
Thread 1 cannot allocate new log, sequence 1540
Private strand flush not complete
Current log# 3 seq# 1539 mem# 0: /vnporadataSYSTEM/VNP/redo03.log
Thread 1 advanced to log sequence 1540
Current log# 4 seq# 1540 mem# 0: /vnprctl/redoVNP_multiplex/redo04.log
Current log# 4 seq# 1540 mem# 1: /vnprctl/redoVNP_multiplex/redo05.log
Yeap,
Thread 1 cannot allocate new log, sequence 1539.
Private strand flush not complete
.
But well, it is likely to
Thread 1 cannot allocate new log, sequence 1540.
Check point not complete.
Then, I just want to check if the archive log in sequence 1539, 1540, ... existed or not in destination.
$ connect_system
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Feb 12 13:54:20 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
system@VNP> col name format a30
system@VNP> col status format a8
system@VNP> col time_complete format a25
system@VNP> select name, dest_id, status,
2 to_char(completion_time,'DD-MM-YYYY HH24:MI:SS') time_complete,
3 sequence#
4 from v$archived_log
5 where sequence# between 1536 and 1540
6 /
NAME DEST_ID STATUS TIME_COMPLETE SEQUENCE#
-------------------- ---------- -------- ------------------------- ---------
/vnporadataUSERS/arc 1 A 12-02-2009 12:04:40 1536
hiveVNP_dest1/1_1536
_650457529.arc
/vnporadataUSERS/arc 2 A 12-02-2009 12:04:40 1536
hiveVNP_dest2/1_1536
_650457529.arc
/vnporadataUSERS/arc 1 A 12-02-2009 12:05:50 1537
hiveVNP_dest1/1_1537
_650457529.arc
/vnporadataUSERS/arc 2 A 12-02-2009 12:05:50 1537
hiveVNP_dest2/1_1537
_650457529.arc
/vnporadataUSERS/arc 1 A 12-02-2009 12:12:54 1538
hiveVNP_dest1/1_1538
_650457529.arc
/vnporadataUSERS/arc 2 A 12-02-2009 12:12:54 1538
hiveVNP_dest2/1_1538
_650457529.arc
/vnporadataUSERS/arc 1 A 12-02-2009 13:25:18 1539
hiveVNP_dest1/1_1539
_650457529.arc
/vnporadataUSERS/arc 2 A 12-02-2009 13:25:18 1539
hiveVNP_dest2/1_1539
_650457529.arc
8 rows selected.
system@VNP> ! ls -lrt /vnporadataUSERS/archiveVNP_dest2/1_1536_650457529.arc
-rw-r----- 1 oracle dba 145315328 Feb 12 12:04 /vnporadataUSERS/archive
VNP_dest2/1_1536_650457529.arc
Well, it - random file existed in destionation. How about initialization parameters fast_start_mttr_target?
system@VNP> col name format a20
system@VNP> col value format a10
system@VNP> select name, value
2 from v$parameter
3 where name like 'fast_start%';
NAME VALUE
-------------------- ----------
fast_start_io_target 0
fast_start_mttr_targ 640
et
fast_start_parallel_ LOW
rollback
system@VNP>
Yeap, 640(s) for fast_start_mttr_target. And how about redo log files size?
system@VNP> COL group# format 999 heading 'Group'
system@VNP> col member format a30 heading 'Member' justify c
system@VNP> col status format a10 heading 'Status' justify c
system@VNP> col archived format a10 heading 'Archived'
system@VNP> col fsize format 9999,9999
system@VNP> col fsize format 9999,999,999 heading 'Size|(MB)'
system@VNP> select l.group#, MEMBER, MEMBERS, archived,
2 l.status, (BYTES / 1024 / 1024) fsize
3 from v$log l, v$logfile f
4 where f.group#=l.group#
5 order by 1
6 /
Size
Group Member MEMBERS Archived Status (MB)
----- ------------------------- ---------- ---------- ---------- -------------
1 /vnporadataSYSTEM/VNP/red 1 YES INACTIVE 1,000
o01.log
2 /vnporadataSYSTEM/VNP/red 1 YES INACTIVE 1,000
o02.log
3 /vnporadataSYSTEM/VNP/red 1 YES INACTIVE 1,000
o03.log
4 /vnprctl/redoVNP_multiple 2 NO CURRENT 2,000
x/redo04.log
4 /vnprctl/redoVNP_multiple 2 NO CURRENT 2,000
x/redo05.log
5 /vnprctl/redoVNP_multiple 2 YES INACTIVE 2,000
x/redo06.log
5 /vnprctl/redoVNP_multiple 2 YES INACTIVE 2,000
x/redo07.log
7 rows selected.
system@VNP>
11g for redo_log_file. I think it's quite normal for the log check point.
In Metalink, Note 435887.1, it said
Source: https://metalink2.oracle.com/metalink/plsql/f?p=130:14:2273297317127682665::::p14_database_id,p14_docid,p14_show_header,p14_show_help ,p14_black_frame,p14_font:NOT,435887.1,1,1,1,helvetica.
May you clarify me more why did the message occur when manually switch log file, but not automatically?
It is problem or not? And will it cause problem to database?
As a DBA, how will I do?
Thank you so much!
P/S: Please tell me how do I format this metalink address above in some words with hidden link, such as metalink_note_435887.1, the other can click in those words, then it will open the page?
Edit: Mahesh Rajendran
Removed the metalink content.
[Updated on: Thu, 12 February 2009 02:17] by Moderator Report message to a moderator |
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Fri Jul 05 03:59:29 CDT 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
