[ 
https://issues.apache.org/jira/browse/DERBY-1958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12891065#action_12891065
 ] 

Eranda Sooriyabandara commented on DERBY-1958:
----------------------------------------------

Hi Mike,
getIdentity() method only print "Container(0, 161)" for me. Other than that we 
can over right the toString() to print all stuff as Bryan mentioned.
Here is a sample I made,
public String toString(){
            String str = this.identity+" Version="+this.containerVersion+
                                " estRows="+this.estimatedRowCount+" 
inBackup="+this.inBackup+
                                " inRemove="+this.inRemove+" 
isDirty="+this.isDirty+
                                " pageSize="+this.pageSize+" 
fileData="+this.fileData+
                                " actionCode="+this.actionCode;

            return str;      
        }

and its results,

ERROR XSDG3: Meta-data for Container(0, 161) Version=0 estRows=149 
inBackup=false inRemove=false isDirty=false pageSize=4096 
filedata=org.apache.derby.impl.io.dirrandomaccessfi...@1690ab actionCode=1 
could not be accessed to read 
/home/eranda/Desktop/DERBY/Derby-1958/trunk/test/MyDB/seg0/ca1.dat

Also I did not find a variable called FileContainer.estimatedPageCount. So I 
miss it in the toString method.
Thanks
   

> 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
>         Attachments: Derby-1958.diff
>
>
> 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.rafcontai...@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.

Reply via email to