Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (athena.apache.org: domain of georges@mhsoftware.com
 designates 209.169.14.178 as permitted sender)
Message-ID: <528A5261.9070500@mhsoftware.com>
Date: Mon, 18 Nov 2013 10:46:09 -0700
From: "George S." <georges@mhsoftware.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Derby Discussion <derby-user@db.apache.org>
Subject: Re: How to drop a bad table?
References: <1384746786052-135693.post@n7.nabble.com>
In-Reply-To: <1384746786052-135693.post@n7.nabble.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

One solution that would work with pretty much any system is to copy the 
non-bad tables to a new database, drop the bad database, and rename the 
new database.


On 11/17/13 8:53 PM, chongsoft wrote:
> I'm  using derby for 4 years, all the time I don't known how to drop a bad
> table( file damaged)?
>
> For example, if a file in "seg0" named "c20.dat" is damaged or deleted, so
> the associated table "tablexxx" can not be used,and even cannot de droped
> with "drop table tablexxx"(thows exceptions), can someone help me to remove
> the damaged table "tablexxx"?
>
>
>
> --
> View this message in context: http://apache-database.10148.n7.nabble.com/How-to-drop-a-bad-table-tp135693.html
> Sent from the Apache Derby Users mailing list archive at Nabble.com.
>

-- 
George Sexton
MH Software, Inc.
303 438-9585
http://www.mhsoftware.com/