Salesforce

Type II Storage Area - space allocation issue with creates and updates.

« Go Back

Information

 
TitleType II Storage Area - space allocation issue with creates and updates.
URL NameP123316
Article Number000165768
EnvironmentProduct: OpenEdge
Version: 10.0B05, 10.1A02, 10.1B
OS: All supported platforms
Other: Type II Storage Areas
Question/Problem Description
Database engine does not seem to reuse space when creating, deleting or update records in a Type II Storage Area.
Table resides in a Type II Storage Area that exhibits the excessive space usage.
Excessive space usage for a table that is in a Type II Storage Area.
PROSTRCT statistics shows the physical storage used by the table as 100 GB (Data blocks)
DBANALYS shows that Average Record size multiplied by Total # of records should occupy a minimum of 256 MB of disk space.
CHANALYS for the table shows many consecutive blocks with completely free space.
Fix for Defect PSC00174159 / OE00128403 applied.
Steps to Reproduce
Clarifying Information
Multiple users creating and updating records from one table simultaneously.

128 records per block
512 cluster size
8 KB database block size
Default create and toss limits.

 
Error Message
Defect NumberDefect PSC00184456 / OE00148573
Enhancement Number
Cause
It was found that when multiple users were inserting records to the same object in a Type II Storage Area at the same time, the RMCHAIN was not being searched deep enough before allocating additional cluster's worth of space, which causes the Storage Area to grow in excess of the actual space needed to complete the operation. 
Resolution
Upgrade to OpenEdge 10.1B02, 10.1C or later.

After the upgrade, the "excessive" free space on the RMCHAIN will be used for the particular table in the Type II area over time so a D&L is not needed.  However, if the free space is excessive and needs to be reclaimed immediately, a D&L is needed since once that space is allocated to a particular table in a Type II area, it will always be allocated to that table only.


 
Workaround
If applying the fix is not immediately possible, TABLEMOVE (or dump and load) of the affected table(s), which the application design allows for multiple users to be deleting and inserting large amounts of records from one table simultaneously, into it's own Type I Storage Area.
Notes
Keyword Phrase
Last Modified Date9/13/2015 9:59 AM

Powered by