db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ratish ram (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5659) Database corrupted after delete operation - results in sqlcode XSDB2
Date Fri, 16 Mar 2012 14:31:41 GMT

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

ratish ram commented on DERBY-5659:

Hi Rick

Excuse me for the delay, I had to get the log file from the client. I do not see much info
on the log file. 
Another piece of information that I received was, the database was possibly executed by a
duplicate server at the same time. And that might have resulted in this corruption. 

Got two questions:
a) What does it mean by XSDB2Unknown container format at container null : 1,702,392,933 
b) Is there anyway to retrieve the data from the corrupted database or restore the db?

> Database corrupted after delete operation - results in sqlcode XSDB2
> --------------------------------------------------------------------
>                 Key: DERBY-5659
>                 URL: https://issues.apache.org/jira/browse/DERBY-5659
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions:
>         Environment: Windows 7 32 bit
>            Reporter: ratish ram
>            Priority: Critical
>              Labels: corruption, xsdb2
>         Attachments: derby.log
> Derby Embedded Database became non-accessible after a delete operation. Trying to connect
to the database now results in the following exception.
> Caused by: org.apache.derby.client.am.SqlException: DERBY SQL error: SQLCODE: -1, SQLSTATE:
XJ040, SQLERRMC: Failed to start database 'XXXX' with class loader org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader@73983ad7,
see the next exception for details.::SQLSTATE: XSDB2Unknown container format at container
null : 1,702,392,933
> 	at org.apache.derby.client.am.Connection.completeSqlca(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseRdbAccessFailed(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseAccessRdbError(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.parseACCRDBreply(Unknown Source)
> 	at org.apache.derby.client.net.NetConnectionReply.readAccessDatabase(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.readSecurityCheckAndAccessRdb(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.flowSecurityCheckAndAccessRdb(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.flowUSRIDPWDconnect(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.flowConnect(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection.<init>(Unknown Source)
> 	at org.apache.derby.client.net.NetConnection40.<init>(Unknown Source)
> 	at org.apache.derby.client.net.ClientJDBCObjectFactoryImpl40.newNetConnection(Unknown
> 	... 52 more

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message