db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r1557215 - /db/derby/docs/branches/10.8/src/ref/rrefexcept71493.dita
Date Fri, 10 Jan 2014 18:38:07 GMT
Author: rhillegas
Date: Fri Jan 10 18:38:07 2014
New Revision: 1557215

URL: http://svn.apache.org/r1557215
[RELEASE CHECKIN] Check in SQLState tables as part of building a release.


Modified: db/derby/docs/branches/10.8/src/ref/rrefexcept71493.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.8/src/ref/rrefexcept71493.dita?rev=1557215&r1=1557214&r2=1557215&view=diff
--- db/derby/docs/branches/10.8/src/ref/rrefexcept71493.dita (original)
+++ db/derby/docs/branches/10.8/src/ref/rrefexcept71493.dita Fri Jan 10 18:38:07 2014
@@ -898,6 +898,10 @@ the corresponding text in messages.xml a
                             <entry colname="col1">40XT7</entry>
                             <entry colname="col2">Operation is not supported in an
internal transaction.</entry>
+                        <row>
+                            <entry colname="col1">40XT8</entry>
+                            <entry colname="col2">An internal error was identified
by RawStore module. Internal state detail from the transaction is as follows: <varname>&lt;internalTransactionState&gt;</varname></entry>
+                        </row>
@@ -2695,6 +2699,14 @@ the corresponding text in messages.xml a
                             <entry colname="col2">The database directory '<varname>&lt;directoryName&gt;</varname>'
exists. However, it does not contain the expected '<varname>&lt;servicePropertiesName&gt;</varname>'
file. Perhaps Derby was brought down in the middle of creating this database. You may want
to delete this directory and try creating the database again.</entry>
+                            <entry colname="col1">XBM0B</entry>
+                            <entry colname="col2">Failed to edit/write service properties
file: <varname>&lt;errorMessage&gt;</varname></entry>
+                        </row>
+                        <row>
+                            <entry colname="col1">XBM0C</entry>
+                            <entry colname="col2">Missing privilege for operation '<varname>&lt;operation&gt;</varname>'
on file '<varname>&lt;path&gt;</varname>': <varname>&lt;errorMessage&gt;</varname></entry>
+                        </row>
+                        <row>
                             <entry colname="col1">XBM0G</entry>
                             <entry colname="col2">Failed to start encryption engine.
Please make sure you are running Java 2 and have downloaded an encryption provider such as
jce and put it in your class path. </entry>
@@ -4180,6 +4192,10 @@ ln=lower-case two-letter ISO-639 languag
                             <entry colname="col1">XSDAO</entry>
                             <entry colname="col2">Internal error: page <varname>&lt;pageNumber&gt;</varname>
attempted latched twice.</entry>
+                        <row>
+                            <entry colname="col1">XSDAP</entry>
+                            <entry colname="col2">Unexpected no space error while attempting
to update a row on page <varname>&lt;pageId&gt;</varname>. Values of internal
fields at time of error are as follows: slot = <varname>&lt;slot&gt;</varname>,
recordId = <varname>&lt;recordId&gt;</varname>, newColumnList = <varname>&lt;columnList&gt;</varname>,
nextColumn = <varname>&lt;nextColumn&gt;</varname>, mode = <varname>&lt;updateMode&gt;</varname>,
nextPortionHandle = <varname>&lt;nextPortionHandle&gt;</varname>, page
dump = <varname>&lt;pageDump&gt;</varname>.</entry>
+                        </row>
@@ -4398,7 +4414,7 @@ ln=lower-case two-letter ISO-639 languag
                             <entry colname="col1">XSLA4</entry>
-                            <entry colname="col2">Cannot write to the log, most likely
the log is full.  Please delete unnecessary files.  It is also possible that the file system
is read only, or the disk has failed, or some other problems with the media.  </entry>
+                            <entry colname="col2">Error encountered when attempting
to write the transaction recovery log. Most likely the disk holding the recovery log is full.
If the disk is full, the only way to proceed is to free up space on the disk by either expanding
it or deleting files not related to Derby. It is also possible that the file system and/or
disk where the Derby transaction log resides is read-only. The error can also be encountered
if the disk or file system has failed.</entry>
                             <entry colname="col1">XSLA5</entry>

View raw message