1 of 1 people found this helpful
I know we've not had a problem with adding files to Oracle 9i and 10g that are larger than the block size, but I've not used 11g. Perhaps someone else can comment on their experience. But IIUC, Oracle's "db_block_size" simply defines the size of the (internal) blocks, and this does not limit the size of the values. For example, Oracle will use this value to determine if it can inline any LOB value small enough to fit into the same page as the rest of the row data; if not, it will store the LOB "out of line" on (multiple) other pages by breaking the LOB into chunks.
Perhaps you can check the database schema, and verify that the "DATA" column on the "MODE_SIMPLE_LARGE_VALUES" table has an appropriate length. When ModeShape creates this table (via Hibernate) in Oracle, SQL Server, Sybase, MySQL, PostgreSQL, Informix, and Teradata, the length is set to the database's default size for BLOBs. When using DB2 and Derby, ModeShape creates the column to have a length of 1GB.
You should be able to change the length of this column using the DB tools, and there isn't anything to configure in ModeShape.
Thanks for the quick answer,
after checking the data base structure I decided to try manually the query that hibernate does, and they are working. So the problem is not coming from Modeshape, but from the jdbc driver. My mistake was to use the last ojdbc driver available in the maven dependencies. Once I've changed ojdbc for ojdbc6 from Oracle the problem disappeared.
I'm glad it's working for you!