db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Binoy Thomas" <binoy.tho...@sphere.ae>
Subject RE: DB gets corrupts in 10.3.1.2!!
Date Mon, 28 Apr 2008 13:40:13 GMT

We have not used 10.4.x to access the corrupted DB. It was tested by
building the application again with the latest derby jars.

-----Original Message-----
From: Dyre.Tjeldvoll@Sun.COM [mailto:Dyre.Tjeldvoll@Sun.COM] 
Sent: Monday, April 28, 2008 2:43 PM
To: Derby Discussion
Cc: 'Derby Development'
Subject: Re: DB gets corrupts in 10.3.1.2!!

Binoy Thomas <binoy.thomas@sphere.ae> writes:

> We are a firm having multiple software products & we use the Derby DB in
all
> our suite of products for quite many years now. We are facing a blocker
> situation that is halting all our release process.
>
> Any help would be appreciated on the below DB corruption error. 
>
> Derby versions tried: Derby 10.3.1.2 & 10.4.1.3
> User scenario is:
>
> Our base application runs 2 Derby DBs. Another application (which is part
of
> the suite of products) as per deployment strategy would need to be
installed
> on top of it. 
> In this process of installation, the installer first brings down the base
> application (thereby the DBs are shutdown), installs the 2nd application &
> then brings up the base application as well as the other application.
> (Internal process while re-starting application:  DBs from the base
> application are brought up & then the DB from the 2nd application is
brought
> up.)

Have you created a new database with 10.4? If you use 10.4 to access an
already corrupt db you will still get an error, I'm afraid.

Restoring a non-corrupt image from backup and then upgrade, should also
work.

-- 
dt





Mime
View raw message