LOG_CHECKPOINT_INTERVAL

We're having a discussion regarding this parameter and what happens if it is set to 0.

Oracle Support say that this is a __BAD__ thing to do but haven't given a substansive reason why except to say that it forces lots of activity.

On a recent Oracle Performance Tuning (v7) course, my boss was told to set this to 0 in order to disable checkpoints (except when the log file changes over).

The Oracle Performance Tuning manual (O'Reilly & Associates) implies that the only valid parameters are 2 and above.

Any ideas?

Thanks, Andy Received on Wed Jun 17 1998 - 06:28:42 CDT