db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhille...@apache.org
Subject svn commit: r469975 [2/3] - in /db/derby/code/trunk/java: build/org/apache/derbyBuild/ engine/org/apache/derby/loc/
Date Wed, 01 Nov 2006 16:44:27 GMT
Added: db/derby/code/trunk/java/engine/org/apache/derby/loc/messages.xml
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/engine/org/apache/derby/loc/messages.xml?view=auto&rev=469975
==============================================================================
--- db/derby/code/trunk/java/engine/org/apache/derby/loc/messages.xml (added)
+++ db/derby/code/trunk/java/engine/org/apache/derby/loc/messages.xml Wed Nov  1 08:44:26 2006
@@ -0,0 +1,7269 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!DOCTYPE messages SYSTEM "messages.dtd">
+
+<!-- 
+Licensed to the Apache Software Foundation (ASF) under one or more
+contributor license agreements.  See the NOTICE file distributed with
+this work for additional information regarding copyright ownership.
+The ASF licenses this file to You under the Apache License, Version 2.0
+(the "License"); you may not use this file except in compliance with
+the License.  You may obtain a copy of the License at      
+
+http://www.apache.org/licenses/LICENSE-2.0  
+
+Unless required by applicable law or agreed to in writing, software  
+distributed under the License is distributed on an "AS IS" BASIS,  
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.  
+See the License for the specific language governing permissions and  
+limitations under the License.
+-->
+
+
+<!-- 
+This file contains all of the internationalized messages used by
+the Derby engine. For each message, we provide the following
+information:
+
+  * Name of the message - for most messages, this encodes a SQLState
+  * Message text returned to the user
+  * Human-readable names for message arguments
+
+This file is used to generate the following files when Derby is built:
+
+  * messages_en.properties - the English message text shipped with Derby
+  * rrefexcept71493.dita - the source for the table of SQLStates in the Derby Reference Guide.
+
+See the accompanying messages.dtd for an explanation of this xml grammar.-->
+
+<messages>
+
+<!-- 
+This section contains all of the messages which have SQLStates. These
+are the message which turn up in SQLExceptions returned by the Derby
+JDBC drivers. These messages are documented in the Derby Reference
+Guide.
+-->
+
+    <section>
+        <desc>Messages with SQLStates, documented in the Derby Reference Guide</desc>
+        <documented/>
+
+
+        <family>
+            <title>Class 01: Warning</title>
+
+            <msg>
+                <name>01001</name>
+                <text>An attempt to update or delete an already deleted row was made: No row was updated or deleted.</text>
+            </msg>
+
+            <msg>
+                <name>01003</name>
+                <text>Null values were eliminated from the argument of a column function.</text>
+            </msg>
+
+            <msg>
+                <name>01006</name>
+                <text>Privilege not revoked from user {0}.</text>
+                <arg>authorizationID</arg>
+            </msg>
+
+            <msg>
+                <name>0100E</name>
+                <text>XX Attempt to return too many result sets. </text>
+            </msg>
+
+            <msg>
+                <name>01500</name>
+                <text>The constraint {0} on table {1} has been dropped.</text>
+                <arg>constraintName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>01501</name>
+                <text>The view {0} has been dropped.</text>
+                <arg>viewName</arg>
+            </msg>
+
+            <msg>
+                <name>01502</name>
+                <text>The trigger {0} on table {1} has been dropped.</text>
+                <arg>triggerName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>01503</name>
+                <text>The column {0} on table {1} has been modified by adding a not null constraint.</text>
+                <arg>columnName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>01504</name>
+                <text>The new index is a duplicate of an existing index: {0}.</text>
+                <arg>indexName</arg>
+            </msg>
+
+            <msg>
+                <name>01505</name>
+                <text>The value {0} may be truncated.</text>
+                <arg>valueName</arg>
+            </msg>
+
+            <msg>
+                <name>01522</name>
+                <text>The newly defined synonym '{0}' resolved to the object '{1}' which is currently undefined.</text>
+                <arg>synonymName</arg>
+                <arg>objectName</arg>
+            </msg>
+
+            <msg>
+                <name>01J01</name>
+                <text>Database '{0}' not created, connection made to existing database instead.</text>
+                <arg>databaseName</arg>
+            </msg>
+
+            <msg>
+                <name>01J02</name>
+                <text>Scroll sensitive cursors are not currently implemented.</text>
+            </msg>
+
+            <msg>
+                <name>01J04</name>
+                <text>The class '{0}' for column '{1}' does not implement java.io.Serializable or java.sql.SQLData. Instances must implement one of these interfaces to allow them to be stored.</text>
+                <arg>className</arg>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>01J05</name>
+                <text>Database upgrade succeeded. The upgraded database is now ready for use. Revalidating stored prepared statements failed. See next exception for details of failure.</text>
+            </msg>
+
+            <msg>
+                <name>01J06</name>
+                <text>ResultSet not updatable. Query does not qualify to generate an updatable ResultSet.</text>
+            </msg>
+
+            <msg>
+                <name>01J07</name>
+                <text>ResultSetHoldability restricted to ResultSet.CLOSE_CURSORS_AT_COMMIT for a global transaction.</text>
+            </msg>
+
+            <msg>
+                <name>01J08</name>
+                <text>Unable to open resultSet type {0}. ResultSet type {1} opened.</text>
+                <arg>resultSetType</arg>
+                <arg>resultSetType</arg>
+            </msg>
+
+            <msg>
+                <name>01J10</name>
+                <text>Scroll sensitive result sets are not supported by server; remapping to forward-only cursor</text>
+            </msg>
+
+            <msg>
+                <name>01J12</name>
+                <text>Unable to obtain message text from server. See the next exception. The stored procedure SYSIBM.SQLCAMESSAGE is not installed on the server. Please contact your database administrator.</text>
+            </msg>
+
+            <msg>
+                <name>01J13</name>
+                <text>Number of rows returned ({0}) is too large to fit in an integer; the value returned will be truncated.</text>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>01J14</name>
+                <text>SQL authorization is being used without first enabling authentication.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 04: Database authentication</title>
+
+            <msg>
+                <name>04501.C</name>
+                <text>Database connection refused.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 07: Dynamic SQL Error</title>
+
+            <msg>
+                <name>07000</name>
+                <text>At least one parameter to the current statement is uninitialized.</text>
+            </msg>
+
+            <msg>
+                <name>07004</name>
+                <text>Parameter {0} is an {1} procedure parameter and must be registered with CallableStatement.registerOutParameter before execution.</text>
+                <arg>parameterName</arg>
+                <arg>procedureName</arg>
+            </msg>
+
+            <msg>
+                <name>07009</name>
+                <text>No input parameters.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 08: Connection Exception</title>
+
+            <msg>
+                <name>08000</name>
+                <text>Connection closed by unknown interrupt.</text>
+            </msg>
+
+            <msg>
+                <name>08000.S.1</name>
+                <text>Cannot close a connection with an active transaction.  The transaction remains open and the connection was not closed.</text>
+            </msg>
+
+            <msg>
+                <name>08001.C.10</name>
+                <text>A connection could not be established because the security token is larger than the maximum allowed by the network protocol.</text>
+            </msg>
+
+            <msg>
+                <name>08001.C.11</name>
+                <text>A connection could not be established because the user id has a length of zero or is larger than the maximum allowed by the network protocol.</text>
+            </msg>
+
+            <msg>
+                <name>08001.C.12</name>
+                <text>A connection could not be established because the password has a length of zero or is larger than the maximum allowed by the network protocol.</text>
+            </msg>
+
+            <msg>
+                <name>08001.C.1</name>
+                <text>Required Derby DataSource property {0} not set.</text>
+                <arg>propertyName</arg>
+            </msg>
+
+            <msg>
+                <name>08001.C.2</name>
+                <text>{0} : Error connecting to server {1} on port {2} with message {3}.</text>
+                <arg>error</arg>
+                <arg>serverName</arg>
+                <arg>portNumber</arg>
+                <arg>messageText</arg>
+            </msg>
+
+            <msg>
+                <name>08001.C.3</name>
+                <text>SocketException: '{0}'</text>
+                <arg>error</arg>
+            </msg>
+
+            <msg>
+                <name>08001.C.4</name>
+                <text>Unable to open stream on socket: '{0}'.</text>
+                <arg>error</arg>
+            </msg>
+
+            <msg>
+                <name>08001.C.5</name>
+                <text>User id length ({0}) is outside the range of 1 to {1}.</text>
+                <arg>number</arg>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>08001.C.6</name>
+                <text>Password length ({0}) is outside the range of 1 to {1}.</text>
+                <arg>value</arg>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>08001.C.7</name>
+                <text>User id can not be null.</text>
+            </msg>
+
+            <msg>
+                <name>08001.C.8</name>
+                <text>Password can not be null.</text>
+            </msg>
+
+            <msg>
+                <name>08001.C.9</name>
+                <text>A connection could not be established because the database name '{0}' is larger than the maximum length allowed by the network protocol.</text>
+                <arg>databaseName</arg>
+            </msg>
+
+            <msg>
+                <name>08003</name>
+                <text>No current connection.</text>
+            </msg>
+
+            <msg>
+                <name>08003.C.1</name>
+                <text>getConnection() is not valid on a closed PooledConnection.</text>
+            </msg>
+
+            <msg>
+                <name>08003.C.2</name>
+                <text>Lob method called after connection was closed</text>
+            </msg>
+
+            <msg>
+                <name>08003.C.3</name>
+                <text>The underlying physical connection is stale or closed.</text>
+            </msg>
+
+            <msg>
+                <name>08004</name>
+                <text>Connection refused : {0}</text>
+                <arg>connectionName</arg>
+            </msg>
+
+            <msg>
+                <name>08004.C.1</name>
+                <text>Connection authentication failure occurred.  Reason: {0}.</text>
+                <arg>reasonText</arg>
+            </msg>
+
+            <msg>
+                <name>08004.C.2</name>
+                <text>The connection was refused because the database {0} was not found.</text>
+                <arg>databaseName</arg>
+            </msg>
+
+            <msg>
+                <name>08006.C.1</name>
+                <text>An error occurred during connect reset and the connection has been terminated.  See chained exceptions for details.</text>
+            </msg>
+
+            <msg>
+                <name>08006.D</name>
+                <text>Database '{0}' shutdown.</text>
+                <arg>databaseName</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 0A: Feature not supported</title>
+
+            <msg>
+                <name>0A000.S</name>
+                <text>Feature not implemented: {0}.</text>
+                <arg>featureName</arg>
+            </msg>
+
+            <msg>
+                <name>0A000.C.6</name>
+                <text>The DRDA command {0} is not currently implemented.  The connection has been terminated.</text>
+                <arg>commandName</arg>
+            </msg>
+
+            <msg>
+                <name>0A000.S.1</name>
+                <text>JDBC method is not yet implemented.</text>
+            </msg>
+
+            <msg>
+                <name>0A000.S.2</name>
+                <text>JDBC method {0} is not supported by the server. Please upgrade the server.</text>
+                <arg>methodName</arg>
+            </msg>
+
+            <msg>
+                <name>0A000.S.3</name>
+                <text>resultSetHoldability property {0} not supported</text>
+                <arg>propertyName</arg>
+            </msg>
+
+            <msg>
+                <name>0A000.S.4</name>
+                <text>cancel() not supported by the server.</text>
+            </msg>
+
+            <msg>
+                <name>0A000.S.5</name>
+                <text>Security mechanism '{0}' is not supported.</text>
+                <arg>mechanismName</arg>
+            </msg>
+
+            <msg>
+                <name>0A000.S.7</name>
+                <text>The data type '{0}' is not supported.</text>
+                <arg>datatypeName</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 21: Cardinality Violation</title>
+
+            <msg>
+                <name>21000</name>
+                <text>Scalar subquery is only allowed to return a single row.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 22: Data Exception</title>
+
+            <msg>
+                <name>22001</name>
+                <text>A truncation error was encountered trying to shrink {0} '{1}' to length {2}.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>22003</name>
+                <text>The resulting value is outside the range for the data type {0}.</text>
+                <arg>datatypeName</arg>
+            </msg>
+
+            <msg>
+                <name>22003.S.1</name>
+                <text>Year ({0}) exceeds the maximum '{1}'.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>22003.S.2</name>
+                <text>Decimal may only be up to 31 digits.</text>
+            </msg>
+
+            <msg>
+                <name>22003.S.3</name>
+                <text>Overflow occurred during numeric data type conversion of '{0}' to {1}.</text>
+                <arg>datatypeName</arg>
+                <arg>datatypeName</arg>
+            </msg>
+
+            <msg>
+                <name>22004.S.4</name>
+                <text>The length ({0}) exceeds the maximum length for the data type ({1}).</text>
+                <arg>number</arg>
+                <arg>datatypeName</arg>
+            </msg>
+
+            <msg>
+                <name>22005.S.1</name>
+                <text>Unable to convert a value of type '{0}' to type '{1}' : the encoding is not supported.</text>
+                <arg>typeName</arg>
+                <arg>typeName</arg>
+            </msg>
+
+            <msg>
+                <name>22005.S.2</name>
+                <text>The required character converter is not available.</text>
+            </msg>
+
+            <msg>
+                <name>22005.S.3</name>
+                <text>Unicode string cannot convert to Ebcdic string</text>
+            </msg>
+
+            <msg>
+                <name>22005.S.4</name>
+                <text>Unrecognized JDBC type. Type: {0}, columnCount: {1}, columnIndex: {2}.</text>
+                <arg>typeName</arg>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>22005.S.5</name>
+                <text>Invalid JDBC type for parameter {0}.</text>
+                <arg>parameterName</arg>
+            </msg>
+
+            <msg>
+                <name>22005.S.6</name>
+                <text>Unrecognized Java SQL type {0}.</text>
+                <arg>datatypeName</arg>
+            </msg>
+
+            <msg>
+                <name>22005</name>
+                <text>An attempt was made to get a data value of type '{0}' from a data value of type '{1}'.</text>
+                <arg>datatypeName</arg>
+                <arg>datatypeName</arg>
+            </msg>
+
+            <msg>
+                <name>22007.S.180</name>
+                <text>The string representation of a datetime value is out of range.</text>
+            </msg>
+
+            <msg>
+                <name>22007.S.181</name>
+                <text>The syntax of the string representation of a datetime value is incorrect.</text>
+            </msg>
+
+            <msg>
+                <name>22008.S</name>
+                <text>'{0}' is an invalid argument to the {1} function.</text>
+                <arg>argument</arg>
+                <arg>functionName</arg>
+            </msg>
+
+            <msg>
+                <name>2200L</name>
+                <text>Values assigned to XML columns must be well-formed DOCUMENT nodes.</text>
+            </msg>
+
+            <msg>
+                <name>2200M</name>
+                <text>Invalid XML DOCUMENT: {0}</text>
+                <arg>parserError</arg>
+            </msg>
+
+            <msg>
+                <name>2200V</name>
+                <text>Invalid context item for {0} operator; context items must be well-formed DOCUMENT nodes.</text>
+                <arg>operatorName</arg>
+            </msg>
+
+            <msg>
+                <name>2200W</name>
+                <text>XQuery serialization error: Attempted to serialize one or more top-level Attribute nodes.</text>
+            </msg>
+
+            <msg>
+                <name>22011</name>
+                <text>The second or third argument of the SUBSTR function is out of range.</text>
+            </msg>
+
+            <msg>
+                <name>22012</name>
+                <text>Attempt to divide by zero.</text>
+            </msg>
+
+            <msg>
+                <name>22013</name>
+                <text>Attempt to take the square root of a negative number, '{0}'.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>22014</name>
+                <text>The start position for LOCATE is invalid; it must be a positive integer. The index  to start the search from is '{2}'.  The string to search for is '{0}'.  The string to search from is '{1}'. </text>
+                <arg>startIndex</arg>
+                <arg>searchString</arg>
+                <arg>fromString</arg>
+            </msg>
+
+            <msg>
+                <name>22015.S.1</name>
+                <text> Invalid data conversion: requested conversion would result in a loss of precision of {0}</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>22015</name>
+                <text>The '{0}' function is not allowed on the following set of types.  First operand is of type '{1}'.  Second operand is of type '{2}'.  Third operand (start position) is of type '{3}'.</text>
+                <arg>functionName</arg>
+                <arg>typeName</arg>
+                <arg>typeName</arg>
+                <arg>typeName</arg>
+            </msg>
+
+            <msg>
+                <name>22018</name>
+                <text>Invalid character string format for type {0}.</text>
+                <arg>typeName</arg>
+            </msg>
+
+            <msg>
+                <name>22019</name>
+                <text>Invalid escape sequence, '{0}'. The escape string must be exactly one character. It cannot be a null or more than one character.</text>
+                <arg>sequenceName</arg>
+            </msg>
+
+            <msg>
+                <name>22025</name>
+                <text>Escape character must be followed by escape character, '_', or '%'. It cannot be followed by any other character or be at the end of the pattern.</text>
+            </msg>
+
+            <msg>
+                <name>22027</name>
+                <text>The built-in TRIM() function only supports a single trim character.  The LTRIM() and RTRIM() built-in functions support multiple trim characters.</text>
+            </msg>
+
+            <msg>
+                <name>22028</name>
+                <text>The string exceeds the maximum length of {0}.</text>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>22501</name>
+                <text>An ESCAPE clause of NULL returns undefined results and is not allowed.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 23: Constraint Violation </title>
+
+            <msg>
+                <name>23502</name>
+                <text>Column '{0}'  cannot accept a NULL value.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>23503</name>
+                <text>{2} on table '{1}' caused a violation of foreign key constraint '{0}' for key {3}.  The statement has been rolled back.</text>
+                <arg>value</arg>
+                <arg>tableName</arg>
+                <arg>constraintName</arg>
+                <arg>keyName</arg>
+            </msg>
+
+            <msg>
+                <name>23505</name>
+                <text>The statement was aborted because it would have caused a duplicate key value in a unique or primary key constraint or unique index identified by '{0}' defined on '{1}'.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>23513</name>
+                <text>The check constraint '{1}' was violated while performing an INSERT or UPDATE on table '{0}'.</text>
+                <arg>constraintName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 24: Invalid Cursor State</title>
+
+            <msg>
+                <name>24000</name>
+                <text>Invalid cursor state - no current row.</text>
+            </msg>
+
+            <msg>
+                <name>24501.S</name>
+                <text>The identified cursor is not open.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 25: Invalid Transaction State</title>
+
+            <msg>
+                <name>25000</name>
+                <text>Invalid transaction state.</text>
+            </msg>
+
+            <msg>
+                <name>25001</name>
+                <text>Cannot close a connection while a transaction is still active.</text>
+            </msg>
+
+            <msg>
+                <name>25501</name>
+                <text>Unable to set the connection read-only property in an active transaction.</text>
+            </msg>
+
+            <msg>
+                <name>25502</name>
+                <text>An SQL data change is not permitted for a read-only connection, user or database.</text>
+            </msg>
+
+            <msg>
+                <name>25503</name>
+                <text>DDL is not permitted for a read-only connection, user or database.</text>
+            </msg>
+
+            <msg>
+                <name>25505</name>
+                <text>A read-only user or a user in a read-only database is not permitted to disable read-only mode on a connection.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 28: Invalid Authorization Specification</title>
+
+            <msg>
+                <name>28501</name>
+                <text>Invalid database authorization property '{0}={1}'.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>28502.C</name>
+                <text>The user name '{0}' is not valid. </text>
+                <arg>authorizationID</arg>
+            </msg>
+
+            <msg>
+                <name>28503</name>
+                <text>User(s) '{0}' must not be in both read-only and full-access authorization lists.</text>
+                <arg>authorizationID</arg>
+            </msg>
+
+            <msg>
+                <name>28504</name>
+                <text>Repeated user(s) '{1}' in access list '{0}';</text>
+                <arg>authorizationID</arg>
+                <arg>listName</arg>
+            </msg>
+
+            <msg>
+                <name>28505</name>
+                <text>Internal Error: invalid {0} id in statement permission list.</text>
+                <arg>authorizationID</arg>
+            </msg>
+
+            <msg>
+                <name>28506</name>
+                <text>User '{0}' does not have {1} permission on table '{2}'.'{3}'.</text>
+                <arg>authorizationID</arg>
+                <arg>permissionType</arg>
+                <arg>schemaNamet</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>28507</name>
+                <text>User '{0}' does not have {1} permission on table '{2}'.'{3}' for grant.</text>
+                <arg>authorizationID</arg>
+                <arg>permissionType</arg>
+                <arg>schemaNamet</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>28508</name>
+                <text>User '{0}' does not have {1} permission on column '{2}' of table '{3}'.'{4}'.</text>
+                <arg>authorizationID</arg>
+                <arg>permissionType</arg>
+                <arg>columnName</arg>
+                <arg>schemaName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>28509</name>
+                <text>User '{0}' does not have {1} permission on column '{2}' of table '{3}'.'{4}' for grant.</text>
+                <arg>authorizationID</arg>
+                <arg>permissionType</arg>
+                <arg>columnName</arg>
+                <arg>schemaName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>2850A</name>
+                <text>User '{0}' does not have execute permission on {1} '{2}'.'{3}'.</text>
+                <arg>authorizationID</arg>
+                <arg>objectName</arg>
+                <arg>schemaName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>2850B</name>
+                <text>User '{0}' does not have execute permission on {1} '{2}'.'{3}' for grant.</text>
+                <arg>authorizationID</arg>
+                <arg>objectName</arg>
+                <arg>schemaName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>2850C</name>
+                <text>User '{0}' is not the owner of {1} '{2}'.'{3}'.</text>
+                <arg>authorizationID</arg>
+                <arg>objectName</arg>
+                <arg>schemaName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>2850D</name>
+                <text>User '{0}' can not perform the operation in schema '{1}'.</text>
+                <arg>authorizationID</arg>
+                <arg>schemaName</arg>
+            </msg>
+
+            <msg>
+                <name>2850E</name>
+                <text>User '{0}' can not create schema '{1}'. Only database owner could issue this statement.</text>
+                <arg>authorizationID</arg>
+                <arg>schemaName</arg>
+            </msg>
+
+            <msg>
+                <name>2850F</name>
+                <text>Specified grant or revoke operation is not allowed on object '{0}'.</text>
+                <arg>objectName</arg>
+            </msg>
+
+            <msg>
+                <name>2850G</name>
+                <text>User '{0}' does not have {1} permission on object '{2}'.'{3}'.</text>
+                <arg>authorizationID</arg>
+                <arg>permissionName</arg>
+                <arg>schemaName</arg>
+                <arg>objectName</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 2D: Invalid Transaction Termination</title>
+
+            <msg>
+                <name>2D521.S.1</name>
+                <text>setAutoCommit(true) invalid during global transaction.</text>
+            </msg>
+
+            <msg>
+                <name>2D521.S.2</name>
+                <text>COMMIT or ROLLBACK invalid for application execution environment. </text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 38: External Function Exception</title>
+
+            <msg>
+                <name>38000</name>
+                <text>The exception '{0}' was thrown while evaluating an expression.</text>
+                <arg>exception</arg>
+            </msg>
+
+            <msg>
+                <name>38001</name>
+                <text>The external routine is not allowed to execute SQL statements.</text>
+            </msg>
+
+            <msg>
+                <name>38002</name>
+                <text>The routine attempted to modify data, but the routine was not defined as MODIFIES SQL DATA.</text>
+            </msg>
+
+            <msg>
+                <name>38004</name>
+                <text>The routine attempted to read data, but the routine was not defined as READS SQL DATA.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 39: External Routine Invocation Exception</title>
+
+            <msg>
+                <name>39004</name>
+                <text>A NULL value cannot be passed to a method which takes a parameter of primitive type '{0}'.</text>
+                <arg>type</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 3B: Invalid SAVEPOINT</title>
+
+            <msg>
+                <name>3B001.S</name>
+                <text>SAVEPOINT, {0} does not  exist or is not active in the current transaction.</text>
+                <arg>savepointName</arg>
+            </msg>
+
+            <msg>
+                <name>3B002.S</name>
+                <text>The maximum number of savepoints has been reached. </text>
+            </msg>
+
+            <msg>
+                <name>3B501.S</name>
+                <text>A SAVEPOINT with the passed name already exists in the current transaction.</text>
+            </msg>
+
+            <msg>
+                <name>3B502.S</name>
+                <text>A RELEASE or ROLLBACK TO SAVEPOINT was specified, but the savepoint does not exist.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 40: Transaction Rollback</title>
+
+            <msg>
+                <name>40001</name>
+                <text>A lock could not be obtained due to a deadlock, cycle of locks and waiters is:
+{0}. The selected victim is XID : {1}.</text>
+                <arg>lockCycle</arg>
+                <arg>transactionID</arg>
+            </msg>
+
+            <msg>
+                <name>40XC0</name>
+                <text>Dead statement. This may be caused by catching a transaction severity error inside this statement.</text>
+            </msg>
+
+            <msg>
+                <name>40XD0</name>
+                <text>Container has been closed</text>
+            </msg>
+
+            <msg>
+                <name>40XD1</name>
+                <text>Container was opened in read-only mode.   </text>
+            </msg>
+
+            <msg>
+                <name>40XD2</name>
+                <text>Container {0} cannot be opened; it either has been dropped or does not exist.</text>
+                <arg>containerName</arg>
+            </msg>
+
+            <msg>
+                <name>40XL1</name>
+                <text>A lock could not be obtained within the time requested</text>
+            </msg>
+
+            <msg>
+                <name>40XL2</name>
+                <text>A lock could not be obtained within the time requested.  The lockTable dump is: {0}</text>
+                <arg>tableDump</arg>
+            </msg>
+
+            <msg>
+                <name>40XT0</name>
+                <text>An internal error was identified by RawStore module.</text>
+            </msg>
+
+            <msg>
+                <name>40XT1</name>
+                <text>An exception was thrown during transaction commit.</text>
+            </msg>
+
+            <msg>
+                <name>40XT2</name>
+                <text>An exception was thrown during rollback of a SAVEPOINT.</text>
+            </msg>
+
+            <msg>
+                <name>40XT4</name>
+                <text>An attempt was made to close a transaction that was still active. The transaction has been aborted.</text>
+            </msg>
+
+            <msg>
+                <name>40XT5</name>
+                <text>Exception thrown during an internal transaction.</text>
+            </msg>
+
+            <msg>
+                <name>40XT6</name>
+                <text>Database is in quiescent state, cannot activate transaction.  Please wait for a moment till it exits the quiescent state.</text>
+            </msg>
+
+            <msg>
+                <name>40XT7</name>
+                <text>Operation is not supported in an internal transaction.</text>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 42: Syntax Error or Access Rule Violation</title>
+
+            <msg>
+                <name>42000</name>
+                <text>Syntax error or access rule violation; see additional errors for details.</text>
+            </msg>
+
+            <msg>
+                <name>42601</name>
+                <text>In an ALTER TABLE statement, the column '{0}' has been specified as NOT NULL and either the DEFAULT clause was not specified or was specified as DEFAULT NULL.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42601.S.372</name>
+                <text>ALTER TABLE statement cannot add an IDENTITY column to a table.</text>
+            </msg>
+
+            <msg>
+                <name>42605</name>
+                <text>The number of arguments for function '{0}' is incorrect.</text>
+                <arg>functionName</arg>
+            </msg>
+
+            <msg>
+                <name>42606</name>
+                <text>An invalid hexadecimal constant starting with '{0}' has been detected.</text>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>42610</name>
+                <text>All the arguments to the COALESCE/VALUE function cannot be parameters. The function needs at least one argument that is not a parameter.</text>
+            </msg>
+
+            <msg>
+                <name>42611</name>
+                <text>The length, precision, or scale attribute for column, or type mapping '{0}' is not valid. </text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42613</name>
+                <text>Multiple or conflicting keywords involving the '{0}' clause are present.</text>
+                <arg>clause</arg>
+            </msg>
+
+            <msg>
+                <name>42621</name>
+                <text>A check constraint or generated column that is defined with '{0}' is invalid.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42622</name>
+                <text>The name '{0}' is too long. The maximum length is '{1}'.</text>
+                <arg>name</arg>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>42734</name>
+                <text>Name '{0}' specified in context '{1}' is not unique.</text>
+                <arg>name</arg>
+                <arg>context</arg>
+            </msg>
+
+            <msg>
+                <name>42802</name>
+                <text>The number of values assigned is not the same as the number of specified or implied columns.</text>
+            </msg>
+
+            <msg>
+                <name>42803</name>
+                <text>An expression containing the column '{0}' appears in the SELECT list and is not part of a GROUP BY clause.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42815.S.713</name>
+                <text>The replacement value for '{0}' is invalid.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42815.S.171</name>
+                <text>The data type, length or value of arguments '{0}' and '{1}' is incompatible.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42818</name>
+                <text>Comparisons between '{0}' and '{1}' are not supported.</text>
+                <arg>value</arg>
+                <arg>alue1</arg>
+            </msg>
+
+            <msg>
+                <name>42820</name>
+                <text>The floating point literal '{0}' contains more than 30 characters.</text>
+                <arg>string</arg>
+            </msg>
+
+            <msg>
+                <name>42821</name>
+                <text>Columns of type '{0}' cannot hold values of type '{1}'. </text>
+                <arg>type</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42824</name>
+                <text>An operand of LIKE is not a string, or the first operand is not a column.</text>
+            </msg>
+
+            <msg>
+                <name>42831</name>
+                <text>'{0}' cannot be a column of a primary key or unique key because it can contain null values.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42834</name>
+                <text>SET NULL cannot be specified because FOREIGN KEY '{0}'  cannot contain null values.  </text>
+                <arg>key</arg>
+            </msg>
+
+            <msg>
+                <name>42837</name>
+                <text>ALTER TABLE '{0}' specified attributes for column '{1}' that are not compatible with the existing column.</text>
+                <arg>tableName</arg>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42846</name>
+                <text>Cannot convert types '{0}' to '{1}'.</text>
+                <arg>type</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42877</name>
+                <text>A qualified column name '{0}' is not allowed in the ORDER BY clause.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42884</name>
+                <text>No authorized routine named '{0}' of type '{1}' having compatible arguments was found.</text>
+                <arg>routineName</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42886</name>
+                <text>'{0}' parameter '{1}' requires a parameter marker '?'.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42894</name>
+                <text>DEFAULT value or IDENTITY attribute value is not valid for column '{0}'.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>428C1</name>
+                <text>Only one identity column is allowed in a table.</text>
+            </msg>
+
+            <msg>
+                <name>428EK</name>
+                <text>The qualifier for a declared global temporary table name must be SESSION.</text>
+            </msg>
+
+            <msg>
+                <name>42903</name>
+                <text>Invalid use of an aggregate function.</text>
+            </msg>
+
+            <msg>
+                <name>42908</name>
+                <text>The CREATE VIEW statement does not include a column list.</text>
+            </msg>
+
+            <msg>
+                <name>42915</name>
+                <text>Foreign  Key '{0}' is invalid because '{1}'. </text>
+                <arg>key</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42916</name>
+                <text>Synonym '{0}' cannot be created for '{1}' as it would result in a circular synonym chain.</text>
+                <arg>synonym2</arg>
+                <arg>synonym1</arg>
+            </msg>
+
+            <msg>
+                <name>42939</name>
+                <text>An object cannot be created with the schema name '{0}'.</text>
+                <arg>schemaNamet</arg>
+            </msg>
+
+            <msg>
+                <name>42962</name>
+                <text>Long column type column or parameter '{0}' not permitted in declared global temporary tables or procedure definitions. </text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42972</name>
+                <text>An ON clause associated with a JOIN operator is not valid.</text>
+            </msg>
+
+            <msg>
+                <name>42995</name>
+                <text>The requested function does not apply to global temporary tables.</text>
+            </msg>
+
+            <msg>
+                <name>42X01</name>
+                <text>Syntax error: {0}.</text>
+                <arg>error</arg>
+            </msg>
+
+            <msg>
+                <name>42X02</name>
+                <text>{0}.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X03</name>
+                <text>Column name '{0}' is in more than one table in the FROM list.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X04</name>
+                <text>Column '{0}' is either not in any table in the FROM list or appears within a join specification and is outside the scope of the join specification or appears in a HAVING clause and is not in the GROUP BY list. If this is a CREATE or ALTER TABLE  statement then '{0}' is not a column in the target table.</text>
+                <arg>columnName</arg>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X05</name>
+                <text>Table/View '{0}' does not exist.</text>
+                <arg>objectName</arg>
+            </msg>
+
+            <msg>
+                <name>42X06</name>
+                <text>Too many result columns specified for table '{0}'.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X07</name>
+                <text>Null is only allowed in a VALUES clause within an INSERT statement.</text>
+            </msg>
+
+            <msg>
+                <name>42X08</name>
+                <text>The constructor for class '{0}' cannot be used as an external virtual table because the class does not implement '{1}'. </text>
+                <arg>className</arg>
+                <arg>constructorName</arg>
+            </msg>
+
+            <msg>
+                <name>42X09</name>
+                <text>The table or alias name '{0}' is used more than once in the FROM list.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X10</name>
+                <text>'{0}' is not an exposed table name in the scope in which it appears.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X12</name>
+                <text>Column name '{0}' appears more than once in the CREATE TABLE statement.  </text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X13</name>
+                <text>Column name '{0}' appears more than once times in the column list of an INSERT statement. </text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X14</name>
+                <text>'{0}' is not a column in table or VTI '{1}'.</text>
+                <arg>columnName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X15</name>
+                <text>Column name '{0}' appears in a statement without a FROM list.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X16</name>
+                <text>Column name '{0}' appears multiple times in the SET clause of an UPDATE statement.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X17</name>
+                <text>In the Properties list of a FROM clause, the value '{0}' is not valid as a joinOrder specification. Only the values FIXED and UNFIXED are valid.  </text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X19</name>
+                <text>The WHERE or HAVING clause or CHECK CONSTRAINT definition is a '{0}' expression.  It must be a BOOLEAN expression.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X23</name>
+                <text>Cursor {0} is not updatable.</text>
+                <arg>cursorName</arg>
+            </msg>
+
+            <msg>
+                <name>42X25</name>
+                <text>The '{0}' function is not allowed on the '{1}' type.</text>
+                <arg>functionName</arg>
+                <arg>1</arg>
+            </msg>
+
+            <msg>
+                <name>42X26</name>
+                <text>The class '{0}' for column '{1}' does not exist or is inaccessible. This can happen if the class is not public.</text>
+                <arg>className</arg>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X28</name>
+                <text>Delete table '{0}' is not target of cursor '{1}'.</text>
+                <arg>tableName</arg>
+                <arg>cursorName</arg>
+            </msg>
+
+            <msg>
+                <name>42X29</name>
+                <text>Update table '{0}' is not the target of cursor '{1}'.</text>
+                <arg>tableName</arg>
+                <arg>cursorName</arg>
+            </msg>
+
+            <msg>
+                <name>42X30</name>
+                <text>Cursor '{0}' not found. Verify that autocommit is OFF.</text>
+                <arg>cursorName</arg>
+            </msg>
+
+            <msg>
+                <name>42X31</name>
+                <text>Column '{0}' is not in the FOR UPDATE list of cursor '{1}'.</text>
+                <arg>columnName</arg>
+                <arg>cursorName</arg>
+            </msg>
+
+            <msg>
+                <name>42X32</name>
+                <text>The number of columns in the derived column list must match the number of columns in table '{0}'.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X33</name>
+                <text>The derived column list contains a duplicate column name '{0}'.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X34</name>
+                <text>There is a ? parameter in the select list.  This is not allowed.</text>
+            </msg>
+
+            <msg>
+                <name>42X35</name>
+                <text>It is not allowed for both operands of '{0}' to be ? parameters.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X36</name>
+                <text>The '{0}' operator is not allowed to take a ? parameter as an operand.</text>
+                <arg>operator</arg>
+            </msg>
+
+            <msg>
+                <name>42X37</name>
+                <text>The unary '{0}' operator is not allowed on the '{1}' type.</text>
+                <arg>operator</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42X38</name>
+                <text>'SELECT *' only allowed in EXISTS and NOT EXISTS subqueries.</text>
+            </msg>
+
+            <msg>
+                <name>42X39</name>
+                <text>Subquery is only allowed to return a single column.</text>
+            </msg>
+
+            <msg>
+                <name>42X40</name>
+                <text>A NOT statement has an operand that is not boolean . The operand of NOT must evaluate to TRUE, FALSE, or UNKNOWN. </text>
+            </msg>
+
+            <msg>
+                <name>42X41</name>
+                <text>In the Properties clause of a FROM list, the property '{0}' is not valid (the property was being set to '{1}'). </text>
+                <arg>propertyName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X42</name>
+                <text>Correlation name not allowed for column '{0}' because it is part of the FOR UPDATE list.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X43</name>
+                <text>The ResultSetMetaData returned for the class/object '{0}' was null. In order to use this class as an external virtual table, the ResultSetMetaData cannot be null. </text>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42X44</name>
+                <text>Invalid length '{0}' in column specification.</text>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>42X45</name>
+                <text>{0} is an invalid type for argument number {1} of {2}.</text>
+                <arg>type</arg>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X46</name>
+                <text>There are multiple functions named '{0}'. Use a the full signature or the specific name.</text>
+                <arg>functionName</arg>
+            </msg>
+
+            <msg>
+                <name>42X47</name>
+                <text>There are multiple procedures named '{0}'. Use a the full signature or the specific name.</text>
+                <arg>procedureName</arg>
+            </msg>
+
+            <msg>
+                <name>42X48</name>
+                <text>Value '{1}' is not a valid precision for {0}.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X49</name>
+                <text>Value '{0}' is not a valid integer literal.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X50</name>
+                <text>No method was found that matched the method call {0}.{1}({2}), tried all combinations of object and primitive types and any possible type conversion for any  parameters the method call may have. The method might exist but it is not public and/or static, or the parameter types are not method invocation convertible.</text>
+                <arg>methodName</arg>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X51</name>
+                <text>The class '{0}' does not exist or is inaccessible. This can happen if the class is not public.</text>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42X52</name>
+                <text>Calling  method ('{0}') using a receiver of the Java primitive type '{1}" is not allowed.</text>
+                <arg>methodName</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42X53</name>
+                <text>The LIKE predicate can only have 'CHAR' or 'VARCHAR' operands. Type '{0}' is not permitted.</text>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42X54</name>
+                <text>The Java method '{0}' has a ? as a receiver.  This is not allowed.</text>
+                <arg>methodName</arg>
+            </msg>
+
+            <msg>
+                <name>42X55</name>
+                <text>Table name '{1}' should be the same as '{0}'.</text>
+                <arg>tableName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X56</name>
+                <text>The number of columns in the view column list does not match the number of columns in the underlying query expression in the view definition for '{0}'.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X57</name>
+                <text>The getColumnCount() for external virtual table '{0}' returned an invalid value '{1}'.  Valid values are greater than or equal to 1. </text>
+                <arg>tableName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X58</name>
+                <text>The number of columns on the left and right sides of the {0} must be the same.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X59</name>
+                <text>The number of columns in each VALUES constructor must be the same.</text>
+            </msg>
+
+            <msg>
+                <name>42X60</name>
+                <text>Invalid value '{0}' for insertMode property specified for table '{1}'.</text>
+                <arg>value</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X61</name>
+                <text>Types '{0}' and '{1}' are not {2} compatible.</text>
+                <arg>type</arg>
+                <arg>type</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X62</name>
+                <text>'{0}' is not allowed in the '{1}' schema.</text>
+                <arg>value</arg>
+                <arg>schemaNamet</arg>
+            </msg>
+
+            <msg>
+                <name>42X63</name>
+                <text>The USING clause did not return any results. No parameters can be set. </text>
+            </msg>
+
+            <msg>
+                <name>42X64</name>
+                <text>In the Properties list, the invalid value '{0}' was specified for the useStatistics property. The only valid values are TRUE or FALSE. </text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X65</name>
+                <text>Index '{0}' does not exist.</text>
+                <arg>index</arg>
+            </msg>
+
+            <msg>
+                <name>42X66</name>
+                <text>Column name '{0}' appears more than once in the CREATE INDEX statement.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X68</name>
+                <text>No field '{0}' was found belonging to class '{1}'.  It may be that the field exists, but it is not public, or that the class does not exist or is not public.</text>
+                <arg>fieldName</arg>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42X69</name>
+                <text>It is not allowed to reference a field ('{0}') using a referencing expresssion of the Java primitive type '{1}'.</text>
+                <arg>fieldName</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42X72</name>
+                <text>No static field '{0}' was found belonging to class '{1}'.  The field might exist, but it is not public and/or static, or the class does not exist or the class is not public.  </text>
+                <arg>fieldName</arg>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42X73</name>
+                <text>Method resolution for signature {0}.{1}({2}) was ambiguous. (No single maximally specific method.)</text>
+                <arg>value</arg>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X74</name>
+                <text>Invalid CALL statement syntax.</text>
+            </msg>
+
+            <msg>
+                <name>42X75</name>
+                <text>No constructor was found with the signature {0}({1}).  It may be that the parameter types are not method invocation convertible.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X76</name>
+                <text>At least one column, '{0}', in the primary key being added is nullable. All columns in a primary key must be non-nullable.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X77</name>
+                <text>Column position '{0}' is out of range for the query expression.</text>
+                <arg>columnPosition</arg>
+            </msg>
+
+            <msg>
+                <name>42X78</name>
+                <text>Column '{0}' is not in the result of the query expression.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X79</name>
+                <text>Column name '{0}' appears more than once in the result of the query expression.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X80</name>
+                <text>VALUES clause must contain at least one element. Empty elements are not allowed. </text>
+            </msg>
+
+            <msg>
+                <name>42X82</name>
+                <text>The USING clause returned more than one row. Only single-row ResultSets are permissible.</text>
+            </msg>
+
+            <msg>
+                <name>42X83</name>
+                <text>The constraints on column '{0}' require that it be both nullable and not nullable.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X84</name>
+                <text>Index '{0}' was created to enforce constraint '{1}'.  It can only be dropped by dropping the constraint.</text>
+                <arg>index</arg>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42X85</name>
+                <text>Constraint '{0}'is required to be in the same schema as table '{1}'.</text>
+                <arg>constraintName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X86</name>
+                <text>ALTER TABLE failed. There is no constraint '{0}' on table '{1}'. </text>
+                <arg>constraintName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X87</name>
+                <text>At least one result expression (THEN or ELSE) of the '{0}' expression must not be a '?'. </text>
+                <arg>expression</arg>
+            </msg>
+
+            <msg>
+                <name>42X88</name>
+                <text>A conditional has a non-Boolean operand. The operand of a conditional must evaluate to TRUE, FALSE, or UNKNOWN.  </text>
+            </msg>
+
+            <msg>
+                <name>42X89</name>
+                <text>Types '{0}' and '{1}' are not type compatible. Neither type is assignable to the other type.  </text>
+                <arg>type</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42X90</name>
+                <text>More than one primary key constraint specified for table '{0}'.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42X91</name>
+                <text>Constraint name '{0}' appears more than once in the CREATE TABLE statement. </text>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42X92</name>
+                <text>Column name '{0}' appears more than once in a constraint's column list.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X93</name>
+                <text>Table '{0}' contains a constraint definition with column '{1}' which is not in the table.</text>
+                <arg>tableName</arg>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42X94</name>
+                <text>{0} '{1}' does not exist.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42X96</name>
+                <text>The database class path contains an unknown jar file '{0}'.</text>
+                <arg>fileName</arg>
+            </msg>
+
+            <msg>
+                <name>42X98</name>
+                <text>Parameters are not allowed in a VIEW definition.</text>
+            </msg>
+
+            <msg>
+                <name>42Y00</name>
+                <text>Class '{0}' does not implement org.apache.derby.iapi.db.AggregateDefinition and thus cannot be used as an aggregate expression.</text>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42Y01</name>
+                <text>Constraint '{0}' is invalid.</text>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y03</name>
+                <text>'{0}' is not recognized as a function or procedure.</text>
+                <arg>statement</arg>
+            </msg>
+
+            <msg>
+                <name>42Y04</name>
+                <text>Cannot create a procedure or function with EXTERNAL NAME '{0}' because it is not a list separated by periods. The expected format is &lt;full java path&gt;.&lt;method name&gt;.</text>
+                <arg>name</arg>
+            </msg>
+
+            <msg>
+                <name>42Y05</name>
+                <text>There is no Foreign Key named '{0}'.</text>
+                <arg>key</arg>
+            </msg>
+
+            <msg>
+                <name>42Y07</name>
+                <text>Schema '{0}' does not exist</text>
+                <arg>schemaNamet</arg>
+            </msg>
+
+            <msg>
+                <name>42Y08</name>
+                <text>Foreign key constraints are not allowed on system tables.</text>
+            </msg>
+
+            <msg>
+                <name>42Y09</name>
+                <text>Void methods are only allowed within a CALL statement.</text>
+            </msg>
+
+            <msg>
+                <name>42Y10</name>
+                <text>A table constructor that is not in an INSERT statement has all ? parameters in one of its columns.  For each column, at least one of the rows must have a non-parameter.</text>
+            </msg>
+
+            <msg>
+                <name>42Y11</name>
+                <text>A join specification is required with the '{0}' clause.</text>
+                <arg>clauseName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y12</name>
+                <text>The ON clause of a JOIN is a '{0}' expression.  It must be a BOOLEAN expression.</text>
+                <arg>expressionType</arg>
+            </msg>
+
+            <msg>
+                <name>42Y13</name>
+                <text>Column name '{0}' appears more than once in the CREATE VIEW statement.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y16</name>
+                <text>No public static method '{0}' was found in class '{1}'. The method might exist, but it is not public, or it is not static. </text>
+                <arg>methodName</arg>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42Y22</name>
+                <text>Aggregate {0} cannot operate on type {1}.</text>
+                <arg>aggregateType</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42Y23</name>
+                <text>Incorrect JDBC type info returned for column {0}.</text>
+                <arg>colunmName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y24</name>
+                <text>View '{0}' is not updatable. (Views are currently not updatable.) </text>
+                <arg>viewName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y25</name>
+                <text>'{0}' is a system table.  Users are not allowed to modify the contents of this table.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y26</name>
+                <text>Aggregates are not allowed in the GROUP BY list.</text>
+            </msg>
+
+            <msg>
+                <name>42Y27</name>
+                <text>Parameters are not allowed in the trigger action.</text>
+            </msg>
+
+            <msg>
+                <name>42Y29</name>
+                <text>The SELECT list of a non-grouped query contains at least one invalid expression. When the SELECT list contains at least one aggregate then all entries must be valid aggregate expressions.</text>
+            </msg>
+
+            <msg>
+                <name>42Y30</name>
+                <text>The SELECT list of a grouped query contains at least one invalid expression. If a SELECT list has a GROUP BY, the list may only contain valid grouping expressions and valid aggregate expressions.  </text>
+            </msg>
+
+            <msg>
+                <name>42Y32</name>
+                <text>Aggregator class '{0}' for aggregate '{1}' on type {2} does not implement com.ibm.db2j.aggregates.Aggregator. </text>
+                <arg>className</arg>
+                <arg>aggregateName</arg>
+                <arg>type</arg>
+            </msg>
+
+            <msg>
+                <name>42Y33</name>
+                <text>Aggregate {0} contains one or more aggregates.</text>
+                <arg>aggregateName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y34</name>
+                <text>Column name '{0}' matches more than one result column in table '{1}'.</text>
+                <arg>columnName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y35</name>
+                <text>Column reference '{0}' is invalid. When the SELECT list contains at least one aggregate then all entries must be valid aggregate expressions.  </text>
+                <arg>reference</arg>
+            </msg>
+
+            <msg>
+                <name>42Y36</name>
+                <text>Column reference '{0}' is invalid.  For a SELECT list with a GROUP BY, the list may only contain valid grouping expressions and valid aggregate expressions.  </text>
+                <arg>reference</arg>
+            </msg>
+
+            <msg>
+                <name>42Y37</name>
+                <text>'{0}' is a Java primitive and cannot be used with this operator.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y38</name>
+                <text>insertMode = replace is not permitted on an insert where the target table, '{0}', is referenced in the SELECT.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y39</name>
+                <text>'{0}' may not appear in a CHECK CONSTRAINT definition because it may return non-deterministic results.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y40</name>
+                <text>'{0}' appears multiple times in the UPDATE OF column list for trigger '{1}'.</text>
+                <arg>value</arg>
+                <arg>triggerName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y41</name>
+                <text>'{0}' cannot be directly invoked via EXECUTE STATEMENT because it is part of a trigger.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y42</name>
+                <text>Scale '{1}' is not a valid scale for a {0}.</text>
+                <arg>scaleValue</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y43</name>
+                <text>Scale '{0}' is not a valid scale with precision of '{1}'.</text>
+                <arg>scaleValue</arg>
+                <arg>precision</arg>
+            </msg>
+
+            <msg>
+                <name>42Y44</name>
+                <text>Invalid key '{0}' specified in the Properties list of a FROM list. The case-sensitive keys that are currently supported are '{1}'. </text>
+                <arg>key</arg>
+                <arg>key</arg>
+            </msg>
+
+            <msg>
+                <name>42Y45</name>
+                <text>VTI '{0}' cannot be bound because it is a special trigger VTI and this statement is not part of a trigger action or WHEN clause.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y46</name>
+                <text>Invalid Properties list in FROM list.  There is no index '{0}' on table '{1}'.</text>
+                <arg>index</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y48</name>
+                <text>Invalid Properties list in FROM list.  Either there is no named constraint '{0}' on table '{1}' or the constraint does not have a backing index.</text>
+                <arg>constraintName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y49</name>
+                <text>Multiple values specified for property key '{0}'. </text>
+                <arg>key</arg>
+            </msg>
+
+            <msg>
+                <name>42Y50</name>
+                <text>Properties list for table '{0}' may contain values for index or for constraint but not both.</text>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y55</name>
+                <text>'{0}' cannot be performed on '{1}' because it does not exist.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y56</name>
+                <text>Invalid join strategy '{0}' specified in Properties list on table '{1}'. The currently supported values for a join strategy are: 'hash' and 'nestedloop'.</text>
+                <arg>strategyValue</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y58</name>
+                <text>NumberFormatException occurred when converting value '{0}' for optimizer override '{1}'.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y59</name>
+                <text>Invalid value, '{0}', specified for hashInitialCapacity override. Value must be greater than 0.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y60</name>
+                <text>Invalid value, '{0}', specified for hashLoadFactor override. Value must be greater than 0.0 and less than or equal to 1.0.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y61</name>
+                <text>Invalid value, '{0}', specified for hashMaxCapacity override. Value must be greater than 0.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y62</name>
+                <text>'{0}' is not allowed on '{1}' because it is a view.</text>
+                <arg>statement</arg>
+                <arg>viewName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y63</name>
+                <text>Hash join requires an optimizable equijoin predicate on a column in the selected index or heap.  An optimizable equijoin predicate does not exist on any column in table or index '{0}'. Use the 'index' optimizer override to specify such an index or the heap on table '{1}'.</text>
+                <arg>index</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y64</name>
+                <text>bulkFetch value of '{0}' is invalid. The minimum value for bulkFetch is 1.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y65</name>
+                <text>bulkFetch is not permitted on '{0}' joins.</text>
+                <arg>joinType</arg>
+            </msg>
+
+            <msg>
+                <name>42Y66</name>
+                <text>bulkFetch is not permitted on updatable cursors. </text>
+            </msg>
+
+            <msg>
+                <name>42Y67</name>
+                <text>Schema '{0}' cannot be dropped.</text>
+                <arg>schemaNamet</arg>
+            </msg>
+
+            <msg>
+                <name>42Y69</name>
+                <text>No valid execution plan was found for this statement. This may have one of two causes: either you specified a hash join strategy when hash join is not allowed (no optimizable equijoin) or you are attempting to join two external virtual tables, each of which references the other, and so the statement cannot be evaluated.  </text>
+            </msg>
+
+            <msg>
+                <name>42Y70</name>
+                <text>The user specified an illegal join order. This could be caused by a join column from an inner table being passed as a parameter to an external virtual table.</text>
+            </msg>
+
+            <msg>
+                <name>42Y71</name>
+                <text>System function or procedure '{0}' cannot be dropped.</text>
+                <arg>procedureName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y82</name>
+                <text>System generated stored prepared statement '{0}' that cannot be dropped using DROP STATEMENT. It is part of a trigger. </text>
+                <arg>statement</arg>
+            </msg>
+
+            <msg>
+                <name>42Y83</name>
+                <text>An untyped null is not permitted as an argument to aggregate {0}.  Please cast the null to a suitable type.</text>
+                <arg>aggregateName</arg>
+            </msg>
+
+            <msg>
+                <name>42Y84</name>
+                <text>'{0}' may not appear in a DEFAULT definition.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y85</name>
+                <text>The DEFAULT keyword is only allowed in a VALUES clause when the VALUES clause appears within an INSERT statement.</text>
+            </msg>
+
+            <msg>
+                <name>42Y90</name>
+                <text>FOR UPDATE is not permitted in this type of statement.  </text>
+            </msg>
+
+            <msg>
+                <name>42Y91</name>
+                <text>The USING clause is not permitted in an EXECUTE STATEMENT for a trigger action.</text>
+            </msg>
+
+            <msg>
+                <name>42Y92</name>
+                <text>{0} triggers may only reference {1} transition variables/tables.</text>
+                <arg>triggerName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Y93</name>
+                <text>Illegal REFERENCING clause: only one name is permitted for each type of transition variable/table.</text>
+            </msg>
+
+            <msg>
+                <name>42Y94</name>
+                <text>An AND or OR has a non-boolean operand. The operands of AND and OR must evaluate to TRUE, FALSE, or UNKNOWN.  </text>
+            </msg>
+
+            <msg>
+                <name>42Y95</name>
+                <text>The '{0}' operator with a left operand type of '{1}' and a right operand type of '{2}' is not supported.</text>
+                <arg>operatorName</arg>
+                <arg>operandType</arg>
+                <arg>operandType</arg>
+            </msg>
+
+            <msg>
+                <name>42Y97</name>
+                <text>Invalid escape character at line '{0}', column '{1}'.</text>
+                <arg>lineNumber</arg>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z02</name>
+                <text>Multiple DISTINCT aggregates are not supported at this time.</text>
+            </msg>
+
+            <msg>
+                <name>42Z07</name>
+                <text>Aggregates are not permitted in the ON clause.</text>
+            </msg>
+
+            <msg>
+                <name>42Z08</name>
+                <text>Bulk insert replace is not permitted on '{0}' because it has an enabled trigger ({1}).</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z15</name>
+                <text>Invalid type specified for column '{0}'. The type of a column may not be changed.  </text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z16</name>
+                <text>Only columns of type VARCHAR may have their length altered. </text>
+            </msg>
+
+            <msg>
+                <name>42Z17</name>
+                <text>Invalid length specified for column '{0}'. Length must be greater than the current column length.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z18</name>
+                <text>Column '{0}' is part of a foreign key constraint '{1}'. To alter the length of this column, you should drop the constraint first, perform the ALTER TABLE, and then recreate the constraint.</text>
+                <arg>columnName</arg>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z19</name>
+                <text>Column '{0}' is being referenced by at least one foreign key constraint '{1}'. To alter the length of this column, you should drop referencing constraints, perform the ALTER TABLE and then recreate the constraints. </text>
+                <arg>columnName</arg>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z20</name>
+                <text>Column '{0}' cannot be made nullable. It is part of a primary key or unique constraint, which cannot have any nullable columns.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z21</name>
+                <text>Invalid increment specified for identity for column '{0}'. Increment cannot be zero.  </text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z22</name>
+                <text>Invalid type specified for identity column '{0}'. The only valid types for identity columns are BIGINT, INT and SMALLINT.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z23</name>
+                <text>Attempt to modify an identity column '{0}'. </text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z24</name>
+                <text>Overflow occurred in identity value for column '{1}' in table '{0}'.</text>
+                <arg>columnName</arg>
+                <arg>tableName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z25</name>
+                <text>INTERNAL ERROR identity counter. Update was called without arguments with current value \= NULL.</text>
+            </msg>
+
+            <msg>
+                <name>42Z26</name>
+                <text>A column, '{0}', with an identity default cannot be made nullable.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z27</name>
+                <text>A nullable column, '{0}', cannot be modified to have identity default.</text>
+                <arg>columnName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z50</name>
+                <text>INTERNAL ERROR: Unable to generate code for {0}.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z53</name>
+                <text>INTERNAL ERROR: Type of activation to generate for node choice {0} is unknown.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z60</name>
+                <text>{0} not allowed unless database property {1} has value '{2}'.</text>
+                <arg>value</arg>
+                <arg>propertyName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z70</name>
+                <text>Binding directly to an XML value is not allowed; try using XMLPARSE.</text>
+            </msg>
+
+            <msg>
+                <name>42Z71</name>
+                <text>XML values are not allowed in top-level result sets; try using XMLSERIALIZE.</text>
+            </msg>
+
+            <msg>
+                <name>42Z72</name>
+                <text>Missing SQL/XML keyword(s) '{0}' at line {1}, column {2}.</text>
+                <arg>keywords</arg>
+                <arg>lineNumber</arg>
+                <arg>columnNumber</arg>
+            </msg>
+
+            <msg>
+                <name>42Z73</name>
+                <text>Invalid target type for XMLSERIALIZE: '{0}'.</text>
+                <arg>typeName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z74</name>
+                <text>XML feature not supported: '{0}'.</text>
+                <arg>featureName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z75</name>
+                <text>XML query expression must be a string literal.</text>
+            </msg>
+
+            <msg>
+                <name>42Z76</name>
+                <text>Multiple XML context items are not allowed.</text>
+            </msg>
+
+            <msg>
+                <name>42Z77</name>
+                <text>Context item must have type 'XML'; '{0}' is not allowed.</text>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z79</name>
+                <text>Unable to determine the parameter type for XMLPARSE; try using a CAST.</text>
+            </msg>
+
+            <msg>
+                <name>42Z90</name>
+                <text>Class '{0}' does not return an updatable ResultSet.</text>
+                <arg>className</arg>
+            </msg>
+
+            <msg>
+                <name>42Z91</name>
+                <text>subquery</text>
+            </msg>
+
+            <msg>
+                <name>42Z92</name>
+                <text>repeatable read</text>
+            </msg>
+
+            <msg>
+                <name>42Z93</name>
+                <text>Constraints '{0}' and '{1}' have the same set of columns, which is not allowed. </text>
+                <arg>constraintName</arg>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z97</name>
+                <text>Renaming column '{0}' will cause check constraint '{1}' to break.</text>
+                <arg>columnName</arg>
+                <arg>constraintName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z99</name>
+                <text>String or Hex literal cannot exceed 64K.</text>
+            </msg>
+
+            <msg>
+                <name>42Z9A</name>
+                <text>read uncommitted</text>
+            </msg>
+
+            <msg>
+                <name>42Z9B</name>
+                <text>The external virtual table interface does not support BLOB or CLOB columns. '{0}' column '{1}'. </text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z9D.S.1</name>
+                <text>Procedures that modify SQL data are not allowed in BEFORE triggers.</text>
+            </msg>
+
+            <msg>
+                <name>42Z9D</name>
+                <text>'{0}' statements are not allowed in '{1}' triggers.</text>
+                <arg>statement</arg>
+                <arg>triggerName</arg>
+            </msg>
+
+            <msg>
+                <name>42Z9E</name>
+                <text>Constraint '{0}' is not a {1} constraint.</text>
+                <arg>constraintName</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>42Z9F</name>
+                <text>Too many indexes ({0}) on the table {1}. The limit is {2}.  </text>
+                <arg>index</arg>
+                <arg>tableName</arg>
+                <arg>number</arg>
+            </msg>
+
+            <msg>
+                <name>42ZA0</name>
+                <text>Statement too complex. Try rewriting the query to remove complexity. Eliminating many duplicate expressions or breaking up the query and storing interim results in a temporary table can often help resolve this error.</text>
+            </msg>
+
+            <msg>
+                <name>42ZA1</name>
+                <text>Invalid SQL in Batch: '{0}'.</text>
+                <arg>batch</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 57: DRDA Network Protocol: Execution Failure</title>
+
+            <msg>
+                <name>57017.C</name>
+                <text>There is no available conversion for the source code page, {0}, to the target code page, {1}.  The connection has been terminated.</text>
+                <arg>codePage</arg>
+                <arg>codePage</arg>
+            </msg>
+
+        </family>
+
+
+        <family>
+            <title>Class 58: DRDA Network Protocol: Protocol Error</title>
+
+            <msg>
+                <name>58009.C.10</name>
+                <text>Network protocol exception: only one of the VCM, VCS length can be greater than 0.  The connection has been terminated.</text>
+            </msg>
+
+            <msg>
+                <name>58009.C.11</name>
+                <text>The connection was terminated because the encoding is not supported.</text>
+            </msg>
+
+            <msg>
+                <name>58009.C.12</name>
+                <text>Network protocol exception: actual code point, {0}, does not match expected code point, {1}.  The connection has been terminated.</text>
+                <arg>value</arg>
+                <arg>value</arg>
+            </msg>
+
+            <msg>
+                <name>58009.C.13</name>
+                <text>Network protocol exception: DDM collection contains less than 4 bytes of data.  The connection has been terminated.</text>
+            </msg>
+
+            <msg>
+                <name>58009.C.14</name>

[... 4821 lines stripped ...]


Mime
View raw message