Kbase P103940: Error 9452 trying to start a database - before-image extent had NOT reached 2GB limit
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
06/05/2005 |
|
Status: Unverified
SYMPTOM(s):
Error 9452 trying to start a database
SYSTEM ERROR: Attempted to exceed maximum size on file <pname>.bx (9452)
SYSTEM ERROR: Attempted to exceed maximum size on file <pname>. (9452)
Error 9452 refers to a before-image extent
Database before-image extent is variable but limited to a specific size
Database extent had not reached 2GB limit (2147483648 bytes)
CAUSE:
Size for the database extent has been reached
FIX:
Execute the following steps:
1) If you have a current copy of the structure file (.st file) and you are sure that this is the current setting you can skip 2 and go to directly to step 3.
2) If you don't have a current or do not a .st file available for this database Run prostruct with option LIST to generate a new .st file.
*** Warning *** If you currently have a .st file that has the same file name of your database and wish to save a copy at it is, you need to have a copy of it to another directory or move it to another directory before executing this step, otherwise this file will be overwritten with the current information obtained from the current .db file.
prostrct list <database name>
3) Edit the .st file and remove the argument that is making it fixed in size or increase the current size.
eg: in the .st file you may have a line that looks like
b .\sports.b1 v 100
by removing the "v 100" from this line or increasing the value, you are allowing it to grow beyond 100 MB.
Remember you may still have OS limitation of 2GB unless that you have enable Large Files support. See Solution 21184 for more information on enabling Large Files.
4) Save the changes that you made to your .st file.
5) Run prostruct again but now using option REPAIR to apply the changes to the database.
prostrct repair <database name> <.st file>
6) Restart the database.
** Note that you may experience some delay on this database startup depending on how many pending transactions or how long may take to undo those pending transaction that were left behind when the limitation on the file size occurred.
The database startup may looks like hanging for while displaying message
"Begin Physical Redo Phase at <current address>. (5326)"
but this is expected.