db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r1495036 - /db/derby/docs/branches/10.10/src/ref/rrefexcept71493.dita
Date Thu, 20 Jun 2013 14:56:27 GMT
Author: rhillegas
Date: Thu Jun 20 14:56:27 2013
New Revision: 1495036

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

Modified:
    db/derby/docs/branches/10.10/src/ref/rrefexcept71493.dita

Modified: db/derby/docs/branches/10.10/src/ref/rrefexcept71493.dita
URL: http://svn.apache.org/viewvc/db/derby/docs/branches/10.10/src/ref/rrefexcept71493.dita?rev=1495036&r1=1495035&r2=1495036&view=diff
==============================================================================
--- db/derby/docs/branches/10.10/src/ref/rrefexcept71493.dita (original)
+++ db/derby/docs/branches/10.10/src/ref/rrefexcept71493.dita Thu Jun 20 14:56:27 2013
@@ -934,6 +934,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>
+                        <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>
                     </tbody>
                 </tgroup>
             </table>
@@ -4459,6 +4463,14 @@ ln=lower-case two-letter ISO-639 languag
                             <entry colname="col1">XSDFI</entry>
                             <entry colname="col2">Error encountered while trying to
write data to disk during database recovery.  Check that the database disk is not full. If
it is then delete unnecessary files, and retry connecting to the database.  It is also possible
that the file system is read only, or the disk has failed, or some other problem with the
media.  System encountered error while processing page <varname>&lt;page&gt;</varname>.</entry>
                         </row>
+                        <row>
+                            <entry colname="col1">XSDFJ</entry>
+                            <entry colname="col2">Error encountered while trying to
remove database file <varname>&lt;fileName&gt;</varname>, as part of encrypting
or decrypting database files. Incorrect file or directory ownership or permissions could cause
remove of the file to fail.  Processes not controlled by Derby like backup or virus checkers
could also be responsible.</entry>
+                        </row>
+                        <row>
+                            <entry colname="col1">XSDFK</entry>
+                            <entry colname="col2">Error encountered while trying to
remove a jar file <varname>&lt;fileName&gt;</varname> stored in the database.
Incorrect file or directory ownership or permissions could cause remove of the file to fail.
 Processes not controlled by Derby like backup or virus checkers could also be responsible.</entry>
+                        </row>
                     </tbody>
                 </tgroup>
             </table>
@@ -4545,7 +4557,7 @@ ln=lower-case two-letter ISO-639 languag
                         </row>
                         <row>
                             <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>
                         </row>
                         <row>
                             <entry colname="col1">XSLA5</entry>



Mime
View raw message