Summary: What to do when Entry arrays or collection attribute types are very large, so that the database cannot store them in a one-column cell.
OverviewWhen persisting a space with JDBC, there are situations where Entry arrays or collection attribute types are very large and the database in use cannot store such objects in a one-column cell. In such situations, the following recommendations might help:
Using BLOBs with Oracle DatabaseTo store large binary fields using BLOBs with Oracle 9i and earlier versions, add the following line to the jdbc.properties file: lobHandlerClass=com.j_spaces.sadapter.GenericJDBC.OracleLobHandler (default = com.j_spaces.sadapter.GenericJDBC.DefaultLobHandler) Oracle LOB definitions can be customized in the jdbc.properties using the LOB clause while creating a table, for example: CREATE TABLE ContainsLOB_tab (n NUMBER, c BLOB) LOB (c) STORE AS SEGNAME (TABLESPACE lobtbs1 CHUNK 4096PCTVERSION 5NOCACHE LOGGINGSTORAGE (MAXEXTENTS 5)); Each Entry class with large fields can be customized in the jdbc.properties in the following way: entryClassName.lobClause = LOB (c) STORE AS SEGNAME ( TABLESPACE lobtbs1 CHUNK 4096PCTVERSION 5NOCACHE LOGGINGSTORAGE (MAXEXTENTS 5)); |
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |