db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@gmail.com>
Subject Re: How to migrate a Derby database?
Date Tue, 30 Jun 2020 23:11:03 GMT
I don't have enough information about the original database corruption 
to speculate about the aptness of your solution. Maybe the corruption 
could have been repaired in place without the need to create a new 
database. For my money, 2ii is a faster solution than 2i, but your 
mileage may vary. Glad to hear that you fixed your problem.


On 6/30/20 8:37 AM, David Gowdy wrote:
> There were a couple of factors related to this initial post. First, 
> was that I'd encountered a somewhat minor problem with an application 
> that I've been using for a bit more than 15 years without any prior 
> problem.  Second, I do some work with relational databases and thought 
> I should know how to do such things with Derby.
> The minor problem was a failure to allow insertion of a specific new 
> row into a table.  Based on knowledge of what was being shown to be in 
> the database this should have worked fine.  Other insertions were also 
> working as expected.  Therefore, I deduced that a plausible 
> explanation would be some kind of corruption that may have crept into 
> the underlying files used to store the data. This could have happened 
> anytime but based on the specific elements involved I thought it 
> likely to be something that happened long ago.
> Therefore, my idea was to want to recover as much of the data as 
> possible and then create a new database using that data.  I determined 
> that when it came to your suggestions 2i was the only one that fit 
> this criteria.  In that, this produces new database files that are 
> completely independent from the original ones. Fortunately, my 
> archives did have a text file that contained the SQL for creating the 
> tables.  I haven't used the resulting database much yet but I was able 
> to insert the row that previously failed and have no reason to think 
> there is any problem.
> When compared to the MySQL/phpMyAdmin export/import technique this one 
> is NOT quite as simple.  On the other hand ending up with the data in 
> .csv format could be considered more desirable for generalized 
> compatibility reasons than the SQL format used for MySQL.
> Would be grateful to learn about any flaws in my assessment of this 
> situation and many thanks for the help.
> ajax ...
> On 6/29/2020 6:40 PM, Rick Hillegas wrote:
>> Hi Ajax,
>> I don't know why you are not receiving email which I posted to the 
>> derby-user list. In any event, you can try posting your messages both 
>> to me and to derby-user. I will respond to all so that you and 
>> derby-user should be copied on the whole conversation.
>> Thanks,
>> -Rick
>> On 6/29/20 7:39 AM, receiver@gowdygroup.net wrote:
>>> <quote author='Rick Hillegas-3'>
>>> Hi Ajax,
>>> Here are a couple points to consider:
>>> ...
>>> </quote>
>>> Quoted from:
>>> http://apache-database.10148.n7.nabble.com/How-to-migrate-a-Derby-database-tp151268p151269.html

>>> I'm NOT completely sure what I'm doing right now.  I think this 
>>> message should end up being an email addressed to Rick Hillegas.  
>>> I'm able to do this because of his reply to my original post which 
>>> was done by sending an email.  It seems that I'm not able to respond 
>>> to that reply via the website being used to send this message.  I 
>>> sort of thought your reply might have shown up in my inbox as a 
>>> result of having subscribed to the mailing list.  However, even 
>>> after checking SPAM boxes I can find nothing.
>>> While I do have a question related to your excellent reply to my 
>>> original post, the question for now is "How am I supposed to submit 
>>> such questions?  In that, how to respond to your reply?".
>>> _____________________________________
>>> Sent from http://apache-database.10148.n7.nabble.com

View raw message