Re: [h2] What would be the best update-candidate
what does your database URL look like? -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
[h2] What would be the best update-candidate
Hello, We are currently using version h2-1.3.176 In AUTO_SERVER mode we experiece corruption of various kinds: index not found 202 File corrupted while reading record: \[1280] stream data key:1344 pos:11 remaining:0\. rowCount expected 11462 got 11466 What would be the best / most stable update candidate ? (with the least ore none modification to our source ) Thanks in advance, Rinse -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] What would be the best update-candidate
OK, that's good, there is nothing problematic in your settings. Probably the best update-candidate is 1.4.184, but add MV_STORE=false to your URL to keep using the old(stable) storage engine. On 2015-01-09 10:23 AM, Rinse Lemstra wrote: Connecting to H2 database: jdbc:h2:file:c:\TimeWriter5Std\lib\..\data\xso_standard\default\Data.std.h2.db H2 properties: {AUTO_SERVER=TRUE, MODE=REGULAR, CACHE_SIZE=16384, DB_CLOSE_DELAY=0, IGNORECASE=TRUE, DATABASE_TO_UPPER=TRUE} Does this make sense ? -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] 1.4.182 corruption
he means 1.4.183 Op donderdag 8 januari 2015 23:52:40 UTC+1 schreef marcolopes: 1.3.183 ?? On Thursday, December 18, 2014 at 9:07:16 PM UTC, Thomas Mueller wrote: Hi, Yes, this looks like the bug that was fixed in version 1.3.183. I'm afraid this database is not recoverable. Regards, Thomas On Thu, Dec 18, 2014 at 1:53 PM, Dieter Cailliau dieter@gmail.com wrote: File corrupted while reading record: /tmp/bms.auto.mv.db. Possible solution: use the recovery tool [90030-182] http://127.0.1.1:8082/login.do?jsessionid=cd6441ab484bba9d2abe4db0d5455f69# 90030/90030 (Help) http://h2database.com/javadoc/org/h2/constant/ErrorCode.html#c90030 org.h2.jdbc.JdbcSQLException: File corrupted while reading record: /tmp/bms.auto.mv.db. Possible solution: use the recovery tool [90030-182] at org.h2.message.DbException.getJdbcSQLException(DbException.java:345 http://h2database.com/html/source.html?file=org/h2/message/DbException.javaline=345build=182 ) at org.h2.message.DbException.get(DbException.java:168 http://h2database.com/html/source.html?file=org/h2/message/DbException.javaline=168build=182 ) at org.h2.mvstore.db.MVTableEngine.init(MVTableEngine.java:115 http://h2database.com/html/source.html?file=org/h2/mvstore/db/MVTableEngine.javaline=115build=182 ) at org.h2.engine.Database.getPageStore(Database.java:2376 http://h2database.com/html/source.html?file=org/h2/engine/Database.javaline=2376build=182 ) at org.h2.engine.Database.open(Database.java:666 http://h2database.com/html/source.html?file=org/h2/engine/Database.javaline=666build=182 ) at org.h2.engine.Database.openDatabase(Database.java:266 http://h2database.com/html/source.html?file=org/h2/engine/Database.javaline=266build=182 ) at org.h2.engine.Database.init(Database.java:260 http://h2database.com/html/source.html?file=org/h2/engine/Database.javaline=260build=182 ) at org.h2.engine.Engine.openSession(Engine.java:60 http://h2database.com/html/source.html?file=org/h2/engine/Engine.javaline=60build=182 ) at org.h2.engine.Engine.openSession(Engine.java:167 http://h2database.com/html/source.html?file=org/h2/engine/Engine.javaline=167build=182 ) at org.h2.engine.Engine.createSessionAndValidate(Engine.java:145 http://h2database.com/html/source.html?file=org/h2/engine/Engine.javaline=145build=182 ) at org.h2.engine.Engine.createSession(Engine.java:128 http://h2database.com/html/source.html?file=org/h2/engine/Engine.javaline=128build=182 ) at org.h2.engine.Engine.createSession(Engine.java:26 http://h2database.com/html/source.html?file=org/h2/engine/Engine.javaline=26build=182 ) at org.h2.engine.SessionRemote.connectEmbeddedOrServer(SessionRemote.java:347 http://h2database.com/html/source.html?file=org/h2/engine/SessionRemote.javaline=347build=182 ) at org.h2.jdbc.JdbcConnection.init(JdbcConnection.java:108 http://h2database.com/html/source.html?file=org/h2/jdbc/JdbcConnection.javaline=108build=182 ) at org.h2.jdbc.JdbcConnection.init(JdbcConnection.java:92 http://h2database.com/html/source.html?file=org/h2/jdbc/JdbcConnection.javaline=92build=182 ) at org.h2.Driver.connect(Driver.java:72 http://h2database.com/html/source.html?file=org/h2/Driver.javaline=72build=182 ) at org.h2.server.web.WebServer.getConnection(WebServer.java:750 http://h2database.com/html/source.html?file=org/h2/server/web/WebServer.javaline=750build=182 ) at org.h2.server.web.WebApp.login(WebApp.java:957 http://h2database.com/html/source.html?file=org/h2/server/web/WebApp.javaline=957build=182 ) at org.h2.server.web.WebApp.process(WebApp.java:211 http://h2database.com/html/source.html?file=org/h2/server/web/WebApp.javaline=211build=182 ) at org.h2.server.web.WebApp.processRequest(WebApp.java:170 http://h2database.com/html/source.html?file=org/h2/server/web/WebApp.javaline=170build=182 ) at org.h2.server.web.WebThread.process(WebThread.java:137 http://h2database.com/html/source.html?file=org/h2/server/web/WebThread.javaline=137build=182 ) at org.h2.server.web.WebThread.run(WebThread.java:93 http://h2database.com/html/source.html?file=org/h2/server/web/WebThread.javaline=93build=182 ) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.IllegalStateException: Chunk 42948 not found [1.4.182/6] at org.h2.mvstore.DataUtils.newIllegalStateException(DataUtils.java:762 http://h2database.com/html/source.html?file=org/h2/mvstore/DataUtils.javaline=762build=182 ) at org.h2.mvstore.MVStore.getChunk(MVStore.java:853 http://h2database.com/html/source.html?file=org/h2/mvstore/MVStore.javaline=853build=182 ) at org.h2.mvstore.MVStore.readPage(MVStore.java:1805 http://h2database.com/html/source.html?file=org/h2/mvstore/MVStore.javaline=1805build=182 ) at org.h2.mvstore.MVMap.readPage(MVMap.java:769
Re: [h2] What would be the best update-candidate
Connecting to H2 database: jdbc:h2:file:c:\TimeWriter5Std\lib\..\data\xso_standard\default\Data.std.h2.db H2 properties: {AUTO_SERVER=TRUE, MODE=REGULAR, CACHE_SIZE=16384, DB_CLOSE_DELAY=0, IGNORECASE=TRUE, DATABASE_TO_UPPER=TRUE} Does this make sense ? regards, Rinse -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
Re: [h2] What would be the best update-candidate
Thanks for your advice. One final question: 1.3.176 is the last version with the 'Beta' addition. Am I right that this 'Beta' addition applies particulary on the MVstore code ? regards, Rinse Op vrijdag 9 januari 2015 09:36:20 UTC+1 schreef Noel Grandin: OK, that's good, there is nothing problematic in your settings. Probably the best update-candidate is 1.4.184, but add MV_STORE=false to your URL to keep using the old(stable) storage engine. On 2015-01-09 10:23 AM, Rinse Lemstra wrote: Connecting to H2 database: jdbc:h2:file:c:\TimeWriter5Std\lib\..\data\xso_standard\default\Data.std.h2.db H2 properties: {AUTO_SERVER=TRUE, MODE=REGULAR, CACHE_SIZE=16384, DB_CLOSE_DELAY=0, IGNORECASE=TRUE, DATABASE_TO_UPPER=TRUE} Does this make sense ? -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.
[h2] Should SHUTDOWN DEFRAG reduce the DB File size when all tables are empty?
URL: jdbc:h2:../data/audit;COMPRESS=TRUE;AUTOCOMMIT=FALSE;TRACE_LEVEL_FILE=4;lock_timeout=6;MVCC=FALSE;DB_CLOSE_ON_EXIT=TRUE;MV_STORE=TRUE;AUTO_SERVER=TRUE;AUTO_SERVER_PORT=7899 Version 1.4.184 - svn revision 6003 I know you must be tired of questions regarding db file size. I am just having difficulty understanding expected behavior versus potential issues. It db file is 3GB in size. My application has been running all night. I have been running pseudo compact routines every 10 minutes. pseudo compact: stmt.addBatch( set EXCLUSIVE 1 ); stmt.addBatch( set retention_time 0 ); stmt.addBatch( checkpoint ); stmt.addBatch( checkpoint ); stmt.addBatch( checkpoint ); stmt.addBatch( checkpoint ); stmt.addBatch( checkpoint ); stmt.addBatch( checkpoint ); stmt.addBatch( set retention_time 45000 ); stmt.addBatch( set EXCLUSIVE 0 ); stmt.executeBatch(); conn.commit(); *Note: my pseudo compact code actually appears to have no effect ( the code runs extremely fast which might indicate that it is not actually doing anything ) .* I paused my input and let everything quiesce. My DB has two tables. At this point both tables are empty - select count(*) from table X returns 0 for both tables. I then ran SHUTDOWN DEFRAG; It ran about 2 mins and the DB Size shrunk to 1.3GB - still quite large for any empty database. I re-ran the SHUTDOWN DEFRAG two more times each taking about 1.5 mins and had no change to file size. I do not have any specific indexes on my tables, however I do have primary keys defined which would create default indexes. I was thinking the index table space may have been taking this extra space. I dropped the primary keys and attempted the shutdown defrag again with no change. So am I seeing expected behavior or is this signs of a potential issue? -- 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 post to this group, send email to h2-database@googlegroups.com. Visit this group at http://groups.google.com/group/h2-database. For more options, visit https://groups.google.com/d/optout.