db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From dag.wan...@oracle.com (Dag H. Wanvik)
Subject Re: Derby Database start failed on Z/OS
Date Tue, 03 Apr 2012 17:18:21 GMT
"Pallimakkal, Ambili V" <Ambili.Pallimakkal@ca.com> writes:

> Hi,
>
> We are having some issues with derby database on Z/OS.

You are using a fairly old version of Derby, 10.5.3.0. Can you
reproduce this problem with a newer version [1]?

[1] http://db.apache.org/derby/releases/release-10.8.2.2.cgi

Thanks,
Dag

>
> The install is created on a HFS file system. And we create DB using this command
> java -cp . -jar derbyrun.jar ij databaseAuth.sql
> and  databaseAuth.sql  content is given below.
>
> connect 'jdbc:derby: /HO43/Vantagegmi/webclientdb/VantageDb';create=true;dataEncryption=true;bootPassword=Password;encryptionAlgorithm=AES/CBC/NoPadding;';
>
> --------------------------------------------------------------------------------
> -- CREATE USER_CREDENTIALS TABLE WITH PRIMARY KEY OF USERNAME
> -- STEP 2
> --------------------------------------------------------------------------------
> CREATE TABLE USER_CREDENTIALS
> (
>           USERNAME VARCHAR(30) NOT NULL,
>           PASSWORD VARCHAR(30) NOT NULL,
>           PRIMARY KEY (USERNAME)
> );
>
> --------------------------------------------------------------------------------
> -- INSERT USER INTO USER_CREDENTIALS TABLE
> -- STEP 3
> --------------------------------------------------------------------------------
> INSERT INTO USER_CREDENTIALS VALUES('APP', 'Password');
>
> EXIT;
>
> Create was successful. But when we try to connect to DB again it fails to start with
error.
> ----------------------------------------------------------------
> 2012-03-15 19:12:32.335 GMT:
> Booting Derby version The Apache Software Foundation - Apache Derby - 10.5.3.0 - (802917):
instance a816c00e-0136-17c6-951f-0000001a40a0
> on database directory /HO43/Vantagegmi/webclientdb/VantageDb
> ------------  BEGIN SHUTDOWN ERROR STACK -------------
>
> ERROR XSLA6: Cannot recover the database.
>                 at org.apache.derby.iapi.error.StandardException.newException(Unknown
Source)
>                 at org.apache.derby.impl.store.raw.log.LogToFile.recover(Unknown Source)
>                 at org.apache.derby.impl.store.raw.RawStore.boot(Unknown Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
>                 at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
Source)
>                 at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
Source)
>                 at org.apache.derby.impl.store.access.RAMAccessManager.boot(Unknown Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
>                 at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(Unknown
Source)
>                 at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Unknown
Source)
>                 at org.apache.derby.impl.db.BasicDatabase.bootStore(Unknown Source)
>                 at org.apache.derby.impl.db.BasicDatabase.boot(Unknown Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
>                 at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown
Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown
Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(Unknown
Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(Unknown
Source)
>                 at org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(Unknown
Source)
>                 at org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Unknown
Source)
>                 at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(Unknown Source)
>                 at org.apache.derby.impl.jdbc.EmbedConnection.<init>(Unknown Source)
>                 at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(Unknown
Source)
>                 at org.apache.derby.impl.jdbc.EmbedConnection40.<init>(Unknown
Source)
>                 at org.apache.derby.jdbc.Driver40.getNewEmbedConnection(Unknown Source)
>                 at org.apache.derby.jdbc.InternalDriver.connect(Unknown Source)
>                 at org.apache.derby.jdbc.AutoloadedDriver.connect(Unknown Source)
>                 at java.sql.DriverManager.getConnection(DriverManager.java:379)
>                 at java.sql.DriverManager.getConnection(DriverManager.java:354)
>                 at org.apache.derby.impl.tools.ij.ij.dynamicConnection(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.ij.ConnectStatement(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.ij.ijStatement(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.utilMain.runScriptGuts(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.utilMain.go(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.Main.go(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.Main.mainCore(Unknown Source)
>                 at org.apache.derby.impl.tools.ij.Main.main(Unknown Source)
>                 at org.apache.derby.tools.ij.main(Unknown Source)
>                 at org.apache.derby.iapi.tools.run.main(Unknown Source)
> Caused by: java.lang.NullPointerException
>                 at org.apache.derby.impl.store.raw.log.Scan.getNextRecordForward(Unknown
Source)
>                 at org.apache.derby.impl.store.raw.log.Scan.getNextRecord(Unknown Source)
>                 at org.apache.derby.impl.store.raw.log.FileLogger.redo(Unknown Source)
>
> The java version we are running is
> Java Version
> =========
> Java Virtual Machine created. Version information follows:
> java version "1.6.0"
> Java(TM) SE Runtime Environment (build pmz3160_26sr1-20111114_01 (SR1))
> IBM J9 VM (build 2.6, JRE 1.6.0 z/OS s390-31 20111113_94967 (JIT enabled, AOT enabled)
> J9VM - R26_Java626_SR1_20111113_1649_B94967
> JIT  - r11_20111028_21230
> GC   - R26_Java626_SR1_20111113_1649_B94967
> J9CL - 20111113_94967)
>
>
> The os system properties are attached here.
>
> Is this an already existing issue? Can someone help me to resolve this issue.
>
> It happens when the tomcat server starts to use the database. But for testing when I
just used cmd line script , it fails there also.
>
> I would really appreciate any help to resolve this issue.
>
> Regards
> Ambili

Mime
View raw message