Add new variable database extent and give previous var extent a fixed size

Len Kramer

New Member
I have a database with 14 fixed extents of 2Gb and 1 variable overflow extent. The variable extent is getting used now so I want to add some new extents.
But when I add a new variable extent, the current one will be made 'fixed' with the current size.
Is there a way to make this previous variable extent fixed with a size of 2Gb, like all other fixed size extents, instead of the current size without the need to resolve to a dump and load?
Version is 11.2
 
Last edited:

Rob Fitzpatrick

ProgressTalk.com Sponsor
When asking questions about OpenEdge capabilities, it is important to say which release you are using.

Is there a way to make this previous variable extent fixed with a size of 2Gb, like all other fixed size extents, instead of the current size
Yes. You can do this in OpenEdge 12.1+:

  • Extend and mark variable-length extents as fixed—Database administrators can now extend and mark variable-length extents as fixed as well as create and extend new variable-length extents.
    This feature allows you to:
    • Extend the size of an existing variable-length extent before converting it to fixed-length when adding a new variable-length extent to a storage area
    • Extend the size of an existing variable-length extent to a specific pre-grown size whether it is empty or already contains data
    • Extend the size of an existing variable-length extent to a specific pre-grown size and impose a maximum size cap
    • Create a new variable-length extent pre-extended to a specific size in a new or existing area
    • Create a new pre-extended variable-length extent with an imposed maximum size in a new or existing area
    • For more information, see Extend variable-length database extents.

without the need to resolve to a dump and load?
You don't need to dump and load to change the number or size of your extents. You can change such things with a backup and then a restore with a modified structure file.

I have a database with 14 fixed extents of 2Gb and 1 variable overflow extent.
Why do you feel the need for many extents that are exactly 2 GB in size? Do you not have large file support enabled? (proutil dbname -C describe).

Shameless plug:
If you want to monitor your storage areas and have the option of being alerted when areas or extents reach certain thresholds, you could use ProTop.
 

Len Kramer

New Member
Thanks for the feedback Rob.

Version is 11.2
I wrote 'dump and load' where I meant 'backup and restore'....
The 2 Gb fixed size is a historical thing I guess. No specific need for.
What info in the 'proutil describe' output tells me I have large file support enabled ?
I've made my own monitoring of the DB size. It sends me an e-mail when the 'overflow' extent starts to grow.
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
If you have database feature 5 enabled, you have large file support: extents can grow up to 1 TB instead of 2 GB. E.g.:

Code:
Database Features

   ID   Feature                            Active  Details
  ----  ---------------------------------  ------  -------
     5  Large Files                        Yes
     9  64 Bit DBKEYS                      Yes
    10  Large Keys                         Yes
    11  64 Bit Sequences                   Yes
    14  Multi-tenancy                      Yes
    23  New VST Tables                     Yes
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
I only have features 9, 10 and 11

Then that explains keeping your extents at no more than 2 GB! But with a modern (21st century) OS and OE 11, there is no reason not to have large file support enabled. You can do this the next time you shut down your database.

proutil dbname -C enablelargefiles
 

Len Kramer

New Member
Ok. The databases are on Windows server 2008 R2 standard, 64-bit and the daily backup already has a size of 33Gb so that's 'large file'.
These databases are up 24/7 but I can schedule a short maintance shutdown when there are no users logged on.
So a shutdown, the proutil command and a startup are all there is to it ?
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
So a shutdown, the proutil command and a startup are all there is to it ?
Yep. :)

While you're down, it's a good time to think of anything else you may want to do that requires downtime, to avoid a later shutdown. E.g.:
  • proutil dbname -C updateschema and updatevst, if you haven't done them since your last DLC install/service pack.
  • Set -tablerangesize/-indexrangesize/-omsize, if you haven't increased them since your last schema addition.
  • Any other database broker parameters you want to add or adjust.
  • Changing AI or BI block size or BI cluster size.
 

Stefan

Well-Known Member
Then that explains keeping your extents at no more than 2 GB! But with a modern (21st century) OS and OE 11, there is no reason not to have large file support enabled. You can do this the next time you shut down your database.

proutil dbname -C enablelargefiles
Good luck doing that with 11.2 and a workgroup database license ;-)
 

Rob Fitzpatrick

ProgressTalk.com Sponsor
Good luck doing that with 11.2 and a workgroup database license ;-)
I didn't see a mention of Workgroup in this thread...

And in my opinion, Workgroup RDBMS shouldn't be used for real application environments unless their DB size is trivial and add-ons are largely unneeded. I wouldn't call >28 GB trivial.

You should also be upgrading up from 11.2 to at least 11.7 and, better, 12.2
I second that.
 
Top