Dear All, good news first: the error was caused by running out of file-system space. Although this leads to a few questions:
1) would it not be possible to throw a more meaningful exception, e.g. "Failed to allocate table space" 2) why do especially indexes and constraints consume so much space in H2? To elaborate on question 2): I basically copy a few tables from Oracle to H2 using exactly the same table structures and indexes. Oracle shows a total table space size on 20 GBytes for these tables, indexes, lobs etc. Less than halve of that content transferred to H2 consumed more than 50 GByte already? I used only INSERT INTO statements. Not one single SELECT or VIEW has been used, so I can assume that is "data only". After having dropped all Constraints and Indexes from the H2 database, I ran the transfer again. This time it worked and much(!) less filespace is used: [manticore@ifrsbox-app ~]$ ls -lh .manticore/ifrsbox_bak.* -rw-rw-r-- 1 manticore manticore *9.5G* Aug 29 05:25 .manticore/ifrsbox_bak.mv.db -rw-rw-r-- 1 manticore manticore 3.6K Aug 29 04:30 .manticore/ifrsbox_bak.trace.db -rw-rw-r-- 1 manticore manticore 47K Aug 29 03:51 .manticore/ifrsbox_bak.xml 40+ GByte for Indexes and Constraints on 10 GByte of content? Last question please: 3) Is the a way to use compression when writing the H2 database file? I would like to use the H2 merely as a container for transporting data (instead of Schema dumps) and I wounder if a GZIP/BZIP stream could be used to write a compressed file. Compressing the H2 file with LZMA reduces the size to 2GB (only), so there seems to be a lot of redundancy. Thank you for kind help and support in advance. Cheers Andreas -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To unsubscribe from this group and stop receiving emails from it, send an email to h2-database+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/h2-database/e866f7e6-baea-4cd2-a03b-b543bf2b511f%40googlegroups.com.
