[NAS-2030] Both adminDB and harvestDB if derby-based uses same derby.system.home value Created: 23/Jan/12  Updated: 15/Jun/15

Status: Open
Project: NetarchiveSuite
Component/s: Deploy
Affects Version/s: 3.18.0
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Søren Vejrup Carlsen (Inactive) Assignee: Unassigned
Resolution: Unresolved  
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File start_external_admin_database.sh.txt    
Organization:
SB/KB

 Description   

Both adminDB and harvestDB if derby-based uses same derby.system.home value.
This has the consequence, that both databases uses the same derby.properties file and
and even worse the same derby.log

A workaround for this is creating a databasedir '$INSTALLDIR/admindatabasedir', moving the
adminDB into that directory, and adding the -Dderby.system.home=$INSTALLDIR/admindatabasedir

Then the adminDB will use the derby.properties in $INSTALLDIR/admindatabasedir, and the harvestDB will use the old derby.properties in $INSTALLDIR.

Each server will then also write to its own derby.log file.



 Comments   
Comment by Søren Vejrup Carlsen (Inactive) [ 23/Jan/12 ]

Modified startup script that fixes this bug
for INSTALLDIR=/home/test/SVC

Generated at Thu Apr 25 17:00:50 CEST 2024 using Jira 9.4.15#940015-sha1:bdaa9cbecfb6791ea579749728cab771f0dfe90b.