SQL Anywhere database - "Log file corrupted" error in dbremote

Author

"Log file corrupted" error in dbremote

Oliver Schulze L.

2005-12-20, 11:23 am

Hi,
I have a remote DB, and I noted this error message in
the dbremote output:
E. 12/20 12:40:23. Log file corrupted (invalid operation)
E. 12/20 12:40:23. Corruption of log starts at offset 0024310036

The DB is ASA 6.0.4.

I searched and readed that I can try recovering using a newer
eval version of ASA. For example, I download ASA 9 eval and
try to recover.

My question is, how do I recover?

Should I use dbtran to translate the .log file into SQL statements?
And later add those statement to the DB using dbeng6 -a ?

If I need to send the .log file to Sybase, will it cost something?

Many thanks
Oliver

Oliver Schulze L.

2005-12-20, 11:23 am

Just a note,
dbtran sucessfully readed the .log file.
Does this means that only dbremote has problem reading the .log file?

How can I fix the .log file in order to dbremote to read it?

Many Thanks
Oliver

Oliver Schulze L. wrote:
> Hi,
> I have a remote DB, and I noted this error message in
> the dbremote output:
> E. 12/20 12:40:23. Log file corrupted (invalid operation)
> E. 12/20 12:40:23. Corruption of log starts at offset 0024310036
>
> The DB is ASA 6.0.4.
>
> I searched and readed that I can try recovering using a newer
> eval version of ASA. For example, I download ASA 9 eval and
> try to recover.
>
> My question is, how do I recover?
>
> Should I use dbtran to translate the .log file into SQL statements?
> And later add those statement to the DB using dbeng6 -a ?
>
> If I need to send the .log file to Sybase, will it cost something?
>
> Many thanks
> Oliver

Reg Domaratzki $iAnywhere Solutions$

2005-12-20, 11:23 am

Can you post the entire dbremote output file?

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"

"Oliver Schulze L." <news.oliver@samera.com.py> wrote in message
news:43a82d21$1@foru
ms-1-dub...
> Hi,
> I have a remote DB, and I noted this error message in
> the dbremote output:
> E. 12/20 12:40:23. Log file corrupted (invalid operation)
> E. 12/20 12:40:23. Corruption of log starts at offset 0024310036
>
> The DB is ASA 6.0.4.
>
> I searched and readed that I can try recovering using a newer
> eval version of ASA. For example, I download ASA 9 eval and
> try to recover.
>
> My question is, how do I recover?
>
> Should I use dbtran to translate the .log file into SQL statements?
> And later add those statement to the DB using dbeng6 -a ?
>
> If I need to send the .log file to Sybase, will it cost something?
>
> Many thanks
> Oliver

Oliver Schulze L.

2005-12-20, 11:23 am

Sure,
here it is:

I. 12/20 12:40:20. Copyright 1989-2000 Sybase, Inc. All rights reserved.
I. 12/20 12:40:20. All unpublished rights reserved.
I. 12/20 12:40:20.
I. 12/20 12:40:20. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
94608, USA
I. 12/20 12:40:20.
I. 12/20 12:40:23. Scanning logs starting at offset 0024204562
I. 12/20 12:40:23. Processing transactions from active transaction log
E. 12/20 12:40:23. Log file corrupted (invalid operation)
E. 12/20 12:40:23. Corruption of log starts at offset 0024310036
I. 12/20 12:40:24. Execution completed

Thanks Reg,
Oliver

Reg Domaratzki (iAnywhere Solutions) wrote:
> Can you post the entire dbremote output file?
>

Oliver Schulze L.

2005-12-20, 8:24 pm

More info, I edited the .log file in an hex editor and
found at the end too many 00 caracters.
Then, I made a network backup of the .db and .log files
and the trailling zeros desapering, but, I still have the
same error.

Is there a way to "regenerate" the .log file?
Because the dbtran, dbeng6 and dbbackup seems to read
very well the .log file, only dbremote has problems.

I also tested running the .db file in ASA8 and running
dbremote from ASA8, I got the same error.

Will try to download ASA9 eval and test.

Thanks
Oliver

Oliver Schulze L. wrote:[color=darkred
]
> Sure,
> here it is:
>
> I. 12/20 12:40:20. Copyright 1989-2000 Sybase, Inc. All rights reserved.
> I. 12/20 12:40:20. All unpublished rights reserved.
> I. 12/20 12:40:20.
> I. 12/20 12:40:20. Sybase, Inc. 6475 Christie Avenue, Emeryville, CA
> 94608, USA
> I. 12/20 12:40:20.
> I. 12/20 12:40:23. Scanning logs starting at offset 0024204562
> I. 12/20 12:40:23. Processing transactions from active transaction log
> E. 12/20 12:40:23. Log file corrupted (invalid operation)
> E. 12/20 12:40:23. Corruption of log starts at offset 0024310036
> I. 12/20 12:40:24. Execution completed
>
> Thanks Reg,
> Oliver
>
> Reg Domaratzki (iAnywhere Solutions) wrote:

Reg Domaratzki $iAnywhere Solutions$

2005-12-21, 9:23 am

There's nothing wrong with the 0x00 characters at the end of the log file.
When the last byte of the current log file is used, we grow the transaction
log by 16 pages and zero out the pages. When you take a backup, we don't
copy empty pages, so the file seems shorter.

There's no way to regenerate the log file. If dbtran reads the log file
fine, then I suspect it's a log scanning problem in v604. If you can
reproduce the problem (using the v604 DB+LOG) using v902, I'd be interested
in getting the repro from you.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"

"Oliver Schulze L." <news.oliver@samera.com.py> wrote in message
news:43a86784@forums
-1-dub...[color=darkred]
> More info, I edited the .log file in an hex editor and
> found at the end too many 00 caracters.
> Then, I made a network backup of the .db and .log files
> and the trailling zeros desapering, but, I still have the
> same error.
>
> Is there a way to "regenerate" the .log file?
> Because the dbtran, dbeng6 and dbbackup seems to read
> very well the .log file, only dbremote has problems.
>
> I also tested running the .db file in ASA8 and running
> dbremote from ASA8, I got the same error.
>
> Will try to download ASA9 eval and test.
>
> Thanks
> Oliver
>
>
> Oliver Schulze L. wrote:
reserved.[color=darkred]

Oliver Schulze L.

2005-12-21, 11:23 am

Hi Reg,
thanks for the explanation.

I have been using ASA 6.0.4 since 6 years now and this is the
first time I saw the problem.
The PC where the remote DB was running run out of space a few
weeks ago, so I think that may have trigger the .log corruption.

May solution was to manually insert the rows from the remote DB
into the consolidated DB, unload/reload the consolidated DB,
rename the .log and set the apropiate offset with dblog as
explained in the ASA help file.

Then, I dbxtracted the db for the remote db that has the .log problem.

I'm sorry I can not reproduce the error, but will be watching
more carefully the .logs now ;)

Thanks for all the help, Regards,
Oliver

Reg Domaratzki (iAnywhere Solutions) wrote:
> There's nothing wrong with the 0x00 characters at the end of the log file.
> When the last byte of the current log file is used, we grow the transaction
> log by 16 pages and zero out the pages. When you take a backup, we don't
> copy empty pages, so the file seems shorter.
>
> There's no way to regenerate the log file. If dbtran reads the log file
> fine, then I suspect it's a log scanning problem in v604. If you can
> reproduce the problem (using the v604 DB+LOG) using v902, I'd be interested
> in getting the repro from you.
>

Sponsored Links