Kbase P101520: What are the consequences of using the No Crash Recovery (-i) parameter?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/25/2005 |
|
Status: Unverified
GOAL:
What are the consequences of using the No Crash Recovery (-i) parameter?
GOAL:
What is the No Crash Recovery (-i) option?
GOAL:
How does using the -i option affect BI growth?
FIX:
The -i startup parameter tells Progress to run without using database integrity or recovery.
Do not use this options unless you have a complete backup of the database and can rerun procedures in case of a system failure. If the system fails for any reason when the database is running in no integrity mode, then there is no chance for recovery other than restoring from a backup. Furthermore, the -i parameter should never be used on a database with AI enabled.
Progress running with the -i parameter will eliminate a significant amount of I/O, writing less data and BI blocks out to disk, thereby improving the performance of some procedures. However, even if the -i parameter is specified, Progress still provides Undo/Redo logging so that transactions that have not yet been committed can still be backed out. Therefore, whilst BI growth will be reduced, it will not be eliminated entirely as Undo/Redo logging will still be occurring, especially during large transactions. Only those notes related specifically to crash recovery are omitted.
The No Crash Recovery option is intended for use when doing bulk data loading or large batch runs as a means to boost performance. The -i parameter is not intended as a means to reduce BI growth or to save file system space on the disk where the BI file is located; use of the -i parameter in this fashion is not supported.