[
https://issues.apache.org/jira/browse/DERBY-3607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-3607:
----------------------------------
> 1. Corrupted DB can not be used in any case, so we are using fresh db but once
generated.
great, that is fine.
> 2. Online back up component is on but it never happened, DB gets corrupted bef
ore back up. so it never happened during tests.
ok, now I won't worry about looking at the online backup code.
> 3. Shutdown process, I already explained in previous posts and startup is simp
le, we just start the dbs, start the connections and start the normal work for a
pplication. We do the same work to reproduce the same, the only difference is th
at some times it appears quickly and some times it needs some 6-7 restarts. Our
application doesn't know when its corrupted, but as user we can know with functi
onality failures and logs. Corrupted tables are not consistent meaning some time
s some tables and some times another tables.
> 4. Do you want to say that corruption happens during running of application?
It is all a guess at this point. But often with these types a problems the
corruption happens at an earlier time either as part of the application or
part of a previous shutdown. This problem has the feel of the page being
fine in the buffer cache, but somehow being corrupted as it is being written
out. Because of the cache the application may run just fine accessing the
"corrupted on disk page" because the good copy is still in cache.
> 5. I can send you application exe with DB, which is around 200 MB, as sample i
s not able to corrupt the same. for the same we can create one ftp account for y
ou guys to download and test from their.
if you can set up a download site and instructions on how to reproduce, seems
much more likely someone will be able to figure out what is going on.
If the 200mb example does not reproduce the issue then that does not seem
helpful. Go ahead and set up ftp of case that reproduces the problem,
along with details on how to reproduce.
> Invalid checksum error in Derby 10.3.2.1
> ----------------------------------------
>
> Key: DERBY-3607
> URL: https://issues.apache.org/jira/browse/DERBY-3607
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.3.2.1, 10.4.1.3
> Environment: OS-WIN XP SP2, 1.86GHz, 2GB, JVM 1.5, disk caching
> disabled, Hibernate 3.1.1.RC3,c3p0
> Reporter: Shahbaz
> Priority: Critical
> Attachments: DB_10.4logs.zip, derby.log, derby.log, derby.log,
> hibernate.cfg.xml, hibernate.cfg.xml, hibernate.cfg.xml, modules.properties,
> SingleThread Test.zip
>
>
> I am getting this execption when ever I try to restart my application
> java.sql.SQLException: Invalid checksum on Page Page(0,Container(0, 2033)),
> expected=2,731,401,932, on-disk version=2,375,776,513, page dump follows: Hex
> dump:
> 00000000: 0076 0000 0001 0000 0000 0000 0002 0000 .v..............
> 00000010: 0000 0006 0000 0000 0000 0000 0000 0000 ................
> 00000020: 0000 0000 0001 0000 0000 0000 0000 0000 ................
> 00000030: 0000 0000 0000 0000 0000 0000 ffff ffff ................
> 00000040: ffff ffff 0000 0000 0000 0000 0000 0000 ................
> 00000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 00000060: 0000 0000 0000 0000 0000 0000 5000 0000 ............P...
> at org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.TransactionResourceImpl.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedConnection.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.ConnectionChild.handleException(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedPreparedStatement.executeStatement(Unknown
> Source)
> at
> org.apache.derby.impl.jdbc.EmbedCallableStatement.executeStatement(Unknown
> Source)
> at org.apache.derby.impl.jdbc.EmbedPreparedStatement.execute(Unknown
> Source)
> at
> com.mchange.v2.c3p0.impl.NewProxyCallableStatement.execute(NewProxyCallableStatement.java:3044)
> at
> ae.sphere.arena.database.management.backup.BackupStategy.createBackup(BackupStategy.java:56)
> at
> ae.sphere.arena.database.management.backup.BackupStategy.doSchedulerJob(BackupStategy.java:41)
> at
> ae.sphere.arena.common.jobscheduler.Scheduler$1.run(Scheduler.java:49)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
> 00000070: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 00000080: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 00000090: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 000000a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
> 000000b0: 0000 0
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
