Skip to Content
avatar image
Former Member

Unable to start specified database: dblog.log is an invalid transaction log

Hi,

I am working on SQL Anywhere 12.

I have created a new db and after several weeks of work when I try to start my db from Sybase Central I get following error:

[Sybase][ODBC Driver][SQL Anywhere]Unable to start specified database: baza1.log is an invalid transaction log

SQLCODE=-82

SQLSTATE=08001

When I am trying to start it from command line I get following logs:

I. 06/27 11:48:01. Starting database "baza1" (c:\baza\baza1.db) at Fri Jun 27 2014 11:48
I. 06/27 11:48:01. Database recovery in progress
I. 06/27 11:48:01. Last checkpoint at Wed Jun 18 2014 21:15
I. 06/27 11:48:01. Checkpoint log...
I. 06/27 11:48:02. Transaction log: c:\baza\backup\baza1.log...
E. 06/27 11:48:03. Error: Database cannot be started -- c:\baza\backup\baza1.log is an invalid transaction log

E. 06/27 11:48:03. Database cannot be started -- c:\baza\backup\baza1.log is an invalid transaction log
I. 06/27 11:48:05. Database server shutdown due to startup error
I. 06/27 11:48:05. Database server stopped at Fri Jun 27 2014 11:48

It happened already 2nd time...

Can somebody tell me what could be the reason or how I can find out what is the reason myself?

Thanks,

ak

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • Best Answer
    Jun 30, 2014 at 04:34 PM

    Please make copies of the database and transaction log. The error being reported suggests that the transaction log is damaged. Can you run dbtran on the copied transaction log to see if it reports the same error or something different - if so, please post the error/message.

    When you say this is the 2nd time, how did you correct the issue in the previous case?

    What is the media that the database file is stored? And the transaction log?

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Andrzej,

      Are there any tools to help find out what was the reason for db failure?

      Both of the tools 'dbvalid' and 'dbtran' can help establish that there was a corruption of the database / transaction log (respectively), but not exactly how it occurred.

      Database corruption can come from many sources - from both inside and outside of the database server:

      1. The database server software
      2. The file system
      3. The operating system
      4. The hardware (media / driver)

      Taking a look at the actual file bytes would give us a better understanding of what happened.

      From your problem description though, it sounds like one of your files might have been mixed up during your backup / restore process. We would then have to try and go back to figure out when the 'other' file was introduced into the process and where it originally came from.

      Regards,

      Jeff Albion

      SAP Active Global Support