[jira] Updated: (DERBY-1958) improve XSDG3 error to print container, actual i/o operation, and file name.

["Mike Matrigali (JIRA)" <ji...@apache.org>]

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

Mike Matrigali updated DERBY-1958:
----------------------------------


As others have suggested, in order to go through those routines you need to "avoid" the page cache.
Here are some suggestions:
    o for read the easiest thing is probably to shut down the database
       and restart.  On restart there is nothing in the cache so it is
       necessary to read pages from disk to the cache.
    o to cause both read and write I would suggest changing the
       size of the page cache from it's default of 1000 pages to
       something much smaller, like 40 pages using    derby.storage.pageCacheSize.  Then create a table that has actual data in it that is bigger than 40*32k.  Maybe a row with a blob that has actual data in it bigger than this number.  Updates to that blob should cause both reads and writes since the pages should not fit in the cache.  

> improve XSDG3 error to print container, actual i/o operation, and file name.
> ----------------------------------------------------------------------------
>
>                 Key: DERBY-1958
>                 URL: https://issues.apache.org/jira/browse/DERBY-1958
>             Project: Derby
>          Issue Type: Improvement
>          Components: Store
>    Affects Versions: 10.1.3.1, 10.2.1.6, 10.3.1.4
>            Reporter: Mike Matrigali
>            Priority: Trivial
>
> The current error does not give enough information to know what container is the problem:
> ERROR XSDG3: Meta-data for Container
> org.apache.derby.impl.store.raw.data.RAFContainer@10632cd could not be
> accessed 

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