We use progress 9.1D and we have two After Image extents.
st file:
a /ext2/mfgdata/prod/mfgprod.a1
a /ext2/mfgdata/prod/mfgprod.a2
Sometimes we run into the limit of 2 gb and the database crashes.
How can we setup these after image files with fixed and growing extents?
9.1D is, of course, ancient, obsolete and unsupported. You should upgrade to at least 9.1E04.
Two extents is wrong.
You should always have at least 4. 8 is better.
So step #1 would be to add a couple more extents.
Depending on your OS you could also enable large files.
I am guessing, however, that your real problem is that you do not really understand after-imaging and that you have no process in place to automatically switch extents and archive the full extents to an external location on a regular schedule (like every 15 minutes). You are probably only switching extents when you backup (look in your .lg file to see how often you switch extents). Am I right?
This presentation should answer a lot of questions about how AI works and how you should set it up.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.