Thanks Kerry. Finally found 'derby.log' which was in my $HOME (not in
$DERBY_HOME), perhaps because that's where I started derby network from.
The log file has following 3 entries towards the end, and indeed it seems
to be permission problem:
Fri Nov 08 12:34:46 IST 2019 Thread[DRDAConnThread_4,5,main] (DATABASE =
seconddb), (DRDAID = {5}), Failed to create database 'seconddb', see the
next exception for details.
Fri Nov 08 12:34:46 IST 2019 Thread[DRDAConnThread_4,5,main] (DATABASE =
seconddb), (DRDAID = {5}), Startup failed due to an exception. See next
exception for details.
Fri Nov 08 12:34:46 IST 2019 Thread[DRDAConnThread_4,5,main] (DATABASE =
seconddb), (DRDAID = {5}), Java exception: 'access denied
("java.lang.RuntimePermission" "getenv.SOURCE_DATE_EPOCH"):
java.security.AccessControlException'.
What should be done to provide permissions ? Is the permission going to be
Derby specific ?
On Fri, Nov 8, 2019 at 2:44 PM Kerry <karaf-u...@avionicengineers.com>
wrote:
> Hi,
>
> This sounds like it might be a Java permissions error as you are using
> Open JDK 11. If you look in the derby.log file located in $DERBY_HOME it
> will give an indication. Post the content of it here.
>
> Kerry
>
> Sent from BlueMail <http://www.bluemail.me/r?b=15726>
> On 8 Nov 2019, at 07:29, Banibrata Dutta <banibrata.du...@gmail.com>
> wrote:
>>
>> Hi Folk,
>>
>> Trying to use Derby for the first time. I am not an expert Java developer
>> but dabbling for learning me some. I followed the official Derby
>> instructions for installing the latest Derby on my freshly minted Lubuntu
>> (lighter Ubuntu using LXDE) 64-bit 18.04.3 setup, with OpenJDK11 (default).
>>
>> Have started Derby in network server mode like this:
>> $ java -jar $DERBY_HOME/lib/derbyrun.jar server start
>>
>> And then trying to using ij to create the database like this:
>> $ ij
>> ij version 10.15
>> ij> CONNECT 'jdbc:derby://localhost:1527/seconddb;create=true';
>> ERROR XJ041: DERBY SQL error: ERRORCODE: 40000, SQLSTATE: XJ041,
>> SQLERRMC: Failed to create database 'seconddb', see the next exception for
>> details.::SQLSTATE: XBM01::SQLSTATE: XJ001
>> ij>
>>
>> Trying to read around, there are suggestions to look into derby.log file,
>> but I found none so far. What gives ? How to proceed ? Didn't find any
>> general troubleshooting instructions in the docs. Tried the FAQ, but no
>> obvious clues.
>>
>> cheers,
>> B
>>
>>
--
regards,
Banibrata
http://www.linkedin.com/in/bdutta
http://twitter.com/edgeliving
