Re: Back End Database Files [SEC=UNCLASSIFIED]

[Mamta Satoor <ms...@gmail.com>]

Hi Ashley,

Yes, it is ok to move the databases as long as you copy the entire database
directory strucutre.

You can find a thread on the similar topic at
http://www.nabble.com/Porting-Derby-Database-files-between-machines-tf1521904.html#a4135501


Mamta

On 3/7/07, ashley.davidson@abs.gov.au <as...@abs.gov.au> wrote:
>
> Can Derby databases be updated by swapping the files in the back end?
>
> We have a rather slow process that we have to run to completely re-create
> our Derby back end each time we update our metadata. I have tried backing
> up the database files created by Derby and then using a file copy to
> another machine to effect changes and this seems to work well.
>
> I'm looking for confirmation that the files are not system dependant.
>
> The files I'm talking about are those in the log, seg0 and tmp folders, as
> well as the db.lck and service.properties files. I'm assuming at this
> stage
> that the naming conventions are standard.
>
>
>
>
> ------------------------------------------------------------------------------------------------
> Free publications and statistics available on www.abs.gov.au
>
>

Re: Back End Database Files [SEC=UNCLASSIFIED]

[Mike Matrigali <mi...@sbcglobal.net>]

The safest thing to do is to follow the documented ways to backup a 
database.  Once the database has been backed up in a supported manner
then that backup can be moved to any machine you want - the files
are system independent.

Without using the supported ways it is quite easy to get inconsistent
versions of the files leading to various db corruptions.  This is
especially easy if you try to copy files while any access to the db
is going on (since you see a db.lck file it could easily be that
the copy is happening while the db is active).  10.2 provides online
backup which provides a supported way to backup the database
concurrently with active work happening in the database.

Mamta Satoor wrote:
> Hi Ashley,
>  
> Yes, it is ok to move the databases as long as you copy the entire 
> database directory strucutre.
>  
> You can find a thread on the similar topic at 
> http://www.nabble.com/Porting-Derby-Database-files-between-machines-tf1521904.html#a4135501 
> <http://www.nabble.com/Porting-Derby-Database-files-between-machines-tf1521904.html#a4135501> 
>  
> Mamta
>  
> On 3/7/07, *ashley.davidson@abs.gov.au 
> <ma...@abs.gov.au>* <ashley.davidson@abs.gov.au 
> <ma...@abs.gov.au>> wrote:
> 
>     Can Derby databases be updated by swapping the files in the back end?
> 
>     We have a rather slow process that we have to run to completely
>     re-create
>     our Derby back end each time we update our metadata. I have tried
>     backing
>     up the database files created by Derby and then using a file copy to
>     another machine to effect changes and this seems to work well.
> 
>     I'm looking for confirmation that the files are not system dependant.
> 
>     The files I'm talking about are those in the log, seg0 and tmp
>     folders, as
>     well as the db.lck and service.properties files. I'm assuming at
>     this stage
>     that the naming conventions are standard.
> 
> 
> 
>     ------------------------------------------------------------------------------------------------
>     Free publications and statistics available on www.abs.gov.au
>     <http://www.abs.gov.au>
> 
>