2GB Limitation Of JDBC Filestore When Using Zip Rendition Management
(Doc ID 1466729.1)
Last updated on SEPTEMBER 21, 2023
Applies to:
Oracle WebCenter Content - Version 11.1.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
A content server is configured to store all content using a webless jdbc storage rule. The ZipRenditionManagement component is also being used. When the combined size of all attachments to a single revision exceeds 2.0GB, the zip file containing the attachments can no longer be pulled successfully from the database.
The zip file appears to be successfully stored in the FileStorage table, however when the cached file system copy on the weblayout directory expires from cache and is deleted from the file system, UCM cannot retrieve a valid copy from the FileStorage table. The first 2 gigabytes of the zip file are successfully pulled from the database, but can't retrieve any more of it. The transfer then stops and the zip file is corrupted, causing the attachments to be corrupted and unretrievable as well.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |