Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Fri, 20 Jul 2012 21:51:35 +0000 (UTC)
From: "Mike Matrigali (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1384929939.84216.1342821095068.JavaMail.jiratomcat@issues-vm>
In-Reply-To: <1006091611.47396.1342173454320.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Commented] (DERBY-5858) java.sql.SQLException: nospc.U
 trying to update a row
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/DERBY-5858?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1341=
9600#comment-13419600 ]=20

Mike Matrigali commented on DERBY-5858:
---------------------------------------

another possible workaround for people running into this problem would be t=
o try offline compressing the table -=20
SYSCS_UTIL.SYSCS_COMPRESS_TABLE.  The system is supposed to reserve enough =
space in a page
such that any update is always possible.  There have been bugs fixed in the=
 past in this area where there
were off by one cases dealing with variable compressed fields.  Running off=
line compress sometimes can=20
change how the rows are packed on the page when they are copied to a new co=
ntainer.  It is not guaranteed
to work, but a relatively easy workaround if it does.
               =20
> java.sql.SQLException: nospc.U trying to update a row
> -----------------------------------------------------
>
>                 Key: DERBY-5858
>                 URL: https://issues.apache.org/jira/browse/DERBY-5858
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.8.2.2
>         Environment: Linux 2.6.18-194.el5    Java 1.6.0_23
> Derby 10.8.2.2 - (1181258)
>            Reporter: Gonzalo Herreros
>
> After browsing other issues, it seems the error nospc.U should not be thr=
own whenever there is still space in the disk.
> The issue is that I have a table with about 80k rows and 3 rows for some =
reason became corrupted, The rows where inserted about the same time. The r=
est of the table and the DB is working ok for weeks until I noticed the pro=
blem with those 3.
> The error is triggered when I try to set a value update in the timestamp =
column in any of those 3 rows. If I set that column to null it allows me to=
 update other columns.
> I'm not sure if it is related but I have added 3 other columns to that ta=
ble after it was created but not the timestamp one that is failing.
> The way I worked around this problem was dropping and recreating the time=
stamp column.
> Following the derby log, the problem is in the column named "last_update"=
:
> Fri Jul 13 12:31:57 IDT 2012 Thread[DRDAConnThread_5,5,main] (XID =3D 458=
542073), (SESSIONID =3D 7), (DATABASE =3D twitter), (DRDAID =3D =C3=AF=C2=
=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=
=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD.=C3=AF=C2=BF=
=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD-650487329006424032{4}), Cleanup =
action starting
> Fri Jul 13 12:31:57 IDT 2012 Thread[DRDAConnThread_5,5,main] (XID =3D 458=
542073), (SESSIONID =3D 7), (DATABASE =3D twitter), (DRDAID =3D =C3=AF=C2=
=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=
=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD.=C3=AF=C2=BF=
=C2=BD=C3=AF=C2=BF=C2=BD=C3=AF=C2=BF=C2=BD-650487329006424032{4}), Failed S=
tatement is: UPDATE trend_info SET last_update=3D'2012-07-13 09:30:52' WHER=
E stream=3D'android' AND period_id=3D'2012_06_02_23' AND trend_id=3D262
> 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.writeOpti=
onalDataToBuffer(Unknown Source)
>         at org.apache.derby.impl.store.raw.data.UpdateOperation.<init>(Un=
known Source)
>         at org.apache.derby.impl.store.raw.data.LoggableActions.actionUpd=
ate(Unknown Source)
>         at org.apache.derby.impl.store.raw.data.StoredPage.doUpdateAtSlot=
(Unknown Source)
>         at org.apache.derby.impl.store.raw.data.BasePage.updateAtSlot(Unk=
nown Source)
>         at org.apache.derby.impl.store.access.conglomerate.GenericConglom=
erateController.replace(Unknown Source)
>         at org.apache.derby.impl.sql.execute.RowChangerImpl.updateRow(Unk=
nown Source)
>         at org.apache.derby.impl.sql.execute.UpdateResultSet.collectAffec=
tedRows(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(Unk=
nown Source)
>         at org.apache.derby.impl.jdbc.EmbedStatement.executeStatement(Unk=
nown Source)
>         at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown Sour=
ce)
>         at org.apache.derby.impl.jdbc.EmbedStatement.executeUpdate(Unknow=
n Source)
>         at org.apache.derby.impl.drda.DRDAConnThread.parseEXCSQLIMM(Unkno=
wn Source)
>         at org.apache.derby.impl.drda.DRDAConnThread.processCommands(Unkn=
own Source)
>         at org.apache.derby.impl.drda.DRDAConnThread.run(Unknown Source)
> Cleanup action completed

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