RE: log file switch - checkpoint incomplete and db file sequential
- From: "Powell, Mark" <mark.powell2@xxxxxx>
- To: ORACLE-L <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 4 Aug 2014 17:38:12 +0000
The REDO processing not dependent on the commit of data. You just need more or
bigger online redo logs to handle the level of activity. UNDO is made
available for reuse on commit.
The topics of REDO and UNDO are introduced in the Concepts manual and more
detail on the management of each exists in the DBA Administration manual.
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Eriovaldo Andrietta
Sent: Sunday, August 03, 2014 1:09 PM
To: ORACLE-L
Subject: log file switch - checkpoint incomplete and db file sequential
Hello,
I have a session that is running for around 3 hours (for 1200.000 lines) and
just 1 commit. And now events I can see are :
log file switch - checkpoint incomplete
db file sequential,
free buffer waits
I got in the net, the following explanation for it :
The log file switch - checkpoint incomplete event tells you that Oracle wants
to reuse a redo log file, but the current checkpoint position is still in that
log file. This results in redo generation being stopped until the log switch is
done. Obviously not good!
My doubt is: my session will return for COMMIT ?
Oracle will release the redo ?
Or must I abort it and control the number of COMMIT´s by code ?
Regards
Eriovaldo
Other related posts:
