[
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 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-000002cd2118
> 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.