On 11/18/13 9:46 AM, George S. wrote:
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.
You may find the foreignViews tool useful for this purpose. Please see
http://db.apache.org/derby/docs/10.10/tools/rtoolsoptforeignviews.html
Hope this helps,
-Rick
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.
