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

Hi,

 

I have copied db and logs.

I run following statement on logs directory:

C:\Users\ADMIN>dbtran -m C:\baza\restore -n c:\baza\restore\restore.sql

 

and got following messages:

 

SQL Anywhere Log Translation Utility Version 12.0.1.3994

Processing transaction logs from directory "C:\baza\restore"

Unexpected end of file

Transaction log "C:\baza\restore\baza1.log" starts at offset 0004374867

Transaction log "C:\baza\restore\140512AA.LOG" starts at offset 0000555605

Transaction log "C:\baza\restore\140512AA.LOG" starts at offset 0000555605

Processing transactions from transaction log "C:\baza\restore\140512AA.LOG"

26% complete

Transaction log ends at offset 0001610451

Transaction log "C:\baza\restore\140512AB.LOG" starts at offset 0001610451

Processing transactions from transaction log "C:\baza\restore\140512AB.LOG"

Transaction log ends at offset 0001618728

Transaction log "C:\baza\restore\140521AA.LOG" starts at offset 0001618728

Processing transactions from transaction log "C:\baza\restore\140521AA.LOG"

48% complete

Transaction log ends at offset 0002466045

Transaction log "C:\baza\restore\140528AA.LOG" starts at offset 0002466045

Processing transactions from transaction log "C:\baza\restore\140528AA.LOG"

55% complete

Transaction log ends at offset 0002769821

Transaction log "C:\baza\restore\140617AA.LOG" starts at offset 0002769821

Processing transactions from transaction log "C:\baza\restore\140617AA.LOG"

91% complete

Transaction log ends at offset 0004192045

Transaction log "C:\baza\restore\140617AB.LOG" starts at offset 0004192045

Processing transactions from transaction log "C:\baza\restore\140617AB.LOG"

92% complete

Transaction log ends at offset 0004200322

Transaction log "C:\baza\restore\140617AC.LOG" starts at offset 0004200322

Processing transactions from transaction log "C:\baza\restore\140617AC.LOG"

Transaction log ends at offset 0004208743

Transaction log "C:\baza\restore\140617AD.LOG" starts at offset 0004208743

Processing transactions from transaction log "C:\baza\restore\140617AD.LOG"

Transaction log ends at offset 0004217164

Transaction log "C:\baza\restore\140617AE.LOG" starts at offset 0004217164

Processing transactions from transaction log "C:\baza\restore\140617AE.LOG"

Transaction log ends at offset 0004225441

Transaction log "C:\baza\restore\140618AA.LOG" starts at offset 0004225441

Processing transactions from transaction log "C:\baza\restore\140618AA.LOG"

96% complete

Transaction log ends at offset 0004374867

Transaction log "C:\baza\restore\baza1.log" starts at offset 0004374867

Processing transactions from transaction log "C:\baza\restore\baza1.log"

100% complete

Transaction log ends at offset 0004524313

 

 

I have recreated db structure manually previous time - it is my sandbox db and do not have much objects there but I have a batch job which loads data every day.

 

When it happened first time I thought it is because tran file became too big so I backup db and truncate tran log every week using:

dbbackup -c "DBF=C:\baza\baza1.db;UID=DBA;PWD=***" -y -r C:\baza\backup

 

 

It is on my laptop on Windows.

 

Regards,

ak


Viewing all articles
Browse latest Browse all 2182

Trending Articles



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