What can I do with this error?
The blob file size is 4GB
I try to optimize but this save the problem only temporary

Thanks Sorin  

On 9/4/2019 11:34 AM, Hershcu Sorin wrote:
> What can I do with this error?
> The blob file size is 4GB
> I try to optimize but this save the problem only temporary

What is the actual error - table full ?

Generally you need to enable largefilesupport if you need to go beyond
4GB file size. Make sure it's enabled for anything that access the file
directly.

Note that as of 2.28 this is ON by so i assume you're using older
version of EDB.

Raul

What is the actual error - table full ?

Generally you need to enable largefilesupport if you need to go beyond
4GB file size. Make sure it's enabled for anything that access the file
directly.

Note that as of 2.28 this is ON by so i assume you're using older
version of EDB.

Thanks Raul

Yes I'm getting the error table full.
I'm working with version 2.31.

I don't find anything about largefilesupport. Can you direct me how to fix this settings?
Thanks

Hershcu


LargeFileSupport is a property in the engine (and possibly the session). If you drop an EDBEngine component of a form look at its properties and set LargeFileSupport to True. I sort of remember that it used to default to False and I always used to reset it to True.

If you're not dropping an engine component on a form/datamodule then Engine.LargeFileSUpport := True at the start of your project should sort it.

You also say BLOB not CLOB so if you're storing graphics in there it may be that you have a malformed jpg (or something). They generally blow memory not file size but I had a few of those in my DBISAM days so in addition to setting LatgeFileSupport I'd also recommend checking your data.

Roy Lambert

Thanks Roy

I don't find LargeFileSupport properties not on EDBEngine and mot on EDBSession
Sorin

Hershcu


I should have checked the release notes before posting. I knew LargeFileSupport had been removed but didn't know when.

<<The following are breaking changes in 2.28:
Large file support is now enabled by default in ElevateDB. Along with this change, the TEDBEngine LargeFileSupport and TEDBSession LocalLargeFileSupport properties have been removed.

These are published properties, so please be sure to open, ignore any warnings about these properties being absent, and re-save any forms or data modules that use the TEDBEngine or TEDBSession components to ensure that you do not see any runtime missing property errors in your application(s).

Warning If you are using local ElevateDB sessions to directly access shared databases on a file server, you need to make sure that all client applications that are accessing the data are either updated to 2.28 or have their pre-2.28 TEDBEngine LargeFileSupport and/or LocalLargeFileSupport properties set to True. Failure to do so can cause the local ElevateDB sessions to not see each other's locks, which can lead to database corruption.>>

So next question - are all clients accessing the database at 2.31?

If so check the data.

Roy Lambert

On 9/5/2019 4:18 AM, Roy Lambert wrote:
>
> So next question - are all clients accessing the database at 2.31?
>
> If so check the data.
>

I'm with Roy here in making sure all clients are on 2.31 - this includes
dbsrvr if you use it.

Can you provide any info on the table itself - for example how large can
each row get ?

EDB (even with large file support) has 2GB max row size but in your case
it looks like a largefilesupprot issue still due to the 4GB blob file
size which was the limit with largefilesupport being off).

Other EDB capacity limits are here :

https://www.elevatesoft.com/manual?action=topics&id=edb2&product=rsdelphiwin32&version=10R&section=appendix_system_cap

Raul