Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Database Recovery Error - Database cannot be started -- xxx is an invalid transaction log

5 posts in General Discussion (old) Last posting was on 2009-05-11 10:33:24.0Z
Jim Diaz Posted on 2009-05-07 20:24:01.0Z
From: "Jim Diaz" <nospam@emprisecorporation.com>
Newsgroups: sybase.public.sqlanywhere
Subject: Database Recovery Error - Database cannot be started -- xxx is an invalid transaction log
Lines: 46
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a034361@forums-1-dub>
Date: 7 May 2009 13:24:01 -0700
X-Trace: forums-1-dub 1241727841 10.22.241.152 (7 May 2009 13:24:01 -0700)
X-Original-Trace: 7 May 2009 13:24:01 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:283
Article PK: 866718

I am recovering a ASA 9.0.2.3546 database and get the error "Database cannot
be started -- xxx is an invalid transaction log"

DBLog and DBTran both indicate the log is fine. Starting Offset matches the
previous ending offset.


I. 05/04 13:19:22. Starting database "SAMM Consolidated" (D:\Sybase ASA
9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
2009 13:19
I. 05/04 13:19:22. Database recovery in progress
I. 05/04 13:19:22. Last checkpoint at Mon May 04 2009 13:19
I. 05/04 13:19:22. Checkpoint log...
I. 05/04 13:19:22. Performance warning: Database file "D:\Sybase ASA
9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of 1364
disk fragments
I. 05/04 13:19:30. Transaction log: D:\Temp\SAMM\090428AA.LOG...
I. 05/04 13:25:30. Rollback log...
I. 05/04 13:25:30. Checkpointing...
I. 05/04 13:25:30. Starting checkpoint of "SAMM Consolidated" (SAMM
Consolidated.db) at Mon May 04 2009 13:25
I. 05/04 13:26:17. Finished checkpoint of "SAMM Consolidated" (SAMM
Consolidated.db) at Mon May 04 2009 13:26
I. 05/04 13:26:17. Recovery complete
I. 05/04 13:26:17. Database server stopped at Mon May 04 2009 13:26
~
~
I. 05/04 13:26:17. Starting database "SAMM Consolidated" (D:\Sybase ASA
9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
2009 13:26
I. 05/04 13:26:17. Database recovery in progress
I. 05/04 13:26:17. Last checkpoint at Mon May 04 2009 13:26
I. 05/04 13:26:17. Checkpoint log...
I. 05/04 13:26:17. Performance warning: Database file "D:\Sybase ASA
9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of 1389
disk fragments
I. 05/04 13:26:24. Transaction log: D:\Temp\SAMM\090429AA.LOG...
E. 05/04 13:29:04. Error: Database cannot be started --
D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
I. 05/04 13:29:04. Error: Database cannot be started --
D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
I. 05/04 13:29:04.
E. 05/04 13:29:04. Database cannot be started -- D:\Temp\SAMM\090429AA.LOG
is an invalid transaction log


Breck Carter [TeamSybase] Posted on 2009-05-08 09:11:07.0Z
From: "Breck Carter [TeamSybase]" <NOSPAM__breck.carter@gmail.com>
Newsgroups: sybase.public.sqlanywhere
Subject: Re: Database Recovery Error - Database cannot be started -- xxx is an invalid transaction log
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__breck.carter@gmail.com
Message-ID: <ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com>
References: <4a034361@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 8 May 2009 02:11:07 -0700
X-Trace: forums-1-dub 1241773867 10.22.241.152 (8 May 2009 02:11:07 -0700)
X-Original-Trace: 8 May 2009 02:11:07 -0700, vip152.sybase.com
Lines: 66
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:284
Article PK: 866720

Show us the dbsrv9 command line you used to apply
D:\Temp\SAMM\090429AA.LOG

Show us the dbtran command line you used to check
D:\Temp\SAMM\090429AA.LOG

When you say dblog indicates the log is fine, what do you mean by
that?

Breck


On 7 May 2009 13:24:01 -0700, "Jim Diaz"

<nospam@emprisecorporation.com> wrote:

>I am recovering a ASA 9.0.2.3546 database and get the error "Database cannot
>be started -- xxx is an invalid transaction log"
>
>DBLog and DBTran both indicate the log is fine. Starting Offset matches the
>previous ending offset.
>
>
>I. 05/04 13:19:22. Starting database "SAMM Consolidated" (D:\Sybase ASA
>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>2009 13:19
>I. 05/04 13:19:22. Database recovery in progress
>I. 05/04 13:19:22. Last checkpoint at Mon May 04 2009 13:19
>I. 05/04 13:19:22. Checkpoint log...
>I. 05/04 13:19:22. Performance warning: Database file "D:\Sybase ASA
>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of 1364
>disk fragments
>I. 05/04 13:19:30. Transaction log: D:\Temp\SAMM\090428AA.LOG...
>I. 05/04 13:25:30. Rollback log...
>I. 05/04 13:25:30. Checkpointing...
>I. 05/04 13:25:30. Starting checkpoint of "SAMM Consolidated" (SAMM
>Consolidated.db) at Mon May 04 2009 13:25
>I. 05/04 13:26:17. Finished checkpoint of "SAMM Consolidated" (SAMM
>Consolidated.db) at Mon May 04 2009 13:26
>I. 05/04 13:26:17. Recovery complete
>I. 05/04 13:26:17. Database server stopped at Mon May 04 2009 13:26
>~
>~
>I. 05/04 13:26:17. Starting database "SAMM Consolidated" (D:\Sybase ASA
>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>2009 13:26
>I. 05/04 13:26:17. Database recovery in progress
>I. 05/04 13:26:17. Last checkpoint at Mon May 04 2009 13:26
>I. 05/04 13:26:17. Checkpoint log...
>I. 05/04 13:26:17. Performance warning: Database file "D:\Sybase ASA
>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of 1389
>disk fragments
>I. 05/04 13:26:24. Transaction log: D:\Temp\SAMM\090429AA.LOG...
>E. 05/04 13:29:04. Error: Database cannot be started --
>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>I. 05/04 13:29:04. Error: Database cannot be started --
>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>I. 05/04 13:29:04.
>E. 05/04 13:29:04. Database cannot be started -- D:\Temp\SAMM\090429AA.LOG
>is an invalid transaction log
>

--
Breck Carter http://sqlanywhere.blogspot.com/

RisingRoad SQL Anywhere and MobiLink Professional Services
breck.carter@risingroad.com


Jim Diaz Posted on 2009-05-08 11:58:11.0Z
From: "Jim Diaz" <nospam@emprisecorporation.com>
Newsgroups: sybase.public.sqlanywhere
References: <4a034361@forums-1-dub> <ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com>
Subject: Re: Database Recovery Error - Database cannot be started -- xxx is an invalid transaction log
Lines: 109
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a041e53$1@forums-1-dub>
Date: 8 May 2009 04:58:11 -0700
X-Trace: forums-1-dub 1241783891 10.22.241.152 (8 May 2009 04:58:11 -0700)
X-Original-Trace: 8 May 2009 04:58:11 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:285
Article PK: 866721

Breck,

Hi and thanks. Regarding dblog, it recognizes the file as a log file and
reports the properties without error (see below).

The command line

"C:\Program Files\Sybase\SQL Anywhere 9\win32\dbeng9" "D:\Sybase ASA
9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" -a
"D:\Temp\SAMM\090429AA.LOG" -o "D:\Temp\SAMM\Recover.log"

DBTran command line and output:
"C:\Program Files\Sybase\SQL Anywhere 9\win32\dbtran.exe" -y
"D:\Temp\SAMM\090429AA.LOG" "D:\Temp\SAMM\090429AA.LOG.sql"

Adaptive Server Anywhere Log Translation Utility Version 9.0.2.3546
Transaction log "D:\Temp\SAMM\090429AA.LOG" starts at offset 0109516958579
Transaction log ends at offset 0109566140930


DBLog Command Line and output:
"C:\Program Files\Sybase\SQL Anywhere 9\win32\dblog.exe"
"D:\Temp\SAMM\090429AA.LOG"

Adaptive Server Anywhere Transaction Log Utility Version 9.0.2.3546
File "D:\Temp\SAMM\090429AA.LOG" is a transaction log file
File version is 41
Log starts at offset 0109516958579
Log ends at offset 0109566140930
Log contains 12008 pages with a page size of 4096 bytes
49182351 bytes in use (100.00%), 2417 bytes free (0.00%)

"Breck Carter [TeamSybase]" <NOSPAM__breck.carter@gmail.com> wrote in
message news:ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com...
> Show us the dbsrv9 command line you used to apply
> D:\Temp\SAMM\090429AA.LOG
>
> Show us the dbtran command line you used to check
> D:\Temp\SAMM\090429AA.LOG
>
> When you say dblog indicates the log is fine, what do you mean by
> that?
>
> Breck
>
>
> On 7 May 2009 13:24:01 -0700, "Jim Diaz"
> <nospam@emprisecorporation.com> wrote:
>
>>I am recovering a ASA 9.0.2.3546 database and get the error "Database
>>cannot
>>be started -- xxx is an invalid transaction log"
>>
>>DBLog and DBTran both indicate the log is fine. Starting Offset matches
>>the
>>previous ending offset.
>>
>>
>>I. 05/04 13:19:22. Starting database "SAMM Consolidated" (D:\Sybase ASA
>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>>2009 13:19
>>I. 05/04 13:19:22. Database recovery in progress
>>I. 05/04 13:19:22. Last checkpoint at Mon May 04 2009 13:19
>>I. 05/04 13:19:22. Checkpoint log...
>>I. 05/04 13:19:22. Performance warning: Database file "D:\Sybase ASA
>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of
>>1364
>>disk fragments
>>I. 05/04 13:19:30. Transaction log: D:\Temp\SAMM\090428AA.LOG...
>>I. 05/04 13:25:30. Rollback log...
>>I. 05/04 13:25:30. Checkpointing...
>>I. 05/04 13:25:30. Starting checkpoint of "SAMM Consolidated" (SAMM
>>Consolidated.db) at Mon May 04 2009 13:25
>>I. 05/04 13:26:17. Finished checkpoint of "SAMM Consolidated" (SAMM
>>Consolidated.db) at Mon May 04 2009 13:26
>>I. 05/04 13:26:17. Recovery complete
>>I. 05/04 13:26:17. Database server stopped at Mon May 04 2009 13:26
>>~
>>~
>>I. 05/04 13:26:17. Starting database "SAMM Consolidated" (D:\Sybase ASA
>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>>2009 13:26
>>I. 05/04 13:26:17. Database recovery in progress
>>I. 05/04 13:26:17. Last checkpoint at Mon May 04 2009 13:26
>>I. 05/04 13:26:17. Checkpoint log...
>>I. 05/04 13:26:17. Performance warning: Database file "D:\Sybase ASA
>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of
>>1389
>>disk fragments
>>I. 05/04 13:26:24. Transaction log: D:\Temp\SAMM\090429AA.LOG...
>>E. 05/04 13:29:04. Error: Database cannot be started --
>>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>>I. 05/04 13:29:04. Error: Database cannot be started --
>>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>>I. 05/04 13:29:04.
>>E. 05/04 13:29:04. Database cannot be started -- D:\Temp\SAMM\090429AA.LOG
>>is an invalid transaction log
>>
>
> --
> Breck Carter http://sqlanywhere.blogspot.com/
>
> RisingRoad SQL Anywhere and MobiLink Professional Services
> breck.carter@risingroad.com


Breck Carter [TeamSybase] Posted on 2009-05-08 20:07:23.0Z
From: "Breck Carter [TeamSybase]" <NOSPAM__breck.carter@gmail.com>
Newsgroups: sybase.public.sqlanywhere
Subject: Re: Database Recovery Error - Database cannot be started -- xxx is an invalid transaction log
Organization: RisingRoad Professional Services
Reply-To: NOSPAM__breck.carter@gmail.com
Message-ID: <dp39055paid5eb6a3gflbmnbjpf503vteq@4ax.com>
References: <4a034361@forums-1-dub> <ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com> <4a041e53$1@forums-1-dub>
X-Newsreader: Forte Agent 2.0/32.640
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 8 May 2009 13:07:23 -0700
X-Trace: forums-1-dub 1241813243 10.22.241.152 (8 May 2009 13:07:23 -0700)
X-Original-Trace: 8 May 2009 13:07:23 -0700, vip152.sybase.com
Lines: 139
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:286
Article PK: 866722

I did not know that (about dblog reporting on a log file)... it is not
documented in the Help, not even 11.0.1.

As for your real problem, it sounds serious enough to call tech
support.

The only workaround I can think of us is use dbtran and apply the
resulting SQL via dbisql... not pretty.

FWIW when applying logs in recovery mode, the server command line
should use the same engine and same performance parameters as the
command line in use when the transaction log entries were originally
recorded. For example, if there were 100 busy connections updating the
database, then the engine's gonna have to use 100 connections to apply
the transaction log in forward recovery. If you ran with dbsrv9, then
recover with dbsrv9.

I doubt that will help here... OTOH maybe the message you got was
misleading about the root cause (like that's never happened before :)

Breck

On 8 May 2009 04:58:11 -0700, "Jim Diaz"

<nospam@emprisecorporation.com> wrote:

>Breck,
>
>Hi and thanks. Regarding dblog, it recognizes the file as a log file and
>reports the properties without error (see below).
>
>The command line
>
>"C:\Program Files\Sybase\SQL Anywhere 9\win32\dbeng9" "D:\Sybase ASA
>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" -a
>"D:\Temp\SAMM\090429AA.LOG" -o "D:\Temp\SAMM\Recover.log"
>
>DBTran command line and output:
>"C:\Program Files\Sybase\SQL Anywhere 9\win32\dbtran.exe" -y
>"D:\Temp\SAMM\090429AA.LOG" "D:\Temp\SAMM\090429AA.LOG.sql"
>
>Adaptive Server Anywhere Log Translation Utility Version 9.0.2.3546
>Transaction log "D:\Temp\SAMM\090429AA.LOG" starts at offset 0109516958579
>Transaction log ends at offset 0109566140930
>
>
>DBLog Command Line and output:
>"C:\Program Files\Sybase\SQL Anywhere 9\win32\dblog.exe"
>"D:\Temp\SAMM\090429AA.LOG"
>
>Adaptive Server Anywhere Transaction Log Utility Version 9.0.2.3546
>File "D:\Temp\SAMM\090429AA.LOG" is a transaction log file
>File version is 41
>Log starts at offset 0109516958579
>Log ends at offset 0109566140930
>Log contains 12008 pages with a page size of 4096 bytes
>49182351 bytes in use (100.00%), 2417 bytes free (0.00%)
>
>
>
>
>"Breck Carter [TeamSybase]" <NOSPAM__breck.carter@gmail.com> wrote in
>message news:ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com...
>> Show us the dbsrv9 command line you used to apply
>> D:\Temp\SAMM\090429AA.LOG
>>
>> Show us the dbtran command line you used to check
>> D:\Temp\SAMM\090429AA.LOG
>>
>> When you say dblog indicates the log is fine, what do you mean by
>> that?
>>
>> Breck
>>
>>
>> On 7 May 2009 13:24:01 -0700, "Jim Diaz"
>> <nospam@emprisecorporation.com> wrote:
>>
>>>I am recovering a ASA 9.0.2.3546 database and get the error "Database
>>>cannot
>>>be started -- xxx is an invalid transaction log"
>>>
>>>DBLog and DBTran both indicate the log is fine. Starting Offset matches
>>>the
>>>previous ending offset.
>>>
>>>
>>>I. 05/04 13:19:22. Starting database "SAMM Consolidated" (D:\Sybase ASA
>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>>>2009 13:19
>>>I. 05/04 13:19:22. Database recovery in progress
>>>I. 05/04 13:19:22. Last checkpoint at Mon May 04 2009 13:19
>>>I. 05/04 13:19:22. Checkpoint log...
>>>I. 05/04 13:19:22. Performance warning: Database file "D:\Sybase ASA
>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of
>>>1364
>>>disk fragments
>>>I. 05/04 13:19:30. Transaction log: D:\Temp\SAMM\090428AA.LOG...
>>>I. 05/04 13:25:30. Rollback log...
>>>I. 05/04 13:25:30. Checkpointing...
>>>I. 05/04 13:25:30. Starting checkpoint of "SAMM Consolidated" (SAMM
>>>Consolidated.db) at Mon May 04 2009 13:25
>>>I. 05/04 13:26:17. Finished checkpoint of "SAMM Consolidated" (SAMM
>>>Consolidated.db) at Mon May 04 2009 13:26
>>>I. 05/04 13:26:17. Recovery complete
>>>I. 05/04 13:26:17. Database server stopped at Mon May 04 2009 13:26
>>>~
>>>~
>>>I. 05/04 13:26:17. Starting database "SAMM Consolidated" (D:\Sybase ASA
>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>>>2009 13:26
>>>I. 05/04 13:26:17. Database recovery in progress
>>>I. 05/04 13:26:17. Last checkpoint at Mon May 04 2009 13:26
>>>I. 05/04 13:26:17. Checkpoint log...
>>>I. 05/04 13:26:17. Performance warning: Database file "D:\Sybase ASA
>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of
>>>1389
>>>disk fragments
>>>I. 05/04 13:26:24. Transaction log: D:\Temp\SAMM\090429AA.LOG...
>>>E. 05/04 13:29:04. Error: Database cannot be started --
>>>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>>>I. 05/04 13:29:04. Error: Database cannot be started --
>>>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>>>I. 05/04 13:29:04.
>>>E. 05/04 13:29:04. Database cannot be started -- D:\Temp\SAMM\090429AA.LOG
>>>is an invalid transaction log
>>>
>>
>> --
>> Breck Carter http://sqlanywhere.blogspot.com/
>>
>> RisingRoad SQL Anywhere and MobiLink Professional Services
>> breck.carter@risingroad.com
>

--
Breck Carter http://sqlanywhere.blogspot.com/

RisingRoad SQL Anywhere and MobiLink Professional Services
breck.carter@risingroad.com


Jim Diaz Posted on 2009-05-11 10:33:24.0Z
From: "Jim Diaz" <nospam@emprisecorporation.com>
Newsgroups: sybase.public.sqlanywhere
References: <4a034361@forums-1-dub> <ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com> <4a041e53$1@forums-1-dub> <dp39055paid5eb6a3gflbmnbjpf503vteq@4ax.com>
Subject: Re: Database Recovery Error - Database cannot be started -- xxx is an invalid transaction log
Lines: 149
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5512
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4a07fef4@forums-1-dub>
Date: 11 May 2009 03:33:24 -0700
X-Trace: forums-1-dub 1242038004 10.22.241.152 (11 May 2009 03:33:24 -0700)
X-Original-Trace: 11 May 2009 03:33:24 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.sqlanywhere:287
Article PK: 866723

Thanks Breck I'll open an case. I tried with the Dbsrv9 same result.

Jim

"Breck Carter [TeamSybase]" <NOSPAM__breck.carter@gmail.com> wrote in
message news:dp39055paid5eb6a3gflbmnbjpf503vteq@4ax.com...
>I did not know that (about dblog reporting on a log file)... it is not
> documented in the Help, not even 11.0.1.
>
> As for your real problem, it sounds serious enough to call tech
> support.
>
> The only workaround I can think of us is use dbtran and apply the
> resulting SQL via dbisql... not pretty.
>
> FWIW when applying logs in recovery mode, the server command line
> should use the same engine and same performance parameters as the
> command line in use when the transaction log entries were originally
> recorded. For example, if there were 100 busy connections updating the
> database, then the engine's gonna have to use 100 connections to apply
> the transaction log in forward recovery. If you ran with dbsrv9, then
> recover with dbsrv9.
>
> I doubt that will help here... OTOH maybe the message you got was
> misleading about the root cause (like that's never happened before :)
>
> Breck
>
> On 8 May 2009 04:58:11 -0700, "Jim Diaz"
> <nospam@emprisecorporation.com> wrote:
>
>>Breck,
>>
>>Hi and thanks. Regarding dblog, it recognizes the file as a log file and
>>reports the properties without error (see below).
>>
>>The command line
>>
>>"C:\Program Files\Sybase\SQL Anywhere 9\win32\dbeng9" "D:\Sybase ASA
>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" -a
>>"D:\Temp\SAMM\090429AA.LOG" -o "D:\Temp\SAMM\Recover.log"
>>
>>DBTran command line and output:
>>"C:\Program Files\Sybase\SQL Anywhere 9\win32\dbtran.exe" -y
>>"D:\Temp\SAMM\090429AA.LOG" "D:\Temp\SAMM\090429AA.LOG.sql"
>>
>>Adaptive Server Anywhere Log Translation Utility Version 9.0.2.3546
>>Transaction log "D:\Temp\SAMM\090429AA.LOG" starts at offset 0109516958579
>>Transaction log ends at offset 0109566140930
>>
>>
>>DBLog Command Line and output:
>>"C:\Program Files\Sybase\SQL Anywhere 9\win32\dblog.exe"
>>"D:\Temp\SAMM\090429AA.LOG"
>>
>>Adaptive Server Anywhere Transaction Log Utility Version 9.0.2.3546
>>File "D:\Temp\SAMM\090429AA.LOG" is a transaction log file
>>File version is 41
>>Log starts at offset 0109516958579
>>Log ends at offset 0109566140930
>>Log contains 12008 pages with a page size of 4096 bytes
>>49182351 bytes in use (100.00%), 2417 bytes free (0.00%)
>>
>>
>>
>>
>>"Breck Carter [TeamSybase]" <NOSPAM__breck.carter@gmail.com> wrote in
>>message news:ait705lf9155jhn7sn1bbt524bj9p476tq@4ax.com...
>>> Show us the dbsrv9 command line you used to apply
>>> D:\Temp\SAMM\090429AA.LOG
>>>
>>> Show us the dbtran command line you used to check
>>> D:\Temp\SAMM\090429AA.LOG
>>>
>>> When you say dblog indicates the log is fine, what do you mean by
>>> that?
>>>
>>> Breck
>>>
>>>
>>> On 7 May 2009 13:24:01 -0700, "Jim Diaz"
>>> <nospam@emprisecorporation.com> wrote:
>>>
>>>>I am recovering a ASA 9.0.2.3546 database and get the error "Database
>>>>cannot
>>>>be started -- xxx is an invalid transaction log"
>>>>
>>>>DBLog and DBTran both indicate the log is fine. Starting Offset matches
>>>>the
>>>>previous ending offset.
>>>>
>>>>
>>>>I. 05/04 13:19:22. Starting database "SAMM Consolidated" (D:\Sybase ASA
>>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>>>>2009 13:19
>>>>I. 05/04 13:19:22. Database recovery in progress
>>>>I. 05/04 13:19:22. Last checkpoint at Mon May 04 2009 13:19
>>>>I. 05/04 13:19:22. Checkpoint log...
>>>>I. 05/04 13:19:22. Performance warning: Database file "D:\Sybase ASA
>>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of
>>>>1364
>>>>disk fragments
>>>>I. 05/04 13:19:30. Transaction log: D:\Temp\SAMM\090428AA.LOG...
>>>>I. 05/04 13:25:30. Rollback log...
>>>>I. 05/04 13:25:30. Checkpointing...
>>>>I. 05/04 13:25:30. Starting checkpoint of "SAMM Consolidated" (SAMM
>>>>Consolidated.db) at Mon May 04 2009 13:25
>>>>I. 05/04 13:26:17. Finished checkpoint of "SAMM Consolidated" (SAMM
>>>>Consolidated.db) at Mon May 04 2009 13:26
>>>>I. 05/04 13:26:17. Recovery complete
>>>>I. 05/04 13:26:17. Database server stopped at Mon May 04 2009 13:26
>>>>~
>>>>~
>>>>I. 05/04 13:26:17. Starting database "SAMM Consolidated" (D:\Sybase ASA
>>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db) at Mon May 04
>>>>2009 13:26
>>>>I. 05/04 13:26:17. Database recovery in progress
>>>>I. 05/04 13:26:17. Last checkpoint at Mon May 04 2009 13:26
>>>>I. 05/04 13:26:17. Checkpoint log...
>>>>I. 05/04 13:26:17. Performance warning: Database file "D:\Sybase ASA
>>>>9.0\Database Files\SAMM Consolidated\SAMM Consolidated.db" consists of
>>>>1389
>>>>disk fragments
>>>>I. 05/04 13:26:24. Transaction log: D:\Temp\SAMM\090429AA.LOG...
>>>>E. 05/04 13:29:04. Error: Database cannot be started --
>>>>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>>>>I. 05/04 13:29:04. Error: Database cannot be started --
>>>>D:\Temp\SAMM\090429AA.LOG is an invalid transaction log
>>>>I. 05/04 13:29:04.
>>>>E. 05/04 13:29:04. Database cannot be started --
>>>>D:\Temp\SAMM\090429AA.LOG
>>>>is an invalid transaction log
>>>>
>>>
>>> --
>>> Breck Carter http://sqlanywhere.blogspot.com/
>>>
>>> RisingRoad SQL Anywhere and MobiLink Professional Services
>>> breck.carter@risingroad.com
>>
>
> --
> Breck Carter http://sqlanywhere.blogspot.com/
>
> RisingRoad SQL Anywhere and MobiLink Professional Services
> breck.carter@risingroad.com