Consultor Eletrônico

Status: Unverified

GOAL:

Use of the -i parameter

FIX:

The following is extracted from the documentation.

No Crash Protection (-i)

The No Crash Protection (-i) parameter tells PROGRESS to run without using database integrity or database recovery. When running PROGRESS without database integrity, it writes fewer data and before-image blocks to the disk. In this mode, some PROGRESS procedures (such as those that create and delete large numbers of records) run significantly faster than if they are running with database integrity.
When running PROGRESS with the -i parameter, transaction undo is supported. Therefore, there will still be a before-image file which might grow quite large during very long transactions.
Use this parameter to do bulk data loading or for large batch runs. It reduces the number of disk input or output operations. Loading a database for the first time is a good example of a use for this parameter.

NOTE: If you run PROGRESS with the -i parameter, and PROGRESS fails for any reason, you cannot recover the database, but must restore a backup.

Do not use the -i parameter unless you have a complete backup of the database and can rerun procedures in case of a system failure. If the system fails during a PROGRESS session started without crash protection, restore the backup copy and rerun the necessary procedures.

The following messages might appear when starting a PROGRESS session after a system failure -

After a system failure while a full-integrity PROGRESS session was running:

**The last session was abnormally terminated.
**Any incomplete transactions are being backed out.
**Database recovery is complete. You must rerun all active transactions.

After a system failure while a no-integrity PROGRESS session (-i) was running, on the other hand:

**The last session was abnormally terminated.
**The last session was run with the -i no integrity option.
**Your database cannot be repaired, you must restore a backup copy.