[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590854#action_12590854 ] Bassel Kh commented on DERBY-2475: -- Hello again, 1- I'm using only one class loader for derby driver. 2- I had two different databases with two different URLs, I thought may be because of that, but I merged them in one database with two different schemas, but the problem is still happening 3- I tried with and without C3P0, the same issue!! 4- I checked derby 10.4, the same issue. 5- This problem is blocking our release, and most of customer's complains are because of loosing information. Thanks in advanced, invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590861#action_12590861 ] Knut Anders Hatlen commented on DERBY-2475: --- You mentioned that you have tested it with Derby 10.4, but you didn't state the exact version number. A problem that could cause database corruption (DERBY-3347) was recently fixed on the 10.4 branch, so it would be interesting to know whether or not you ran your test with that fix. I think the discussion should be moved away from this bug report, as it is closed and its environment description says that it's possibly a broken hard drive, in which case it is not a Derby bug. The following open bug reports also mention invalid checksum errors, and I think it would be best to continue the discussion on one of them: DERBY-2677 DERBY-3087 DERBY-3606 DERBY-3607 DERBY-3611 invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590149#action_12590149 ] Bassel Kh commented on DERBY-2475: -- Win XP SP2 JVM 1.5 also. The problem is still happening frequently. Note1: I've been testing my application on H2 DB, it is working pretty fine without any corruption, so can I say that there is something from Derby side? Note2: I was using C3P0, but after I removed it, it clearly reduced the frequency of corruption invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587126#action_12587126 ] Shahbaz commented on DERBY-2475: Its Win XP SP2, JVM 1.5 invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12587123#action_12587123 ] Kristian Waagan commented on DERBY-2475: I note that you say you are frequently facing this issue. Which platform are you running on? (Windows, Linux, Solaris, Mac etc). invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586761#action_12586761 ] Shahbaz commented on DERBY-2475: I am able to reproduce the same in Derby 10.3.2.2 with JVM 1.5 on WinXP SP2. invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586789#action_12586789 ] Bassel Kh commented on DERBY-2475: -- I'm frequently facing this issue, most of the times; when I shutdown my server then start its service, the database log says (Invalid checksum), I'm working with 10.3.2.2, and I tested it also on 10.4 (latest one), I don't have anything special to do, I'm using Hibernate 3.1.rc3, and JVM 1.6 I'm still stocking in this point waiting for somebody to help, every day we have the same complain from our customers about the same issue. invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are there any follow-on symptoms? yes, my app crashes ;-(( i'm not shure how well i reinit the db connection. Or did the application seem to behave properly after the user shut it down and restarted it? Can the customer later access the data properly on their notebook? Or do you have to move the files to another machine in order to access the data? restarts did not help as far as i know. but but when i copied it onto my harddrive it was ok. thanks, thank you! fabian thanks fabian -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511417 ] James Calfee commented on DERBY-2475: - After the corruption, I restored the latest backup of the database which seemed to cure the problem. The select statement worked fine. However, soon after (new data was inserted) the corruption re-surface in the same way (not sure which row). I'm sorry that I do not have this copy; only the copy after the corruption. This happened on my development database so I probably had to Kill the Java VM. This computer has been very stable. The database files were stored on standard Inspiron E1505 hard drive from on a reiserfs partition (local, non-RAID, non-RAM). Output from the sysinfo program: -- Java Information -- Java Version:1.5.0_08 Java Vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/java-1.5.0-sun-1.5.0.08/jre Java classpath: /home/slim/java/db-derby-10.2.2.0-bin/lib/derby.jar:/home/slim/java/db-derby-10.2.2.0-bin/lib/derbynet.jar:/home/slim/java/db-derby-10.2.2.0-bin/lib/derbytools.jar:/home/slim/java/db-derby-10.2.2.0-bin/lib/derbyclient.jar OS name: Linux OS architecture: i386 OS version: 2.6.17-10-generic Java user name: slim Java user home: /home/slim Java user dir: /home/slim/java/db-derby-10.2.2.0-bin/bin java.specification.name: Java Platform API Specification java.specification.version: 1.5 - Derby Information JRE - JDBC: J2SE 5.0 - JDBC 3.0 [/home/slim/java/db-derby-10.2.2.0-bin/lib/derby.jar] 10.2.2.0 - (485682) [/home/slim/java/db-derby-10.2.2.0-bin/lib/derbytools.jar] 10.2.2.0 - (485682) [/home/slim/java/db-derby-10.2.2.0-bin/lib/derbynet.jar] 10.2.2.0 - (485682) [/home/slim/java/db-derby-10.2.2.0-bin/lib/derbyclient.jar] 10.2.2.0 - (485682) -- - Locale Information - Current Locale : [English/United States [en_US]] Found support for locale: [cs] version: 10.2.2.0 - (485682) Found support for locale: [de_DE] version: 10.2.2.0 - (485682) Found support for locale: [es] version: 10.2.2.0 - (485682) Found support for locale: [fr] version: 10.2.2.0 - (485682) Found support for locale: [hu] version: 10.2.2.0 - (485682) Found support for locale: [it] version: 10.2.2.0 - (485682) Found support for locale: [ja_JP] version: 10.2.2.0 - (485682) Found support for locale: [ko_KR] version: 10.2.2.0 - (485682) Found support for locale: [pl] version: 10.2.2.0 - (485682) Found support for locale: [pt_BR] version: 10.2.2.0 - (485682) Found support for locale: [ru] version: 10.2.2.0 - (485682) Found support for locale: [zh_CN] version: 10.2.2.0 - (485682) Found support for locale: [zh_TW] version: 10.2.2.0 - (485682) -- Ubuntu = Linux, kernel version 2.6.17-10-generic java version 1.6.0 Java(TM) SE Runtime Environment (build 1.6.0-b105) Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing) This is really 1 CPU with a dual core: processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2050 @ 1.60GHz stepping: 8 cpu MHz : 800.000 cache size : 2048 KB physical id : 0 siblings: 1 core id : 255 cpu cores : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr bogomips: 3195.79 processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 14 model name : Genuine Intel(R) CPU T2050 @ 1.60GHz stepping: 8 cpu MHz : 1600.000 cache size : 2048 KB physical id : 1 siblings: 1 core id : 255 cpu cores : 1 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe nx constant_tsc pni monitor est tm2 xtpr bogomips: 3192.13 invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511156 ] Stan Bradbury commented on DERBY-2475: -- These problems could be caused by the environment being used, I/O issues or JVM / memory problems. One vexing issue (vexing because it cannot be reproduced reliably and is set by default for Windows) is the issue write caching being enabled for disks. I recommend disabling this for all database disks as it can cause data loss (e.g. corruption) if there is a failure. For information on disabling write caching see: http://support.microsoft.com/kb/259716. [ NOTE the warning in RED at the end of this article ] I've seen file / store-level corruptions like this caused by environmental factors. It wouild be very helpful to get detailed environment information with these reports. In particular: SYSINFO information to identify build information and environment settings java -version output to provide JVM specifics (build) Description of the processor - SMP? Description of the storage systems - RAM disks? RAID arrays? Local disks (not network mounted disks) being used? The original report where copying the database to another machine resolves the problem sounds like the problem was a in-memory corruption (assuming the system was shutdown and the entire directory tree copied) - possibly a JVM issue? invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Priority: Critical Attachments: defekt2.zip one of my customers gets on a notebook the following exception: 2007-03-17 09:01:53.042 GMT: Booting Derby version The Apache Software Foundation - Apache Derby - 10.2.2.0 - (485682): instance c013800d-0111-5f21-a736-02cd2118 on database directory C:\Programme\merkisoft\kursverwaltung\database\kurs Database Class Loader started - derby.database.classpath='' BEGIN SHUTDOWN ERROR STACK - ERROR XSDG2: Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump hex dump = see attachment i'm using the embedded version together with hibernate on the notebook. when i transfer the db to my pc and execute select * from all tables i get no errors at all. we checked the disk about 3 times (with error correction): no result and it still happens. when i create a new db on the notebook it happens after a while again. the db is about 35 mb. i could put it somewhere for developers (please email me). i've seen someone else having a similar problem but i couldn't find a solution yet. any help is very welcome! -- hi bryan thanks for the quick reply! i tried to answer your questions. i hope it helps. Does this happen for this customer over and over? Or did it happen only once? yes only that, but it happend 6 times. Is the customer able to provoke the error on demand? i tried without success but i keep testing it. Can you relate the exception to any particular action that the customer is taking in your application? till now no. If it has happened multiple times, is it always the same page on the same container? Or is the location different each time? we installed the app serveral times and i think the following lines are per installation (so per installation it happend on the same page): org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(28,Container(0, 1248)), expected=3'455'715'557, on-disk version=3'357'396'866, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(461,Container(0, 1248)), expected=3'908'279'257, on-disk version=137'782'528, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(482,Container(0, 1248)), expected=4'113'528'744, on-disk version=44'301'386, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(702,Container(0, 944)), expected=2'598'292'545, on-disk version=3'174'535'138, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(2767,Container(0, 944)), expected=2'067'623'629, on-disk version=2'180'532'620, page dump follows: Hex dump: org.hibernate.util.JDBCExceptionReporter - Invalid checksum on Page Page(99,Container(0, 1248)), expected=242'030'294, on-disk version=3'389'026'885, page dump follows: Hex dump: When the exception happens, are
[jira] Commented: (DERBY-2475) invalid checksum
[ https://issues.apache.org/jira/browse/DERBY-2475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508706 ] James Calfee commented on DERBY-2475: - Basically the same thing has happened to me twice now. I'm using 10.2.2.0 on Sun's Java 1.5 and Ubuntu. I have a single character column that got hit both times. I can select all the data from other columns just fine. This is occurs using the embedded driver with only one parameter create=true. All settings are out-of-the-box. I have added some code recently to purge a cache in some another table which may have aggravated this bug.It is very irregular and I'm having to restore backups and reset a sequence to recover from it ;-( .. I only wish I knew which (if an) older version of Derby is free from this error. I did see a post back in 2005 about this so I'm not so sure if downgrading could help (or perhaps that was really a disk error). It this case, does not look like a disk error since the corruption is so confined and happened in the exact same place on both occasions. I have been doing routine table compression successfully for some time now. Please let me know if I can help. ERROR XSDG2: Invalid checksum on Page Page(679,Container(0, 19472)), expected=232,875,440, on-disk version=4,193,292,366, page dump follows: Hex dump: : 0075 0001 0004 0003 .u.. 0010: 000a 0020: 0001 0030: 0406 0008 0040: 0004 3e72 002a 0028 6338 3765 3239 .rc87e29 0050: 3936 3630 6137 3962 6433 6565 3737 6465 9660a79bd3ee77de ... snip ... Lots of zeros omitted 7fd0: 7fe0: 10b1 486e 0764 094d ...ﾱHn...d.M 7ff0: 003c 0728 f9f0 904e ..ﾐN at org.apache.derby.iapi.error.StandardException.newException(Unknown Source) at org.apache.derby.impl.store.raw.data.StoredPage.validateChecksum(Unknown Source) at org.apache.derby.impl.store.raw.data.StoredPage.initFromData(Unknown Source) at org.apache.derby.impl.store.raw.data.CachedPage.setIdentity(Unknown Source) at org.apache.derby.impl.services.cache.CachedItem.takeOnIdentity(Unknown Source) at org.apache.derby.impl.services.cache.Clock.addEntry(Unknown Source) at org.apache.derby.impl.services.cache.Clock.find(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.getUserPage(Unknown Source) at org.apache.derby.impl.store.raw.data.FileContainer.getNextHeadPage(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseContainer.getNextPage(Unknown Source) at org.apache.derby.impl.store.raw.data.BaseContainerHandle.getNextPage(Unknown Source) at org.apache.derby.impl.store.access.conglomerate.GenericScanController.positionAtNextPage(Unknown Source) at org.apache.derby.impl.store.access.conglomerate.GenericScanController.fetchRows(Unknown Source) at org.apache.derby.impl.store.access.heap.HeapScan.fetchNextGroup(Unknown Source) at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.reloadArray(Unknown Source) at org.apache.derby.impl.sql.execute.BulkTableScanResultSet.getNextRowCore(Unknown Source) at org.apache.derby.impl.sql.execute.ProjectRestrictResultSet.getNextRowCore(Unknown Source) at org.apache.derby.impl.sql.execute.BasicNoPutResultSetImpl.getNextRow(Unknown Source) at org.apache.derby.impl.jdbc.EmbedResultSet.movePosition(Unknown Source) at org.apache.derby.impl.jdbc.EmbedResultSet.next(Unknown Source) at net.spamcomplaint.dao.JunkMailDAO.getJunkIds(JunkMailDAO.java:337) at net.spamcomplaint.swing.MessagePanel.loadMessages(MessagePanel.java:136) at net.spamcomplaint.swing.MessagePanel.init(MessagePanel.java:92) at net.spamcomplaint.swing.ApplicationPanel.init(ApplicationPanel.java:49) at net.spamcomplaint.swing.ApplicationFrame.createAndShowGUI(ApplicationFrame.java:35) at net.spamcomplaint.swing.ApplicationFrame.init(ApplicationFrame.java:20) at net.spamcomplaint.App.main(App.java:301) Shutting down Derby... invalid checksum Key: DERBY-2475 URL: https://issues.apache.org/jira/browse/DERBY-2475 Project: Derby Issue Type: Bug Components: Store Affects Versions: 10.2.2.0 Environment: windows xp, notebook, possibly broken hard drive! Reporter: Fabian Merki Priority: Critical Attachments: defekt2.zip one of my customers gets on a notebook the following exception:
