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

Mike Matrigali commented on DERBY-6766:
---------------------------------------

do you have a "derby.log" for this event, I am looking at console.log but it 
seems to be client side logging
rather than server side?  If so can you post?
can you post the exact ddl for the table involved?
can you post the query being executed when the error occurs?



> java.sql.SQLException: nospc.U  Unexpected no space error while attempting to 
> update a row on page
> --------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-6766
>                 URL: https://issues.apache.org/jira/browse/DERBY-6766
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.10.2.0
>         Environment: Derby 10.10.2.0 - (1582446), AIX 6.1.0.0 
> (6100-08-03-1339), Hibernate 3.5.6-Final, Java 1.6.0 IBM J9 VM (build 2.4, 
> JRE 1.6.0 IBM J9 2.4 AIX ppc64-64)
>            Reporter: Kai Duckwitz
>            Priority: Critical
>              Labels: nospc
>         Attachments: console.zip
>
>
> We already had this error with version 10.8.2.2 an hoped that it would be 
> fixed in 10.10.2.0 due to [DERBY-4923] - but it is not.
> This error occurs sporadically on updating or inserting objects via 
> hibernate. The application runs for weeks without a problem (20-50 object 
> updates/inserts per second) and then the error occures up to 10 times in 2 
> hours; after that the error can be absent for days or weeks.
> We use only these data types:
> NUMERIC,SMALLINT,TIMESTAMP,VARCHAR
> Stacktrace:
> Caused by: java.sql.SQLException: Unexpected no space error while attempting 
> to update a row on page Page(94,Container(0, 1632)). Values of internal 
> fields at time of error are as follows: slot = 301, recordId = 28, 
> newColumnList = {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13}, nextColumn = -1, 
> mode = 0, nextPortionHandle = null, page dump = 
>       at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
>       at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
>  Source)
>       ... 51 more
> Caused by: java.sql.SQLException: nospc.U
>       at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory.getSQLException(Unknown Source)
>       at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.wrapArgsForTransportAcrossDRDA(Unknown
>  Source)
>       at 
> org.apache.derby.impl.jdbc.SQLExceptionFactory40.getSQLException(Unknown 
> Source)
>       at org.apache.derby.impl.jdbc.Util.generateCsSQLException(Unknown 
> Source)
>       at 
> org.apache.derby.impl.jdbc.TransactionResourceImpl.wrapInSQLException(Unknown 
> Source)
>       ... 48 more
> Caused by: ERROR nospc: nospc.U
>       at org.apache.derby.impl.store.raw.data.StoredPage.logRow(Unknown 
> Source)
>       at 
> org.apache.derby.impl.store.raw.data.UpdateOperation.writeOptionalDataToBuffer(Unknown
>  Source)
>       at org.apache.derby.impl.store.raw.data.UpdateOperation.<init>(Unknown 
> Source)
>       at 
> org.apache.derby.impl.store.raw.data.LoggableActions.actionUpdate(Unknown 
> Source)
>       at 
> org.apache.derby.impl.store.raw.data.StoredPage.doUpdateAtSlot(Unknown Source)
>       at org.apache.derby.impl.store.raw.data.BasePage.updateAtSlot(Unknown 
> Source)
>       at 
> org.apache.derby.impl.store.access.conglomerate.GenericConglomerateController.replace(Unknown
>  Source)
>       at org.apache.derby.impl.sql.execute.RowChangerImpl.updateRow(Unknown 
> Source)
>       at 
> org.apache.derby.impl.sql.execute.UpdateResultSet.collectAffectedRows(Unknown 
> Source)
>       at org.apache.derby.impl.sql.execute.UpdateResultSet.open(Unknown 
> Source)
>       at 
> org.apache.derby.impl.sql.GenericPreparedStatement.executeStmt(Unknown Source)
>       at org.apache.derby.impl.sql.GenericPreparedStatement.execute(Unknown 
> Source)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to