Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (herse.apache.org: domain of amichail@gmail.com designates
 209.85.132.250 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=FgWO1kJl037beo5aOXmttfM/mlfZDKQkmevuuiEhMi9z/MXpV+HlvGTnLfjHvn1N2uXaIxuWeZhwevY5hf/i0XLNyI6QQpnQ0frVMR0SeB7Pdq8ICPkapLPtzgoqzD7peZTgdGjREh3zFoUyO+LUndDFduWSSfupruWUp1BXVzc=
Message-ID: <eb9696930707211514n276df3c5p4e9828c367c22251@mail.gmail.com>
Date: Sat, 21 Jul 2007 18:14:51 -0400
From: "Amir Michail" <amichail@gmail.com>
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: Re: can't access or create a db
In-Reply-To: <eb9696930707211451gcb117eao66a1083e3596a8d6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <eb9696930707211302n2074dafbt1be7b6b0fc49d455@mail.gmail.com>
	 <c25576af0707211309w21a89d13jd7f8428c06201a28@mail.gmail.com>
	 <eb9696930707211451gcb117eao66a1083e3596a8d6@mail.gmail.com>

Hi,

Problem solved.  Please ignore.

Amir

On 7/21/07, Amir Michail <amichail@gmail.com> wrote:
> On 7/21/07, Myrna van Lunteren <m.v.lunteren@gmail.com> wrote:
> > On 7/21/07, Amir Michail <amichail@gmail.com> wrote:
> > > Hi,
> > >
> > > Not sure what happened, but now I can't access or create a db on my server:
> > >
> > > ERROR XJ041: DERBY SQL error: SQLCODE: -1, SQLSTATE: XJ041, SQLERRMC:
> > > Failed to create database 'testDB', see the next exception for
> > > details.::SQLSTATE: XBM0HDirectory /home/.../testDB cannot be created.
> > >
> > > If I copy the db to my laptop, then it works.
> > >
> > > Any ideas on how I could track down this problem?
> > >
> > > Amir
> > >
> > You probably already thought of it, but the only thing I can think of
> > off hand is write permissions on the server. Maybe the umask for the
> > server process' user has been changed? Or the write permission for  /
> > ? Or maybe the server has been started from a different directory from
> > before (if /home/../testDB would not be where your database used to
> > be)?
> >
> > HTH
> > Myrna
> >
> The process accessing the db is tomcat55.  How does umask apply in this case?
>
> This used to work fine.  I have no idea what happened to mess up the
> permissions.
>
> Amir
>