J
Jens Dahlin
Guest
We have (for some forgotten reason) on our main production db * 20 fixed (f 262144) After Image extents. * After Image Archiving set to -1 (ie archive when full). This is a bad combination since extents are almost never full in our environment. Extents are therefore rarely archived. Simply switching to an interval value (10 minutes or similar) is also not very good because of the large extents. What's a good approach here? - Switch to non-fixed extents? - Switch to a fixed but smaller amount of files (200 files x 1/10th the size or similar)? - Combine some of the above with a reasonable interval? - Something else? Note: we also run replication. Linux, 64-bit, 11.6.3 (11.7 in a few weeks).
Continue reading...
Continue reading...