[TABLE="class: htmlDetailElementTable, width: 806"]
[TR]
[TD="bgcolor: initial"]I have a database that has been running since May 2010, when it was dumped and reloaded in OE10.1A, WinSrv2008R2 (later upgraded to OE10.2B). The ST-file gives the db about 10GB of space in several areas (Type II areas), the area "db-rapp" about 7GB. (extent def. looks like this: ...d "db-rapp":9,64;512...).
Yesterday the db shut down and reported "(10601) SYSTEM ERROR: Attempted to exceed maximum size on file ... " on the area "db-rapp" (the variable overflow extent had exceeded 2GB). When I check the _dbstatus._dbstatus-emptyblks, I find that I have very little free space in the db.
However, when I run proutil/dbanalys, it reports that the entire db only uses a total of about 1.5GB, and about 1.2GB in the area "db-rapp".
My question is: how can the area db-rapp go full when it has 7GB of space to use, and the data only takes up 1.2GB? (Indexes are not in the same area). I can see that dump/load probably solves the problem, but probably only temporarliy?
I might add that the area has a lot of data created and deleted all the time - very high turnover.
Best regards
Aasold Ekelund
Orgsoft as, Norway
[/TD]
[/TR]
[/TABLE]
[TR]
[TD="bgcolor: initial"]I have a database that has been running since May 2010, when it was dumped and reloaded in OE10.1A, WinSrv2008R2 (later upgraded to OE10.2B). The ST-file gives the db about 10GB of space in several areas (Type II areas), the area "db-rapp" about 7GB. (extent def. looks like this: ...d "db-rapp":9,64;512...).
Yesterday the db shut down and reported "(10601) SYSTEM ERROR: Attempted to exceed maximum size on file ... " on the area "db-rapp" (the variable overflow extent had exceeded 2GB). When I check the _dbstatus._dbstatus-emptyblks, I find that I have very little free space in the db.
However, when I run proutil/dbanalys, it reports that the entire db only uses a total of about 1.5GB, and about 1.2GB in the area "db-rapp".
My question is: how can the area db-rapp go full when it has 7GB of space to use, and the data only takes up 1.2GB? (Indexes are not in the same area). I can see that dump/load probably solves the problem, but probably only temporarliy?
I might add that the area has a lot of data created and deleted all the time - very high turnover.
Best regards
Aasold Ekelund
Orgsoft as, Norway
[/TD]
[/TR]
[/TABLE]