- 3,733,758 Users
- 2,246,818 Discussions
- 7,856,869 Comments
Forum Stats
Discussions
Howdy, Stranger!
Categories
- 380.9K All Categories
- 2.1K Data
- 203 Big Data Appliance
- 1.9K Data Science
- 446.1K Databases
- 220.4K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 506 MySQL Community Space
- 459 NoSQL Database
- 7.7K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 438 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.4K SQL & PL/SQL
- 20.8K SQL Developer
- 291.3K Development
- 6 Developer Projects
- 117 Programming Languages
- 288K Development Tools
- 96 DevOps
- 3K QA/Testing
- 645.2K Java
- 18 Java Learning Subscription
- 36.9K Database Connectivity
- 148 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.7K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 12 Java Essentials
- 138 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 195 Java User Groups
- 22 JavaScript - Nashorn
- Programs
- 178 LiveLabs
- 34 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 165 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
log file sync and block recovery from logseq
Hi all,
sometimes log file sync event spike on our 11.2.0.4 db on Solaris.
when we look at alert log at the same time we see following messages.
Block recovery from logseq 1462532, block 36595759 to scn 3522018885687
Recovery of Online Redo Log: Thread 1 Group 59 Seq 1462532 Reading mem 0
Mem# 0: +REDO/DBNAME/onlinelog/group_59.272.1047579261
Mem# 1: +REDO/DBNAME/onlinelog/group_59.356.1047581307
Block recovery completed at rba 1462532.36596324.16, scn 820.145702968
Block recovery from logseq 1462532, block 36594513 to scn 3522018885686
Recovery of Online Redo Log: Thread 1 Group 59 Seq 1462532 Reading mem 0
Mem# 0: +REDO/DBNAME/onlinelog/group_59.272.1047579261
Mem# 1: +REDO/DBNAME/onlinelog/group_59.356.1047581307
Block recovery completed at rba 1462532.36596324.16, scn 820.145702967
there is no message on lgwr trace and wait chains are below.
%This SECONDS AAS WAIT_CHAIN
------ ---------- ------- --------------------------------------------------------
32% 2985 96.3 -> log file sync -> LGWR wait for redo copy -> ON CPU
26% 2421 78.1 -> ON CPU
21% 1911 61.6 -> log file sync -> log file parallel write
Do you have reason for that?
Regards.
Answers
-
Do you see ANY trace files around the time of the event?
It looks like it might be a case of the buffered copy of a block being corrupt and Oracle doing an in-memory block recovery by reading the block from disc into the buffer cache than finding and applying any redo for that block to bring the buffer up to date.
If that's correct then it's possible there's an Oracle bug corrupting blocks occasionally, or you have a memory fault which is corrupting Oracle blocks.
Regards
Jonathan Lewis
UPDATE: The last couple of paragraphs of this note of mine make a few comments about the mechanism.
-
Another follow-up (for the same blog note). If you read the conversation starting at comment #9 it suggests that your alert log ought to have some details about the corrupt block just before the bit you've supplied. (So it if doesn't there's presumably some other reason for what's going on.)
Regards
Jonathan Lewis
-
Hi Jonathan,
thanks for reply. We did not see any trace files at that time.
Regards.