Topic
5 replies Latest Post - ‏2010-06-17T17:02:10Z by Stan
SystemAdmin
SystemAdmin
1525 Posts
ACCEPTED ANSWER

Pinned topic ERROR XSLA7: Cannot redo operation null in the log.

‏2005-04-03T23:24:36Z |
Hi,

Has anyone seen this error before. I have been working with Cloudscape for a while now and its been working fine. I recently implemented security in our Cloudscape server also and that all worked fine also. For some reason today, I started my cloudscape server and tried to connect to a database and got this following error:

ij> connect 'jdbc:derby:acl;user=Admin;password=pwd;';
ERROR XJ040: Failed to start database 'acl', see the next exception for details.

ERROR XSDB4: Page Page(1,Container(0, 16)) is at version 135, the log file conta
ins change version 619, either there are log records of this page missing, or th
is page did not get written out to disk properly.
I checked my derby.log file and this is what was in there:

2005-04-03 22:56:57.196 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.0.2.1 - (106978): instance c013800d-0103-0a47-f308-00000013cca8
on database directory C:\acl
BEGIN SHUTDOWN ERROR STACK



ERROR XSLA7: Cannot redo operation null in the log.
at org.apache.derby.iapi.error.StandardException.newException(StandardException.java)
at org.apache.derby.impl.store.raw.log.FileLogger.redo(FileLogger.java)
at org.apache.derby.impl.store.raw.log.LogToFile.recover(LogToFile.java)
at org.apache.derby.impl.store.raw.RawStore.boot(RawStore.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(BaseMonitor.java)
at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Monitor.java)
at org.apache.derby.impl.store.access.RAMAccessManager.boot(RAMAccessManager.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.startModule(BaseMonitor.java)
at org.apache.derby.iapi.services.monitor.Monitor.bootServiceModule(Monitor.java)
at org.apache.derby.impl.db.BasicDatabase.bootStore(BasicDatabase.java)
at org.apache.derby.impl.db.BasicDatabase.boot(BasicDatabase.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.TopService.bootModule(TopService.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.startProviderService(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.findProviderAndStartService(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(BaseMonitor.java)
at org.apache.derby.impl.services.monitor.BaseMonitor.startPersistentService(BaseMonitor.java)
at org.apache.derby.iapi.services.monitor.Monitor.startPersistentService(Monitor.java)
at org.apache.derby.impl.jdbc.EmbedConnection.bootDatabase(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection.<init>(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection20.<init>(EmbedConnection20.java)
at org.apache.derby.impl.jdbc.EmbedConnection30.<init>(EmbedConnection30.java)
at org.apache.derby.jdbc.Driver30.getNewEmbedConnection(Driver30.java)
at org.apache.derby.jdbc.Driver169.connect(Driver169.java)
at java.sql.DriverManager.getConnection(Unknown Source)
at java.sql.DriverManager.getConnection(Unknown Source)
at org.apache.derby.impl.tools.ij.ij.dynamicConnection(ij.java)
at org.apache.derby.impl.tools.ij.ij.ConnectStatement(ij.java)
at org.apache.derby.impl.tools.ij.ij.ijStatement(ij.java)
at org.apache.derby.impl.tools.ij.utilMain.go(utilMain.java)
at org.apache.derby.impl.tools.ij.Main.go(Main.java)
at org.apache.derby.impl.tools.ij.Main.mainCore(Main.java)
at org.apache.derby.impl.tools.ij.Main14.main(Main14.java)
at org.apache.derby.tools.ij.main(ij.java)


END SHUTDOWN ERROR STACK
2005-04-03 22:56:57.407 GMT:
Shutting down instance c013800d-0103-0a47-f308-00000013cca8

Does anyone have a clue as to why all of a sudden I will be getting this error message?? I havent changed anything in my settings or files, everything is the same that used to work.

Please let me know if anyone has seen this error before or know what I can do to fix it.

Thanks,
Updated on 2010-06-17T17:02:10Z at 2010-06-17T17:02:10Z by Stan
  • SystemAdmin
    SystemAdmin
    1525 Posts
    ACCEPTED ANSWER

    Re: ERROR XSLA7: Cannot redo operation null in the log.

    ‏2005-04-04T16:15:20Z  in response to SystemAdmin
    Hi Vsodhi -

    I've seen this error when log corruption has occurred because of dual booting the database. Dual booting is the most common cause of log corruption but, of course, disk failures or other system problems could also cause this to happen. See the sections [i] Is embedded Cloudscape a multiuser database?[/i] and [i]How can double-booting Cloudscape with a read-only connection cause corruption?[/i] in the FAQ document for more information on double booting - http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0408bradbury/#cs_general.
    • SystemAdmin
      SystemAdmin
      1525 Posts
      ACCEPTED ANSWER

      Re: ERROR XSLA7: Cannot redo operation null in the log.

      ‏2005-04-05T16:44:46Z  in response to SystemAdmin
      Thanks! I was able to resolve the problem.
      • SystemAdmin
        SystemAdmin
        1525 Posts
        ACCEPTED ANSWER

        Re: ERROR XSLA7: Cannot redo operation null in the log.

        ‏2006-10-03T19:53:41Z  in response to SystemAdmin
        Could you tell us how you fixed it?
        • bvoi
          bvoi
          1 Post
          ACCEPTED ANSWER

          Re: ERROR XSLA7: Cannot redo operation null in the log.

          ‏2010-04-09T07:37:22Z  in response to SystemAdmin
          Hi,

          Can you please guys tell me how you fixed this issue ?

          Thank you in advance.
          • Stan
            Stan
            267 Posts
            ACCEPTED ANSWER

            Re: ERROR XSLA7: Cannot redo operation null in the log.

            ‏2010-06-17T17:02:10Z  in response to bvoi
            Recovering from backup is the only way get the database up and running.