Enabling large files should be a standard behavior when creating a new database with f.e. prostrct create.
Now you have to do this in a separate step, which is often forgotten.
I agree. Additionally, I would like to have large files support for workgroup database as well.
If your st file has an extent which is larger than 2GB then I believe large files is enabled automatically on create, but it shouldn't have to rely on that.
I am managing more than 10 000 DB which are on 18 servers.
I developp a process which allow to add X extend by area by DB by day
I had to make a choice, if one of the DB is growing abnormaly :
- this DB crash because there is no space left in an area (after several automatical add extend)
- more than 500 databases crash at the same time because there is no space left on the file system.
It is easier to repair & restart one db.
it is harder when you have more than 500 db to repair at the ame time.
Hi Patrice, I understand your situation. I don't say that enabling large files should be the only option. What I say is that I want a change in behavior. So for example PROSTRCT CREATE should standard enable large files. Progress can add an extra parameter to it to disable large files in case that you don't want this, like PROSTRCT CREATE -disablelargefiles. Because I think a majorty of the people wants to enable large files in a enterprise environment.
I think Marko Myllymäki post a good idea on the enhancement "enable_large_files_should_be_removed_or_default" (11/29/2017)
=> It would be great if the large files option could be set while the database is online.
If this option exists, you could run it when you want "on a online DB" (and several times on the same database without issue).
The option to disable the "Enable Large File" will be impossible (if an extend is bigger than 2Gb.) => You must do a Dump&Load
Hi Patrice, I read the post of Marko Myllymäki and I agree with you. The option enablelargefiles should never be removed. Enable large files should be standard on, but there also should be an option to disable large files, like I sugested by using a parameter -disablelargefiles with prostrct create or proutil -C disablelargefiles. And of course this option should be an online option.
How can i do a real "Dump-Load" on line?
i can imagine to do something like a Dump-Load "on line" and remove the area which have extend bigger than 2Gb but :
- i am not sure that there is no "Flag" ">2Gb "
- i should redo my backup and replication target
It is easier to add an option than to remove it.
If i were you, i will use the folowing workaround. it will work with NO modification of OE.
- modify my startup database script to add "proutil [db] -C enablemargefile" before the "proserve [db] ...."
There is no issue to enable large file several time on the same db.