Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Discussion" <derby-user@db.apache.org>
Received-SPF: pass (herse.apache.org: local policy)
thread-index: AccJoi5z/oPmjcogQ5CKubbS0YLzXg==
Message-ID: 
 <2526D42D65F597428BFF422D6AB79E9E0108FB9D@NA1000EXM01.na.ds.monsanto.com>
From: "BALDWIN, ALAN J [AG-Contractor/1000]" <alan.j.baldwin@monsanto.com>
Content-Transfer-Encoding: 7bit
To: "Derby Discussion" <derby-user@db.apache.org>
Subject: RE: java.sql.SQLException: Log Corrupted,
 has invalid data in the log stream.
Date: Thu, 16 Nov 2006 11:01:35 -0600
MIME-Version: 1.0
Importance: normal
Priority: normal
content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="iso-8859-1"

I have not *noticed* any inconsistencies after deleting these files,
however, that doesn't mean there aren't any.  It just means they haven't
been reported.  

I have never run the compress table routines.  Is that something that
can be done programmatically at runtime?  

The corruption is noticed when we try to start the app and connect to
the database.  It won't let us connect.  Also, as expected, we cannot
connect using tools like Cloudscape Workbench either once this state is
reached.

I can't think of anything else that is relevant at this point.  It seems
to be random, and it does not seem to be related to users killing the
app halfway through a transaction or anything like that.

-Alan-

-----Original Message-----
From: Mayuresh Nirhali [mailto:Mayuresh.Nirhali@Sun.COM] 
Sent: Thursday, November 16, 2006 6:04 AM
To: Derby Discussion
Subject: Re: java.sql.SQLException: Log Corrupted, has invalid data in
the log stream.

Alan,

As you are aware, it is not recommended to delete the log fils manually.
The logCorruptedException has another nestedException and it is because 
the value read from the log records is not matched with required 
appropriate data.
But, Did you observe any sort of inconsistencies in your database when 
you boot again after you delete the files. ?

How often do you (or did you ever) run the compress table routines ??

Do you see the log corrupted when you boot the db or during some 
transactions ??

any more information which you think is relevant ??

Mayuresh


BALDWIN, ALAN J [AG-Contractor/1000] wrote:

>More info:
>
>Windows XP
>
>JVM 1.5 and JVM 1.4.2 
>
> 
>
>I don't see any exceptions being thrown in our application before any
of the
>corruption cases that would indicate that something in the app had gone
>awry.  
>
> 
>
>Also, attached is my derby.log file.
>
> 
>
>-Alan-
>
> 
>
> 
>
>-----Original Message-----
>From: BALDWIN, ALAN J [AG-Contractor/1000] 
>Sent: Thursday, November 16, 2006 9:42 AM
>To: derby-user@db.apache.org
>Subject: java.sql.SQLException: Log Corrupted, has invalid data in the
log
>stream.
>
> 
>
>Hi all,
>
>We are having log corruption issues with Derby inside of a java swing
>application.
>
>Here is the error:
>
>java.sql.SQLException: Log Corrupted, has invalid data in the log
stream.
>
>We have about 1000 users using this software, and I would guess that at
any
>given time we see 4-5 with log corruption.  Deleting "logXXX.dat" files
from
>within the log folder fixes the problem for the time being, but I would
like
>to get at the root of the problem.  Is this safe to do as an interim
>solution?  I assume these are transaction logs, so it doesn't seem like
a
>good idea to delete them, but that is the only thing that seems to
work.
>Also, anecdotally, this seems to be more prevalent in version 10.2
since we
>upgraded from 10.1.3 a few weeks ago.
>
>I'm also going to dig around on JIRA to seem if I come up with
anything.
>
>Any ideas?
>
>Thanks,
>
>  
>


---------------------------------------------------------------------------------------------------------
This e-mail message may contain privileged and/or confidential information, and is intended to be received only by persons entitled to receive such information. If you have received this e-mail in error, please notify the sender immediately. Please delete it and all attachments from any servers, hard drives or any other media. Other use of this e-mail by you is strictly prohibited.


All e-mails and attachments sent and received are subject to monitoring, reading and archival by Monsanto. The recipient of this e-mail is solely responsible for checking for the presence of "Viruses" or other "Malware". Monsanto accepts no liability for any damage caused by any such code transmitted by or accompanying this e-mail or any attachment.
---------------------------------------------------------------------------------------------------------