Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D8FD31063B for ; Sat, 22 Mar 2014 00:29:01 +0000 (UTC) Received: (qmail 94633 invoked by uid 500); 22 Mar 2014 00:29:01 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 94607 invoked by uid 500); 22 Mar 2014 00:29:01 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 94598 invoked by uid 99); 22 Mar 2014 00:29:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Mar 2014 00:29:01 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bertlamb@gmail.com designates 209.85.128.173 as permitted sender) Received: from [209.85.128.173] (HELO mail-ve0-f173.google.com) (209.85.128.173) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Mar 2014 00:28:55 +0000 Received: by mail-ve0-f173.google.com with SMTP id oy12so3334473veb.18 for ; Fri, 21 Mar 2014 17:28:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=Ft52qHJOyBF/ImXHOFS7dLmV+qp4UrQvpONjcrSidV4=; b=mTOqawlFSTtXF9AHSTcFnG3QMzYu5VJQPHVvLjLsY2h6Qoo+XhQv96YR5Jfq/rXIB4 patibGWWzIfzimLuSzBoQ8v5LuTIg2gVNCTkd0bA4gla6I5Ttz5ROfYGGVFfN6F4sSuT PIJLS1FJsY7yGOmus6MXTG1Oimgowa8/RZ3o1vmOfGAWOTItFrxA1OkVzuEqeHeg35kA 34qfg06ZTmqjTDRNBjjk9Xskge1OcrU4eyUWGs+tophh0mFf3VJIZ5qgbtXwdXgCHdJf UnArA3ZQokY2Nm1fEm1v8ZU5ma6+0a7fdtWjlZ3zNbf54PkLPHBD74WRucJVXlmzN8Zi 2u0Q== MIME-Version: 1.0 X-Received: by 10.221.40.10 with SMTP id to10mr22696545vcb.22.1395448113660; Fri, 21 Mar 2014 17:28:33 -0700 (PDT) Sender: bertlamb@gmail.com Received: by 10.58.213.165 with HTTP; Fri, 21 Mar 2014 17:28:33 -0700 (PDT) Date: Fri, 21 Mar 2014 20:28:33 -0400 X-Google-Sender-Auth: V7a2FHpVrUhSX-AYGjtBVFO1ZY0 Message-ID: Subject: ERROR XSAI2: The conglomerate (65) requested does not exist. From: Bert Lamb To: derby-user@db.apache.org Content-Type: multipart/alternative; boundary=001a113375761e085104f527155c X-Virus-Checked: Checked by ClamAV on apache.org --001a113375761e085104f527155c Content-Type: text/plain; charset=UTF-8 I have a database that seems to be in a pretty bad state. Is there any graceful way to recover when I am getting conglomerate errors like the one below? This is a 10.8 DB for what it is worth. j> select * from sys.sysconglomerates; ERROR XSAI2: The conglomerate (65) requested does not exist. -Bert --001a113375761e085104f527155c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I have a database that seems to be in a pretty bad state.= =C2=A0 Is there any graceful way to recover when I am getting conglomerate = errors like the one below?=C2=A0 This is a 10.8 DB for what it is worth.

j> select * from sys.sysconglomerates;
ERROR XSAI2: The conglomer= ate (65) requested does not exist.

-Bert
<= /div> --001a113375761e085104f527155c--