Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C1CC810426 for ; Mon, 2 Dec 2013 14:31:02 +0000 (UTC) Received: (qmail 83782 invoked by uid 500); 2 Dec 2013 14:29:41 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 83745 invoked by uid 500); 2 Dec 2013 14:29:38 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 83720 invoked by uid 99); 2 Dec 2013 14:29:36 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Dec 2013 14:29:36 +0000 Date: Mon, 2 Dec 2013 14:29:36 +0000 (UTC) From: "Rick Hillegas (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DERBY-6425) DB got corrupted during the heavy operations. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13836546#comment-13836546 ] Rick Hillegas commented on DERBY-6425: -------------------------------------- Hi Patil, Here are some questions we often ask about data corruptions: 1) Do you run the compression procedures on the tables? 2) Is the conglomerate number (2032) the conglomerate number of a table or an index? The following query will give you that information: select s.schemaName, t.tableName, c.conglomerateName, c.isIndex from sys.sysschemas s, sys.systables t, sys.sysconglomerates c where c.tableid = t.tableid and t.schemaid = s.schemaid and c.conglomerateNumber = 2032; 3) Is the disk write-cache enabled? If so, do you suffer frequent power outages or other system disruptions? Thanks, -Rick > DB got corrupted during the heavy operations. > --------------------------------------------- > > Key: DERBY-6425 > URL: https://issues.apache.org/jira/browse/DERBY-6425 > Project: Derby > Issue Type: Bug > Components: Store > Affects Versions: 10.9.1.0 > Environment: Suse 10. > Reporter: patil devidas > Priority: Critical > > ------------ BEGIN SHUTDOWN ERROR STACK ------------- > ERROR XSDG2: Invalid checksum on Page Page(5482,Container(0, 2032)), expected=3,506,219,016, on-disk version=492,279,644, page dump follows: Hex dump: > 00000000: 0075 0000 0001 0000 0000 0000 0067 0022 .u...........g.. > 00000010: 0000 0028 0000 0000 0000 0000 0000 0000 ................ > 00000020: 0000 0000 0001 0000 0000 0000 0000 0000 ................ > 00000030: 0000 0000 0000 0000 0000 0000 0406 000a ................ > 00000040: 0026 0024 6139 3630 3261 6266 2d33 3163 ....a9602abf.31c > 00000050: 662d 3131 6533 2d38 3363 632d 6231 3935 f.11e3.83cc.b195 > 00000060: 6138 3139 3263 6334 000b 0009 434f 4d50 a8192cc4....COMP > 00000070: 4c45 5445 4400 0c07 dd0a 0a00 1310 0c05 LETED........... > 00000080: 4e08 4000 0c07 dd0a 0a00 1310 1c03 1975 N..............u -- This message was sent by Atlassian JIRA (v6.1#6144)