Quantcast
Channel: SCN: Message List - SAP SQL Anywhere
Viewing all articles
Browse latest Browse all 2182

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

$
0
0

Hello,

 

Based on the paths mentioned, it seems that you are currently copying around files in a backup / recovery situation? Is that correct? Can you be more clear on what steps you have already performed with these files?

 

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...

 

The database is located at 'c:\baza\baza1.db', but the database has a reference to the 'c:\baza\backup' directory for the transaction log. Can you run 'dblog' on the 'baza1.db' file to check the path of the current transaction log? Do you still have the 'c:\baza\baza1.log' file present? Is the "c:\baza\backup\baza1.log" file

 

You may need to use 'dblog -t" against the database in order to properly locate the current transaction log for the database (if there's still a valid transaction log available). Can you run 'dbtran' against just the 'C:\baza\restore\baza1.log' file to confirm that it cannot be successfully translated?

 

If all of your copies of the transaction log are no longer translatable, point the database to a transaction log file that doesn't exist on the file system using dblog (or move the current transaction log to another location), and use "dbsrv12 baza1.db -f" to recover the database without the transaction log.

 

Regards,

 

Jeff Albion

SAP Active Global Support


Viewing all articles
Browse latest Browse all 2182

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>