Feedback
Did this article resolve your question/issue?

   

Article

Can Torn Pages arise when Type II Areas are used

« Go Back

Information

 
TitleCan Torn Pages arise when Type II Areas are used
URL NameCan-torn-pages-happen-on-Type-II-Areas-with-a-database-block-size-bigger-than-4-KB
Article Number000174232
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: Database
Question/Problem Description
Can Torn Pages arise when Type II Areas are used ?
Do Type II Storage Areas prevent Torn Pages when the database blocksize is larger than the filesystem blocksize ?
Can torn pages happen on Type II Areas with a database block size bigger than the filesystem blocksize
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
The torn page problem refers to a problem that may exist when the data block is bigger than the filesystem page size and the data block is not completely written into disk due to a hardware problem or energy failure.

Torn pages can happen to both Type I or Type II areas when a data block write is interrupted.
  • With Type I Storage Areas there is no way to know that a torn page happened. 
  • The difference with Type II areas is that they store a check sum stored in all data block headers, enabling the detection of torn pages with block checksum error 14410:
Checksum validation of dbkey <Arg1> block type <Arg2> in area <Arg3> does not match data. Expected: <Arg4> received <Arg5>. (14410)

For further information on Torn Pages, refer to :

The attached Exchange 2006 presentation by GUS BJORKLUND
"OpenEdge R RDBMS Performance Tuning Made Simple", 5.4 Choosing Data Block Size

The "Using a larger database blocksize than the filesystem blocksize" Section in Article:
The consequence that may arise when using non-Progress backups in Article:
Workaround
Notes
Last Modified Date11/20/2020 7:07 AM
Attachment 
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.