db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4075) ERROR XSDBB: Unknown page format at page Page(613,Container(0, 1024)) when running MailJdbc (Embedded) system tests
Date Thu, 26 Feb 2009 22:53:01 GMT

     [ https://issues.apache.org/jira/browse/DERBY-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mike Matrigali updated DERBY-4075:
----------------------------------


I went through the derby.log - do continue to run this against a SANE server as we are getting
more information into derby.log that way.

I assume the db is too big to post to the jira.  Can you try to connect to it with IJ and
see if it
boots ok?  It would be interesting to know if the problem was in memory or on disk.

Can you post any more information about the environment?  Number of processors, cores per
processor, whether disk write cache is enabled or not, what kind of disks?  Just want to get
a
feel on how concurrent the test is being.

Does this test log what it has done in any other way, maybe some sort of test specific log?
 Off hand do you know if compress table is being tested?  The last thing in the log is a failed
backup, which I think can be ignored as I think it failed because we set the db corrupt by
the previous error.  Did the test do any valid backups before this?  I think this test has
uncovered 
I/O coordination problems between backup and the main code before.

It looks like we got an exception from an initPage() call on Page(613,Container(0, 1024)).
 From the hex dump it looks like the page is all 0's.  A free page should not be all 0's it
should have a valid page header at least.  Only un-allocated page

>From a little bit above this we dumped all the alloc page information on the table.  
Specifics are there but of interest is that pages 1 through 612 are in use, and 613 - 813
free, 814-1050 mostly in use (a few scattered free page), and finally 1050-86672 are unallocated
- I think this is just what the debugging prints for the remaining bits of any alloc page
it dumps.

> ERROR XSDBB: Unknown page format at page Page(613,Container(0, 1024)) when running MailJdbc
(Embedded) system tests
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4075
>                 URL: https://issues.apache.org/jira/browse/DERBY-4075
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions: 10.5.0.0
>         Environment: windows 2000 professional, ibm 1.6 (sr2), revision 10.5: 745360
>            Reporter: Myrna van Lunteren
>            Priority: Blocker
>             Fix For: 10.5.0.0
>
>         Attachments: derbylog.zip
>
>
> I started the org.apache.derbyTesting.system.mailJdbc Embedded test and after about 1
day it ran into an apparently corrupted database.
> 2009-02-19 14:02:44.221 GMT Thread[Refresh Thread,5,main] (XID = 349909), (SESSIONID
= 1), (DATABASE = mailsdb), (DRDAID = null), Failed Statement is: insert into REFRESH.INBOX(from_name,to_name,date,Message,attach_id,size_problem)
values (?,?,?,?,?,?) with 6 parameters begin parameter #1: ABCE :end parameter begin parameter
#2: WXYY :end parameter begin parameter #3: 2009-02-19 06:02:43.705 :end parameter begin parameter
#4: CLOB(org.apache.derby.iapi.types.ReaderToUTF8Stream@41ba41ba) :end parameter begin parameter
#5: 0 :end parameter begin parameter #6: This column is used only to by pass the space problem.
If the problem still exists, then we are going to have a serious issue here.*****************************************************************************************************
:end parameter 
> ERROR XSDBB: Unknown page format at page Page(613,Container(0, 1024)), page dump follows:
Hex dump:
> The error up to that point appear to me no different from other errors that this test
is expected to produce (40001, 23505, 4XL01) except that the very first error is a grant error.
> I think we can't have a release until this corruption is explained away or fixed.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message