Feedback
Did this article resolve your question/issue?

   

Article

What benefit does running a database with the No Crash Protection (-i) provide?

« Go Back

Information

 
TitleWhat benefit does running a database with the No Crash Protection (-i) provide?
URL NameP16747
Article Number000132339
EnvironmentProduct: Progress OpenEdge
Version: All supported versions
OS: All supported platforms
Question/Problem Description
What benefit does running a database with the No Crash Protection Startup Parameter (-i) provide?
How to run a Progress database with No Integrity?
Can Before Image bi-writes be prevented?
What are the risks of running with No Crash Protection?
Should AI be disabled before accessing the database with the -i (no-integrity) flag?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
Running a database with the -i startup parameter causes fewer data and before-image blocks to be written to disk. Running with No Crash Protection (no-integrity) makes I/O intensive operations run much faster, such as binary load operations. This is because when running with the -i (no-integrity) startup flag (-i forces -R) - Buffered Synchronous I/O (O_RDWR) to the bi file and no bi/data order synchronization occurs. For further discussion refer to Article  Does Progress use Synchronous or Asynchronous I/O?   

This means that if the database were to crash or a user get killed even if the system were not to crash as a result, there is no guarantee that crash recovery will complete. In this case, we don't even try to recover, the database is inaccessible:
** The last session was run with the no integrity (-i) parameter. (509) 
** Your database cannot be repaired. You must restore a backup copy. (510)

No Crash Protection (-i) should never be used unless a valid/complete backup exists. Should the database crash while running with No Crash Protection, the database will not be able to go through crash recovery. The only recourse when this happens is to revert to backup. Refer to Article  Database errors 509 and 510 after abnormal shutdown using no crash protection (-i) parameter  

The no-integrity (-i) option should not be used with a database that has AI enabled. Refer to Article  No integrity and AI files   

Understanding the risks, performance is vastly improved running with no integrity (-i) and should be used for distinct I/O intensive operations. For example:
Workaround
Notes
Last Modified Date11/20/2020 7:08 AM
Attachment 
Files
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.