-79759 Invalid port number.
The port number must be a valid four-digit number, as follows:
端口号必须是有效的四位数字，如下所示：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2252 -
jdbc:gbasedbt-sqli://mymachine:1234/mydatabase:user=me:password=secret
In this example, 1234 is the port number.
在本例中，1234 是端口号。
-79760 Invalid database name.
This statement contains the name of a database in some invalid format.
此语句以某种无效格式包含数据库名称。
The maximum length for database names and cursor names depends on the
version of the database server.
extension.
数据库名称和游标名称的最大长度取决于数据库服务器的版本。
-79761 Invalid Property format.
The database URL accepts property values in key=value pairs. For example,
user=gbasedbt:password=gbasedbt adds the key=value pairs to the list of
properties that are passed to the connection object.
数据库 URL 接受键=值对中的属性值。例如，user=gbasedbt：password=gbasedbt 将
键=值对添加到传递给连接对象的属性列表中。
Check the syntax of the key=value pair for syntax errors. Make sure
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2253 -
there is only one = sign; that no spaces separate the key, value,
or =; and that key=value pairs are separated by one colon (:), again
with no spaces.
检查键=值对的语法是否有语法错误。确保只有一个 = 符号；没有空格来分隔键、值
或 =；键=值对由一个冒号(：)分隔，同样没有空格。
-79763 Only CONCUR_READ_ONLY is supported.
GBase 8s JDBC Driver supports only the ResultSet.CONCUR_READ_ONLY method.
GBase 8s JDBC 驱动程序只支持 ResultSet.CONCUR_READ_ONLY 方法。
You can only call the Connection.createStatement(int, int),
Connection.prepareStatement(String, int, int), or
Connection.CallableStatement(String, int, int) method with a result
set concurrency value of CONCUR_READ_ONLY.
只能调用 Connection.createStatement(int, int)、
Connection.prepareStatement(String, int, int), 或
Connection.CallableStatement(String, int, int)方法，其结果集并发值为
CONCUR_READ_ONLY。
-79764 Invalid Fetch Direction value.
An invalid fetch direction was passed as an argument to the
Statement.setFetchDirection() or ResultSet.setFetchDirection() method.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2254 -
将一个无效的提取方向作为参数传递给 Statement.setFetchDirection() 或
ResultSet.setFetchDirection() 方法。
Verify that the argument is one of the valid fetch direction values,
which are FETCH_FORWARD, FETCH_REVERSE, and FETCH_UNKNOWN.
验证该参数是有效的 FETCH 方向值之一，这些值是 FETCH_FORWARD、FETCH_REVERSE
和 FETCH_UNKNOWN。
-79765 ResultSet Type is TYPE_FETCH_FORWARD, direction can only be
FETCH_FORWARD.
The result set type has been set to TYPE_FORWARD_ONLY, but the
setFetchDirection() method has been called with a value other than
FETCH_FORWARD.
结果集类型已设置为 TYPE_FORWARD_ONLY，但 setFetchDirection() 方法的值不是
FETCH_FORWARD。
Verify that the direction specified is consistent with the result type
specified.
验证指定的方向是否与指定的结果类型一致。
-79766 Incorrect Fetch Size value.
The Statement.setFetchSize() method has been called with an invalid
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2255 -
value.
使用无效值调用 Statement.setFetchSize() 方法。
Verify that the value passed in is greater than 0. If the setMaxRows
method has been called, the fetch size must not exceed that value.
验证传入的值大于 0。如果调用了 setMaxRows 方法，则获取大小不能超过该值。
-79767 ResultSet Type is TYPE_FORWARD_ONLY.
A method such as ResultSet.beforeFirst(), ResultSet.afterLast(),
ResultSet.first(), ResultSet.last(), ResultSet.absolute(),
ResultSet.relative(), ResultSet.current(), or ResultSet.previous()
has been called, but the result set type is TYPE_FORWARD_ONLY.
已经调用了一个方法，如 ResultSet.beforeFirst()、ResultSet.afterLast()、
ResultSet.first()、ResultSet.last()、ResultSet.absolute()、
ResultSet.relative()、ResultSet.current() 或 ResultSet.previous()，但结果集
类型是 TYPE_FORWARD_ONLY。
Call only the ResultSet.next() method if the result set type is
TYPE_FORWARD_ONLY.
如果结果集类型为 TYPE_FORWARD_ONLY，则只调用 ResultSet.next() 方法。
-79768 Incorrect row value.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2256 -
The ResultSet.absolute(int) method has been called with a value of 0.
The parameter must be greater than 0.
ResultSet.absolute(int) 方法被 0 值所调用。参数必须大于0。
-79769 A customized type map is required for this data type.
No customized type map exists for an opaque type.
不透明类型不存在自定义类型映射。
You must register a customized type map to use any opaque types.
必须注册自定义类型映射才能使用任何不透明类型。
-79770 Cannot find the SQLTypeName specified in the SQLData or Struct.
The SQLTypename object you specified in the SQLData or Struct class
does not exist in the database.
在SQLData或Struct类中指定的SQLTypename对象在数据库中不存在。
Make sure that the type name is valid.
请确保类型名称有效。
-79771 Input value is not valid.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2257 -
The input value is not accepted for this data type.
此数据类型不接受输入值。
Make sure this input is valid for this data type.
请确保此输入对此数据类型有效。
-79772 No more data to read. Verify your SQLdata class or
getSQLTypeName().
You have asked for more data than is available.
您要求的数据比可用的要多。
Check your SQLData class to make sure it matches what is in the
database schema. The SQLTypeName object might also be incorrect.
检查 SQLData 类，确保它与数据库模式中的内容匹配。SQLTypeName 对象也可能不正
确。
-79773 Invalid arguments.
The GBase 8s JDBC Driver throws this exception whenever a method is called
with an invalid argument. Refer to the JDBC API documentation to ensure that a
valid argument is being passed to the method that is throwing this exception.
每当调用带有无效参数的方法时，GBase 8s JDBC 驱动程序都会抛出此异常。请参阅
JDBC API 文档，以确保向抛出此异常的方法传递有效的参数。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2258 -
-79774 Unable to create local file.
Large object data read from the database server can be stored either in
memory or in a local file. If the LOBCACHE value is 0 or the large object
size is greater than the LOBCACHE value, the large object data from the
database server is always stored in a file. In this case, if a security
exception occurs, GBase 8s JDBC Driver makes no attempt to store the
large object into memory and throws this exception.
从数据库服务器读取的大对象数据可以存储在内存中，也可以存储在本地文件中。如果
LOBCACHE 值为 0 或大对象大小大于 LOBCACHE 值，则来自数据库服务器的大对象数据
始终存储在文件中。在这种情况下，如果发生安全异常，则 GBase 8s JDBC 驱动程序不
会尝试将大对象存储到内存中并抛出此异常。
-79775 Only TYPE_SCROLL_INSENSITIVE and TYPE_FORWARD_ONLY are
supported.
GBase 8s JDBC Driver only supports a result set type of
TYPE_SCROLL_INSENSITIVE and TYPE_FORWARD_ONLY.
GBase 8s JDBC 驱动程序只支持 TYPE_SCROLL_INSENSITIVE 和 TYPE_FORWARD_ONLY 的
结果集类型。
Use only these values.
仅使用这些值。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2259 -
-79776 Type requested () does not match row type
information () type.
Row-type information was acquired either through the system catalogs or
through the supplied row definition. The row data provided does not match
this row element type.
行类型信息是通过系统目录或通过提供的行定义获取的。提供的行数据与此行元素类型不
匹配。
The type information must be modified, or the data must be provided.
必须修改类型信息，或者必须提供数据。
-79777 readObject/writeObject() only supports UDTs, Distincts and
complex types.
The SQLData.writeObject() method was called for an object that is not a
user-defined, distinct, or complex type.
为对象调用 SQLData.writeObject() 方法，
该对象不是用户定义的、
不同的或复杂的类型。
Verify that you have provided customized type-mapping information.
请确保您提供了自定义的类型映射信息。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2260 -
-79778 Type mapping class must be a java.util.Collection implementation.
You provided a type mapping to override the default for a set, list, or
multiset data type, but the class does not implement the
java.util.Collection interface.
您提供了一个类型映射来覆盖 set、List 或 multiset 数据类型的默认值，但是该类没有
实现 java.util.Collection 接口。
-79779 To insert null data into a row use java null representation.
The GBase 8s JDBC Driver throws this exception whenever an application
attempts to set row column null in an incorrect manner. Ensure that
java null representation is used instead of an object to set null data.
每当应用程序试图以不正确的方式设置行列为 null 时，GBase 8s JDBC驱动程序就会
抛出此异常。确保使用 java null 表示而不是将对象设置为空数据。
-79780 Data within a collection must all be the same Java class and
length.
Collection data was of different Java classes or lengths.
集合的数据是不同的 Java 类或具有不同的长度。
Verify that all the objects in the collection are of the same class.
请集合中的所有对象都属于同一个类。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2261 -
-79781 Index/Count out of range.
Array.getArray() or Array.getResultSet() was called with index and count
values. Either the index is out of range or the count is too big.
使用索引和计数值调用了 Array.getArray() 或 Array.getResultSet()。索引超出
范围或计数太大。
Verify that the number of elements in the array is sufficient for the
index and count values.
请验证数组中的元素数量是否足以满足索引和计数值的需要。
-79782 Method can be called only once.
Make sure methods like Statement.getUpdateCount() and
Statement.getResultSet() are called only once per result.
确保每个结果只调用一次 Statement.getUpdateCount()和Statement.getResultSet()
等方法。
-79783 Encoding or code set not supported.
The encoding or code set entered in the DB_LOCALE or CLIENT_LOCALE
variable is not valid.
DB_LOCALE 或 CLIENT_LOCALE 变量中输入的编码或代码集无效。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2262 -
For valid code sets, see the GBase 8s JDBC Driver Programmer's Guide.
有效的代码集，请参阅《GBase 8s JDBC Driver 程序员指南》。
-79784 Locale not supported.
The locale entered in the DB_LOCALE or CLIENT_LOCALE variable is not
valid.
DB_LOCALE 或 CLIENT_LOCALE 变量中输入的语言环境无效。
For valid locales, see the GBase 8s JDBC Driver Programmer's Guide.
有效的语言环境，请参阅《GBase 8s JDBC Driver 程序员指南》。
-79785 Unable to convert JDBC escape format date string to localized
date string.
The JDBC escape format for date values must be specified in the format
{d 'yyyy-mm-dd'}.
日期值的 JDBC 转义格式必须为 {d 'yyyy-mm-dd'}。
Verify that the JDBC escape date format specified is correct. Verify
the DBDATE and GL_DATE settings for the correct date string format if
either of these was set to a value in the connection database URL
string or property list.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2263 -
验证指定的 JDBC 转义日期格式是否正确。如果将 DBDATE 和 GL_DATE 设置为
连接数据库 URL 字符串或属性列表中的值，则验证正确日期字符串格式的 DBDATE
和 GL_DATE 设置。
-79786 Unable to build a Date object based on localized date string
representation.
The localized date string representation specified in a CHAR, VARCHAR, or
LVARCHAR column is not correct, and a date object cannot be built based on
the year, month, and day values.
CHAR、VARCHAR 或 LVARCHAR 列中指定的语言环境日期字符串表示形式不正确，并且
无法根据年、月和日值构建日期对象。
Verify that the date string representation conforms to the DBDATE or
GL_DATE date formats if either one of these is specified in a connection
database URL string or property list. If neither DBDATE or GL_DATE is
specified but a CLIENT_LOCALE or DB_LOCALE is explicitly set in a
connection database URL string or property list, verify that the
date string representation conforms to the JDK short default format
(DateFormat.SHORT).
如果在连接数据库 URL 字符串或属性列表中指定了日期字符串表示形式，
则验证日期字符
串表示是否符合 DBDATE 或 GL_DATE 格式。如果没有指定 DBDATE 或 GL_DATE，但在连接
数
据库 URL 字符串或属性列表中显式设置了 Client_locale 或 DB_locale，则请验证日期
字
符串表示形式是否符合 JDK 短默认格式 (DateFormates.SHORT)。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2264 -
-79787 Blob/Clob object has not been created from a BLOB/CLOB column.
The GBase 8s JDBC Driver throws this exception whenever an application
calls methods that attempt to use smart large object functionality on an
object that does not represent a smart large object.
For example, smart large objects (BLOB or CLOB) support random access to the
data while simple large objects (TEXT or BYTE) do not support random access.
Ensure that the object being passed has been created from a smart large object.
只要应用程序调用尝试在不代表智能大对象的对象上使用智能大对象功能的方法，
GBase
8s
JDBC Driver
就会抛出此异常。例如，智能大对象（BLOB 或 CLOB）支持对数据的随机访问，而简单的
大对象（TEXT 或
BYTE）不支持随机访问。确保已从智能大对象创建传递的对象。
-79788 User name must be specified.
The user name is required to establish a connection with GBase 8s JDBC
Driver.
用户名是 GBase 8s JDBC Driver 建立连接所必需的。
Make sure you pass in user=your_user_name as part of the database URL
or one of the properties.
确保将 user = your_user_name 作为数据库 URL 或其中一个属性的一部分传递。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2265 -
-79789 Server does not support GLS variables DB_LOCALE, CLIENT_LOCALE,
or GL_DATE.
These variables can only be used if the database server supports GLS.
只有在数据库服务器支持 GLS 时才能使用这些变量。
Check the documentation for your database server version and omit these
variables if they are not supported.
检查数据库服务器版本的文档，如果不支持，请省略这些变量。
-79790 Invalid complex type definition string.
The value that the getSQLtypeName() method returns is either null or invalid.
getSQLtypeName() 方法返回的值为 null 或无效。
Check the string to verify that it is either a valid named-row name or a
valid row-type definition.
检查字符串以验证它是有效的命名行名称还是有效的行类型定义。
-79791 Invalid object. Cannot be inserted into clob/blob column.
GBase 8s JDBC Driver throws this exception whenever an application supplies
an invalid object to the JDBC driver for insertion in a clob/blob column.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2266 -
The JDBC driver attempts to determine if the provided java object may be used
for inserting data in a blob/clob column. If the JDBC driver discovers that the
object is not compatible, this exception is thrown. Make sure that the
application is passing the correct type of object when calling
PreparedStatement::setObject() method.
每当应用程序向 JDBC 驱动程序提供无效对象以插入 clob/blob列时，GBase 8s JDBC
Driver 就会抛出此异常。JDBC 驱动程序尝试确定提供的 java 对象是否可用于在 blob
/clob 列中插入数据。如果 JDBC 驱动程序发现该对象不兼容，则抛出此异常。在调用
PreparedStatement::setObject()方法时，确保应用程序正在传递正确类型的对象。
-79792 Row must contain data.
The Array.getAttributes() or Array.getAttributes(Map) method has
returned 0 elements.
Array.getAttributes()或 Array.getAttributes(Map)方法返回了 0 个元素。
Make sure the method returns a nonzero number.
确保该方法返回非零数字。
-79793 Data in array does not match getBaseType() value.
The Array.getArray() or Array.getArray(Map) method returns an array where
the element type does not match the JDBC base type.
Array.getArray() 或 Array.getArray(Map) 方法返回了一个数组，但其元素类型不符合
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2267 -
JDBC 基类。
-79794 Row length provided () doesn't match row type
information .
Data in the row does not match the length in the row-type information.
行中的数据不符合行类型信息的长度。
You do not have to pad string lengths to match what is in the row
definition, but lengths for other data types should match.
不必填充字符串长度以匹配行定义中的内容，但其他数据类型的长度应匹配。
-79795 Row extended id provided () doesn't match row type
information ().
The extended ID of the object in the row does not match the extended
ID as defined in row-type information.
行中对象的扩展 ID 与行类型信息中定义的扩展 ID 不匹配。
Either update the row-type information (if you are providing the row
definition) or check the type-mapping information.
要么更新行类型信息(如果您正在提供行定义)，要么检查类型映射信息。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2268 -
-79796 Cannot find UDT, distinct or named row () in database.
The getSQLTypeName() method has returned a name that cannot be
found in the database.
getSQLTypeName() 方法返回的名称不在数据库中。
Verify that the Struct or SQLData object returns the correct
information.
验证 Struct 或 SQLData 对象返回了正确的信息。
-79797 DBDATE setting must be at least 4 characters and no longer
than 6 characters.
This error occurs because the DBDATE format string that is passed to
the database server either has too few characters or too many.
发生此错误的原因是传递给数据库服务器的 DBDATE 格式字符串字符太少或太多。
To fix the problem, verify the DBDATE format string with the user
documentation and make sure that the correct year, month, day, and
possibly era parts of the DBDATE format string are correctly identified.
要解决此问题，请使用用户文档验证 DBDATE 格式字符串，并确保正确标识 DBDATE
格式字符串的正确年份、月份、日期和可能的时间部分。
-79798 A numerical year expansion is required after 'Y' character in
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2269 -
DBDATE string.
This error occurs because the DBDATE format string has a year designation
(specified by the character Y), but no character follows the year
designation to denote the numerical year expansion (2 or 4).
发生此错误的原因是 DBDATE 格式字符串具有年份指示符（由字符 Y 指定），但
年份后面没有字符表示数字年份扩展（2 位数或 4 位数）。
To fix the problem, modify the DBDATE format string to include the
numerical year expansion value after the Y character.
要解决此问题，请修改 DBDATE 格式字符串以包含 Y 字符后面的数字年份扩展值。
-79799 An invalid character is found in the DBDATE string after
the 'Y' character.
This error occurs because the DBDATE format string has a year
designation (specified by the character Y), but the character that
follows the year designation is not a 2 or 4 (for two-digit years and
four-digit years, respectively).
发生此错误是因为 DBDATE 格式字符串有一个年份指示符(由字符Y指定)，但在
指定年份之后的字符不是 2 或 4(分别用于两位数年份和四位数年份)。
To fix the problem, modify the DBDATE format string to include the
required numerical year expansion value after the Y character. Only
a 2 or 4 character should immediately follow the Y character designation.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2270 -
若要解决此问题，请修改 DBDATE 格式字符串，以便在 Y 字符之后包含所需的数字年展开
值。
只有 2 或 4 个字符应立即紧跟 Y 字符。
-79800 No 'Y' character is specified before the numerical year
expansion value.
This error occurs because the DBDATE format string has a numerical year
expansion (2 or 4 to denote two-digit years or four-digit years,
respectively), but the year designation character (Y) was not found
immediately before the numerical year expansion character specified.
发生此错误的原因是 DBDATE 格式字符串具有数字年份扩展
（2 或 4 分别表示两位数年份
或四位数年份），但在指定的数字年份扩展字符之前未找到年份指定字符(Y)。
To fix the problem, modify the DBDATE format string to include the
required Y character immediately before the numerical year expansion
value requested.
要解决此问题，请修改 DBDATE 格式字符串，以便在请求的数字年份扩展值之前
包含所需的 Y 字符。
-79801 An invalid character is found in DBDATE format string.
This error occurs because the DBDATE format string has a character that
is not allowed.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2271 -
发生此错误的原因是 DBDATE 格式字符串具有不允许的字符。
To fix the problem, modify the DBDATE format string to include only
the correct date part designations: year (Y), numerical year expansion
value (2 or 4), month (M), and day (D). Optionally, you can include an
era designation (E) and a default separator character (hyphen, dot, or
slash), which is specified at the end of the DBDATE format string.
For further information on correct DBDATE format string character
designations, refer to the user documentation.
要解决此问题，请修改 DBDATE 格式字符串以仅包括正确的日期部分名称：年(Y)、
数字年份扩展值(2 或 4)、月(M)和日(D)。 （可选）您可以包含时代标识（E）和
默认分隔符（连字符、点或斜杠），它在 DBDATE 格式字符串的末尾指定。有关正
确的 DBDATE 格式字符串字符指定的更多信息，请参阅用户文档。
-79802 Not enough tokens are specified in the string representation
of a date value.
This error occurs because the date string specified does not have the
minimum number of tokens or separators needed to form a valid date value
(composed of year, month, and day numerical parts). For example,
12/15/98 is a valid date string representation with the slash character
as the separator or token. But 12/1598 is not a valid date string
representation because there are not enough separators or tokens.
To fix the problem, modify the date string representation to include
a valid format for separating the day, month, and year parts of a date
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2272 -
value.
发生此错误是因为指定的日期字符串没有形成有效日期值所需的最小数目的标记或分隔符
(由年份、
月份和日数字部分组成)。例如，12/15/98 是以斜杠字符作为分隔符或标记的有效日期字
符串表
示形式。但是 12/1598 不是一个有效的日期字符串表示，因为没有足够的分隔符或标记。
若要解
决此问题，请修改日期字符串表示形式，以包括用于分隔日期值的日期、月份和年份部分
的有效
格式。
-79803 Date string index out of bounds during date format parsing to
build Date object.
This error occurs because there is not a one-to-one correspondence
between the date string format required by DBDATE or GL_DATE and the
actual date string representation you defined. For example, if GL_DATE
is set to %b %D %y and you specify a character string of 'Oct', there is
a definite mismatch between the format required by GL_DATE and the
actual date string.
发生此错误是因为 DBDATE 或 GL_DATE 所需的日期字符串格式与您定义的实际
日期字符串表示之间没有一对一的对应关系。例如，如果 GL_Date 设置为 %b%D%y，
并且指定一个字符串‘OCT’，则 GL_DATE 所需的格式与实际日期字符串之间存在不
匹配。
To fix the problem, modify the date string representation of the DBDATE
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2273 -
or GL_DATE setting so that the date format specified matches one-to-one
with the required date string representation.
要解决此问题，请修改 DBDATE 或 GL_DATE 设置的日期字符串表示形式，以便
指定的日期格式与所需的日期字符串表示形式一对一匹配。
-79804 No more tokens are found in DBDATE string representation of
a date value.
This error occurs because the date string specified does not have any more
tokens or separators needed to form a valid date value (composed of year,
month, and day numerical parts) based on the DBDATE format string. For
example, 12/15/98 is a valid date string representation when DBDATE is
set to MDY2/. But 12/1598 is not a valid date string representation
because there are not enough separators or tokens.
发生此错误是因为指定的日期字符串不具有基于 DBDATE 格式字符串形成有效日期值（由
年、
月和日数字部分组成）
所需的标记或分隔符。
例如，
当 DBDATE 设置为 MDY2/ 时，
12/15/98
是有效的日期字符串表示。但 12/1598 不是有效的日期字符串表示形式，因为没有足够的
分
隔符或标记。
To fix the problem, modify the date string representation to include a
valid format for separating the day, month, and year parts of a date
value based on the DBDATE format string setting.
要解决此问题，请修改日期字符串表示，以包含基于 DBDATE 格式字符串设置分隔日
期值的日、月和年部分的有效格式。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2274 -
-79805 No era designation found in DBDATE/GL_DATE string representation
of date value.
This error occurs because the date string specified does not have a valid
era designation as required by the DBDATE or GL_DATE format string setting.
For example, if DBDATE is set to Y2MDE-, but the date string representation
specified by the user is 98-12-15, this is an error because no era
designation is at the end of the date string value.
发生此错误的原因是指定的日期字符串没有 DBDATE 或 GL_DATE 格式字符串设置所需的
有效时
代标识。例如，如果 DBDATE 设置为 Y2MDE-，但用户指定的日期字符串表示形式为
98-12-15，
这是一个错误，因为没有时间标记位于日期字符串值的末尾。
To fix the problem, modify the date string representation to include a
valid era designation based on the DBDATE or GL_DATE format string
setting. In this example, a date string representation of 98-12-15 AD
would probably suffice, depending on the locale.
要解决此问题，
请修改日期字符串表示以包含基于 DBDATE 或 GL_DATE 格式字符串设置的
有效
时代标识。在此示例中，日期字符串表示 98-12-15
AD 可能就足够了，具体取决于区域设
置。
-79806 Numerical day value cannot be determined from date string
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2275 -
based on DBDATE.
This error occurs because the date string specified does not have a valid
numerical day designation as required by the DBDATE format string setting.
For example, if DBDATE is set to Y2MD-, but the date string representation
you specify is 98-12-nn, this is an error, because nn is not a valid
numerical day representation.
发生此错误是因为指定的日期字符串不具有 DBDATE 格式字符串设置所要求的有效的数字
日指定。
例如，如果 DBDATE 设置为 Y2MD-，但是您指定的日期字符串表示形式是 98-12-nn，这是
一个错
误，因为 nn 不是有效的数字日表示形式。
To fix the problem, modify the date string representation to include a
valid numerical day designation (1-31) based on the DBDATE format string
setting.
要解决此问题，请修改日期字符串表示，以包含基于 DBDATE 格式字符串设置的有效数字
日期指定
（1-31）。
-79807 Numerical month value cannot be determined from date string
based on DBDATE.
This error occurs because the date string specified does not have a valid
numerical month designation as required by the DBDATE format string setting.
For example, if DBDATE is set to Y2MD-, but the date string representation
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2276 -
you specify is 98-nn-15, this is an error, because nn is not a valid
numerical month representation.
发生此错误是因为指定的日期字符串不具有 DBDATE 格式字符串设置所要求的有效的数字
月份指定。
例如，如果 DBDATE 设置为 Y2md-，但是您指定的日期字符串表示形式是98-nn-15，这是
一个错误，
因为 nn 不是有效的数字月份表示形式。
To fix the problem, modify the date string representation to include a
valid numerical month designation (1-12) based on the DBDATE format
string setting.
要解决此问题，请修改日期字符串表示形式，以包括基于 DBDATE 格式字符串设置的
有效的数字月份指定(1-12)。
-79808 Not enough tokens specified in %D directive representation
of date string.
This error occurs because the date string specified does not have the
correct number of tokens or separators needed to form a valid date value
based on the GL_DATE %D directive (mm/dd/yy format). For example, 12/15/98
is a valid date-string representation based on the GL_DATE %D directive,
but 12/1598 is not a valid date-string representation because there are not
enough separators or tokens.
发生此错误的原因是指定的日期字符串没有基于 GL_DATE％D 指令（mm/dd/yy 格式）形成
有效日期
值所需的正确数量的标记或分隔符。例如，12/15/98 是基于 GL_DATE％D 指令的有效日期
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2277 -
字符串表
示，但 12/1598 不是有效的日期字符串表示，因为没有足够的分隔符或标记。
To fix the problem, modify the date-string representation to include a valid
format for the GL_DATE %D directive.
要解决此问题，请修改日期字符串表示以包含 GL_DATE％D 指令的有效格式。
-79809 Not enough tokens specified in %x directive representation of
date string.
This error occurs because the date string specified does not have the correct
number of tokens or separators needed to form a valid date value based on
the GL_DATE %x directive (format required is based on day, month, and year
parts, and the ordering of these parts is determined by the specified
locale). For example, 12/15/98 is a valid date-string representation based
on the GL_DATE %x directive for the U.S. English locale, but 12/1598 is not
a valid date-string representation because there are not enough separators or
tokens.
发生此错误的原因是指定的日期字符串没有根据 GL_DATE％x 指令形成有效日期值所需的
正确数量
的标记或分隔符（所需格式基于日、月和年部分，以及这些部分由指定的语言环境决定）。
例如，
12/15/98 是基于美国英语语言环境的 GL_DATE％x 指令的有效日期字符串表示形式，但
12/1598
不是有效的日期字符串表示形式，因为没有足够的分隔符或标记。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2278 -
To fix the problem, modify the date-string representation to include a valid
format for the GL_DATE %x directive based on the locale.
要解决此问题，请修改日期字符串表示，以包含基于语言环境的 GL_DATE％x 指令的有效
格式。
-79810 This release of JDBC requires to be run with JDK 1.2+.
GBase 8s JDBC Driver, Version 2.x, requires a JDK version of 1.2 or greater.
GBase 8s JDBC Driver V2.x，要求 JDK 版本为 1.2 或更高版本。
-79811 Connection without user/password not supported.
You called the getConnection() method for the DataSource object, and the
user name or the password is null.
您为 DataSource 对象调用了getConnection() 方法，并且用户名或密码为 null。
Use the user name and password arguments of the getConnection() method or
set these values in the DataSource object.
使用 getConnection()方法的用户名和密码参数，或在 DataSource 对象中设置这些值。
-79812 User/Password does not match with Datasource.
You called the getConnection(user, passwd) method for the DataSource
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2279 -
object, and the values you supplied did not match the values already found
in the data source.
为 DataSource 对象调用了 getConnection(user，passwd)方法，但是提供的值与在
数据源中找到的值不一致。
-79813 Cannot call setBindColType() after executeQuery().
GBase 8s JDBC Driver allows an application to specify the
output type of the resultset values so that the server can cast to that
type before returning to the client. However the output type needs to be
specified before the query is executed.This error occurs when an application
attempts to specify the output type after the query has been executed.
GBase 8s JDBC Driver 允许应用程序指定结果集值的输出类型，以便服务器可以在
返回到客户端之前强制转换为该类型。但是，在执行查询之前需要指定输出类型。
当应用程序在执行查询后尝试指定输出类型时，会发生此错误。
-79814 Blob/Clob object is either closed or invalid.
If you retrieve a smart large object using the ResultSet.getBlob() or
ResultSet.getClob() method or create one using the IfxBlob() or IfxCblob()
constructor, a smart large object is opened. You can then read from or write
to the smart large object.
如果使用 ResultSet.getBlob()或 ResultSet.getClob()方法检索智能大对象或使用
IfxBlob()或 IfxCblob()构造函数创建一个智能大对象，则会打开智能大对象。然后，
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2280 -
可以读取或写入智能大对象。
After you execute the IfxBlob.close() method, do not use the
smart-large-object handle for further read/write operations, or this
exception is thrown.
执行 IfxBlob.close()方法后，请不要使用 smart-large-object 句柄进行进一步的
读/写操作，否则抛出此异常。
-79815 Not in Insert mode. Need to call moveToInsertRow() first.
You tried to use the insertRow() method, but the mode is not set to Insert.
尝试使用 insertRow() 方法，但是模式没有设置为 Insert。
Call the moveToInsertRow() method before you call insertRow().
请在调用 insertRow() 前调用 moveToInsertRow() 方法。
-79816 Cannot determine the table name.
The table name in the query either is incorrect or refers to a table that
does not exist.
查询中的表名不是不正确，就是不存在。
-79817 No serial, rowid, or primary key specified in the statement.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2281 -
The updatable scrollable feature works only for tables that have a SERIAL
column, a primary key, or a row ID specified in the query. If the table does
not have any of these, an updatable scrollable cursor cannot be created.
可更新的可滚动功能仅适用于具有查询中指定的 SERIAL 列、主键或行 ID的表。
如果表中没有任何这些项，则无法创建可更新的可滚动游标。
-79818 Statement concurrency type is not set to CONCUR_UPDATABLE.
You tried to call the insertRow(), updateRow(), or deleteRow() method for a
statement that has not been created with the CONCUR_UPDATABLE concurrency
type.
您尝试为未用 CONCUR_UPDATABLE 并发类型创建的语句调用 insertRow()、updateRow()
或 deleteRow()方法。
Re-create the statement with this type set for the concurrency attribute.
使用并发属性类型重新创建语句。
-79819 Still in Insert mode. Call moveToCurrentRow() first.
You cannot call the updateRow() or deleteRow() method while still in Insert
mode.
在 Insert 模式下无法调用 updateRow() 或 deleteRow() 方法。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2282 -
Call the moveToCurrentRow() method first.
请先调用 moveToCurrentRow() 方法。
-79820 Function contains an output parameter.
You have passed in a statement that contains an OUT parameter, but you have
not used the drivers CallableStatement.registerOutParameter() and getXXX()
methods to process the OUT parameter.
您已经传递了包含 OUT 参数的语句，但没有使用驱动程序
CallableStatement.RegierOutParameter()
和 getXXX()方法来处理 OUT 参数。
-79821 Name unnecessary for this data type.
The data type you specified does not require a name.
指定的数据类型不需要名称。
Use another method that does not have a type parameter.
使用另一个没有类型参数的方法。
If you have a data type that requires a name (an opaque type or complex
type), you must call a method that has a parameter for the name, such as the
following methods:
如果您的数据类型需要名称(不透明类型或复杂类型)，则必须调用具有名称参数的方法，
如以下方法：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2283 -
public void IfxSetNull(int i, int ifxType, String name)
public void registerOutParameter(int parameterIndex, int sqlType,
java.lang.String name);
public void IfxRegisterOutParameter(int parameterIndex, int ifxType,
java.lang.String name);
-79822 OUT parameter has not been registered.
The function you specified using the CallableStatement interface has an OUT
parameter that has not been registered.
使用 CallableStatement 接口指定的函数具有一个未注册的 OUT 参数。
Call one of the registerOutParameter() or IfxRegisterOutParameter() methods
to register the OUT parameter type before you call the executeQuery() method.
在调用 executeQuery() 方法之前，请调用 registerOutParameter() 或
IfxRegisterOutParameter()
方法注册 OUT 参数。
-79823 IN parameter has not been set.
The function you specified using the CallableStatement interface has an IN
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2284 -
parameter that has not been set.
使用 CallableStatement 接口指定的函数具有一个未设置的 IN 参数。
Call the setNull() or IfxSetNull() method if you want to set a null IN
parameter. Otherwise, call one of the set methods inherited from the
PreparedStatement interface.
如果要设置 null IN 参数，则调用 setNull() 或 IfxSetNull() 方法。否则，调用
从 PreparedStatement 接口继承的 SET 方法之一。
-79824 OUT parameter has not been set.
The function specified using the CallableStatement interface has an OUT
parameter that has not been set.
使用 CallableStatement 接口指定的函数具有一个未设置的 OUT 参数。
Call the setNull() or IfxSetNull() method if you want to set a null OUT
parameter. Otherwise, call one of the set methods inherited from the
PreparedStatement interface.
如果要设置 null OUT 参数，则调用 setNull() 或 IfxSetNull() 方法。否则，调用
从 PreparedStatement 接口继承的 SET 方法之一。
-79825 Type name is required for this data type.
This data type is an opaque type, distinct type, or complex type, and it
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2285 -
requires a name.
此数据类型是 opaque 类型、distinct 类型或复杂类型，它需要一个名称。
Use set methods for IN parameters and register methods for OUT parameters
that take a type name as a parameter.
对 IN 参数使用 set 方法，并为类型名称作为参数的 OUT 参数注册方法。
-79826 Ambiguous java.sql.Type. Use IfxRegisterOutParameter().
The SQL type specified either has no mapping to an GBase 8s data type or has
more than one mapping.
指定的 SQL 类型没有映射到 GBase 8s 数据类型或具有多个映射。
Use one of the IfxRegisterOutParameter() methods to specify the GBase 8s data
type.
使用 IfxRegisterOutParameter（）方法之一指定 GBase 8s 数据类型。
-79827 Function does not have an output parameter.
This function does not have an OUT parameter, or this function has an OUT
parameter whose value the server version does not return. None of the
methods in the CallableStatement interface apply.
此函数没有 OUT 参数，或者此函数具有 OUT 参数，其值不是服务器版本不返回的值。
CallableStatement 接口中的所有方法都不适用。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2286 -
Use the inherited methods from the PreparedStatement interface.
使用 PreparedStatement 接口中的继承方法。
-79828 Function parameter specified is not an OUT parameter.
GBase 8s functions can have only one OUT parameter, and it is always the last
parameter.
GBase 8s 函数只能有一个 OUT 参数，它始终是最后一个参数。
-79829 Invalid directive used for the GL_DATE environment variable.
One or more of the directives that the GL_DATE environment variable specifies
is not allowed.
不允许 GL_DATE 环境变量指定的一个或多个指令。
For a list of the valid directives for a GL_DATE format, see the GBase 8s
JDBC Driver Programmer's Guide.
有关 GL_DATE 格式的有效指令的列表，请参阅 “GBase 8s JDBC Driver 程序员指南”。
-79830 Insufficient information given for building a Time or Timestamp
Java object.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2287 -
For correct performance of string to binary conversions for building a
java.sql.Timestamp or java.sql.Time object, all the DATETIME fields must be
specified for the chosen date-string representation.
为了正确执行字符串到二进制转换以构建 java.sql.Timestamp 或 java.sql.Time 对象，
必须为所选的日期字符串表示指定所有 DATETIME 字段。
For java.sql.Timestamp objects, specify the year, month, day, hour, minute,
and second parts in the string representation.
对于 java.sql.Timestamp 对象，请在字符串表示中指定年、月、日、小时、分钟和秒。
For java.sql.Time objects, specify the hour, minute, and second parts in the
string representation.
对于 java.sql.Time 对象，请在字符串表示中指定小时、分钟和秒部分。
-79831 Exceeded maximum number of connections configured for Connection
Pool Manager.
If you repeatedly connect to a database using a DataSource object without
closing the connection, connections accumulate. When the total number of
connections for the DataSource object exceeds the maximum limit (100), this
error is thrown.
如果使用 DataSource 对象重复连接到数据库而不关闭连接，则会累积连接。当
DataSource 对象
的连接总数超过最大限制（100）时，将引发此错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2288 -
-79832 Netscape Exception! Permission to connect denied by user.
User does not have permission to connect.
用户没有权限进行连接。
-79833 Netscape Exception! Unknown exception while enabling privilege.
This error is raised by the GBase 8s JDBC Driver when it fails to perform
a privileged operation. Check the java security policy file to make sure that
necessary privileges have been granted.
当 GBase 8s JDBC Driver 无法执行特权操作时，会引发此错误。检查 java 安全策略文
件以
确保已授予必要的权限。
-79834 Distributed transactions (XA) not supported by this server.
This error results when an application attempts to open an XA connection
to a server that does not support distributed transactions. Ensure that the
server that the application is connecting to supports distributed transactions.
当应用程序尝试打开与不支持分布式事务的服务器的 XA 连接时，会出现此错误。
确保应用程序连接的服务器支持分布式事务。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2289 -
-79835 RowSet is set to ReadOnly.
This error results when an application attempts an update/insert or delete
operation on a read-only RowSet. Ensure that the RowSet in use is not read-only.
当应用程序尝试对只读 RowSet 执行更新/插入或删除操作时，会出现此错误。
确保使用的 RowSet 不是只读的。
-79836 Proxy Error: No database connection.
This error is thrown by the GBase 8s HTTP Proxy if you try to communicate
with the database on an invalid or bad database connection.
如果您尝试在无效或错误的数据库连接上与数据库通信，则 GBase 8s HTTP 代理会抛出
此错误。
Make sure your application has opened a connection to the database. Check your
Web server and database error logs.
确保您的应用程序已打开与数据库的连接。检查 Web 服务器和数据库错误日志。
-79837 Proxy Error: Input/output error while communicating with the
database.
This error is thrown by the GBase 8s HTTP Proxy if an error is detected while
the proxy is communicating with the database. This error can occur if your
database server is not accessible.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2290 -
如果在代理与数据库通信时检测到错误，则 GBase 8s HTTP 代理会抛出此错误。
如果您的数据库服务器不可访问，则会发生此错误。
Make sure your database server is accessible. Check your database and Web
server error logs.
确保您的数据库服务器可访问。检查数据库和 Web 服务器错误日志。
-79838 Cannot execute change permission command (chmod/attrib).
The driver is unable to change the permissions on the client JAR file. This
could happen if your client platform does not support the chmod or attrib
command, or if the user running the JDBC application does not have the
authority to change access permissions on the client JAR file.
驱动程序无法更改客户端 JAR 文件的权限。
如果您的客户端平台不支持 chmod 或 attrib
命令，
或者运行 JDBC 应用程序的用户无权更改客户端 JAR 文件的访问权限，
则可能会发生这种
情况。
Make sure the chmod or attrib command is available for your platform and that
the user running the application has the authority to change access
permissions on the client JAR file.
确保 chmod 或 attrib 命令可用于您的平台，
并且运行该应用程序的用户有权更改客户端
JAR 文件
的访问权限。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2291 -
-79839 Same Jar SQL name already exists in the system catalog.
The JAR filename specified when your application called
UDTManager.createJar() has already been registered in the database server.
应用程序调用 UDTManager.createJar()时指定的 JAR 文件名已在数据库服务器中注册。
Use UDTMetaData.setJarFileSQLName() to specify a different SQL name for the
JAR file.
使用 UDTMetaData.setJarFileSQLName() 为 JAR 文件指定不同的 SQL 名称。
-79840 Unable to copy JAR file from client to server.
This error occurs when the pathname set using setJarTmpPath() is not writable
by user gbasedbt or the user specified in the JDBC connection.
当使用 setJarTmpPath() 设置的路径名不能由用户 gbasedbt 或 JDBC 连接中指定的用
户写入时，
会发生此错误。
Make sure the pathname is readable and writable by any user.
确保路径名是任何用户都可读写的。
-79841 Invalid or Inconsistent Tuning Parameters for Connection Pool Datasource
The GBase 8s JDBC Driver encountered an invalid Connection Pool Datasource
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2292 -
property value. Make sure that application is using valid values to set
Connection Pool Datasource properties. Refer to the GBase 8s JDBC
Programmer's Guide for details of valid values.
GBase 8s JDBC Driver 遇到无效的连接池 Datasourcemproperty 值。确保应用程
序使用有效值来设置 setmConnection 池数据源属性。有关有效值的详细信息，请
参阅“GBase 8s JDBC 程序员指南”。
-79842 No UDR information was set in UDRMetaData.
Your application called the UDRManager.createUDRs() method without specifying
any UDRs for the database server to register.
应用程序调用 UDRManager.createUDRs()方法，而没有为数据库服务器指定任何要注册的
UDR。
Specify UDRs for the database server to register by calling the
UDRMetaData.setUDR() method before calling the UDRManager.createUDRs()
method.
在调用 UDRManager.createUDRs()方法之前，通过调用 UDRMetaData.setUDR()方法为要
注册的数据库服务器指定 UDR。
-79843 SQL name of the JAR file was not set in UDR/UDT metaData.
Your application called either the UDTManager.createUDT() method or the
UDRManager.createUDRs() method without specifying an SQL name for the JAR
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2293 -
file that contains the opaque types or UDRs for the database server to
register.
应用程序调用了 UDTManager.createUDT() 方法或 UDRManager.createUDRs() 方法，
而没
有为包含不透明类型的 JAR 文件指定 SQL 名称，也没有为数据库服务器注册 UDR 指定
SQL 名称。
Specify an SQL name for a JAR file by calling the
UDTMetaData.setJarFileSQLName() or UDRMetaData.setJarFileSQLName() method
before you call the UDTManager.createUDT() or UDRManager.createUDRs() method.
在调用 UDTManager.createUDT()或 UDRManager.createUDRs()方法之前，通过调用
UDTMetaData.setJarFileSQLName()或 UDRMetaData.setJarFileSQLName()方法为 JAR
文件指定 SQL 名称。
-79844 Cannot create/remove UDT/UDR as no database is specified in the
connection.
Your application created a connection without specifying a database.
应用程序创建了连接，但是没有指定数据库。
The following example establishes a connection and opens a database
named "test":
以下示例建立一个连接并打开数据库 "test"：
url = "jdbc:gbasedbt-sqli:myhost:1533/test:" +
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2294 -
"gbasedbtserver=myserver;user=rdtest;password=test";
conn = DriverManager.getConnection(url);
The following example establishes a connection with no database open:
以下示例建立一个连接，但未打开数据库：
url = "jdbc:gbasedbt-sqli:myhost:1533:" +
"gbasedbtserver=myserver;user=rdtest;password=test";
conn = DriverManager.getConnection(url);
To resolve this problem, use the following SQL statements after the
connection is established and before you call the createUDT() or
createUDRs() method:
要解决此问题，在建立连接之后，调用 createUDT() 或 createUDRs() 之前，
使用以下SQL 语句：
Statement stmt = conn.createStatement();
stmt.executeUpdate("create database test ...");
Alternatively, use the following code:
或者，使用以下代码：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2295 -
stmt.executeUpdate("database test");
-79845 JAR file on the client does not exist or cannot be read.
This error occurs for one of the following reasons:
出现此错误的原因有以下几种：
You failed to create a client JAR file.
您无法创建客户端 JAR 文件。
You specified an incorrect pathname for the client JAR file.
您为客户端JAR文件指定了错误的路径名。
The user running the JDBC application or the user specified in the
connection does not have permission to open or read the client JAR file.
运行 JDBC 应用程序的用户或连接中指定的用户无权打开或读取客户端 JAR 文件。
-79846 Invalid JAR file name.
The client JAR file your application specified as the second parameter to
UDTManager.createUDT() or UDRManager.createUDRs() must end with the .jar
extension.
应用程序为 UDTManager.createUDT() 或 UDRManager.createUDRs()指定的第二参
数-客户端 JAR 文件，必须具有 .jar 扩展名。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2296 -
-79847 The javac or jar command failed.
The driver encountered compilation errors in one of the following cases:
在以下某种情况下，驱动程序遇到编译错误：
Compiling .class files into .jar files, using the jar command, in response
to a createJar() command from a JDBC application
使用 jar 命令将 .class 文件编译为 .jar 文件，以响应 JDBC 应用程序中的
createJar()命令
Compiling .java files into .class files and .jar files, using the javac
and jar commands, in response to a call to the UDTManager.createUDTClass()
method from a JDBC application
使用 javac 和 jar 命令将 .java 文件编译为 .class 文件和 .jar 文件，以响应
从 JDBC 应用程序调用 UDTManager.createUDTClass()方法
-79848 Same UDT SQL name already exists in the system catalog.
Your application called UDTMetaData.setSQLName() and specified a name that is
already in the database server.
应用程序调用了 UDTMetaData.setSQLName()，但指定了数据库服务器中已有的名称。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2297 -
-79849 UDT SQL name was not set in UDTMetaData.
Your application failed to call UDTMetaData.setSQLName() to specify an SQL
name for the opaque type.
您的应用程序无法调用 UDTMetaData.setSQLName() 来指定 opaque 类型的 SQL 名称。
-79850 UDT field count was not set in UDTMetaData.
Your application called UDTManager.createUDTClass() without first specifying
the number of fields in the internal data structure that defines the opaque
type.
您的应用程序调用了 UDTManager.createUDTClass()，但之前没有指定定义不透明类型的
内部
数据结构中的字段数。
Specify the number of fields by calling UDTMetaData.setFieldCount().
通过调用 UDTMetaData.setFieldCount() 指定字段数。
-79851 UDT length was not set in UDTMetaData.
Your application called UDTManager.createUDTClass() without first specifying
a length for the opaque type.
您的应用程序调用 UDTManager.createUDTClass() 而不首先指定 opaque 类型的长度。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2298 -
Specify the total length for the opaque type by calling
UDTMetaData.setLength().
通过调用 UDTMetaData.setLength() 指定 opaque 类型的总长度。
-79852 UDT field name or field type was not set in UDTMetaData.
Your application called UDTManager.createUDTClass() without first specifying
a field name and data type for each field in the data structure that defines
the opaque type.
您的应用程序调用 UDTManager.createUDTClass()，而不首先为定义 opaque 类型的
数据结构中的每个字段指定字段名称和数据类型。
Specify each field name by calling UDTMetaData.setFieldName(). Specify a data
type for each field by calling UDTMetaData.setFieldType().
通过调用 UDTMetaData.setFieldName()指定每个字段名称。通过调用
UDTMetaData.setFieldType()
为每个字段指定数据类型。
-79853 No class files to be put into the jar.
Your application called the createJar() method and passed a zero-length
string for the classnames parameter.
您的应用程序调用了 createJar() 方法，并为 classnames 参数传递了一个零长度字符
串。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2299 -
The method signature is as follows:
方法签名如下：
createJar(UDTMetaData mdata, String[] classnames)
-79854 UDT java class must implement java.sql.SQLData interface.
Your application called UDTManager.createUDT() to create an opaque type whose
class definition does not implement the java.sql.SQLData interface.
UDTManager cannot create an opaque type from a class that does not implement
this interface.
您的应用程序调用 UDTManager.createUDT() 来创建 opaque 类型，但其类定义没有实
现java.sql.SQLData 接口。UDTManager 无法从未实现此接口的类创建 opaque 类型。
-79855 Specified UDT java class is not found.
Your application called the UDTManager.createUDT() method, but the driver
could not find a class with the name you specified for the third parameter.
应用程序调用UDTManager.createUDT() 方法，但驱动程序找不到具有您为第三个参
数指定的名称的类。
-79856 Specified UDT does not exists in the database.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2300 -
Your application called UDTManager.removeUDT(String sqlname) to remove an
opaque type named sqlname from the database, but no opaque type with that
name exists in the database.
您的应用程序调用 UDTManager.removeUDT(String sqlname)，从数据库中删除名为
sqlname 的 opaque 类型，但数据库中不存在具有该名称的 opaque 类型。
-79857 Invalid support function type.
This error occurs only if your application calls the
UDTMetaData.setSupportUDR() method and passes an integer other
than 0 through 7 for the type parameter.
仅当应用程序调用 UDTMetaData.setSupportUDR() 方法并为 type 参数传递 0 到 7
之间的整数时，才会发生此错误。
Use the constants defined for the support UDR types. For more information,
see the GBase 8s JDBC Driver Programmer's Guide.
使用为支持 UDR 类型定义的常量。有关更多信息，请参阅“GBase 8s JDBC 驱动程序
程序员指南”。
-79858 The command to remove file on the client failed.
If UDTMetaData.keepJavaFile() is not called or is set to FALSE, the driver
removes the generated .java file when the UDTManager.createUDTClass() method
executes. This error results if the driver was unable to remove the .java
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2301 -
file.
如果未调用 UDTMetaData.keepJavaFile()或将其设置为false，则在执行
UDTManager.createUDTClass()
方法时，驱动程序将删除生成的 .java文件。如果驱动程序无法删除 .java文件，则会出
现此错误。
-79859 Invalid UDT field number.
Your application called a UDTMetaData.setXXX() or UDTMetaData.getXXX() method
and specified a field number that was less than 0 or greater than the value
set through the UDTMetaData.setFieldCount() method.
您的应用程序调用了 UDTMetaData.setXXX() 或 UDTMetaData.getXXX() 方法，并指定
了一个字段号，该字段号小于或大于 UDTMetaData.setFieldCount() 方法设置的值。
-79860 Ambiguous java type - cannot use Object/SQLData as method
argument.
One or more parameters of the method to be registered as a UDR is of type
java.lang.Object or java.sql.SQLData. These Java data types can be mapped to
more than one GBase 8s data type, so the driver is unable to choose a type.
要注册为 UDR 的方法的一个或多个参数是 java.lang.Object 或 java.sql.SQLData
类型。这些 Java 数据类型可以映射到多个 GBase 8s 数据类型，因此驱动程序无法
选择一个类型。
Avoid using java.lang.Object or java.sql.SQLData as a method argument.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2302 -
避免使用 java.lang.Object 或 java.sql.SQLData 作为方法参数。
-79861 Specified UDT field type has no Java type match.
Your application called UDTMetaData.setFieldType() and specified a data type
that has no 100% match in Java. The following data types are in this
category:
您的应用程序调用了 UDTMetaData.setFieldType()，并指定了在 Java 中没有 100%
匹配的数据类型。以下数据类型属于此类别：
IfxTypes.IFX_TYPE_BYTE
IfxTypes.IFX_TYPE_TEXT
IfxTypes.IFX_TYPE_VARCHAR
IfxTypes.IFX_TYPE_NVCHAR
IfxTypes.IFX_TYPE_LVARCHAR
Use IFX_TYPE_CHAR or IFX_TYPE_NCHAR instead; these data types map to
java.lang.String.
使用 IFX_TYPE_CHAR 或 IFX_TYPE_NCHAR 代替；
这些数据类型映射到 java.lang.String。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2303 -
-79862 Invalid UDT field type.
Your application called UDTMetaData.setFieldType() and specified an
unsupported data type for the opaque type.
应用程序调用了 UDTMetaData.setFieldType()，
但为 opaque 类型指定了一个不支持的数
据类型。
For supported data types, see the GBase 8s JDBC Driver Programmer's Guide.
有关支持的数据类型，请参阅《GBase 8s JDBC Driver 程序员指南》。
-79863 UDT field length was not set in UDTMetaData.
Your application specified a field of a character, datetime, or interval
data type by calling UDTMetaData.setFieldType() but failed to specify a field
length.
应用程序通过调用 UDTMetaData.setFieldType() 指定字符、日期时间或间隔数据类型的
字段，
但未能指定字段长度。
Call UDTMetaData.setFieldLength() to set a field length.
调用 UDTMetaData.setFieldLength() 设置字段长度。
-79864 Statement length exceeds the maximum.
Your application issued an SQL PREPARE, DECLARE, or EXECUTE IMMEDIATE
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2304 -
statement that is longer than the database server can handle. The limit
differs with different implementations but in most cases is up to 65,535
characters.
您的应用程序发出了比数据库服务器可以处理的更长的 SQL PREPARE、DECLARE 或
EXECUTE IMMEDIATE 语句。语句的限制因不同的实现而不同，但在大多数情况下最多
为 65,535 个字符。
Review the program logic to ensure that an error has not caused your
application to present a string that is longer than intended. If the text has
the intended length, revise the application to present fewer statements at a
time.
检查程序逻辑以确保错误未导致应用程序显示超出预期的字符串。
如果文本具有预期长度，
则修改应用程序以一次显示较少的语句。
This error is the same as error -460 that the database server returns.
此错误与数据库服务器返回的错误 -460 相同。
-79865 'Statement' already closed.
This error occurs when an application attempts to call a method on a
Statement object that has already been closed.
Make sure that the Statement object has not already been closed.
当应用程序尝试在已关闭的 Statement 对象上调用方法时，会发生此错误。
确保尚未关闭 Statement 对象。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2305 -
-79868 ResultSet not open, operation not permitted.
This error occurs when an application attempts to call a method on a ResultSet
object that has already been closed.The method can be called only on an open
ResultSet object. Ensure that the ResultSet object in use has not already been
implicitly or explicitly closed.
当应用程序尝试在已关闭的 ResultSet 对象上调用方法时，会发生此错误。此方法只能在
打开的
ResultSet 对象上调用。确保没有隐式或显式关闭正在使用的 ResultSet 对象。
-79877 Invalid parameter value for setting maximum field size.
This error occurs when an application attempts to set a maximum field size
to a negative value. Ensure that application is passing a non-negative integer
when calling the setMaxFieldSize() method on a Statement object.
当应用程序尝试将最大字段大小设置为负值时，会发生此错误。在 Statement 对象上
调用 setMaxFieldSize() 方法时，确保应用程序传递非负整数。
-79878 ResultSet not open, operation 'next' not permitted. Verify that autocommit
is OFF
This message appears when an application attempts to fetch a row using
a ResultSet that has been closed. Make sure that the ResultSet in use has not
been closed, automatically or explicitly.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2306 -
A ResultSet object is automatically closed when the Statement object that
generated the ResultSet object is closed, re-executed, or used to retrieve
the next result from a sequence of multiple results.
当应用程序尝试使用已关闭的 ResultSet 获取行时，将显示此消息。确保未关闭、自动或
显式地关闭
正在使用的 ResultSet。当生成 ResultSet 对象的语句对象关闭、重新执行或用于从多个
结果序列
检索下一个结果时，ResultSet 对象将自动关闭。
-79879 An unexpected exception was thrown. See next exception for details.
This message appears when the JDBC driver encounters an exception that is not
anticipated in the normal course of events.Another exception chained to this
exception contains further information regarding the unexpected error condition
that occurred.
当 JDBC 驱动程序遇到在正常事件过程中未预料到的异常时，将显示此消息。链接到此异
常的另一个
异常，它包含有关发生的意外错误情况的更多信息。
-79880 Unable to set JDK Version for the Driver.
This message appears when the JDBC driver fails to determine which version
of JDK is being used to run the java application. JDBC driver attempts to read
"java.version" system property to find out which JDK version is being used.
Ensure that the JDBC driver JAR has necessary privileges to access the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2307 -
"java.version" system property.
当 JDBC 驱动程序无法确定正在使用哪个版本的 JDK 来运行 Java 应用程序时，
会出现此
消息。
JDBC 驱动程序尝试读取 “java.version” 系统属性以找出正在使用的JDK 版本。确保
JDBC
驱动程序 JAR 具有访问 “java.version” 系统属性的必要权限。
-79881 Already in local transaction, so cannot start XA transaction.
This error message appears when a JDBC application attempts to start an XA
transaction for a connection that is already associated with a local
transaction. XAResource does not support nested transactions. Before
attempting to start an XA transaction, the application needs to ensure
that the connection is not associated with any other transaction.
当 JDBC 应用程序试图为已经与本地事务关联的连接启动 XA 事务时，
会出现此错误消息。
XAResource 不支持嵌套事务。在尝试启动 XA 事务之前，应用程序需要确保连接与任何
其他事务无关。
-79882 Method not supported with this server.
This error message appears when a JDBC client attempts to use functionality
that is not supported by the version of server the JDBC client is connected to.
This functionality is available in later versions of the server.
You can migrate to the latest server version to use this functionality
当 JDBC 客户机试图使用连接到的服务器版本不支持的功能时，会出现此错误消息。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2308 -
此功能可在服务器的后期版本中使用。您可以迁移到最新的服务器版本以使用此功能。
-79883 Class that implements IfmxPAM interface could not be located or loaded.
This error message appears when the JDBC driver fails to load the class
specified by the IFX_PAM_CLASS connection property.In order to use the PAM
authentication mechanism, the JDBC application specifies the name of a class
as a connection property. The JDBC driver failed to load the specified class.
Ensure that the specified class is in the CLASSPATH.
当 JDBC 驱动程序无法加载 IFX_PAM_class 连接属性指定的类时，将出现此错误消息，
为了使用 PAM 身份验证机制，JDBC 应用程序将类名指定为连接属性。JDBC 驱动程序
未能加载指定的类。确保指定的类在 CLASSPATH 中。
-79884 Class must implement com.gbasedbt.jdbc.IfmxPAM interface for PAM
functionality.
This message appears when the class whose name has been set as a value of
the IFX_PAM_CLASS property does not implement the com.gbasedbt.jdbc.IfmxPAM
interface.In order to use the PAM authentication mechanism, the JDBC
application needs to set the IFX_PAM_CLASS connection property.The class
specified as value of a IFX_PAM_CLASS connection property should Implement
the com.gbasedbt.jdbc.IfmxPAM interface.
当名称设置为 IFX_PAM_CLASS 属性值的类没有实现 com.Gbasedbt.jdbc.IfmxPAM 接口
时，
就会出现此消息。为了使用 PAM 身份验证机制，JDBC 应用程序需要设置 IFX_PAM_CLASS
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2309 -
连接属性。
指定为 IFX_PAM_CLASS 连接属性值的类应该实现 com.sulix.jdbc.IfmxPAM 接
口。
-79885 PAM authorization has failed.
This message appears when PAM authorization of a JDBC client fails.
Ensure that your application is responding with a correct response string
to the challenge message received from a PAM-enabled server.
当 JDBC 客户端的 PAM 授权失败时，就会出现此消息。确保应用程序使用正确的响应字符
串
响应从启用 PAM 的服务器接收的质询消息。
-79886 PAM Response Message Size exceeds maximum size allowed.
Length of the PAM response string set by your application exceeds the
maximum allowed size. The PAM standard defines the maximum size of
a PAM message to be 512 bytes (IfxPAMChallenge.PAM_MAX_MESSAGE_SIZE).
Ensure that a correct PAM response string is supplied by your application.
应用程序设置的 PAM 响应字符串的长度超过了允许的最大大小。PAM 标准将
PAM 消息的最大大小定义为 512 字节（IfxPAMChallenge.PAM_MAX_MESSAGE_SIZE）。
确保应用程序提供了正确的 PAM 响应字符串。
-79887 Parameter name not found.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2310 -
A parameter name is not found in the argument names of the specified
stored procedure. Either one of the parameter names is not valid or
the stored procedure name is incorrect.
在指定的存储过程的参数名称中找不到参数名称。其中一个参数名称无效或
存储过程名称不正确。
Correct the parameter or procedure name and run the procedure again.
更正参数或过程名称并再次运行该过程。
-79888 Parameters are specified by both name and ordinal position for the same
CallableStatement object.
A CallableStatement object must be consistent in the way it specifies
parameters; that is, it must only use methods that take parameter names
(String objects), or it must use only methods that take parameter ordinal
positions (integers). A CallableStatement object that mixes the two types
of references throws an SQLException object.
CallableStatement 对象必须在指定参数的方式上保持一致;也就是说，
它只能使用带有参
数名称
（String 对象）的方法，或者它必须只使用带有参数 ordina 位置（整数）的方法。混合
两种类
型的引用的 CallableStatement 对象将抛出 SQLException 对象。
Specify parameters either by name or by ordinal for a particular
CallableStatement object.
为特定的 CallableStatement 对象按名称或按顺序指定参数。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2311 -
-79889 You cannot set a savepoint, rollback to a savepoint, or release a savepoint
when
the transaction is in autocommit mode.
The JDBC application attempted to create or reference a savepoint while the
autocommit transaction mode was true for the connection. Before attempting
to set a savepoint, to rollback to a savepoint, or to release a savepoint,
the application needs to ensure that autocommit is false. By default,
autocommit is true in JDBC for connections to any IDS database that
supports transaction logging.
当连接的自动提交事务模式为真时，JDBC 应用程序尝试创建或引用保存点。在尝试设置保
存点，
回滚到保存点或释放保存点之前，
应用程序需要确保自动提交为 false。
默认情况下，
JDBC
中
的 autocommit 为 true，用于连接到支持事务日志记录的任何 IDS 数据库。
-79890 You cannot set a savepoint, rollback to a savepoint, or release a savepoint
within an XA transaction.
The JDBC application attempted to create or reference a savepoint within an
XA transaction. Savepoints are not supported in XA transactions.
JDBC 应用程序尝试在 XA 事务中创建或引用保存点。XA 事务不支持保存点。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2312 -
-79891 The identifier declared for the named savepoint cannot be null.
The JDBC application attempted to set a savepoint by passing NULL as the
the savepoint name. The savepoint name cannot be NULL for the connection.
setSavepoint(string) method. Use instead the setSavepoint() method if you
want to create an unnamed savepoint.
JDBC 应用程序尝试通过传递 NULL 作为保存点名称来设置保存点。
连接的保存点名称不能
为
NULL。setSavepoint(string)方法。如果要创建未命名的保存点，请使用 setSavepoint()
方法。
-79892 The savepoint cannot be null when rolling back to a savepoint or releasing
a savepoint.
The JDBC application attempted to rollback to a savepoint or to release a
savepoint by passing a NULL savepoint object. Only savepoint objects
that were created by the setSavepoint() methods can be passed to methods
that rollback to a savepoint or that release a savepoint.
JDBC 应用程序试图回滚到 savepoint，或者通过传递空 savepoint 对象来释放
savepoint。
只有由 setSavepoint()方法创建的 savepoint 对象才能传递给回滚到 savepoint 或发
布
savepoint 的方法。
-79893 The savepoint is not valid in the current connection.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2313 -
The JDBC application attempted to rollback to a savepoint (or to release a
savepoint) by passing an invalid savepoint object. Before the application
can rollback to a savepoint or release a savepoint, that savepoint must
first be created in the current connection.
JDBC 应用程序试图通过传递无效的 savepoint 对象回滚到 savepoint(或释放
savepoint)。
在应用程序回滚到 savepoint 或发布 savepoint 之前，必须首先在当前连接中创建
该 savepoint。
-79894 You cannot return the numeric identifier of a named savepoint.
The JDBC application attempted to call getSavepointId() on a named
savepoint. If the savepoint was declared using the setSavepoint(string)
method, then getSavepointId() is not a valid method, and it returns this
exception. Call instead the getSavepointName() method to return the
name of a savepoint.
JDBC 应用程序试图在命名的 savepoint 上调用 getSavepointId()。如果保存点是使用
setSavepoint(String) 方法声明的，则 getSavepointId()不是有效方法，它将返回此
异常。相反，调用 getSavepointName()方法来返回 savepoint 的名称。
-79895 You cannot return the name of an unnamed savepoint.
The JDBC application attempted to call getSavepointName() on an unnamed
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2314 -
savepoint. If the savepoint was declared using the setSavepoint()
method, then getSavepointName() is not a valid method, and it returns
this exception. Call instead the getSavepointId() method to return the
numeric identifier of an unnamed savepoint.
JDBC 应用程序试图在未命名的 savepoint 上调用 getSavepointName()。
如果保存点是使
用
setSavepoint() 方法声明的，则 getSavepointName()不是有效方法，它将返回此异常。
相
反，调用 getSavepointId() 方法来返回未命名的 savepoint 的数字标识符。
-79896 Incorrect connection array index in the connection pool.
The connection array index is not a valid index.
This is caused when the application tries to remove a connection from the
connection pool and the array index is either negative or more than the
maximum connection size for the pool.
连接数组索引是一个无效索引。当应用程序尝试从连接池中删除连接并且数组索引为负数
或大于
池的最大连接大小时，会导致此问题。
This problem is probably caused by the JVM running out of resources.
Check for any relevant operating system messages.
此问题可能是由 JVM 耗尽资源引起的。检查是否有相关的操作系统消息。
-79999 Message text will be provided in later release.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2315 -
An error message with detailed message text will be provided in future
releases.
将在未来版本中提供带有详细消息文本的错误消息。
21511 Cannot request more than 1 page for online index build.
The online index build has requested more than 1 page during parallel build.
在线索引构建在并行构建期间请求超过 1 页。
-21511 Cannot request more than 1 page for online index build.
The online index build has requested more than 1 page during parallel build.
在线索引构建在并行构建期间请求超过 1 页。
21512 Exclusive access required to pre-image buffer.
Exclusive access required to pre-image buffer. Either a buffer was released
with BF_MODIFY flag, or it was shared or waited for by some other thread.
预映像缓冲区需要独占访问权限。使用 BF_MODIFY 标志释放缓冲区，或者由其他某个线程
共享
或等待它。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2316 -
-21512 Exclusive access required to pre-image buffer.
Exclusive access required to pre-image buffer. Either a buffer was released
with BF_MODIFY flag, or it was shared or waited for by some other thread.
预映像缓冲区需要独占访问权限。使用 BF_MODIFY 标志释放缓冲区，或者由其他某个线程
共享
或等待它。
21513 Error in online index operation
Some internal error occurred during the online index operation.
在线索引操作期间发生了一些内部错误。
-21513 Error in online index operation
Some internal error occurred during the online index operation.
在线索引操作期间发生了一些内部错误。
21514 Error saving keyp after online index build
There was some error when saving new keyp after online index build.
在线索引构建后保存新 keyp 时出现错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2317 -
-21514 Error saving keyp after online index build
There was some error when saving new keyp after online index build.
在线索引构建后保存新 keyp 时出现错误。
21515 Cannot perform online index build for attached indices
Online index build is allowed only for detached and semi-detached indices.
It is not supported for attached index builds.
只有分离和半分离的索引允许在线索引构建。附加的索引构建不支持。
-21515 Cannot perform online index build for attached indices
Online index build is allowed only for detached and semi-detached indices.
It is not supported for attached index builds.
只有分离和半分离的索引允许在线索引构建。附加的索引构建不支持。
21516 Partially read row
This is an internally set error on reading rows for parallel index build.
It is ignored if the parallel build is being performed for an online index
这是为并行索引生成读取行的内部设置错误。如果要为联机索引执行并行生成，则忽略它。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2318 -
-21516 Partially read row
This is an internally set error on reading rows for parallel index build.
It is ignored if the parallel build is being performed for an online index
这是为并行索引生成读取行的内部设置错误。如果要为联机索引执行并行生成，则忽略它。
21517 Error allocating bufQ for preimage or updator log
Error occurred when allocating buffer queue for preimage or updator logging.
为预映像或更新程序日志分配缓冲区队列时发生错误。
-21517 Error allocating bufQ for preimage or updator log
Error occurred when allocating buffer queue for preimage or updator logging.
为预映像或更新程序日志分配缓冲区队列时发生错误。
21518 Error occurred while starting a thread to process preimage or updator
log.
Error occurred while starting a thread for processing preimage or updator log.
启动用于处理预映像或更新程序日志的线程时发生错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2319 -
-21518 Error occurred while starting a thread to process preimage or updator
log.
Error occurred while starting a thread for processing preimage or updator log.
启动用于处理预映像或更新程序日志的线程时发生错误。
21519 No preimage exists
No preimage exists when one was believed to be there.
没有预映象存在，误认为有一个预映象存在。
-21519 No preimage exists
No preimage exists when one was believed to be there.
没有预映象存在，误认为有一个预映象存在。
21520 Bad temp partition physaddr
Bad temp partition physaddr was obtained for preimage or updator log partition.
为 preimage 或 updator 日志分区获取了错误的临时分区 physaddr。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2320 -
-21520 Bad temp partition physaddr
Bad temp partition physaddr was obtained for preimage or updator log partition.
为 preimage 或 updator 日志分区获取了错误的临时分区 physaddr。
21521 More than 1 online index operation on the same table
More than 1 online index operation is not allowed on the same table.
同一个表上只能有一个联机索引操作。
-21521 More than 1 online index operation on the same table
More than 1 online index operation is not allowed on the same table.
同一个表上只能有一个联机索引操作。
21522 No online index build possible
No online index build is possible in the requested scenario.
The index build requires reading rows one by one, or online index builds
are not allowed in this IDS edition.
在请求的方案中无法进行在线索引构建。索引构建需要逐行读取，或者在此 IDS 版本中不
允许
联机索引构建。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2321 -
-21522 No online index build possible
No online index build is possible in the requested scenario.
The index build requires reading rows one by one, or online index builds
are not allowed in this IDS edition.
在请求的方案中无法进行在线索引构建。索引构建需要逐行读取，或者在此 IDS 版本中不
允许
联机索引构建。
21523 Cannot proceed with a dirty/modified table data dictionary entry.
DML operations are susceptible to this error when they are referencing an
older copy of the table's data dictionary information.
Most likely, the database server just completed a 'CREATE/DROP INDEX ... '
operation on the table referred to by the DML operation.
DML 操作在引用表的数据字典信息的旧副本时容易发生此错误。最有可能的是，数据库服
务器
刚刚完成了 DML 操作所引用的表上的 “CREATE/DROP INDEX...” 操作。
This error is accompanied by SQL Error -710.
此错误伴随 SQL 错误 -710。
-21523 Cannot proceed with a dirty/modified table data dictionary entry.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2322 -
DML operations are susceptible to this error when they are referencing an
older copy of the table's data dictionary information.
Most likely, the database server just completed a 'CREATE/DROP INDEX ... '
operation on the table referred to by the DML operation.
DML 操作在引用表的数据字典信息的旧副本时容易发生此错误。最有可能的是，数据库服
务器
刚刚完成了 DML 操作所引用的表上的 “CREATE/DROP INDEX...” 操作。
This error is accompanied by SQL Error -710.
此错误伴随 SQL 错误 -710。
21524 Cannot create a temporary operating system file to use in a sort
A sort was being performed that did not use a dbspace partition to store
overflow data. Overflow data is written to a temporary operating system
file. However, the database server could not create a temporary operating
system file for this sort. Consider setting the PSORT_DBTEMP environment
variable to a secure directory with a minimum of 200 MB of free space.
If PSORT_DBTEMP is not set then the database server stores overflow data
in the /tmp or $GBS_HOME/tmp directory.
正在执行的排序不使用 dbspace 分区来存储溢出数据。溢出数据将写入临时操作系统文
件。
但是，数据库服务器无法为此类型创建临时操作系统文件。考虑将 PSORT_DBTEMP 环境变
量
设置为具有至少 200
MB 可用空间的安全目录。如果未设置 PSORT_DBTEMP，则数据库服务
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2323 -
器将溢出数据存储在 /tmp 或 $GBS_HOME/tmp 目录中。
-21524 Cannot create a temporary operating system file to use in a sort
A sort was being performed that did not use a dbspace partition to store
overflow data. Overflow data is written to a temporary operating system
file. However, the database server could not create a temporary operating
system file for this sort. Consider setting the PSORT_DBTEMP environment
variable to a secure directory with a minimum of 200 MB of free space.
If PSORT_DBTEMP is not set then the database server stores overflow data
in the /tmp or $GBS_HOME/tmp directory.
正在执行的排序不使用 dbspace 分区来存储溢出数据。溢出数据将写入临时操作系统文
件。
但是，数据库服务器无法为此类型创建临时操作系统文件。考虑将 PSORT_DBTEMP 环境变
量
设置为具有至少 200
MB 可用空间的安全目录。如果未设置 PSORT_DBTEMP，则数据库服务
器将溢出数据存储在 /tmp 或 $GBS_HOME/tmp 目录
中。
21525 Cannot write to a temporary operating system file during a sort
A sort was being performed that did not use a dbspace partition to store
overflow data. Overflow data is written to a temporary operating
system file. However, the database server could not write to this
temporary operating system file, most likely because the file directory
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2324 -
is out of space. The location of this file is in the path specified by
the PSORT_DBTEMP environment variable. If PSORT_DBTEMP is not set then
the database server puts these temporary files in the /tmp or
$GBS_HOME/tmp directory.
正在执行不使用 dbspace 分区存储溢出数据的排序。溢出数据写入临时操作系统文件。但
是，
数据库服务器无法写入此临时操作系统文件，这很可能是因为文件目录空间不足。此文件
的位
置位于 PSORT_DBTEMP 环境变量指定的路径中。如果未设置 PSORT_DBTEMP，则数据库服
务器将这些临时文件放在 /tmp 或 $GBS_HOME/tmp 目录中。
-21525 Cannot write to a temporary operating system file during a sort
A sort was being performed that did not use a dbspace partition to store
overflow data. Overflow data is written to a temporary operating
system file. However, the database server could not write to this
temporary operating system file, most likely because the file directory
is out of space. The location of this file is in the path specified by
the PSORT_DBTEMP environment variable. If PSORT_DBTEMP is not set then
the database server puts these temporary files in the /tmp or
$GBS_HOME/tmp directory.
正在执行不使用 dbspace 分区存储溢出数据的排序。溢出数据写入临时操作系统文件。但
是，
数据库服务器无法写入此临时操作系统文件，这很可能是因为文件目录空间不足。此文件
的位
置位于 PSORT_DBTEMP 环境变量指定的路径中。如果未设置 PSORT_DBTEMP，则数据库服
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2325 -
务器将这些临时文件放在 /tmp 或 $GBS_HOME/tmp 目录中。
21526 This log cannot be dropped, because the next log has an open transaction.
This error occurs when a log is requested to be dropped, but cannot be
because the next log contains the beginning of an open transaction. This log
is required to roll back that transaction, explicitly or implicitly during
long transaction abort. Also, the remaining log space might not be
sufficient to hold the rollback log records.
当请求删除日志时会发生此错误，但不能这样做，因为下一个日志包含打开事务的开始。
在长事务中止期间，要显式或隐式地回滚该事务，需要此日志。另外，剩余的日志空间
可能不足以保存回滚日志记录。
-21526 This log cannot be dropped, because the next log has an open transaction.
This error occurs when a log is requested to be dropped, but cannot be
because the next log contains the beginning of an open transaction. This log
is required to roll back that transaction, explicitly or implicitly during
long transaction abort. Also, the remaining log space might not be
sufficient to hold the rollback log records.
当请求删除日志时会发生此错误，但不能这样做，因为下一个日志包含打开事务的开始。
在长事务中止期间，要显式或隐式地回滚该事务，需要此日志。另外，剩余的日志空间
可能不足以保存回滚日志记录。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2326 -
21527 The partition could not be created because the dbspace is currently
unavailable.
The partition could not be created in the specified dbspace because that dbspace
is either disabled, in the process of being restored from a backup, or in the
process of being updated as part of fast recovery.
无法在指定的 dbspace 中创建分区，因为该 dbspace 在从备份还原的过程中，或者在作
为快速恢
复的一部分进行更新的过程中是禁用的。
Enable the dbspace or wait for it to complete its recovery, and then run the
command to create the partition again.
启用 dbspace 或等待它完成其恢复，然后运行命令再次创建分区。
-21527 The partition could not be created because the dbspace is currently
unavailable.
The partition could not be created in the specified dbspace because that dbspace
is either disabled, in the process of being restored from a backup, or in the
process of being updated as part of fast recovery.
无法在指定的 dbspace 中创建分区，因为该 dbspace 在从备份还原的过程中，或者在作
为快速恢
复的一部分进行更新的过程中是禁用的。
Enable the dbspace or wait for it to complete its recovery, and then run the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2327 -
command to create the partition again.
启用 dbspace 或等待它完成其恢复，然后运行命令再次创建分区。
-21542 GBase Global Security Kit (GSKit) library call failed.
A call into the GBase Global Security Kit (GSKit) library failed in an
unexpected manner.
对 GBase Global Security Kit (GSKit) 库的调用意外失败。
-21543 Encryption key not found.
An encrypted database server instance was unable to find the encryption key
necessary to perform encryption or decryption.
加密的数据库服务器实例无法找到执行加密或解密所需的加密密钥。
-21544 Attempt to encrypt data that is already encrypted.
An encrypted database server instance unexpectedly encountered data that
appears to be already encrypted while attempting to encrypt data.
加密的数据库服务器实例意外地遇到了在尝试加密数据时似乎已加密的数据。
-21545 Attempt to decrypt data that is not encrypted.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2328 -
An encrypted database server instance unexpectedly encountered data that
appears to be already unencrypted while attempting to decrypt data.
加密的数据库服务器实例意外地遇到了在尝试解密数据时似乎未加密的数据。
-21546 Error registering encryption key.
An encrypted database server instance encountered an error registering
the encryption key with the encryption/decryption subsystem. This may
indicate an illegal or corrupt encryption key. The associated data cannot
be encrypted or decrypted.
加密的数据库服务器实例遇到向加密/解密子系统注册加密密钥的错误。
这可能表示非法或
损坏的加密密钥。相关数据无法加密或解密。
-21547 Encryption of data failed.
An encrypted database server instance encountered an error encrypting
data.
加密的数据库服务器实例遇到加密数据的错误。
-21548 Decryption of data failed.
An encrypted database server instance encountered an error decrypting
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2329 -
data.
加密的数据库服务器实例遇到解密数据的错误。
-21549 Unable to initialize encryption cipher.
This error is raised by an encrypted database server instance. The server
was unable to initialize the encryption cipher due to an internal resource
constraint or because the encryption cipher is unsupported.
加密的数据库服务器实例引发此错误。由于内部资源限制或加密密码不受支持，服务器无
法初始化加密密码。
-21550 Error creating or accessing the Encryption Key Database.
An encrypted database server instance saves encryption keys in an
Encryption Key Database. If this error occurs when initializing a new
encrypted server instance (-i and -e options to oninit) or creating an
encrypted instance from an archive restore ("-E on" option to the restore),
the server encountered an error creating the Encryption Key Database. If
this error occurs when booting an existing server instance, the server
encountered an error accessing the Encryption Key Database.
Refer to the message log for additional information.
加密的数据库服务器实例将加密密钥保存在加密密钥数据库中。如果在初始化新的加密服
务
器实例（-i 和 -e 选项为 oninit）或从存档还原创建加密实例（还原的“-E on”选项）
时发生此错误，则服务器在创建加密时遇到错误密钥数据库。如果在引导现有服务器实例
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2330 -
时
发生此错误，则服务器在访问加密密钥数据库时遇到错误。有关其他信息，请参阅消息日
志。
-26014 Alter fragment on typed table is not allowed.
Alter fragment on table/index is not supported for typed table.
类型表不支持表/索引上的更改分片。
-26015 All fragments of the table or index need to be of same pagesize.
This error can occur on creating a fragmented table or index across dbspaces
of different pagesize. It can also occur while performing an ALTER FRAGMENT
on a table or index and the new dbspaces are of different pagesize than the
dbspaces in the existing fragmentation strategy. For an interval fragmented
table or index, this error can occur if the pagesize of the dbspaces in the
STORE IN clause is different from the pagesize of initial fragment dbspaces.
在跨不同页面大小的 dbspace 创建碎片表或索引时，可能会发生此错误。在对表或索引执
行
ALTER FRAGMENT 时也会发生这种情况，并且新 dbspace 的页面大小与现有分片策略中的
dbspace 不同。对于间隔分片表或索引，如果 STORE IN 子句中的 dbspace 的 pagesize
与初始分片 dbspace 的 pagesize 不同，则会发生此错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2331 -
-26016 Illegal leading byte 0x20 in Index name (index_name).
In some situations, such as when a constraint is defined, the database
server creates indexes internally. These indexes, by convention, always
have a leading ASCII blank (hex 20) as the first byte of their name. To
avoid a conflict, user-created indexes cannot have an ASCII blank (hex 20)
as the first byte of their name. Also, there can be no reference to indexes
with a leading blank in any user-issued statements. This rule is enforced
regardless of the locale. This rule is also enforced regardless of the use
of the DELIMIDENT environment variable.
在某些情况下，例如定义约束时，数据库服务器会在内部创建索引。按照惯例，这些索引
始终
具有前导 ASCII 空白（十六进制 20）作为其名称的第一个字节。为避免冲突，用户创建
的索
引不能将 ASCII 空格（十六进制 20）作为其名称的第一个字节。此外，在任何用户发出
的语
句中都不能引用带有前导空格的索引。无论语言环境如何，都会强制执行此规则。无论是
否使
用 DELIMIDENT 环境变量，都会强制执行此规则。
-26017 External indices are not supported with non-default pagesizes.
Virtual-Index Interface (VII) does not support creating index on non-default
pagesize dbspaces. This error can occur while creating a R-Tree index (which
is part of the server and internally implemented using VII), or when creating
any index which was implemented using VII.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2332 -
虚拟索引接口（VII）不支持在非默认的 pagesize dbspace 上创建索引。创建 R-Tree
索引（它是服务器的一部分并在内部使用 VII 实现）或创建使用 VII 实现的任何索引
时，可能会发生此错误。
32000 The rollback was caused by an unspecified reason.
This error is same as XA_RBROLLBACK in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBROLLBACK 相同。有关更多信息，请参阅
“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, the Resource Manager rolled back the transaction
branch for an unspecified reason. The Resource Manager did not commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
This value can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器未
提交代表事务分支完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有
持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回此值。
In the xa_end context, the Resource Manager marked the transaction branch
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2333 -
rollback-only for an unspecified reason. The Resource Manager has dissociated
the transaction branch from the thread of control and has marked rollback-only
the work performed on behalf of *xid.
在 xa_end 上下文中，资源管理器仅针对未指定的原因标记了事务分支回滚。资源管理器
已将事务
分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager rolled back the transaction
branch for an unspecified reason. The Resource Manager did not prepare to
commit the work done on behalf of the transaction branch. Upon return, the
Resource Manager has rolled back the branch's work and has released all held
resources.
在 xa_prepare 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器没有准
备代表事
务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager rolled back the transaction
branch for an unspecified reason. The Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器已回滚
事务分支
的工作并已释放所有持有的资源。当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager marked the transaction branch
rollback-only for an unspecified reason. The Resource Manager has not
associated the transaction branch with the thread of control and has
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2334 -
marked *xid rollback-only.
在 xa_start 上下文中，资源管理器标记了事务分支回滚 - 仅用于未指定的原因。
资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。
Also refer to the Resource Manager guide for more details.
也请参阅资源管理器指南以获取更多的信息。
-32000 The rollback was caused by an unspecified reason.
This error is same as XA_RBROLLBACK in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBROLLBACK 相同。有关更多信息，请参阅
“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, the Resource Manager rolled back the transaction
branch for an unspecified reason. The Resource Manager did not commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
This value can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器未提交代
表事务
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2335 -
分支完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。仅当
在标志中
设置了 TMONEPHASE 时，才能返回此值。
In the xa_end context, the Resource Manager marked the transaction branch
rollback-only for an unspecified reason. The Resource Manager has dissociated
the transaction branch from the thread of control and has marked rollback-only
the work performed on behalf of *xid.
在 xa_end 上下文中，资源管理器仅针对未指定的原因标记了事务分支回滚。资源管理器
已将事务
分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager rolled back the transaction
branch for an unspecified reason. The Resource Manager did not prepare to
commit the work done on behalf of the transaction branch. Upon return, the
Resource Manager has rolled back the branch's work and has released all held
resources.
在 xa_prepare 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器没有准
备代表事务
分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager rolled back the transaction
branch for an unspecified reason. The Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器因未指定的原因回滚事务分支。资源管理器已回滚
事务分支的
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2336 -
工作并已释放所有持有的资源。当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager marked the transaction branch
rollback-only for an unspecified reason. The Resource Manager has not
associated the transaction branch with the thread of control and has
marked *xid rollback-only.
在 xa_start 上下文中，资源管理器标记了事务分支回滚 - 仅用于未指定的原因。
资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。
Also refer to the Resource Manager guide for more details.
也请参阅资源管理器指南以获取更多的信息。
32001 The rollback was caused by a communication failure.
This error is same as XA_RBCOMMFAIL in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范标准中的 XA_RBCOMMFAIL 相同。有关更多信息，请参阅
“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
A communication failure occurred within the Resource Manager.
资源管理器内部发生通信失败。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2337 -
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已回
滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回
此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器没有准备提交代表事务分支完成的工作。
返回时，资源管理器已回滚了分支的工作，并释放了所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器回滚了事务分支的工作，并释放了所有持有
的资源。当分支已经标记为 ROLLBACK 时，通常会返回这些值。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2338 -
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器没有将事务分支与控制线程关联，而是标记
为 *xid rollback-only。
Also refer to the Resource Manager guide for more details.
可参阅资源管理器指南以获取更多的信息。
-32001 The rollback was caused by a communication failure.
This error is same as XA_RBCOMMFAIL in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范标准中的 XA_RBCOMMFAIL 相同。有关更多信息，请参阅
“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
A communication failure occurred within the Resource Manager.
资源管理器内部发生通信失败。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2339 -
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已回
滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回
此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回
滚代表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，Resource Manager 没有准备提交代表事务分支完成的工作。
返回时，资源管理器已回滚了分支的工作，并释放了所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，
资源管理器回滚了事务分支的工作，
并释放了所有持有的资源。
当分支已经标记为 ROLLBACK 时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2340 -
在 xa_start 上下文中，资源管理器没有将事务分支与控制线程关联，而是标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
可参阅资源管理器指南以获取更多的信息。
32002 The rollback was caused by a deadlock was detected.
This error is same as XA_RBDEADLOCK in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范中的 XA_RBDEADLOCK 相同。有关更多信息，请参阅
“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The Resource Manager detected a deadlock.
资源管理器检测到一个死锁。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2341 -
已回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能
返回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回
滚代表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。
返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2342 -
有关更多详细信息，另请参阅资源管理器指南。
-32002 The rollback was caused by a deadlock was detected.
This error is same as XA_RBDEADLOCK in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范中的 XA_RBDEADLOCK 相同。有关更多信息，请参阅
“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The Resource Manager detected a deadlock.
资源管理器检测到一个死锁。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已
回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2343 -
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。
返回后，资源管理器已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅资源管理器指南。
32003 A condition that violates the integrity of the resources was detected.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2344 -
This error is same as XA_RBINTEGRITY in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBINTEGRITY 相同。有关更多信息，请参阅
“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The Resource Manager detected a violation of the integrity of its resources.
资源管理器检测到违反其资源的完整性。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已回
滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返回
此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2345 -
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器已
回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅资源管理器指南。
-32003 A condition that violates the integrity of the resources was detected.
This error is same as XA_RBINTEGRITY in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2346 -
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBINTEGRITY 相同。有关更多信息，请参阅
“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The Resource Manager detected a violation of the integrity of its resources.
资源管理器检测到违反其资源的完整性。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已
回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2347 -
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅资源管理器指南。
32004 The Resource Manager rolled back the transaction branch for a reason not
on the XA rollback errors.
This error is same as XA_RBOTHER in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范标准中的 XA_RBOTHER 相同。有关更多信息，请参阅
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2348 -
“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, the Resource Manager rolled back the transaction
branch for a reason not on the XA rollback errors. The Resource Manager
did not commit the work done on behalf of the transaction branch. Upon return,
the Resource Manager has rolled back the branch's work and has released all
held resources. This value can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理器
未提交
代表事务分支完成的工作。返回后，资源管理器已回滚分支的工作并释放所有持有的资源。
仅当在标
志中设置了 TMONEPHASE 时，才能返回此值。
In the xa_end context, the Resource Manager marked the transaction branch
rollback-only for a reason not on the XA rollback errors. The Resource Manager
has dissociated the transaction branch from the thread of control and has
marked rollback-only the work performed on behalf of *xid.
在 xa_end 上下文中，资源管理器将事务分支标记为仅回滚，原因不在于 XA 回滚错误。
资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager rolled back the transaction
branch for a reason not on the XA rollback errors. The Resource Manager did
not prepare to commit the work done on behalf of the transaction branch. Upon
return, the Resource Manager has rolled back the branch's work and has released
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2349 -
all held resources.
在 xa_prepare 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理
器没有准备
代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有
的资源。
In the xa_rollback context, the Resource Manager rolled back the transaction
branch for a reason not on the XA rollback errors. The Resource Manager has
rolled back the transaction branch's work and has released all held resources.
These values are typically returned when the branch was already marked
rollback-only.
在 xa_rollback 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理
器已回滚
事务分支的工作并已释放所有持有的资源。当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager marked the transaction branch
rollback-only for a reason not on the XA rollback errors. The Resource Manager
has not associated the transaction branch with the thread of control and has
marked *xid rollback-only.
在 xa_start 上下文中，资源管理器将事务分支标记为仅回滚，原因不在于 XA 回滚错误。
资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32004 The Resource Manager rolled back the transaction branch for a reason not
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2350 -
on the XA rollback errors.
This error is same as XA_RBOTHER in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范标准中的 XA_RBOTHER 相同。有关更多信息，请参阅“分布式事
务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, the Resource Manager rolled back the transaction
branch for a reason not on the XA rollback errors. The Resource Manager
did not commit the work done on behalf of the transaction branch. Upon return,
the Resource Manager has rolled back the branch's work and has released all
held resources. This value can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理器
未提交代表
事务分支完成的工作。返回后，资源管理器已回滚分支的工作并释放所有持有的资源。仅
当在标志中
设置了 TMONEPHASE 时，才能返回此值。
In the xa_end context, the Resource Manager marked the transaction branch
rollback-only for a reason not on the XA rollback errors. The Resource Manager
has dissociated the transaction branch from the thread of control and has
marked rollback-only the work performed on behalf of *xid.
在 xa_end 上下文中，资源管理器将事务分支标记为仅回滚，原因不在于 XA 回滚错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2351 -
资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager rolled back the transaction
branch for a reason not on the XA rollback errors. The Resource Manager did
not prepare to commit the work done on behalf of the transaction branch. Upon
return, the Resource Manager has rolled back the branch's work and has released
all held resources.
在 xa_prepare 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理
器没有准备
代表事务分支提交完成的工作。返回后，资源管理器已回滚分支的工作并已释放所有持有
的资源。
In the xa_rollback context, the Resource Manager rolled back the transaction
branch for a reason not on the XA rollback errors. The Resource Manager has
rolled back the transaction branch's work and has released all held resources.
These values are typically returned when the branch was already marked
rollback-only.
在 xa_rollback 上下文中，资源管理器回滚事务分支的原因不是 XA 回滚错误。资源管理
器已回滚
事务分支的工作并已释放所有持有的资源。当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager marked the transaction branch
rollback-only for a reason not on the XA rollback errors. The Resource Manager
has not associated the transaction branch with the thread of control and has
marked *xid rollback-only.
资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid rollback-only。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2352 -
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32005 A protocol error occurred in the Resource Manager.
This error is same as XA_RBPROTO in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBPROTO 相同。有关更多信息，请参阅
“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
A protocol error occurred within the Resource Manager.
资源管理器中发生协议错误。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已
回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返
回此值。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2353 -
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标
记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2354 -
-32005 A protocol error occurred in the Resource Manager.
This error is same as XA_RBPROTO in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBPROTO 相同。有关更多信息，请参阅 “分布式
事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
A protocol error occurred within the Resource Manager.
资源管理器中发生协议错误。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已
回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2355 -
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代
表 *xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32006 The rollback was caused by a transaction branch took too long.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2356 -
This error is same as XA_RBTIMEOUT in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBTIMEOUT 相同。有关更多信息，请参阅 “分布
式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The work represented by this transaction branch took too long.
此事务分支所代表的工作耗时太长。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已
回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，
资源管理器已将事务分支与控制线程分离，
并标记了仅回滚代表*xid
执行的工作.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2357 -
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32006 The rollback was caused by a transaction branch took too long.
This error is same as XA_RBTIMEOUT in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2358 -
The XA Specification".
此错误与 X/OPEN
XA 规范标准中的 XA_RBTIMEOUT 相同。有关更多信息，请参阅“分布式
事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The work represented by this transaction branch took too long.
此事务分支所代表的工作耗时太长。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器未提交代表事务分支完成的工作。返回后，资源管理
器已
回滚分支的工作并已释放所有持有的资源。仅当在标志中设置了 TMONEPHASE 时，才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，
资源管理器已将事务分支与控制线程分离，
并标记了仅回滚代表*xid
执行的工作.
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2359 -
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32007 The Resource Manager detected transient error.
This error is same as XA_RBTRANSIENT in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN
XA 规范标准中的 XA_RBTRANSIENT 相同。有关更多信息，请参阅“分布
式事务处理：XA 规范”。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2360 -
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The Resource Manager has detected a transient error.
资源管理器检测到一个瞬间错误。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器没有提交代表事务分支完成的工作。返回时，资源管
理器
已回滚分支的工作，并释放了所有持有的资源。只有在 TMONEPHASE 设置为标志时才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2361 -
In the xa_rollback context, the Resource Manager has rolled back the
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32007 The Resource Manager detected transient error.
This error is same as XA_RBTRANSIENT in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RBTRANSIENT 相同。
有关更多信息，请参阅“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2362 -
The Resource Manager detected a transient error.
资源管理器检测到一个瞬间错误。
In the xa_commit context, the Resource Manager did not commit the work done
on behalf of the transaction branch. Upon return, the Resource Manager has
rolled back the branch's work and has released all held resources. This value
can be returned only if TMONEPHASE is set in flags.
在 xa_commit 上下文中，资源管理器没有提交代表事务分支完成的工作。返回时，资源管
理器
已回滚分支的工作，并释放了所有持有的资源。只有在 TMONEPHASE 设置为标志时才能返
回此值。
In the xa_end context, the Resource Manager has dissociated the transaction
branch from the thread of control and has marked rollback-only the work
performed on behalf of *xid.
在 xa_end 上下文中，资源管理器已将事务分支与控制线程分离，并标记了仅回滚代表
*xid 执行的工作。
In the xa_prepare context, the Resource Manager did not prepare to commit the
work done on behalf of the transaction branch. Upon return, the Resource
Manager has rolled back the branch's work and has released all held resources.
在 xa_prepare 上下文中，资源管理器未准备代表事务分支提交完成的工作。返回后，资
源管理器
已回滚分支的工作并已释放所有持有的资源。
In the xa_rollback context, the Resource Manager has rolled back the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2363 -
transaction branch's work and has released all held resources. These values
are typically returned when the branch was already marked rollback-only.
在 xa_rollback 上下文中，资源管理器已回滚事务分支的工作并已释放所有保留的资源。
当分支已标记为仅回滚时，通常会返回这些值。
In the xa_start context, the Resource Manager has not associated the
transaction branch with the thread of control and has marked *xid rollback-only.
在 xa_start 上下文中，资源管理器尚未将事务分支与控制线程相关联，并标记为 *xid
rollback-only。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32009 Routine returned with no effect and may be re-issued.
This error is same as XA_RETRY in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN
XA 规范标准中的 XA_RETRY 相同。有关更多信息，请参阅“分布式事务
处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, the Resource Manager is not able to commit the
transaction branch at this time. This value can be returned when a blocking
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2364 -
condition exists and TMNOWAIT was set. Note, however, that this value can
also be returned even when TMNOWAIT is not set (for example, if the necessary
stable storage is currently unavailable). This value cannot be returned if
TMONEPHASE is set in flags. All resources held on behalf of *xid remain in a
prepared state until commitment is possible. The Transaction Manager should
re-issue xa_commit at a later time.
在 xa_commit 上下文中，资源管理器此时无法提交事务分支。当存在阻塞条件并设置
TMNOWAIT 时，
可以返回此值。但请注意，即使未设置 TMNOWAIT，也可以返回此值（例如，如果必要的稳
定存储当
前不可用）。如果在标志中设置了 TMONEPHASE，则无法返回此值。代表 *xid 持有的所有
资源仍然
处于准备状态，直到可以提交。事务管理器应该在以后重新发出 xa_commit。
In the xa_complete context, TMNOWAIT was set in flags and no asynchronous
operation has completed.
在 xa_complete 上下文中，TMNOWAIT 在标志中设置，并且没有完成异步操作。
In the xa_start context, TMNOWAIT was set in flags and a blocking condition
exists.
在 xa_start 上下文中，TMNOWAIT 在标志中设置并且存在阻塞条件。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32009 Routine returned with no effect and may be re-issued.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2365 -
This error is same as XA_RETRY in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_RETRY 相同。
有关更多信息，请参阅“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, the Resource Manager is not able to commit the
transaction branch at this time. This value can be returned when a blocking
condition exists and TMNOWAIT was set. Note, however, that this value can
also be returned even when TMNOWAIT is not set (for example, if the necessary
stable storage is currently unavailable). This value cannot be returned if
TMONEPHASE is set in flags. All resources held on behalf of *xid remain in a
prepared state until commitment is possible. The Transaction Manager should
re-issue xa_commit at a later time.
在 xa_commit 上下文中，资源管理器此时无法提交事务分支。当存在阻塞条件并设置
TMNOWAIT 时，
可以返回此值。但请注意，即使未设置 TMNOWAIT，也可以返回此值（例如，如果必要的稳
定存储当
前不可用）。如果在标志中设置了 TMONEPHASE，则无法返回此值。代表 *xid 持有的所有
资源仍然
处于准备状态，直到可以提交。事务管理器应该在以后重新发出 xa_commit。
In the xa_complete context, TMNOWAIT was set in flags and no asynchronous
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2366 -
operation has completed.
在 xa_complete 上下文中，TMNOWAIT 在标志中设置，并且没有完成异步操作。
In the xa_start context, TMNOWAIT was set in flags and a blocking condition
exists.
在 xa_start 上下文中，TMNOWAIT 在标志中设置并且存在阻塞条件。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32010 The transaction branch has been heuristically committed and rolled back.
This error is same as XA_HEURMIX in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURMIX 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was partially committed and
partially rolled back.
在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并部
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2367 -
分回滚。
In the xa_rollback context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was partially committed and
partially rolled back. A Resource Manager can return this value only if it
has successfully prepared *xid.
在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并
部分回滚。
仅当资源管理器成功准备好 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32010 The transaction branch has been heuristically committed and rolled back.
This error is same as XA_HEURMIX in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURMIX 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, due to a heuristic decision, the work done on
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2368 -
behalf of the specified transaction branch was partially committed and
partially rolled back.
在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并部
分回滚。
In the xa_rollback context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was partially committed and
partially rolled back. A Resource Manager can return this value only if it
has successfully prepared *xid.
在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被部分提交并
部分回滚。
仅当资源管理器成功准备好 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32011 The transaction branch has been heuristically rolled back.
This error is same as XA_HEURRB in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURRB 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2369 -
In the xa_commit context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was rolled back.
在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。
In the xa_rollback context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was rolled back. A Resource
Manager can return this value only if it has successfully prepared *xid.
在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。
仅当资源管理器已成功准备 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32011 The transaction branch has been heuristically rolled back.
This error is same as XA_HEURRB in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURRB 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2370 -
In the xa_commit context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was rolled back.
在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。
In the xa_rollback context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was rolled back. A Resource
Manager can return this value only if it has successfully prepared *xid.
在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作被回滚。
仅当资源管理器已成功准备 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32012 The transaction branch has been heuristically committed.
This error is same as XA_HEURCOM in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURCOM 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, due to a heuristic decision, the work done on
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2371 -
behalf of the specified transaction branch was committed.
在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。
In the xa_rollback context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was committed. A Resource
Manager can return this value only if it has successfully prepared *xid.
在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。
仅当资源管理器已成功准备 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32012 The transaction branch has been heuristically committed.
This error is same as XA_HEURCOM in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURCOM 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was committed.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2372 -
在 xa_commit 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。
In the xa_rollback context, due to a heuristic decision, the work done on
behalf of the specified transaction branch was committed. A Resource
Manager can return this value only if it has successfully prepared *xid.
在 xa_rollback 上下文中，由于启发式决策，代表指定事务分支完成的工作已提交。
仅当资源管理器已成功准备 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32013 The transaction branch might have been heuristically completed.
This error is same as XA_HEURHAZ in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURHAZ 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, due to some failure, the work done on behalf of
the specified transaction branch might have been heuristically completed.
在 xa_commit 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完成
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2373 -
的。
In the xa_rollback context, due to some failure, the work done on behalf of
the specified transaction branch might have been heuristically completed. A
Resource Manager can return this value only if it has successfully prepared
*xid.
在 xa_rollback 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完
成的。
仅当资源管理器已成功准备 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32013 The transaction branch might have been heuristically completed.
This error is same as XA_HEURHAZ in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_HEURHAZ 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit context, due to some failure, the work done on behalf of
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2374 -
the specified transaction branch might have been heuristically completed.
在 xa_commit 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完成
的。
In the xa_rollback context, due to some failure, the work done on behalf of
the specified transaction branch might have been heuristically completed. A
Resource Manager can return this value only if it has successfully prepared
*xid.
在 xa_rollback 上下文中，由于某些失败，代表指定事务分支完成的工作可能是启发式完
成的。
仅当资源管理器已成功准备 *xid 时，它才能返回此值。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32014 Resumption must occur where suspension occurred.
This error is same as XA_NOMIGRATE in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_NOMIGRATE 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2375 -
In the xa_end context, the Resource Manager was unable to prepare the
transaction context for migration. However, the Resource Manager has
suspended the association. The Transaction Manager can resume the
association only in the current thread. This code can be returned only
when both TMSUSPEND and TMMIGRATE are set in flags. A Resource Manager
that sets TMNOMIGRATE in the flags element of its xa_switch_t structure
need not return [XA_NOMIGRATE].
在 xa_end 上下文中，资源管理器无法为迁移准备事务上下文。但是，资源管理器已暂停
该关联。
事务管理器只能在当前线程中恢复关联。
仅当在标志中设置 TMSUSPEND 和 TMMIGRATE 时，
才
能返回此代码。
在其 xa_switch_t 结构的 flags 元素中设置 TMNOMIGRATE 的资源管理器
不需要返回 [XA_NOMIGRATE]。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32014 Resumption must occur where suspension occurred.
This error is same as XA_NOMIGRATE in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XA_NOMIGRATE 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2376 -
根据 X/OPEN XA 规范标准：
In the xa_end context, the Resource Manager was unable to prepare the
transaction context for migration. However, the Resource Manager has
suspended the association. The Transaction Manager can resume the
association only in the current thread. This code can be returned only
when both TMSUSPEND and TMMIGRATE are set in flags. A Resource Manager
that sets TMNOMIGRATE in the flags element of its xa_switch_t structure
need not return [XA_NOMIGRATE].
在 xa_end 上下文中，资源管理器无法为迁移准备事务上下文。但是，资源管理器已暂停
该关联。
事务管理器只能在当前线程中恢复关联。
仅当在标志中设置 TMSUSPEND 和 TMMIGRATE 时，
才
能返回此代码。
在其 xa_switch_t 结构的 flags 元素中设置 TMNOMIGRATE 的资源管理器
不需要返回 [XA_NOMIGRATE]。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32015 Asynchronous operation already outstanding.
This error is same as XAER_ASYNC in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范标准中的 XAER_ASYNC 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2377 -
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
TMASYNC was set in flags, and either the maximum number of outstanding
asynchronous operations has been exceeded, or TMUSEASYNC is not set in the
flags element of the Resource Manager's xa_switch_t structure.
TMASYNC 是在标志中设置的，并且超过了未完成的异步操作的最大数量，或者 TMUSEASYNC
没有在资源管理器的 xa_Switch_t 结构的标志元素中设置。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32015 Asynchronous operation already outstanding.
This error is same as XAER_ASYNC in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPENXA 规范标准中的 XAER_ASYNC 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
TMASYNC was set in flags, and either the maximum number of outstanding
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2378 -
asynchronous operations has been exceeded, or TMUSEASYNC is not set in the
flags element of the Resource Manager's xa_switch_t structure.
TMASYNC 是在标志中设置的，并且超过了未完成的异步操作的最大数量，或者 TMUSEASYNC
没有在资源管理器的 xa_Switch_t 结构的标志元素中设置。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32016 An Resource Manager error occurred in the transaction branch.
This error is same as XAER_RMERR in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_RMERR 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_close context, an error occurred when closing the resource.
在 xa_close 上下文中，关闭资源时发生错误。
有关更多详细信息，另请参阅“资源管理器”指南
In the xa_commit context, an error occurred in committing the work performed
on behalf of the transaction branch and the branch's work has been rolled back.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2379 -
Note that returning this error signals a catastrophic event to a Transaction
Manager because other Resource Managers might successfully commit their work on
behalf of this branch. This error should be returned only when a Resource
Manager concludes that it can never commit the branch and that it cannot hold
the branch's resources in a prepared state. Otherwise, [XA_RETRY] should be
returned.
在 xa_commit 上下文中，在提交代表事务分支执行的工作时发生错误，并且已回滚分支的
工作。
请注意，返回此错误意味着事务管理器发生灾难性事件，因为其他资源管理器可能代表此
分支成
功提交其工作。仅当资源管理器断定它永远不能提交分支并且不能将分支的资源保持在准
备状态
时，才应返回此错误。否则，应返回 [XA_RETRY]。
In the xa_end context, an error occurred in dissociating the transaction
branch from the thread of control.
在 xa_end 上下文中，在将事务分支与控制线程分离时发生错误。
In the xa_forget context, an error occurred in the Resource Manager and the
Resource Manager has not forgotten the transaction branch.
在 xa_forget 上下文中，资源管理器中发生错误，资源管理器未忘记事务分支。
In the xa_open context, an error occurred when opening the resource.
在 xa_open 上下文中，打开资源时发生错误。
In the xa_prepare context, the Resource Manager encountered an error in
preparing to commit the transaction branch's work. The specified XID might or
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2380 -
might not have been prepared.
在 xa_prepare 上下文中，资源管理器在准备提交事务分支的工作时遇到错误。
指定的 XID 可能已准备好，也可能未准备好。
In the xa_recover context, an error occurred in determining the XIDs to return.
在 xa_recover 上下文中，确定要返回的 XID 时发生错误。
In the xa_rollback context, an error occurred in rolling back the transaction
branch. The Resource Manager is free to forget about the branch when returning
this error so long as all accessing threads of control have been notified of
the branch's state.
在 xa_rollback 上下文中，回滚事务分支时发生错误。资源管理器在返回此错误时可以自
由地忘记分支，
只要所有访问控制线程都已被通知分支的状态。
In the xa_start context, an error occurred in associating the transaction
branch with the thread of control.
在 xa_start 上下文中，将事务分支与控制线程相关联时发生错误。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32016 An Resource Manager error occurred in the transaction branch.
This error is same as XAER_RMERR in the X/OPEN XA Specification Standard.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2381 -
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_RMERR 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_close context, an error occurred when closing the resource.
在 xa_close 上下文中，关闭资源时发生错误。
In the xa_commit context, an error occurred in committing the work performed
on behalf of the transaction branch and the branch's work has been rolled back.
Note that returning this error signals a catastrophic event to a Transaction
Manager because other Resource Managers might successfully commit their work on
behalf of this branch. This error should be returned only when a Resource
Manager concludes that it can never commit the branch and that it cannot hold
the branch's resources in a prepared state. Otherwise, [XA_RETRY] should be
returned.
在 xa_commit 上下文中，在提交代表事务分支执行的工作时发生错误，并且已回滚分支的
工作。
请注意，返回此错误意味着事务管理器发生灾难性事件，因为其他资源管理器可能代表此
分支成
功提交其工作。仅当资源管理器断定它永远不能提交分支并且不能将分支的资源保持在准
备状态
时，才应返回此错误。否则，应返回 [XA_RETRY]。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2382 -
In the xa_end context, an error occurred in dissociating the transaction
branch from the thread of control.
在 xa_end 上下文中，在将事务分支与控制线程分离时发生错误。
In the xa_forget context, an error occurred in the Resource Manager and the
Resource Manager has not forgotten the transaction branch.
在 xa_forget 上下文中，资源管理器中发生错误，资源管理器未忘记事务分支。
In the xa_open context, an error occurred when opening the resource.
在 xa_open 上下文中，打开资源时发生错误。
In the xa_prepare context, the Resource Manager encountered an error in
preparing to commit the transaction branch's work. The specified XID might or
might not have been prepared.
在 xa_prepare 上下文中，资源管理器在准备提交事务分支的工作时遇到错误。
指定的 XID 可能已准备好，也可能未准备好。
In the xa_recover context, an error occurred in determining the XIDs to return.
在 xa_recover 上下文中，确定要返回的 XID 时发生错误。
In the xa_rollback context, an error occurred in rolling back the transaction
branch. The Resource Manager is free to forget about the branch when returning
this error so long as all accessing threads of control have been notified of
the branch's state.
在 xa_rollback 上下文中，回滚事务分支时发生错误。资源管理器在返回此错误时可以自
由地忘记分支，
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2383 -
只要所有访问控制线程都已被通知分支的状态。
In the xa_start context, an error occurred in associating the transaction
branch with the thread of control.
在 xa_start 上下文中，将事务分支与控制线程相关联时发生错误。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32017 The XID is not valid.
This error is same as XAER_NOTA in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_NOTA 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit, xa_end, xa_prepare, xa_rollback context, the specified XID is
not known by the Resource Manager.
在 xa_commit、xa_end、xa_prepare、xa_rollback 上下文中，资源管理器不知道指定的
xid。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2384 -
In the xa_forget context, the specified XID is not known by the Resource
Manager as a heuristically completed XID.
在 xa_forget 上下文中，资源管理器不知道指定的 XID 是启发式完成的 XID。
In the xa_start context, either TMRESUME or TMJOIN was set in flags, and the
specified XID is not known by the Resource Manager.
在 xa_start 上下文中，在标志中设置了 TMRESUME 或 TMJOIN，并且资源管理器不知道指
定的 XID。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32017 The XID is not valid.
This error is same as XAER_NOTA in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_NOTA 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit, xa_end, xa_prepare, xa_rollback context, the specified XID is
not known by the Resource Manager.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2385 -
在 xa_commit、xa_end、xa_prepare、xa_rollback 上下文中，资源管理器不知道指定的
xid。
In the xa_forget context, the specified XID is not known by the Resource
Manager as a heuristically completed XID.
在 xa_forget 上下文中，资源管理器不知道指定的 XID 是启发式完成的 XID。
In the xa_start context, either TMRESUME or TMJOIN was set in flags, and the
specified XID is not known by the Resource Manager.
在 xa_start 上下文中，在标志中设置了 TMRESUME 或 TMJOIN，并且资源管理器不知道指
定的 XID。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32018 Invalid arguments were given.
This error is same as XAER_INVAL in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_INVAL 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2386 -
In the xa_close, xa_commit, xa_complete, xa_end, xa_forget, xa_open,
xa_prepare, xa_rollback, or xa_start context, invalid arguments were specified.
在 xa_close、xa_commit、xa_complete、xa_end、xa_forget、xa_open、xa_prepare、
xa_rollback 或 xa_start 上下文中，指定了无效参数。
In the xa_recover context, the pointer xids is NULL and count is greater
than 0, count is negative, or an invalid flags was specified, or the thread of
control does not have a recovery scan open and did not specify TMSTARTRSCAN
in flags.
在 xa_recover 上下文中，指针 xids 为 NULL 并且 count 大于0、count为负数、
或者指定了无效标志，或者控制线程没有打开恢复扫描并且未在 flags 中指定
TMSTARTRSCAN。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32018 Invalid arguments were given.
This error is same as XAER_INVAL in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_INVAL 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2387 -
根据 X/OPEN XA 规范标准：
In the xa_close, xa_commit, xa_complete, xa_end, xa_forget, xa_open,
xa_prepare, xa_rollback, or xa_start context, invalid arguments were specified.
在 xa_close、xa_commit、xa_complete、xa_end、xa_forget、xa_open、xa_prepare、
xa_rollback 或 xa_start 上下文中，指定了无效参数。
In the xa_recover context, the pointer xids is NULL and count is greater
than 0, count is negative, or an invalid flags was specified, or the thread of
control does not have a recovery scan open and did not specify TMSTARTRSCAN
in flags.
在 xa_recover 上下文中，指针 xids 为 NULL 并且 count 大于 0、count 为负数、或
者指定了无效标志，或者控制线程没有打开恢复扫描并且未在 flags 中指定
TMSTARTRSCAN。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32019 Routine invoked in improper context.
This error is same as XAER_PROTO in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_PROTO 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2388 -
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The routine was invoked in an improper context.
在不正确的上下文中调用该例程。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32019 Routine invoked in improper context.
This error is same as XAER_PROTO in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_PROTO 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
The routine was invoked in an improper context.
在不正确的上下文中调用该例程。
Also refer to the Resource Manager guide for more details.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2389 -
有关更多详细信息，另请参阅“资源管理器”指南。
32020 Resource Manager unavailable.
This error is same as XAER_RMFAIL in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_RMFAIL 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit, xa_end, xa_forget, xa_recover, xa_rollback, xa_start context,
An error occurred that makes the Resource Manager unavailable.
在 xa_commit、xa_end、xa_forget、xa_recover、xa_rollback、xa_start 上下文中，
发生了使资源管理器不可用的错误。
In the xa_prepare context, an error occurred that makes the Resource Manager
unavailable. The specified XID might or might not have been prepared.
在 xa_prepare 上下文中，发生了使资源管理器不可用的错误。
指定的 XID 可能已准备好，也可能未准备好。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2390 -
-32020 Resource Manager unavailable.
This error is same as XAER_RMFAIL in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_RMFAIL 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_commit, xa_end, xa_forget, xa_recover, xa_rollback, xa_start context,
An error occurred that makes the Resource Manager unavailable.
在 xa_commit、xa_end、xa_forget、xa_recover、xa_rollback、xa_start 上下文中，
发生了使资源管理器不可用的错误。
In the xa_prepare context, an error occurred that makes the Resource Manager
unavailable. The specified XID might or might not have been prepared.
在 xa_prepare 上下文中，发生了使资源管理器不可用的错误。
指定的 XID 可能已准备好，也可能未准备好。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2391 -
32021 The XID already exists.
This error is same as XAER_DUPID in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_DUPID 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_start context, if neither TMRESUME nor TMJOIN was set in flags
(indicating the initial use of *xid) and the XID already exists within the
Resource Manager, the Resource Manager must return [XAER_DUPID]. The Resource
Manager failed to associate the transaction branch with the thread of control.
在 xa_start 上下文中，如果在 flag 中未设置 TMRESUME 和 TMJOIN（表示初始使用
*xid）
并且资源管理器中已存在 XID，则资源管理器必须返回[XAER_DUPID]。资源管理器无法将
事
务分支与控制线程相关联。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32021 The XID already exists.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2392 -
This error is same as XAER_DUPID in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_DUPID 相同。
有关更多信息，请参阅“分布式事务处理：XA规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_start context, if neither TMRESUME nor TMJOIN was set in flags
(indicating the initial use of *xid) and the XID already exists within the
Resource Manager, the Resource Manager must return [XAER_DUPID]. The Resource
Manager failed to associate the transaction branch with the thread of control.
在 xa_start 上下文中，如果在 flag 中未设置 TMRESUME 和 TMJOIN（表示初始使用
*xid）
并且资源管理器中已存在 XID，则资源管理器必须返回[XAER_DUPID]。资源管理器无法将
事
务分支与控制线程相关联。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32022 Resource Manager doing work outside global transaction.
This error is same as XAER_OUTSIDE in the X/OPEN XA Specification Standard.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2393 -
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_OUTSIDE 相同。
有关更多信息，请参阅“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
In the xa_start context, the Resource Manager is doing work outside any global
transaction on behalf of the application.
在 xa_start 上下文中，资源管理器代表应用程序在任何全局事务之外工作。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
-32022 Resource Manager doing work outside global transaction.
This error is same as XAER_OUTSIDE in the X/OPEN XA Specification Standard.
For more information, refer to the "Distributed Transaction Processing:
The XA Specification".
此错误与 X/OPEN XA 规范标准中的 XAER_OUTSIDE 相同。
有关更多信息，请参阅“分布式事务处理：XA 规范”。
According to the X/OPEN XA Specification Standard :
根据 X/OPEN XA 规范标准：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2394 -
In the xa_start context, the Resource Manager is doing work outside any global
transaction on behalf of the application.
在 xa_start 上下文中，资源管理器代表应用程序在任何全局事务之外工作。
Also refer to the Resource Manager guide for more details.
有关更多详细信息，另请参阅“资源管理器”指南。
32023 Error in executing an xadatasource purpose routine execution sequence.
An error occurred when an attempt was made to execute an xadatasource purpose
routine. Try the statement again.
当尝试执行 xadatasource 用途的例程时，发生了错误。重新执行该语句。
-32023 Error in executing an xadatasource purpose routine execution sequence.
An error occurred when an attempt was made to execute an xadatasource purpose
routine. Try the statement again.
当尝试执行 xadatasource 用途的例程时，发生了错误。重新执行该语句。
32024 Error indicated by an xadatasource purpose routine.
An xadatasource purpose routine returned MI_ERROR.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2395 -
xadatasource 目的例程返回 MI_ERROR。
-32024 Error indicated by an xadatasource purpose routine.
An xadatasource purpose routine returned MI_ERROR.
xadatasource 目的例程返回 MI_ERROR。
32025 Improper return value from xadatasource purpose routine.
An xadatasource purpose routine returned a value that is not valid. Possibly a
bug exists in the xadatasource purpose routine.
xadatasource 目的例程返回的值无效。可能是因为 xadatasource 目的例程存在问题。
-32025 Improper return value from xadatasource purpose routine.
An xadatasource purpose routine returned a value that is not valid. Possibly a
bug exists in the xadatasource purpose routine.
xadatasource 目的例程返回的值无效。可能是因为 xadatasource 目的例程存在问题。
-26018 Table %s has a referential key constraint and is not empty.
The table being truncated has a unique or primary key that is referenced by
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2396 -
the above table.
被截断的表具有由上面的表引用的唯一或主键。
-26019 Purpose function am_truncate not defined for table or index.
The am_truncate purpose function is not defined for the VTI table or
a VII index on the table being truncated.
没有为要截断的表上的 VTI 表或 VII 索引定义 am_truncate 用途函数。
-26020 Truncating a table with delete trigger requires ALTER privilege.
You cannot truncate a table that has delete triggers unless you have ALTER
privilege. A user with DELETE privilege can truncate such a table only
if there are no delete triggers active.
除非您具有 ALTER 权限，否则不能截断具有删除触发器的表。具有 DELETE 权限的用户
只有在没有活动的删除触发器时才能截断此类表。
-26021 No operations allowed after truncate or online alter fragment in a
transaction.
The only allowed operations in a transaction after a truncate or online alter
fragment are COMMIT and ROLLBACK.
在截断或在线更改分片之后，事务中唯一允许的操作是 COMMIT 和 ROLLBACK。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2397 -
-26022 EXTERNAL NAME too long.
The EXTERNAL NAME clause of the CREATE FUNCTION or CREATE PROCEDURE
cannot contain more than 255 characters.
CREATE FUNCTION 或 CREATE PROCEDURE 的 EXTERNAL NAME 子句不能包含超
过 255 个字符。
26023 Cannot perform rename operation while non-mastered or strict mastered --
column and table names must match along with data types across all replicate
participants -- replicates are defined for it
Rename table and column operations are allowed only on Enterprise Replication
tables that are defined with non-strict mastered replicates.
With non-strict mastered replicates, column names can be different but
column data types must match. Non-strict mastered replicates can be defined
with --name=n attribute of 'cdr define repl' or with 'cdr modify repl' commands.
For more information about non-strict mastered replicates, mastered replicates
and non-mastered replicates see Enterprise Replication Manual.
只有在使用非严格主复制定义的 Enterprise
Replication 表上才允许重命名表和列操作。
对于非严格的主复制，
列名可以不同，但列数据类型必须匹配。非严格主复制可以用 ‘cdr define repl’的
--name=n
属性来定义，也可以用‘cdr modify repl’ 命令来定义。有关非严格主复制、主复制和
不是主复
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2398 -
制的详细信息，请参阅《Enterprise Replication 手册》。
-26023 Cannot perform rename operation while non-mastered or strict mastered --
column and table names must match along with data types across all replicate
participants -- replicates are defined for it
Rename table and column operations are allowed only on Enterprise Replication
tables that are defined with non-strict mastered replicates.
With non-strict mastered replicates, column names can be different but
column data types must match. Non-strict mastered replicates can be defined
with --name=n attribute of 'cdr define repl' or with 'cdr modify repl' commands.
For more information about non-strict mastered replicates, mastered replicates
and non-mastered replicates see Enterprise Replication Manual.
只有在使用非严格主复制定义的 Enterprise
Replication 表上才允许重命名表和列操作。
对于非严格的主复制，
列名可以不同，但列数据类型必须匹配。非严格主复制可以用 ‘cdr define repl’的
--name=n
属性来定义，也可以用‘cdr modify repl’ 命令来定义。有关非严格主复制、主复制和
不是主复
制的详细信息，请参阅《Enterprise Replication 手册》。
-26024 The sysdbopen and sysdbclose routines cannot have arguments or return
values.
The SPL routines sysdbopen and sysdbclose must be defined without any arguments
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2399 -
or return values.
SPL 例程 sysdbopen 和 sysdblose 必须在没有任何参数或返回值的情况下定义。
-26025 SELECT FROM INSERT syntax is disallowed in this context.
SELECT FROM INSERT syntax is not allowed in the following cases
不允许在以下情况下使用 SELECT FROM INSERT 语法
* SELECT statement is part of join or is nested as a subquery.
SELECT 语句是连接的一部分或它嵌套为子查询。
* SELECT statement is part of CREATE VIEW statement.
SELECT 语句是 CREATE VIEW 语句的一部分。
* SELECT statement appears as a subquery either in query predicates or
projection
list.
SELECT 语句作为子查询春夏在查询预备或投影列表中。
* SELECT statement appears as part of INSERT INTO SELECT statement.
SELECT 语句作为 INSERT INTO SELECT 语句的一部分。
-26026 Remote
table
reference
in
INSERT
statement
disallowed
in
SELECT
FROM
INSERT
syntax.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2400 -
SELECT FROM INSERT statement does not support remote object references in the
INSERT part of statement. Please rewrite the query so that there are no remote
object references in the INSERT part of the statement.
SELECT FROM INSERT 语句不支持语句的 INSERT 部分中的远程对象引用。
请重写查询，在语句的 INSERT 部分中不要出现远程对象引用。
-26027 Label label-name specified on a GOTO statement is not valid.
An undefined or invalid label is used with the GOTO statement.
The GOTO label must be defined within the same procedure.
Check the label-name for correct spelling.
未定义或无效的标签与 GOTO 语句一起使用。必须在同一程序中定义 GOTO 标签。
检查 label-name 是否正确拼写。
-26028 Label label-name must be unique within an SPL procedure.
The scope of the label-name is a procedure, so the label names must be unique
between the CREATE [PROCEDURE|FUNCTION] and END [PROCEDURE|FUNCTION] keywords.
label-name 的范围是一个过程，因此标签名称在 CREATE [PROCEDURE | FUNCTION] 和
END [PROCEDURE | FUNCTION] 关键字之间必须是唯一的。
-26029 GOTO cannot be used, and labels cannot be defined, within an exception h
andler.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2401 -
Rewrite the exception handler block so that it includes no GOTO statements.
重写异常处理程序块，使其不包含 GOTO 语句。
Example of error:
错误示例：
CREATE PROCEDURE testproc()
BEGIN
ON EXCEPTION IN (-206)
<> -- error
CREATE TABLE emp_list (lname CHAR(15));
GOTO ex_label; -- error
INSERT INTO emp_list VALUES ('john');
END EXCEPTION WITH RESUME
INSERT INTO emp_list VALUES ('john');
END
...
...
END PROCEDURE;
-26030 Invalid usage of EXIT or CONTINUE statement, which should be within a st
atement loop.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2402 -
Within the SPL routine,EXIT and CONTINUE statements must be placed within
a WHILE, FOR or LOOP statement loop.
在 SPL 例程中，EXIT 和 CONTINUE 语句必须放在 WHILE、FOR 或 LOOP 语句循环中。
-26031 END LOOP label label-name doesn't not match with the LOOP label label-na
me.
The LOOP lable-name and END LOOP label-name do not match.
Check the label-names for correct spelling.
LOOP 标签名称和 END LOOP 标签名称不匹配。检查标签名称是否正确拼写。
-26032 Invalid label label-name used with EXIT WHEN clause.
The label is not defined or is not a valid label for the LOOP statement.
The EXIT WHEN label must be defined within a scope that the LOOP
statement can reach. Check the label-names for correct spelling.
标签未定义或不是 LOOP 语句的有效标签。
必须在 LOOP 语句可以达到的范围内定义 EXIT
WHEN 标签。
检查标签名称是否正确拼写。
-26041 Invalid values specified for the %s environment variable.
An invalid value was provided for the environment variable. Please check your
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2403 -
user documentation, and provide the correct value, and try again.
为环境变量提供了无效值。请检查您的用户文档，并提供正确的值，然后重试。
-26042 Function (explain_sql) failed in %s.
In the explain_sql UDR, the execution failed in the specified function.
在 explain_sql UDR 中，指定函数中的执行失败。
-26043 Function (explain_sql): The required parameter %s is NULL
The required parameter is missing when you execute the explain_sql UDR.
执行 explain_sql UDR 时缺少必需的参数。
-26044 Function (explain_sql): An error occurred during the reading of the
parameter %s.
An error occurred during the reading of the parameter.
读取参数时发生错误。
-26045 Warning:
Function
(explain_sql)
%s
and
the
current
support
version
does
not
match.
The provided major_version or minor_version of explain_sql does not match the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2404 -
current
server
version.
Please
check
your
client
version
and
make
the
necessary
adjustment.
提供的 explain_sql 的 major_version 或 minor_version 与当前服务器版本不匹配。
请检查您的客户端版本并进行必要的调整。
-26046 Warning: Function (explain_sql): The requested locale was not provided.
The default locale %s will be used.
Because a locale was not provided in explain_sql UDR, the default locale will be
used in the query.
由于 explain_sql UDR 中未提供语言环境，因此将在查询中使用缺省的语言环境。
-26047 Function (explain_sql) does not support the query provided in (%s).
Only a single select statement is supported.
Explain_sql only supports a single SELECT statement. Please change your query.
Explain_sql 仅支持单个 SELECT 语句。请更改您的查询。
-26048 Function (explain_sql) has an invalid parameter %s parameter.
The value you provided for the parameter is invalid.
您为参数提供的值无效。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2405 -
-26049 Function (explain_sql) has invalid encoding (%s) for xml_input.
Xml_input should be in UTF-8 encoding.
Xml_input 应采用 UTF-8 编码。
-26050 Function (explain_sql) does not support a query with host variables.
Explain_sql only supports a single SELECT statement without any host variables.
Please change your query.
Explain_sql 仅支持没有任何主机变量的单个 SELECT 语句。请更改您的查询。
-84500 Attempt to update a stale version of a row
An attempt was made to update a stale copy of a row. This caused a
optimistic concurrancy failure.
尝试更新行的历史副本。这引起了乐观的并发失败。
This error can occur when using updates on secondary and the current
verstion of the row has not yet been replicated to the secondary on which
the client application is connected.
在辅助节点上使用更新时，可能会发生此错误，并且该行的当前版本尚未复制到客户端应
用程序
所连接的辅助节点。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2406 -
-84501 Connection between secondary and primary has been lost
The connection between the secondary and the primary has been lost. This
will prevent the updates on secondary until connectivity has been
reestablished.
次要和主要之间的连接已丢失。这将阻止次要更新，直到重新建立连接。
-26036 Cannot use the WITH VERCOLS clause because the table already has version
columns.
The table already has version columns created by the WITH VERCOLS clause.
You cannot add additional version columns.
该表已包含由 WITH VERCOLS 子句创建的版本列。您无法添加其他版本列。
-26037 Cannot drop VERCOLS when table does not have version columns.
The table that you were attempting to alter does not have VERCOLS columns.
您尝试更改的表没有 VERCOLS 列。
-26051 EXECUTE IMMEDIATE and PREPARE cannot take NULL statement
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2407 -
Expression that specifies SQL statement text in either EXECUTE IMMEDIATE
or PREPARE evaluates to a NULL value. Make sure to pass the text of a
valid SQL statement to these statements.
在 EXECUTE IMMEDIATE 或 PREPARE 中指定 SQL 语句文本的表达式求值为 NULL 值。
确保将有效 SQL 语句的文本传递给这些语句。
This error can be prevented by testing the expression passed to either
EXECUTE IMMEDIATE or PREPARE for a NULL value:
通过测试传递给 EXECUTE IMMEDIATE 或 PREPARE 的表达式以获取 NULL 值，可以防止此
错误：
Example (1)
示例（1）
DEFINE qStr CHAR(255);
...
LET qStr = ;
-- validate if above evalutes to NULL
IF (qStr IS NOT NULL) THEN
EXECUTE IMMEDIATE qStr;
ELSE
...
END IF;
Example (2)
示例（2）
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2408 -
DEFINE def_lc1 INTEGER;
DEFINE lc1 INTEGER;
LET def_lc1 = 10;
SELECT c1 INTO lc1 FROM t1 WHERE c2 = 10;
-- validate if query above returns a NULL value to lc1
-- if it is NULL then logic below should use default
-- lc1 (def_lc1) to avoid concatenation that returns NULL
IF (lc1 IS NOT NULL) THEN
PREPARE stmtId FROM "select c2[" || lc1 || "] FROM t2";
ELSE
PREPARE stmtId FROM "select c2[" || def_lc1 || "] FROM t2";
END IF;
-26052 OPEN attempted on already opened cursor (%s)
This OPEN statement referenced a cursor that has already been opened. Review
the program logic, and CLOSE the cursor before attempting to reopen it.
此 OPEN 语句引用了已打开的游标。查看程序逻辑，并在尝试重新打开之前关闭游标。
Example below makes sure to CLOSE the cursor before trying to OPEN the
same cursor with different input parameter values:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2409 -
下面的示例确保在尝试使用不同的输入参数值打开相同的游标之前关闭游标：
Example
示例
OPEN c_emp USING lgivenname;
...
CLOSE c_emp;
OPEN c_emp USING lfamilyname;
...
CLOSE c_emp;
-26053 FETCH or CLOSE cannot reference cursor (%s) that is not opened
The FETCH or CLOSE statement attempted to use an unopened cursor.
Make sure to OPEN the cursor before attempting FETCH or CLOSE that
cursor.
FETCH 或 CLOSE 语句尝试使用未打开的游标。确保在尝试 FETCH 或 CLOSE 游标
之前打开游标。
Example
示例
OPEN c_cust USING lfname, llname;
...
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2410 -
FETCH c_cust INTO lcustomer_num, lcompany;
...
CLOSE c_cust;
-26054 Cannot FREE a cursor (%s) that is in use
This FREE statement attempts to free a cursor that is still in use
(i.e. not closed yet). Make sure to close this cursor by using the
CLOSE statement before a FREE attempt.
此 FREE 语句尝试释放仍在使用中的游标（即尚未关闭）。确保在尝试 FREE
之前使用 CLOSE 语句关闭此光标。
Example
示例
DECLARE c_cust CURSOR FOR s_cust;
OPEN c_cust USING lfname, llname;
FETCH c_cust INTO lcustomer_num, lcompany;
CLOSE c_cust;
FREE c_cust;
-26055 Either statement-id or cursor name (%s) is not defined
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2411 -
This error occurs when either statement-id or a cursor name is not
defined before attempting to use it. Make sure to either PREPARE
the statement-id or DECLARE the cursor before using it.
在尝试使用它之前未定义 statement-id 或游标名称时会发生此错误。
确保在使用之前预先使用 statement-id 或 DECLARE 游标。
-26056 Function cursor (%s) in SPL cannot have WITH HOLD option
In SPL routines, the WITH HOLD option is not allowed for a function
cursor declared for the EXECUTE PROCEDURE or EXECUTE FUNCTION statement.
Omit the WITH HOLD keywords while declaring this cursor.
在 SPL 例程中，对于为 EXECUTE PROCEDURE 或 EXECUTE FUNCTION 语句声明的函
数游标，不允许使用 WITH HOLD 选项。在声明此游标时省略 WITH HOLD 关键字。
Only ESQL/C routines support function cursors WITH HOLD.
只有 ESQL/C 例程支持 WITH HOLD 的函数游标。
-26057 Either statement-id or cursor (%s) is already in use
This error can be returned in either of the following two cases:
可以在以下两种情况之一中返回此错误：
Case (1)
情况（1）
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2412 -
Attempt to PREPARE a statement with the same identifier that
an earlier PREPARE or DECLARE statement declared, and that has
not yet been freed for re-use. Review the program logic, and
either FREE this identifier before using it again for this
PREPARE statement, or else specify a different identifier.
尝试使用与先前的 PREPARE 或 DECLARE 语句声明的标识符相同的标
识符进行 PREPARE，并且尚未释放以备重用。查看程序逻辑，并在为
此 PREPARE 语句再次使用之前释放此标识符，或者指定其他标识符。
Example below demonstrates possible way to avoid this error:
下面的示例演示了避免此错误的可能方法：
PREPARE s_emp FROM "select givenname from employee";
PREPARE s_cust FROM "select fname from customer";
...
FREE s_cust;
PREPARE s_cust FROM "select lname from customer";
...
FREE s_cust;
FREE s_emp;
Case (2)
情况（2）
Attempt to DECLARE a cursor with the same identifier that an
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2413 -
earlier PREPARE or DECLARE statement declared, and that has not
yet been freed for re-use. Review the program logic, and either
FREE this identifier before using it again for this DECLARE
statement, or else specify a different identifier.
尝试使用与先前的 PREPARE 或 DECLARE 语句声明的标识符相同的标识
来 DECLARE 游标，并且尚未释放它以备重用。查看程序逻辑，并在为此
DECLARE 语句再次使用之前释放此标识符，或者指定其他标识符。
Example below demonstrates possible way to avoid this error:
下面的示例演示了避免此错误的可能方法：
DECLARE c_emp CURSOR FOR s_emp;
DECLARE c_cust CURSOR FOR s_cust;
...
FREE c_emp;
DECLARE c_cust CURSOR FOR s_cust;
...
FREE c_cust;
FREE c_emp;
-26058 EXECUTE IMMEDIATE and PREPARE in SPL cannot allow multiple SQL statements
Either EXECUTE IMMEDIATE or PREPARE statement in an SPL routine is trying
to process an expression that evaluates to the text of more than one SQL
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2414 -
statement. Change your program logic to pass to the EXECUTE IMMEDIATE or
PREPARE statement an expression or a quoted string that evaluates to the
text of only a single SQL statement.
SPL 例程中的 EXECUTE IMMEDIATE 或 PREPARE 语句正在尝试处理一个表达式，该表达式
求值
为多个 SQL 语句的文本。更改程序逻辑以将表达式或带引号的字符串传递给 EXECUTE
IMMEDIATE
或 PREPARE 语句，该字符串仅计算单个 SQL 语句的文本。
In an SPL routine, the following examples are not valid because the EXECUTE
IMMEDIATE or PREPARE statement specifies the text of more than one SQL
statement:
在 SPL 例程中，以下示例无效，因为 EXECUTE IMMEDIATE 或 PREPARE 语句指定了
多个 SQL 语句的文本：
Case (1)
...
EXECUTE IMMEDIATE "create table t1(c1 int); create table t2(c2 int);" ;
Case (2)
...
LET qry = "select c1,c2 from t1; select c1,c2 from t2";
PREPARE stmt_id FROM qry;
These examples of EXECUTE IMMEDIATE and PREPARE statements are valid in an
SPL routine:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2415 -
这些 EXECUTE IMMEDIATE 和 PREPARE 语句的示例在 SPL 例程中有效：
Case (3)
...
EXECUTE IMMEDIATE "create table t1(c1 int);" ;
EXECUTE IMMEDIATE "create table t2(c2 int);" ;
Case (4)
...
LET qry1 = "select c1,c2 from t1 ;";
PREPARE stmt_id1 FROM qry1;
LET qry2 = "select c1,c2 from t2 ;";
PREPARE stmt_id2 FROM qry2;
Only ESQL/C routines can use the EXECUTE IMMEDIATE or PREPARE statement to
process a semicolon-separated list of SQL statements.
只有 ESQL/C 例程可以使用 EXECUTE IMMEDIATE 或 PREPARE 语句来处理以分号分隔
的 SQL 语句列表。
-26059 Unsupported data type in EXECUTE IMMEDIATE or PREPARE statement
A variable passed to the EXECUTE IMMEDIATE statement or PREPARE statement
in SPL must be one of the data types CHAR, VARCHAR, LVARCHAR, NCHAR, or
NVARCHAR. Change your program logic to pass a variable of one of these
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2416 -
supported data types to the EXECUTE IMMEDIATE statement or PREPARE
statement in the SPL routine.
传递给 SPL 中的 EXECUTE IMMEDIATE 语句或 PREPARE 语句的变量必须是 CHAR、
VARCHAR、LVARCHAR、NCHAR 或 NVARCHAR 等数据类型。更改程序逻辑，将这些
支持的数据类型的变量传递给 SPL 例程中的 EXECUTE IMMEDIATE 语句或 PREPARE
语句。
In an SPL routine, the following examples are not valid because the
EXECUTE IMMEDIATE or PREPARE statement does not support variables of
type TEXT:
在 SPL 例程中，以下示例无效，因为 EXECUTE IMMEDIATE 或 PREPARE 语句
不支持 TEXT 类型的变量：
Case (1)
DEFINE qstr REFERENCES TEXT;
...
LET qstr = (SELECT textcol FROM t1 WHERE qryid = 100);
EXECUTE IMMEDIATE qstr;
Case (2)
DEFINE qstr REFERENCES TEXT;
...
LET qstr = (SELECT textcol FROM t1 WHERE qryid = 100);
PREPARE stmt_id FROM qstr;
The following examples include a valid EXECUTE IMMEDIATE statement and a
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2417 -
PREPARE statement in SPL routine:
以下示例在 SPL 例程中包含一个有效的 EXECUTE IMMEDIATE 语句和 PREPARE 语句:
Case (3)
DEFINE qstr varchar(120);
...
LET qstr = "create table t1 (c1 int);";
EXECUTE IMMEDIATE qstr;
Case (4)
DEFINE qstr lvarchar;
...
LET qstr = "select lvarcol from t1 where qryid = 100";
PREPARE stmt_id FROM qstr;
-26060 Procedure was created with an older version of the engine and must
be dropped and created again in order to work properly.
This procedure was created with an older version of the engine and
contains statements like CREATE TRIGGER, CREATE TABLE with fragmentation
expressions, ALTER TABLE or CREATE TABLE with constraint expressions
or nested CREATE PROCEDURE statements. Such procedures must be dropped
and created again using the current engine.
此过程是使用较旧版本的引擎创建的，包含 CREATE TRIGGER、带有分片表达式的 CREATE
TABLE、
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2418 -
带有约束表达式的 ALTER TABLE 或 CREATE TABLE 或嵌套的 CREATE PROCEDURE 语句等语
句。
必须使用当前引擎删除并再次创建此类过程。
-26061 Procedure (%s) was created with an older version of the server and must
be dropped and recreated again in order to work properly.
This procedure was created with an older version of the server and
contains statements similar to: CREATE TRIGGER statements, CREATE TABLE
statements with fragmentation expressions, ALTER TABLE or CREATE TABLE with
constraint expressions or nested CREATE PROCEDURE statements. These types of
procedures must be dropped and recreated again using the current server.
此过程是使用较旧版本的服务器创建的，包含类似于以下语句的语句：CREATE TRIGGER
语句、带有分片表达式的 CREATE
TABLE 语句、带有约束表达式的 ALTER
TABLE 或 CREATE
TABLE
或嵌套的 CREATE
PROCEDURE 语句。必须使用当前服务器删除并重新创建这些类型的过程。
-26062 The specified case is not defined in the CASE statement
The value of the case did not match any value in the WHEN clause of the CASE
statement and no ELSE clause is defined. The following example returns this
error because the LET statement specifies a case that is not defined in the
CASE statement.
此条件的值与 CASE 语句的 WHEN 子句中的任何值都不匹配，并且未定义 ELSE 子句。
以下示例返回此错误，因为 LET 语句指定了 CASE 语句中未定义的条件。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2419 -
CREATE PROCEDURE case_proc( )
RETURNING CHAR(1);
DEFINE grade CHAR(1);
LET grade = 'D';
CASE grade
WHEN 'A' THEN LET grade = 'a';
WHEN 'B' THEN LET grade = 'b';
WHEN 'C' THEN LET grade = 'c';
END CASE;
RETURN grade;
END PROCEDURE;
EXECUTE PROCEDURE case_proc();
To reduce the risk of this error, you might revise your CASE statement logic to
include an ELSE clause to take appropriate action if no WHEN condition is true,
or to add additional WHEN clauses that define how to handle additional cases.
要降低此错误的风险，您可以修改 CASE 语句逻辑以包含 ELSE 子句，以便在 WHEN 条件
不为真时
采取适当的操作，或者添加定义如何处理其他 case 的其他 WHEN 子句。
-26063 Data type not supported with CASE statement of SPL
The value specified in the CASE statement cannot be of type BLOB, CLOB, BYTE,
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2420 -
TEXT, Collection, DISTINCT, or OPAQUE. The BOOLEAN and LVARCHAR types are the
only built-in opaque data types that the CASE statement in SPL supports.
CASE 语句中指定的值不能是 BLOB、CLOB、BYTE、TEXT、Collection、DISTINCT 或 OPAQUE
类型。BOOLEAN 和 LVARCHAR 类型是 SPL 中 CASE 语句支持的唯一内置不透明数据类型。
-26064 The stored procedure execution failed because a statement cannot be
prepared(%s).
The stored procedure execution failed because a statement with in the stored
procedure could not be prepared. Change the statement or try to run it with the
EXECUTE IMMEDIATE statement.
存储过程执行失败，因为无法准备存储过程中的语句。更改语句或尝试使用 EXECUTE
IMMEDIATE 语句运行它。
-26071 Update statistics is not allowed on cross database or cross server objects
You can only update statistics on objects that reside in the local database.
To update statistics on objects in a remote database, connect to that
database directly.
您只能更新驻留在本地数据库中的对象的统计信息。
要更新远程数据库中对象的统计信息，
请直接连接到该数据库。
-26072 The (%s) operator cannot be used in this context.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2421 -
The word (%s) is an operator in the server and cannot be used in this context.
字符（%s）是服务器中的运算符，不能在此上下文中使用。
-11417 Selected locale/codeset will result in performance degradation.
The selected locale/codeset will result in performance degradation.
For optimum performance, use the same client and database locale.
选定的语言环境/代码集将导致性能下降。为获得最佳性能，请使用相同的客户端
和数据库语言环境。
-11418 Locales not found.
The displayed locale and codeset have not been found on the client machine.
Using these locale/codeset will result in -23101 Unable to load locale
categories error message. Please install the locales.
在客户端计算机上找不到显示的语言环境和代码集。使用这些语言环境/代码集将导致
-23101
无法加载语言环境类别错误消息。请安装语言环境。
-11419 The connection could not be enlisted with MSDTC.
The connection could not be enlisted with MSDTC because the distributed
transaction has been committed or aborted by the transaction manager. This
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2422 -
problem could be the result of a short transaction timeout in your
application or MSDTC configuration.
无法使用 MSDTC 连接该连接，因为事务管理器已提交或中止分布式事务。此问题可能是您
的
应用程序或 MSDTC 配置中的短暂的事务超时引发的结果。
-11420 The MSDTC transaction is no longer active.
The MSDTC transaction is no longer active. This problem could be the result
of a short transaction timeout in your application or MSDTC configuration.
MSDTC 事务无效。此问题可能是您的应用程序或 MSDTC 配置中的事务短暂超时的结果。
-11422 Smart
large
objects
can
only
be
used
by
setting
SQL_INFX_ATTR_LO_AUTOMATIC.
The SQL_INFX_ATTR_LO_AUTOMATIC connection or statement level attribute must be
set when working with smart large objects. You can set the
SQL_INFX_ATTR_LO_AUTOMATIC
attribute by setting the SQLSetConnectAttr or SQLSetStmtAttr functions or by
turning
on the Report Standard ODBC Types option under the Advanced tab of the ODBC
Administration
for GBase 8s Driver DSN.
使用智能大对象时，必须设置 SQL_INFX_ATTR_LO_AUTOMATIC 连接或语句级属性。您可以
通过设置
SQLSetConnectAttr 或 SQLSetStmtAttr 函数或打开 GBase
8s 驱动程序 DSN 的 ODBC 管
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2423 -
理的“高级”
选项卡下的“报告标准 ODBC 类型”选项来设置 SQL_INFX_ATTR_LO_AUTOMATIC 属性。
-26073 Savepoint name is unspecified.
The savepoint action - SAVEPOINT or RELEASE SAVEPOINT - requires a savepoint
name to identify the action. Please provide a name for this action.
保存点操作 - SAVEPOINT 或 RELEASE SAVEPOINT - 需要保存点名称来标识操作。
请提供此操作的名称。
-26074 Unable to set savepoint %s.
The savepoint referenced in the statement could not be set. Check the
accompanying isam error for more details.
无法设置语句中引用的保存点。请查看随附的 isam 错误以获取更多详细信息。
-26075 Unable to release savepoint %s.
The savepoint referenced in the statement could not be released. Check the
accompanying isam error for more details.
无法释放语句中引用的保存点。请查看随附的 isam 错误以获取更多详细信息。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2424 -
-26076 Unable to rollback to savepoint %s.
The transaction could not be rolled back to the savepoint referenced in the
statement. Check the accompanying ISAM error for more details.
无法将事务回滚到语句中引用的保存点。查看随附的 ISAM 错误以获取更多详细信息。
-32026 Savepoint not found.
The savepoint referenced in the statement could not be found in the current
transaction. Set a new savepoint using the "SAVEPOINT "
statement.
在当前事务中找不到语句中引用的保存点。使用 “SAVEPOINT ” 语句
设置新的保存点。
-26077 Savepoint statements are disallowed inside triggers.
Savepoint statements cannot be executed as a trigger action.
Savepoint 语句不能作为触发器操作执行。
-32027 A savepoint with the same name exists and the UNIQUE option was specified.
The savepoint name specified in the SAVEPOINT statement was used in creating
a previous savepoint, with either the previous, current, or both savepoints
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2425 -
having the UNIQUE option. After the UNIQUE option is specified, another
savepoint with the same name cannot be set in the same savepoint level until
the original savepoint is released. You must either specify a different
name, or else first release the UNIQUE savepoint before you reuse its
identifier.
在 SAVEPOINT 语句中指定的保存点名称用于创建前一个保存点，其中前一个保存点、当前
保存点
或两个保存点都具有 UNIQUE 选项。指定 UNIQUE 选项后，在释放原始保存点之前，不能
在相同的
保存点级别上设置同名的另一个保存点。您必须指定不同的名称，或者在重用其标识符之
前首先发
布唯一保存点。
-32028 Limit on savepoint levels reached.
No more than 2 ** 30 of savepoint levels are valid in a transaction. New
savepoint levels are automatically created for the duration of execution of
a stored procedure or UDR. Recursive calls to the stored procedure or UDR
also increment the savepoint level of the current transaction.
在事务中保存点级别不超过 2**30 是有效的。在存储过程或 UDR 的执行期间自动创建新
的保存点级别。对存储过程或 UDR 的递归调用也会增加当前事务的保存点级别。
-26078 Rollback to savepoint disallowed on updating an old server in same
transaction
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2426 -
Rolling back to a savepoint set within a cross-server transaction is not allowed
if
a participating server that does not support savepoints is also updated
in the same transaction. End the transaction that updated that server,
and retry the ROLLBACK TO SAVEPOINT statement.
如果在同一事务中也更新了不支持保存点的参与服务器，则不允许回滚到跨服务器事务中
设
置的保存点。结束更新该服务器的事务，然后重试 ROLLBACK TO SAVEPOINT 语句。
-26079 CONNECT BY query resulted in a loop.
A CONNECT BY query is resulting in a cycle/loop. Use CONNECT_BY_ISCYCLE
psuedo column to identify the row causing cycle/loop. Change your
query to remove the row or use the NOCYCLE keyword to allow the query to
skip the row.
CONNECT BY 查询导致 cycle/loop。使用 CONNECT_BY_ISCYCLE 伪标题列来标识导致
cycle/loop 的行。更改查询以删除行或使用 NOCYCLE 关键字以允许查询跳过该行。
-26080 Generic error in CONNECT BY query processing.
There was a problem in processing the CONNECT BY query.
处理 CONNECT BY 查询时出现问题。
-26081 Incorrect use of the CONNECT BY keywords in this context.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2427 -
The statement could not be run because CONNECT BY clause keywords were
used incorrectly.Keywords that can only be used in the context of a CONNECT BY
clause were used outside of a CONNECT BY clause.One of the following keywords
was used outside of the context of a CONNECT BY clause:
无法运行该语句，因为 CONNECT BY 子句关键字使用不正确。只能在 CONNECT BY 子句
的上下文中使用的关键字在 CONNECT BY 子句之外使用。在 CONNECT BY 子句的上下文
之外使用以下关键字之一：
- the LEVEL, CONNECT_BY_ISLEAF, or CONNECT_BY_ISCYCLE pseudocolumn
LEVEL、CONNECT_BY_ISLEAF 或 CONNECT_BY_ISCYCLE 伪列
- the PRIOR or CONNECT_BY_ROOT unary operator
PRIOR 或 CONNECT_BY_ROOT 一元运算符
- the SYS_CONNECT_BY_PATH() function
SYS_CONNECT_BY_PATH() 函数
- the ORDER SIBLINGS BY clause
ORDER SIBLINGS BY 子句
- the START WITH expression clause
START WITH 表达式子句
Make sure that you have provided CONNECT BY keywords in this context.
请确保您在此上下文中已经提供了 CONNECT BY 关键字。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2428 -
Make sure that you have not used nested CONNECT BY clauses in the query.
请确保您没有在此查询中使用嵌套的 CONNECT BY 子句。
-26082 CONNECT_BY_ISCYCLE is used without the NOCYCLE keyword.
The CONNECT_BY_ISCYCLE keyword is used without the NOCYCLE keyword
in a CONNECT BY query. Include the NOCYCLE keyword in the
CONNECT_BY_ISCYCLE context.
在 CONNECT BY 查询中使用 CONNECT_BY_ISCYCLE 关键字时没有 NOCYCLE 关键字。
在 CONNECT_BY_ISCYCLE 上下文中包含 NOCYCLE 关键字。
-26084 Cross server objects cannot be referenced in CONNECT BY queries.
The table specified in the FROM clause of a CONNECT BY query must
be in a database of the Dynamic Server instance to which the session
is connected. No clause of a SELECT statement that includes the
CONNECT BY clause can reference a database object that is managed
by a remore database server.
CONNECT BY 查询的 FROM 子句中指定的表必须位于会话所连接的 Dynamic Server
实例的数据库中。包含 CONNECT BY 子句的 SELECT 语句的子句不能引用由远程数
据库服务器管理的数据库对象。
If you need to perform a CONNECT BY query on a table that resides
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2429 -
in a database of a remote server, you should first connect to that
database, and then issue the CONNECT BY query on the (local) table.
如果需要对驻留在远程服务器的数据库中的表执行 CONNECT BY 查询，则应首先连接
到该数据库，然后在（本地）表上发出 CONNECT BY 查询。
-26085 You cannot have a CONNECT BY query on a join of two or more tables.
The FROM clause of a CONNECT BY query cannot have a join of two or more
tables.
CONNECT BY 查询的 FROM 子句不能具有两个或多个表的连接。
For example, the following statements generate an error:
例如，以下语句生成错误：
SELECT empid, name, mgrid, deptdesc
FROM (employee INNER JOIN department
ON employee.deptid == department.deptid)
START WITH employee.name = 'David'
CONNECT BY PRIOR employee.empid = employee.mgrid;
SELECT *
FROM employee, employee AS new
CONNECT BY PRIOR employee.empid = new.mgrid;
The following statement is correct:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2430 -
以下语句是正确的：
SELECT empid, name, mgrid
FROM employee
START WITH employee.name = 'David'
CONNECT BY PRIOR employee.empid = employee.mgrid;
-26087 Incorrect use of the bson unwind in this context.
The statement could not be run because bson unwind clause was used incorrectly.
无法运行该语句，因为 bson unwind 子句使用不正确。
-26090 Column (%s) not found in the target table.
This error is generated when a user tries to insert or update data into a
column that is not from the target table. For example:
当用户尝试将数据插入或更新到不是目标表的列时，会生成此错误。例如：
create table bonus (id int, bonus int);
create table emp(id int, salary int);
MERGE INTO bonus D
USING emp S ON D.id = S.id
WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2431 -
WHEN NOT MATCHED THEN INSERT (id, salary) VALUES (S.id, salary);
This will generate the following error because salary in the insert column
list is not from the target table, bonus:
这将生成以下错误，因为插入列列表中的工资不是来自目标表，bonus：
26090: Column (salary) not found in the target table.
Error in line 4
Near character position 41
MERGE INTO bonus
USING emp ON bonus.id = emp.id
WHEN MATCHED THEN UPDATE SET salary = 1000
WHEN NOT MATCHED THEN INSERT VALUES (10, 100);
This will generate the following error because salary in the set clause of
the update is not from the target table, bonus:
这将生成以下错误，因为更新的 set 子句中的 salary 不是来自目标表 bonus：
26090: Column (salary) not found in the target table.
Error in line 3
Near character position 44
-26091 Table (%s) is not the target table.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2432 -
This error is generated when a user tries to insert data into a column that
is not from the target table. For example:
当用户尝试将数据插入非目标表的列时，会生成此错误。例如：
create table bonus (id int, bonus int);
create table emp(id int, salary int);
MERGE INTO bonus D
USING emp S ON D.id = S.id
WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01
WHEN NOT MATCHED THEN INSERT (id, emp.bonus) VALUES (S.id, salary);
This will generate the following error because the emp.bonus table name is
not the bonus target table:
这将生成以下错误，因为 emp.bonus 表名称不是 bonus 目标表：
26091: Table (emp) is not the target table.
Error in line 4
Near character position 47
-26092 Column (%s) is not found in the source table.
This error is generated when a user tries to insert data into the target table
using a column from the target table. For example:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2433 -
当用户尝试使用目标表中的列将数据插入目标表时，会生成此错误。例如：
create table bonus (id int, bonus int);
create table emp(id int, salary int);
MERGE INTO bonus D
USING emp S ON D.id = S.id
WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01
WHEN NOT MATCHED THEN INSERT (D.id, D.bonus) VALUES (S.id, bonus);
This will generate the following error because in the VALUE clause the
bonus column is not from the emp source table:
这将生成以下错误，因为在 VALUE 子句中，bonus 列不是来自 emp 源表：
26092: Column (bonus) not found in the source table.
Error in line 4
Near character position 66
-26093 Table (%s) is not the source table.
This error is generated when a user tries to insert data into the
target table using the column from the target table. For example:
当用户尝试使用目标表中的列将数据插入目标表时，会生成此错误。例如：
create table bonus (id int, bonus int);
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2434 -
create table emp(id int, salary int);
MERGE INTO bonus D
USING emp S ON D.id = S.id
WHEN MATCHED THEN UPDATE SET bonus = bonus + salary*.01
WHEN NOT MATCHED THEN INSERT (D.id, D.bonus) VALUES (D.id, salary);
This will generate the following error because the salary column in the VALUE
clause is not from the source table, emp:
这将生成以下错误，因为 VALUE 子句中的 salary 列不是来自源表 emp：
26093: Table (d) is not the source table.
Error in line 4
Near character position 61
-26094 The MERGE operation is not allowed on this target table (%s).
The Target table in a MERGE statement cannot be a pseudo SMI table, a catalog
table, a remote table, a VTI table or an external table.
MERGE 语句中的 Target 表不能是伪 SMI 表、目录表、远程表、VTI 表或外部表。
-26095 Cannot update or delete a row twice in a MERGE statement.
If you do a MERGE operation, the join condition and any filters must be
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2435 -
sufficiently strict so that no row of the target table is produced more than
once for updating or deleting. The error occurred because the same row was
processed twice. The query was terminated abnormally.
如果执行 MERGE 操作，则连接条件和任何过滤器必须足够严格，以便不会多次生成目标表
的行以
进行更新或删除。发生错误是因为同一行处理了两次。查询异常终止。
Either clean the data source or sources, or make the query more restrictive
so that no target table row is produced more than once for updating or deleting.
清理一个或多个数据源，或使查询更具限制性，以便不会多次生成目标表行以进行更新或
删除。
-26096 Cannot define INSTEAD OF trigger on a view when the view is specified
as the target in the MERGE statement.
When the target of a MERGE statement is a view, then INSTEAD OF insert and
update triggers cannot be defined on the view. Delete triggers can be specified
as they are anyway ignored by the MERGE statement.
当 MERGE 语句的目标是视图时，无法在视图上定义 INSTEAD OF 插入和更新触发器。
可以指定删除触发器，因为 MERGE 语句无论如何都会忽略它们。
When this situation occurs, consider merging into the base table directly
instead of into the view. The other alternative is to drop or disable the
trigger.
发生这种情况时，请考虑直接合并到基表中而不是合并到视图中。另一种方法是删除或禁
用触发器。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2436 -
-26098 In a MERGE statement, the security policies of the target table and source
table (%s) do not match.
The Label Based Access Control security polices of the source and target tables
in a MERGE statement must be the same.
MERGE 语句中源表和目标表的基于标签的访问控制安全策略必须相同。
If the source table object in the USING clause is a subquery that accesses
multiple tables, you can remove the source table whose policy differs from
the target table from the USING clause of the MERGE statement.
如果 USING 子句中的源表对象是访问多个表的子查询，
则可以从 MERGE 语句的 USING 子
句
中删除其策略与目标表不同的源表。
-26099 The optimizer cannot choose a viable plan based on the ON clause filter
specified in the MERGE statement.
Hash-join is the preferred join method between source and target tables in
the MERGE statement. The optimizer currently prevents nested loop joins from
occurring when the target table is the inner table of a join. If a hash-join
plan is also not feasible, then the optimizer throws this error.
哈希连接是 MERGE 语句中源表和目标表之间的首选连接方法。当目标表是连接的内部表
时，优化器
阻止发生嵌套循环连接。如果散列连接计划也不可行，则优化器会抛出此错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2437 -
When this error occurs, try to change the ON condition so that at least
one equality predicate is specified between the source and target tables
on non-complex data-types. If this is not feasible, please contact
GBase 8s technical support.
发生此错误时，尝试更改 ON 条件，以便在非复杂数据类型的源表和目标表之间指定至少
一个等号。
如果不可行，请联系 GBase 8s 技术支持。
-26151 Could not write to external table file: errno, filename.
An error occurred when the database server tried to write to the reject file.
数据库服务器尝试写入拒绝文件时发生错误。
Look for operating-system messages that might give more information.
Possible causes include a full disk or a disk quota limit.
查找可能提供更多信息的操作系统消息可能的原因包括完整磁盘或磁盘配额限制。
-26152 Could not exclusively lock external table.
Another user is currently using the external table.
Wait for the external table to be unlocked before you proceed.
另一个用户当前正在使用外部表。等待外部表解锁，然后再继续。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2438 -
-26153 Could not close external table.
An error occurred when the database server tried to close the external
table lock. Note all circumstances and contact GBase Software Support.
数据库服务器尝试关闭外部表锁时发生错误。请注意所有情况并联系 GBase 软件支持。
-26154 Could not open file: errno, filename.
An error occurred when the database server tried to open the file. Check the
accompanying error for more information. Possible causes include missing
file or incorrect permissions.
数据库服务器尝试打开文件时发生错误。请查看随附的错误以获取更多信息。
可能的原因包括丢失文件或不正确的权限。
-26155 Could not close external table file: errno, filename.
An error occurred when the database server tried to close the file. Look
for operating-system messages that might give more information.
Possible causes include a full disk or hardware errors.
数据库服务器尝试关闭该文件时发生错误。查找可能提供更多信息的操作系统消息。
可能的原因包括磁盘已满或硬件错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2439 -
-26156 Failed to read from file: errno, filename.
An error occurred when the database server tried to read from the file.
Check the accompanying error for more information.
数据库服务器尝试从该文件读取时发生错误。请查看随附的错误以获取更多信息。
-26157 File is incorrectly specified as a DISK type: (file)=(%s).
The file named in the external table was designated as a "DISK" file type,
but it is not a disk file. If this file is a UNIX named pipe, change the
file type in the external table to type "PIPE".
外部表中指定的文件被指定为 “DISK” 文件类型，但它不是磁盘文件。如果此文件是
UNIX
命名管道，请更改外部表中的文件类型以键入 “PIPE”。
-26158 File is incorrectly specified as a PIPE type: (file)=(%s).
The file named in the external table was called a "PIPE" file type,
but it is not a UNIX named pipe. If this file is a disk file, change
the file type in the external table to "DISK".
外部表中指定的文件称为 “PIPE” 文件类型，但它不是 UNIX 命名管道。如果此文件是
磁盘文件，
请将外部表中的文件类型更改为 “DISK”。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2440 -
-26159 Error accessing AIO buffer: errno, filename.
An error occurred when the database server tried to read or write from an
internal AIO buffer. Note all circumstances and contact GBase Software
Support.
数据库服务器尝试从内部 AIO 缓冲区读取或写入时发生错误。请注意所有情况并联系
GBase 软件支持。
-26160 Could not remove the external table file: errno, filename.
An error occurred when the database server tried to remove the
indicated file. Look for operating-system messages that might give
more information. A likely cause is incorrect permissions.
数据库服务器尝试删除指定的文件时发生错误。查找可能提供更多信息的操作系统消息。
可能的原因是权限不正确。
-26161 External table internal error: errno, filename.
Note all circumstances and contact GBase Software Support
regarding this internal error.
请注意所有情况并联系 GBase 软件支持以了解此内部错误。
-26162 Failed to start an AIO operation: errno, filename.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2441 -
An error occurred when the database server tried to read or write to a
datafile. Check the accompanying error for more information.
数据库服务器尝试读取或写入数据文件时发生错误。请查看随附的错误以获取更多信息。
-26163 Target table cannot have any BLOB columns.
The BLOB column type is not supported for the target column in
an External table.
外部表中的目标列不支持 BLOB 列类型。
-26164 External table data conversion failure (unload).
A conversion failure occurred when the database server tried to convert
the data to ASCII format.
数据库服务器尝试将数据转换为 ASCII 格式时发生转换失败。
Check that the external table columns have enough space reserved to
write the ASCII representation of the data and that the
columns in the external table are compatible with the data selected.
检查外部表列是否有足够的空间来写入数据的 ASCII 表示以及外部表中的列。
-26165 Datafile full (unload).
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2442 -
An error occurred when the database server tried to write to the unload
data file. No additional data can be written to the file.
数据库服务器尝试写入卸载数据文件时发生错误。无法将其他数据写入文件。
Allocate more space for the file and try again.
为文件分配更多空间，然后重试。
-26166 Datafile AIO write error (unload): errno.
An error occurred when the database server tried to write to the unload
datafile. Check the accompanying error for more information.
数据库服务器尝试写入卸载数据文件时发生错误。请查看随附的错误以获取更多信息。
-26167 All data files are either full or corrupted (unload).
An error occurred during the unload. Look for operating-system messages
that might give more information. Possibly all disks with data files
are full hardware problems have occurred.
卸载期间发生错误。查找可能提供更多信息的操作系统消息。
可能所有带有数据文件的磁盘都发生了完整的硬件问题。
-26168 Conversion error: errno, filename.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2443 -
When the database server tried to load from the file, it encountered an
error. Unless a reject file is specified in the external table, the
database server returns the error message, and the load job ends without
saving loaded data.
当数据库服务器尝试从该文件加载时，它遇到错误。除非在外部表中指定了拒绝文件，
否则数据库服务器将返回错误消息，并且加载作业将结束而不保存已加载的数据。
Check for conversion errors, rows that violate constraints defined on
the external table, or null columns that were defined as NOT NULL.
检查转换错误，违反外部表定义的约束的行，或者定义为 NOT NULL 的空列。
A reason code of UNSUPPORTED_ROW_SIZE indicates that the external table
row size (other than BYTE and TEXT columns) is greater than 32K.
UNSUPPORTED_ROW_SIZE 的原因代码表示外部表行大小
（BYTE 和 TEXT 列除外）
大于 32
K。
-26169 Failed to access file: errno, filename.
An error occurred when the database server tried to write to the reject file.
数据库服务器尝试写入拒绝文件时发生错误。
Check the accompanying operating-system error indication for more information.
有关详细信息，请查看随附的操作系统错误指示。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2444 -
-26170 Could not find record end: must stop loading.
An error occurred when the database server tried to find a record delimiter
in the delimited load file.
数据库服务器尝试在分隔的加载文件中查找记录分隔符时发生错误。
Check to see that the file has record delimiters (normally new-line
characters) and that the external table has defined the correct record
delimiter.
检查文件是否有记录分隔符（通常是换行符），并且外部表已定义了正确的记录分隔符。
-26171 Cannot undo partial write to filename when detecting a full disk.
An error occurred when the database server tried to continue after running
out of space for one data file. When the database server detects that the
disk is full, it writes to the data file a partial record, which cannot be
truncated.
数据库服务器在耗尽一个数据文件的空间后尝试继续时发生错误。当数据库服务器检测到
磁盘已满时，
它会向数据文件写入部分记录，该记录不能被截断。
Look for operating-system messages that might give more information.
查找可能提供更多信息的操作系统消息。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2445 -
-26172 There are too many keywords in USING clause.
The CREATE EXTERNAL table statement contains more than one
occurrence of a keyword expected in the USING clause.
CREATE EXTERNAL 表语句包含 USING 子句中预期的多个关键字。
Review the statement. If you meant to use another keyword, correct the
statement before you reissue it.
检查语句。如果打算使用其他关键字，请在重新发布之前更正该语句。
-26173 Incorrect value for a keyword.
The CREATE EXTERNAL TABLE statement contains an incorrect value
for one of the USING clause keywords.
CREATE EXTERNAL TABLE 语句包含的 USING 子句关键字的值不正确。
Review the statement to see if the value of the keyword is misspelled.
For the MAXERRORS keyword, make sure the value is a valid number.
查看该语句以查看关键字的值是否拼写错误。对于 MAXERRORS 关键字，请确保该值为有效
数字。
-26174 Incorrect DATAFILES entry.
A DATAFILES entry does not have the correct format. The format for an
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2446 -
entry is filetype:rooted-path-name.
DATAFILES 条目的格式不正确。条目的格式为 filetype:rooted-path-name。
Check that the file type is a valid type (DISK or PIPE), that the
second item names a item names a file that can be accessed.
检查文件类型是否为有效类型（DISK 或 PIPE），第二项指定可以访问的文件。
-26175 DATAFILES entry are missing.
The DATAFILES entry in the CREATE EXTERNAL TABLE statement
is missing. Add a DATAFILES entry and reissue the statement.
CREATE EXTERNAL TABLE 语句中的 DATAFILES 条目丢失。添加一个 DATAFILES
条目并重新发出该语句。
-26176 Cannot use SAMEAS for FIXED format tables.
The CREATE EXTERNAL TABLE statement does not allow the SAMEAS keyword
for FIXED format tables. The column entries must also define an external
type to describe how to access the data in the fixed file.
CREATE EXTERNAL TABLE 语句不允许 FIXED 格式表的 SAMEAS 关键字。列项还必
须定义外部类型，以描述如何访问固定文件中的数据。
Revise the CREATE EXTERNAL TABLE statement to enumerate the column
information and reissue the statement.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2447 -
修改 CREATE EXTERNAL TABLE 语句以枚举列信息并重新发出该语句。
-26178 Incorrect external column type column-name.
The CREATE EXTERNAL TABLE statement contains an incorrect external column
type.
CREATE EXTERNAL TABLE 语句包含不正确的外部列类型。
Make sure the external column type is CHAR(size)
确保外部列类型为 CHAR(size)。
-26179 FIXED or DELIMITED columns must be external CHAR type column-name.
The CREATE EXTERNAL TABLE statement contains an external column type
that is not valid. If the table describes a FIXED format file, the valid
external- column type is CHAR. CHAR data must be enclosed in quotation marks.
CREATE EXTERNAL TABLE 语句包含无效的外部列类型。如果表描述了 FIXED 格式文件，
则有效的外部列类型为 CHAR。CHAR 数据必须用引号括起来。
If the table describes a DELIMITED format file and includes
external-column types, then the type must be CHAR. A table that
describes DELIMITED format files does not need to include
external-column-type information.
如果表描述 DELIMITED 格式文件并包含外部列类型，则类型必须为 CHAR。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2448 -
描述 DELIMITED 格式文件的表不需要包含外部列类型信息。
-26180 Missing external column type column-name.
The CREATE EXTERNAL TABLE statement is missing the external-column-
type information. This information is required for tables that describe
FIXED format files.
CREATE
EXTERNAL
TABLE 语句缺少外部列类型信息。
描述 FIXED 格式文件的表需要此信息。
Add the column-type information and resubmit the statement.
添加列类型信息并重新提交该语句。
-26181 Only FIXED format columns can declare a null column-name.
The CREATE EXTERNAL TABLE table statement has found a column defining a
null string with the NULL "null-string" syntax that is not valid. Only
tables that describe FIXED format files can have a null value defined
with the NULL keyword.
CREATE EXTERNAL TABLE 表语句找到了一个列，该列定义了一个空字符串，其 NULL
“null-string”
语法无效。只有描述 FIXED 格式文件的表可以使用 NULL 关键字定义空值。
Rework the statement and resubmit it.
修改语句并重新提交。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2449 -
-26182 Incorrect file type in DATAFILES string datafile entry.
An error occurred when the database server tried to expand the DATAFILES
entries in an INSERT or SELECT statement for an external table. The
external table has a DATAFILES entry with an incorrect file type. Only
DISK and PIPE file types are allowed for external tables.
当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生
错误。
外部表具有 DATAFILES 条目，文件类型不正确。外部表只允许使用 DISK 和 PIPE 文件类
型。
Examine the external-table entry, drop the external table, and reissue
a corrected CREATE EXTERNAL TABLE statement to correct this error.
检查外部表条目，删除外部表，然后重新发出更正的 CREATE EXTERNAL TABLE
语句以更正此错误。
-26183 Could not replace r macro in filename entry.
An error occurred when the database server tried to expand the node
host-name macro in the filename in a DATAFILES entry in an INSERT or
SELECT statement for an external table.
当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句的 DATAFILES 条目中的文件名
中展开节点主机名宏时发生错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2450 -
If the error recurs, note all circumstances and contact
GBase Software Support.
如果错误再次出现，请记录所有情况并联系 GBase 软件支持。
-26184 Could not parse r macro in filename entry.
An error occurred when the database server tried to expand the DATAFILES
entries in an INSERT or SELECT statement for an external table. The
error occurred when the database server tried to expand the %r macro in
the filename. Check that the syntax for the %r() macro is correct.
当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生
错误。数据库服务器尝试在文件名中展开 %r 宏时发生错误。检查 %r() 宏的语法是否正
确。
-26185 None of the DATAFILES strings name valid data files.
An error occurred when the database server tried to expand the
DATAFILES entries in an INSERT or SELECT statement for an external
table. No valid filenames were found in the DATAFILES entries.
当数据库服务器尝试在外部表的 INSERT 或 SELECT 语句中展开 DATAFILES 条目时发生
错误。在 DATAFILES 条目中找不到有效的文件名。
Examine the external tables entry, drop the external table, and reissue
a corrected CREATE EXTERNAL TABLE statement.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2451 -
检查外部表条目，删除外部表，然后重新发出更正的 CREATE EXTERNAL TABLE 语句。
-26186 File name is too long: file_name.
The name of the file in the external table is too long (after expanding
all the file macros). Check to see that the full path name of the
file is less than 257 characters long.
外部表中文件的名称太长
（在展开所有文件宏之后）
。
检查文件的完整路径名是否小于 257
个字符。
-26187 Cannot select from multiple external tables.
Only one external table can be used in a SELECT query. For unions,
each UNION contributor can have one external table. External tables
are allowed as participants in joins and subqueries along with
other database tables.
SELECT 查询中只能使用一个外部表。
对于 unions，
每个 UNION 贡献者可以有一个外部表。
允许将外部表与其他数据库表一起作为联接和子查询的参与者。
-26188 Null string is too long or has an incorrect format.
The CREATE EXTERNAL TABLE statement has a column with incorrect NULL
"null-string" syntax. The NULL string for this column is longer than
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2452 -
the external column length declared or is not a recognized format for
the external type.
CREATE EXTERNAL TABLE 语句的列具有不正确的 NULL“null-string” 语法。
此列的 NULL 字符串比声明的外部列长度长，或者不是外部类型的可识别格式。
Check the CREATE EXTERNAL TABLE statement to make sure that the NULL
"null-string" length agrees with the size and format defined for the
external column type.
检查 CREATE EXTERNAL TABLE 语句以确保 NULL“null-string” 长度与为外部列类型
定义的大小和格式一致。
-26189 Cannot use a clause with a SELECT statement into an
external table.
The SELECT statement contains a FOR UPDATE or FORMAT "FIXED" clause.
When the database server unloads to an external table, these clauses
are not allowed.
SELECT 语句包含 FOR UPDATE 或F ORMAT“FIXED” 子句。当数据库服务器卸载到外部表
时，
不允许使用这些子句。
Check the SELECT statement or when the SELECT cursor was defined, and
make sure you do not include either of these clauses.
检查 SELECT 语句或定义 SELECT 游标时，确保不包含这些子句。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2453 -
-26190 Insert into an external table must provide values for all columns in
the table.
The INSERT statement does not list all the columns that the external
table defines. When the database server unloads to an external table, all
columns must have values described by the SELECT list.
INSERT 语句不会列出外部表定义的所有列。当数据库服务器卸载到外部表时，所有列都必
须
具有 SELECT 列表描述的值。
Check the INSERT statement to make sure that all columns are included
in the INSERT clause and that every column has a value supplied by the
SELECT list.
检查 INSERT 语句以确保 INSERT 子句中包含所有列，并且每列都有 SELECT 列表提供的
值。
-26191 Incorrect use of an external table tablename in query.
This statement describes an operation that is not allowed on an external
table. The types of operations allowed for external tables are
CREATE EXTERNAL TABLE, SELECT, DROP TABLE, GRANT (only SELECT and INSERT),
REVOKE, CREATE SYNONYM, CREATE SCHEMA, RENAME COLUMN, RENAME TABLE,
SELECT ... INTO EXTERNAL.
此语句描述外部表上不允许的操作。外部表允许的操作类型有:CREATE EXTERNAL TABLE、
SELECT、DROP TABLE、GRANT （仅限于 SELECT 和 INSERT）、REVOKE、CREATE SYNONYM、
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2454 -
CREATE SCHEMA、RENAME COLUMN、RENAME TABLE、SELECT ... INTO EXTERNAL。
The types of operations not allowed for external tables are
TRUNCATE, UPDATE STATISTICS, START VIOLATION, STOP VIOLATION, ALTER TABLE,
UPDATE, DELETE, CREATE TRIGGER, CREATE INDEX, CONNECT BY, INSERT INTO ...
VALUES, LBAC operations, target tables of MERGE statements and template
table for SAMEAS clause of CREATE EXTERNAL TABLE.
外部表不允许的操作类型是 TRUNCATE、UPDATE STATISTICS、START VIOLATION、
STOP VIOLATION、ALTER TABLE、UPDATE、DELETE、CREATE TRIGER、CREATE INDEX、
CONNECT BY、INSERT INTO ... VALUES、LBAC 操作、MERGE 语句的目标表 CREATE
的 SAMEAS 子句的模板表外部表。
-26192 Column too long for fixed field. (Val = value, Col = colno,
Len = converted length, Max = maxLen).
When the database server tried to convert the column to FIXED file format, the
size of the converted value was longer than the maximum size defined
for the fixed- size field.
当数据库服务器试图将列转换为固定文件格式时，转换值的大小大于为固定大小字段定义
的最大大小。
Check that the external table description defines enough space in the
external column type to hold the data selected after conversion.
检查外部表描述是否在外部列类型中定义了足够的空间来保存转换后选择的数据。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2455 -
-26193 An external table must be a fixed format file if it has an
external column type column-name.
An external column type of CHAR was found for an external table that
is not defined as a FIXED-format file.
为外部表找到了外部列类型的 CHAR，该外表未定义为 FIXED 格式文件。
-26194 Unknown external column type column-name.
The CREATE EXTERNAL TABLE statement contains an external-column type
that was not recognized. The valid external-column type is CHAR. CHAR
values must be in quotation marks.
CREATE EXTERNAL TABLE 语句包含无法识别的外部列类型。有效的外部列类型是 CHAR。
CHAR 值必须使用引号。
Check the CREATE EXTERNAL TABLE statement to make sure that the
external-column types are valid.
检查 CREATE EXTERNAL TABLE 语句以确保外部列类型有效。
-26195 No constraints can be defined for external tables.
The CREATE EXTERNAL TABLE statement contains one or more types of
constraint that are not allowed.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2456 -
CREATE EXTERNAL TABLE 语句包含一个或多个不允许的约束类型。
Check the statement for primary-key, referential, or unique constraints
on a column or for the table.
检查语句中列或表的主键、引用或唯一约束。
-26196 Internal type must be a numeric type column-name.
The CREATE EXTERNAL TABLE statement contains external-column types that
do not agree with the internal-column type.
CREATE EXTERNAL TABLE 语句包含与内部列类型不一致的外部列类型。
Check the CREATE EXTERNAL TABLE statement to make sure any external-
column types agree with the internal-column type.
检查 CREATE EXTERNAL TABLE 语句以确保外部列类型与内部列类型一致。
-26197 Reached maximum error limit during load: errno, filename.
When the database server tried to load the data from the external table,
the server reached the MAXERRORS limit defined for the external table.
当数据库服务器尝试从外部表加载数据时，服务器达到为外部表定义的 MAXERRORS 限制。
-26198 Cannot modify an external table that is also used in the subquery.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2457 -
The external table cannot be used in the subquery. Check the
statement to see if the external table is used in the subquery.
不能在子查询中使用外部表。检查语句以查看子查询中是否使用了外部表。
-26199 The RETAINUPDATELOCKS session environment cannot be set in a
nonlogging database.
-26200 The RETAINUPDATELOCKS session environment cannot be set on
secondary server in a high-availability cluster.
-26213 CREATE EXTERNAL TABLE: The DELIMITER keyword is not valid for
FIXED format tables.
-26214 Cannot perform this operation on an external table.
The following types of operations with external tables are not allowed:
不允许使用以下类型的外部表操作：
- including an external table in a subquery or in an outer join
在子查询或外连接中包括外部表
- including BLOB or CLOB columns from external tables in joins, UNION
clauses, or ORDER BY clauses
包括连接、UNION 子句或 ORDER BY 子句中的从外部表中包含 BLOB 或 CLOB 列
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2458 -
- including a subquery or stored procedure if the main query references
BLOB or CLOB columns in external tables
如果主查询引用外部表中的 BLOB 或 CLOB 列，则包括子查询或存储过程
- using subscripts as BLOB or CLOB columns from external tables
使用下标作为外部表的 BLOB 或 CLOB 列
- selecting BLOB or CLOB columns from external tables out of order
不按顺序从外部表中选择 BLOB 或 CLOB 列
- selecting a BLOB or CLOB column from one external table and inserting
it into a different external table
从一个外部表中选择 BLOB 或 CLOB 列并将其插入到不同的外部表中
- selecting BYTE and TEXT column to temporary table or through client API
选择 BYTE 和 TEXT 列到临时表或通过客户端 API
-26216 CREATE EXTERNAL TABLE: The RECORDEND keyword is not valid for
FIXED format tables.
-26381 BLOBDIR directory (%s) does not exist or is not accessible.
The BLOBDIR value specified with the CREATE EXTERNAL or SELECT INTO EXTERNAL
statement does not exist or is not accessible
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2459 -
使用 CREATE EXTERNAL 或 SELECT INTO EXTERNAL 语句指定的 BLOBDIR 值不存在或无法
访问。
-26382 CLOBDIR directory (%s) does not exist or is not accessible.
The CLOBDIR value specified with the CREATE EXTERNAL or SELECT INTO EXTERNAL
statement does not exist or is not accessible
使用 CREATE EXTERNAL 或 SELECT INTO EXTERNAL 语句指定的 CLOBDIR 值不存在或不可
访问。
-26383 DATAFILES string (%s) with file type PIPE is not supported with BLOB/CLOB
types
The PIPE option is not supported in the DATAFILES clause when BLOB or CLOB data
types are specified in the external table definition or in the table referenced
in
the SAMEAS clause. The following is an example of when this error is returned:
当在外部表定义或 SAMEAS 子句中引用的表中指定 BLOB 或 CLOB 数据类型时，
DATAFILES 子句中不支持 PIPE 选项。以下是返回此错误的示例：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB)
USING
(
DATAFILES
(
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2460 -
"PIPE:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR:/tmp/clobdir1.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
To fix the problem in example above, please change the definition
to use file type DISK instead of PIPE.
要解决上述示例中的问题，请更改定义以使用 DISK 文件类型而不是 PIPE。
-26384 FORMAT (%s) is not supported with BLOB, CLOB, BYTE or TEXT types
The FORMAT type specified is not supported with BLOB, CLOB, BYTE or TEXT types.
Use DELIMITED FORMAT when specifying BLOB, CLOB, BYTE, TEXT data types.
The following is an example when this error is returned:
BLOB、CLOB、BYTE 或 TEXT 类型不支持指定的格式类型。在指定 BLOB、CLOB、BYTE 和
TEXT 数据类型时使用分隔格式。以下是返回此错误时的示例：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB, col4 BYTE,
col5 TEXT)
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2461 -
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR:/tmp/clobdir1.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
FORMAT 'FIXED'
);
To fix the problem in example above, please change the definition
to use FORMAT type DELIMITED instead of type FIXED.
若要解决上述示例中的问题，
请将定义更改为使用 FORMAT 类型 DELIMITED 而不是 FIXED
类型。
FORMAT cannot be GBASEDBT or FIXED if the external table contains BLOB, CLOB,
BYTE or TEXT columns.
如果外部表包含 BLOB、CLOB、BYTE 或 TEXT 列，则 FORMAT 不能是 GBASEDBT 或 FIXED。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2462 -
-26385 Could not parse r macro in BLOBDIR %s.
Could not parse the formatting macro r in BLOBDIR string. Refer to the
example below for the correct usage:
无法解析 BLOBDIR 字符串中的格式化宏 r。请参阅以下示例以了解正确用法：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR:/tmp/clobdir1.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
-26386 Could not parse r macro in CLOBDIR %s.
Could not parse the formatting macro r in CLOBDIR string. Refer to the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2463 -
example below for the correct usage:
无法解析 CLOBDIR 字符串中的格式化宏 r。有关正确用法，请参阅下面的示例：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB, col3 CLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR:/tmp/clobdir1.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
-26387 Cannot use r macro in BLOBDIR %s without having a matching macro in
filename %s.
Could
not
use
the
formatting
macro
r
in
BLOBDIR
string
without
having
a
corresponding
r macro in the DISK filename.
The following is an example of when this error is returned:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2464 -
如果磁盘文件名中没有相应的 r 宏，则无法使用 BLOBDIR 字符串中的格式化宏 r。
以下是返回此错误的示例：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat;
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
To fix the error remove the formatting macro r completely or change the
CREATE EXTERNAL TABLE statement to:
若要修复此错误，请完全删除格式化宏 r 或将 CREATE EXTERNAL TABLE 语句更改为：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)
USING
(
DATAFILES
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2465 -
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
-26388 Cannot use r macro in CLOBDIR %s without having a matching macro in
filename %s.
Could
not
use
the
formatting
macro
r
in
CLOBDIR
string
without
having
a
corresponding
r macro in the DISK filename. The following is an example of when this error is
returned:
如果磁盘文件名中没有相应的 r 宏，则无法使用 CLOBDIR 字符串中的格式化宏 r 。
以下是返回此错误的示例：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat;
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2466 -
CLOBDIR=/tmp/clobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
To fix the error remove the formatting macro r completely or change the
CREATE EXTERNAL TABLE statement to:
若要修复此错误，请完全删除格式化宏 r 或将 CREATE EXTERNAL TABLE 语句更改为：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR=/tmp/clobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2467 -
);
-26389 Range for r macro in BLOBDIR %s does not match range in filename %s.
The r macro range in the BLOBDIR string and filename in the DISK string
must match exactly.
The following is an example of when this error is returned:
BLOBDIR 字符串中的 r 宏范围和 DISK 字符串中的文件名必须完全匹配。
以下是返回此错误的示例：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(10..20)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2468 -
To fix the error change the CREATE EXTERNAL TABLE statement to:
若要修复此错误，请将 CREATE EXTERNAL TABLE 语句更改为：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 BLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
BLOBDIR=/tmp/blobdir1.%r(1..2)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
-26390 Range for r macro in CLOBDIR %s does not match range in filename %s.
The r macro range in the CLOBDIR string and the file name in the DISK string
must match exactly.
The following is an example of when this error is returned:
CLOBDIR 字符串中的 r 宏范围和 DISK 字符串中的文件名必须完全匹配。
以下是返回此错误的示例：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2469 -
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR=/tmp/clobdir1.%r(10..20)"
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
To fix the error change the CREATE EXTERNAL TABLE statement to:
若要修复此错误，请将 CREATE EXTERNAL TABLE 语句更改为：
CREATE EXTERNAL TABLE exttab (col1 INTEGER, col2 CLOB)
USING
(
DATAFILES
(
"DISK:/tmp/ext_byte.dat.%r(1..2);
CLOBDIR=/tmp/clobdir1.%r(1..2)"
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2470 -
),
DELUXE,
DELIMITER "%",
recordend "\n",
maxerrors 20,
rejectfile "/tmp/ext_byte.log"
);
-26391 FORMAT (%s) is not supported with collection types.
The FORMAT type specified is not supported with collection types.
Use DELIMITED or FIXED FORMAT when specifying collection data types.
集合类型不支持指定的 FORMAT 类型。指定集合数据类型时，请使用 DELIMITED
或 FIXED FORMAT。
-26392 The
INSERT
operation
into
an
external
table
failed
because
a
row
size
exceeds
the maximum limit of %s.
During an unload to an external table, the row size exceeded the maximum limit
for external tables.
在卸载到外部表期间，行大小超出了外部表的最大限制。
ACTION
操作
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2471 -
Collection data types or variable length user-defined types in the table can cause
the
row
sizeto
exceed
the
external
table
limit.
Large
object
columns
are
not
included
in the row size.Use another method to unload and load the table, such as the
High-Performance
Loader,the UNLOAD and LOAD statements in the DB-Access utility, or the onunload
and
onload utilities.
表中的集合数据类型或可变长度的用户定义类型可能导致行大小超过外部表限制。行大小
中不包括大对
象列使用另一种方法来卸载和加载表，例如高性能加载程序，DB-Access 实用程序中的
UNLOAD 和
LOAD 语句，或 onunload 和 onload 实用程序。
-26431 [Internal] Extended type is not valid.
If you cannot find a direct cause for this internal error, note
all circumstances and contact GBase Technical Support.
如果找不到此内部错误的直接原因，请记录所有情况并联系 GBase 技术支持。
-26600 Exceeded limit on maximum number of concurrent open databases.
The query is requesting too many concurrent open databases. The query is
likely to have nested routine calls or cascading trigger actions. Reduce the
nested routine calls or the cascading trigger actions and retry the query.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2472 -
该查询请求太多并发打开的数据库。查询可能具有嵌套的例程调用或级联触发器操作。
减少嵌套例程调用或级联触发器操作，然后重试查询。
-26601 Cannot define a partial-column index on the non-character column,
column-name.
You can specify a substring size in the CREATE INDEX statement only for
columns of character data types, such as CHAR, LVARCHAR, NCHAR, NVARCHAR,
or VARCHAR.
For the specified column, the index key must be the entire column value.
可以在 CREATE INDEX 语句中仅为字符数据类型的列指定子字符串大小，例如 CHAR、
LVARCHAR、NCHAR、NVARCHAR 或 VARCHAR。对于指定的列，索引键必须是整个列值。
Remove the substring size value that follows the column name and rerun
the statement.
删除列名后面的子字符串大小值，然后重新运行该语句。
-26736 The statement failed because the escape character is not a constant of type
CHARACTER.
When you use the LIKE or MATCHES operator, the character in the ESCAPE clause
must be a constant of type CHARACTER.
使用 LIKE 或 MATCHES 运算符时，ESCAPE 子句中的字符必须是 CHARACTER 类型的常量。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2473 -
-43026 The new chunk path does not exist. User interaction failed
while prompting user for input to continue further.
-43027 The new chunk path does not exist. User chose to discontinue
the rename chunk operation when prompted for input.
-43028 The new chunk path does not exist. User chose to continue the
rename chunk operation without creating the chunk path when prompted
for input.
-43063 The IFX_SERVERNUM environment variable is set to . Using
this value
to get logical logs from storage manager for imported restore.
-43064 The IFX_SERVERNUM environment variable is set to an invalid value of
.
Using
value
specified
by
SERVERNUM
parameter
in
the
ONCONFIG
file
to get
logical logs from storage manager for imported restore.
使用由 NCONFIG 文件中的 SERVERNUM 参数指定 值 ，
以从存储管理器
获取导入还原的逻
辑日志。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2474 -
The IFX_SERVERNUM environment variable set for imported restore is invalid.
为导入的还原设置的 IFX_SERVERNUM 环境变量无效。
ACTION
Set the IFX_SERVERNUM environment variable to a valid value.
行动
将 IFX_SERVERNUM 环境变量设置为有效值。
-43065 If doing an imported restore, and if the value of SERVERNUM parameter in
ONCONFIG file of the current database server is different from that of the
source database server, try setting IFX_SERVERNUM environment variable
to the source SERVERNUM value prior to re-starting log restore.
The value of SERVERNUM parameter in ONCONFIG file of the current database
server may be different from that of the source database server.
当前数据库服务器的 ONCONFIG 文件中 SERVERNUM 参数的值可能与源数据库服务器的值
不同。
ACTION
Try setting IFX_SERVERNUM environment variable to the same value as that
of the value of SERVERNUM parameter in ONCONFIG file of the source database
server prior to re-starting log restore.
行动
在重新启动日志还原之前，尝试将 IFX_SERVERNUM 环境变量设置为与源数据库服务器的
ONCONFIG
文件中的 SERVERNUM 参数值相同的值。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2475 -
-43195 ERROR: Logical Logs will not be backed up / salvaged because
LTAPEDEV value is . Normal backup (onbar -b) cannot be done
without logical logs being backed up, because restore of such backups
requires a logical log restore.
If the LTAPEDEV parameter value in your ONCONFIG file is /dev/null (UNIX)
or NUL (NT) or blank, logical log backup is not performed. These are
special values that the user sets to tell the server and ON-Bar that
log backups are not desired. Data in the logical log cannot be restored.
Normal backups (that are not whole system backups) cannot be restored
without logical log restore. Therefore such backups are not possible
without logical logs being backed up.
如果 ONCONFIG 文件中的 LTAPEDEV 参数值为 /dev/null（UNIX）或 NUL（NT）或为空，
则不执行逻辑日志备份。它们是用户设置的特殊值，用于告知服务器和 ON-Bar 不需要
日志备份。无法恢复逻辑日志中的数据。如果逻辑日志没有还原，则无法恢复正常备份
不是整个系统备份）。因此，如果不备份逻辑日志，则无法进行此类备份。
ACTION
Set the LTAPEDEV parameter value to something other than /dev/null (UNIX)
or NUL (NT) or blank if logical log backups are desired. Or use whole
system backup (onbar -b -w) and whole system physical-only restore
(onbar -r -w -p) which can be performed without logical logs being backed
up / restored.
行动
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2476 -
如果需要逻辑日志备份，请将 LTAPEDEV 参数值设置为 /dev/null（UNIX）或 NUL（NT）
以外的值或为空。或者使用整个系统备份（onbar -b -w）和整个系统物理还原（onbar
-r -w -p），它们可以在不备份/恢复逻辑日志的情况下执行。
-43196 ERROR: Logical Logs cannot be restored because LTAPEDEV value is
.
Restoring a normal backup (done by onbar -b) is not possible without restore
of logical logs. Only whole system backups (done with onbar -b -w) can be
restored without logical logs as whole system physical-only restore
(using onbar -r -w -p). Then use onmode commands (options -s or -m) to
bring server up without logical log restore.
如果不还原逻辑日志，则无法恢复正常备份（由 onbar -b 完成）。只有整个系统物理恢
复
（使用 onbar -r -w -p），才能恢复整个系统备份（使用 onbar -b -w 完成）而无需
逻辑日志。然后使用 onmode 命令（选项 -s 或 -m ）使服务器启动而不进行逻辑日志恢
复。
If the LTAPEDEV parameter value in your ONCONFIG file is /dev/null (UNIX)
or NUL (NT) or blank, logical log restore cannot be performed. These are
special values that the user sets to tell the server and ON-Bar that
log backup and restore is not desired. Data in the logical log cannot
be restored.
如果 ONCONFIG 文件中的 LTAPEDEV 参数值为 /dev/null（UNIX）或 NUL（NT）或为空，
则无法执行逻辑日志还原。这些是用户设置的特殊值，用于告知服务器和 ON-Bar 不
需要日志备份和还原。无法还原逻辑日志中的数据。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2477 -
ACTION
Set the LTAPEDEV parameter value to something other than /dev/null (UNIX)
or NUL (NT) or blank if logical log backup and restore is desired.
Only whole system backups (done with onbar -b -w) can be restored
without logical logs as whole system physical-only restore (using
onbar -r -w -p).
行动
如果需要逻辑日志备份和还原，请将 LTAPEDEV 参数值设置为 /dev/null（UNIX）
或 NUL（NT）以外的值或为空。只有整个系统物理恢复（使用 onbar -r -w -p），
才能恢复整个系统备份（使用 onbar -b -w 完成）而无需逻辑日志。
-43197 Duplicate log unique ID found for specified point-in-log
restore.
Onbar is restoring to the latest log unique ID .
Onbar found more than one of the specified point-in-log log unique IDs.
This situation can occur due to multiple timelines. Onbar will restore to
the latest timeline.
Onbar 发现了多个指定的日志记录日志唯一 ID。由于多个时间线，可能会出现这种情况。
Onbar 将恢复到最新的时间线。
ACTION
Onbar will restore to the latest timeline. Please use point-in-time restore
to restore to other timelines.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2478 -
行动
Onbar 将恢复到最新的时间线。请使用时间点恢复来恢复到其他时间线。
-43250 The child process for the backup and restore filter is terminating
with exit code .
This is an ON-Bar status message. The Child process used during
the backup and restore filter operation is exiting.
这是一个 ON-Bar 状态消息。在备份和还原过滤器操作期间使用的子进程正在退出。
ACTION
None
行动
无
-43298 Warning: BSA version is .
This version does not match with the version(s) specified in .
The version of XBSA shared library could not be identified in sm_versions file.
无法在 sm_versions 文件中标识 XBSA 共享库的版本。
ACTION
Look at the contents of the sm_versions file in $GBS_HOME/etc or
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2479 -
%GBS_HOME%\etc. Make sure the data match the version of your storage
manager, and confirm that this version of the storage manager has been
certified with this version of ON-Bar.
行动
查看 $GBS_HOME/etc 或 %GBS_HOME%\etc 中的 sm_versions 文件的内容。
确保数据与存储管理器的版本匹配，并确认此版本的存储管理器已通过此版本的 ON-Bar
认证。
-43299 Error identifying storage manager in XBSA shared library or sm_versions
file.
No storage manager could be identified in XBSA shared library or sm_versions
file.
在 XBSA 共享库或 sm_versions 文件中无法识别存储管理器。
ACTION
Look at the contents of the sm_versions file in $GBS_HOME/etc or
%GBS_HOME%\etc. Make sure the data match the version of your storage
manager, and confirm that this version of the storage manager has been
certified with this version of ON-Bar.
行动
查看 $GBS_HOME/etc 或 %GBS_HOME%\etc 中的 sm_versions 文件的内容。
确保数据与存储管理器的版本匹配，并确认此版本的存储管理器已通过此版本的 ON-Bar
认证。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2480 -
-43301 Filter terminated.
This is an ON-Bar status message. The backup and restore filter process
created by ON-Bar has terminated.
这是一个 ON-Bar 状态消息。ON-Bar 创建的备份和恢复过滤器进程已终止。
ACTION
None
行动
无
-43302 Using filter .
This is an ON-Bar status message. ON-Bar is using this filter program
for backup or restore.
这是一个 ON-Bar 状态消息。ON-Bar 正在使用此过滤器程序进行备份或还原。
ACTION
None
行动
无
-43311 Some
backups
that
can
be
expired
were
not
successfully
expired
at
the
Storage
Manager.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2481 -
Onsmsync requested the Storage Manager to expire a backup that is no longer
needed, but the expiration request did not complete successfully.
Onsmsync 请求 Storage Manager 使不再需要的备份到期，但是到期请求未成功完成。
ACTION
Examine Storage Manager logs and ON-Bar activity log for details.
行动
检查 Storage Manager 日志和 ON-Bar 活动日志以获取详细信息。
-43317 The
feature
requires
GBase
8s
Primary
Storage
Manager
(GBase 8s PSM).
Onsmsync can not complete the request because the Storage Manager does not
support it.
Onsmsync 无法完成请求，因为 Storage Manager 不支持。
ACTION
To enable this feature, configure ON-Bar to use GBase 8s Primary Storage
Manager (GBase 8s PSM) as its storage manager.
行动
要启用此功能，请将 ON-Bar 配置为使用 GBase 8s Primary Storage Manager
（GBase 8s PSM）作为其存储管理器。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2482 -
-43335 Too many onbar command line arguments, maximum allowed:
This error occurs during read command line arguments.
在读取命令行参数期间发生此错误。
ACTION
Limit the number of command line arguments to the maximum allowed value.
行动
将命令行参数的数量限制为允许的最大值。
-43334 (-43334) ERROR: Invalid copy ids received from Storage Manager.
The copy ID that the storage manager returned is inconsistent with the return code
存储管理器返回的副本 ID 与返回代码不一致。
ACTION
Check with the vendor of the Storage Manager.
行动
请与 Storage Manager 的供应商联系。
-43336 (-43336) Logical Logs cannot be backed-up because the database server is
dismissing the logical logs.
If the database server was started with an ONCONFIG file containing the LTAPEDEV
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2483 -
parameter with a value of '/dev/null' (UNIX), 'NUL', (Windows) or blank,logical
log back up cannot be performed. These special values indicate that log backups
are not desired. Data in this logical log cannot be restored in the future. Only
whole-system backups are allowed.
如果数据库服务器是使用包含值为 '/dev/null' (UNIX)、'NUL'(Windows)、或空白的
LTAPEDEV
参数的 ONCONFIG 文件启动的，则无法执行逻辑日志备份。这些特殊值表示不需要日志备
份。
此逻辑日志中的数据将来无法恢复。仅允许整个系统备份。
ACTION
If logical log restores are desired, then set the LTAPEDEV configuration
parameter value to something other than '/dev/null' (UNIX), 'NUL' (Windows)
or blank.
行动
如果需要逻辑日志还原，那么将 LTAPEDEV 配置参数值设置为 ‘/dev/null’(UNIX)、
‘nul’(Windows) 或空白以外的其他值。
-43338 (-43338) Non whole-system backups are not allowed if the database server
is dismissing logical logs.
Non whole-system backups need logical logs to be restored to bring the database
server to a consinstent state. If logs cannot be backed up, non whole-system
backups are not allowed.
非全系统备份需要还原逻辑日志，以使数据库服务器处于一致状态。
如果无法备份日志，则不允许进行非全系统备份。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2484 -
ACTION
Set the LTAPEDEV parameter value in the ONCONFIG file to something other than
'/dev/null' (UNIX), 'NUL' (Windows), or blank and restart the database server.
行动
将 ONCONFIG 配置文件中 LTAPEDEV 配置参数值设置为 ‘/dev/null’(UNIX)、
‘nul’(Windows)
或空白以外的其他值，并重新启动数据库服务器。
-43341 (-43341) Logical log is needed by this restore but cannot be
found in (null).
After physical restore of a dbspace, a minimum set of logs can be required to
maintain the logical consistency of the database server.
在物理还原 dbspace 后，可能需要较小的日志集来维护数据库服务器的逻辑一致性。
ACTION
If this is a whole-system restore, the logical restore part will be disabled
so the DBA can find the logs (if needed) and perform a logical restore (-r -l).
行动
如果这是一个完全系统还原，则将禁用逻辑还原部分，以便 DBA 可以找到日志（如果
需要）并执行逻辑还原（-r -l）。
If this is a non whole-system restore, the restore cannot proceed until the
missing log are found.
如果这是非完全系统还原，则在找到丢失的日志之前无法继续还原。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2485 -
-43342 (-43342) Cannot read reserved pages from rootdbs object.
The ON-Bar process tried to extract the reserved pages from a rootdbs backup but
was unsuccessful.
ON-Bar 进程试图从 rootdbs 备份中提取保留页面但是不成功。
ACTION
Call GBase Support.
行动
联系 GBase 支持。
-43343 (-43343) No suitable root dbspace backup was found.
The ON-Bar boot file (ixbar) does not contain a backup for the rootdbs that can
be restored with the selected options.
ON-Bar boot 文件（ixbar）不包含可以使用所选选项还原的 rootdbs 的备份。
ACTION
If you received this message after running the onbar -r -w command, check if your
last backup was a whole backup performed with the onbar -b -w command. You can only
do a whole restore on a whole backup. If your last backup was not a whole backup,
use the onbar -r command to perform the restore. If your last backup was a whole
restore, the ixbar file might be inconsistent. Contact GBase Support.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2486 -
行动
如果在运行 onbar
-r
-w 命令后收到此消息，请检查上次备份是否是使用 onbar
-b
-w 命
令执行的
整库备份。
您只能对整库备份执行整库还原。
如果上次备份不是整库备份，
请使用 onbar
-r
命令执行
还原。如果您的上次备份是整库还原，则 ixbar 文件可能不一致。联系 GBase 支持。
If you received this message after running the onbar -r command, the ixbar file
might
be inconsistent. Contact GBase Support.
如果在运行 onbar
-r 命令后收到此消息，则 ixbar 文件可能不一致。联系 GBase 支持。
-43344 (-43344) The rootdbs level 0 restore is not restartable in recovery mode.
Shutdown the server and do a cold restore.
The rootdbs level 0 restore must be a cold restore.
rootdbs 0 级别还原必须是冷还原。
ACTION
Shutdown the server and do a cold restore.
行动
关闭服务器并执行冷恢复。
-43353 WARNING: Logical logs will not be backed up as part of this operation.
Make sure that logical logs are backed up separately.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2487 -
The ON-Bar settings switched off implicit log backup after a dbspace backup.
在 dbspace 备份后，ON-Bar 设置关闭了隐式日志备份。
ACTION
Make sure that logs are backed up with a separate ON-Bar command.
行动
确保使用单独的 ON-Bar 命令备份日志。
-43354 WARNING: Logical logs were not backed up as part of this operation.
Logs through log unique ID %1 are needed for restoring this backup.
Make sure these logs are backed up separately.
还原此备份需要记录日志唯一 ID %1。确保单独备份这些日志。
The ON-Bar settings switched off implicit log backup after a dbspace backup.
在 dbspace 备份后，ON-Bar 设置关闭了隐式日志备份。
ACTION
Make sure that logs are backed up with a separate ON-Bar command.
行动
确保使用单独的 ON-Bar 命令备份日志。
-43355 ERROR: Logical logs are full and must be backed up before dbspace
backup without log backup is possible.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2488 -
The ON-Bar settings switched off implicit log backup.
ON-Bar 设置关闭了隐式日志备份。
ACTION
Backup the logs with a separate ON-Bar command.
行动
使用单独的 ON-Bar 命令备份日志。
-43372 Failed to add selected row to linked list for %1.
Attempt to add the selected row to the linked list failed.
尝试将所选行添加到链接列表失败。
ACTION
Stop ON-Bar and retry your command.
行动
停止 ON-Bar 并重试您的命令。
If the error persists, please note all circumstances, save a copy of
the ON-Bar and ONLine message logs and contact GBase Technical Support。
如果错误仍然存在，请记录所有情况，保存 ON-Bar 和 ONLine 消息日志的副本，
并联系 GBase 技术支持。
-43374 %1 for %2 exceeds it's maximum allowed length of %3 characters.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2489 -
SQL statement is longer than it's maximum allowed size.
SQL 语句超出了其允许的最大长度。
ACTION
Shorten the statement or divide it into multiple statements.
行动
缩减该语句，或将它分成多个语句。
-43375 ERROR: Attempt to build an SQL where clause for %1 failed.
No data was passed to the build-where-clause function, so no SQL where clause
can be built.
没有数据传递给 build-where-clause 函数，因此不能构建 SQL where 子句。
ACTION
Make sure that bar_object and bar_server tables in sysutils
database has data in it.
行动
确保 sysutils 数据库中的 bar_object 和 bar_server 表中包含数据。
-43377 %1 required to insert a row into %2.0
An SQL insert into this table can't happen without the specified data.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2490 -
没有指定的数据，不能在此表中插入 SQL。
ACTION
Stop ON-Bar and retry your command.
行动
停止 ON-Bar 并重试命令。
If the error persists, please note all circumstances, save a copy of
the ON-Bar and ONLine message logs and contact GBase Technical Support.
如果错误仍然存在，请记录所有情况，保存 ON-Bar 和 ONLine 消息日志的副本，
并通过联系 GBase 技术支持。
-43378 Missing data for %1.
Required data is missing.
缺少必需的数据。
ACTION
Stop ON-Bar and retry your command.
行动
停止 ON-Bar 并重试命令。
If the error persists, please note all circumstances, save a copy of
the ON-Bar and ONLine message logs and contact GBase Technical Support.
如果错误仍然存在，请记录所有情况，保存 ON-Bar 和 ONLine 消息日志的副本，
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2491 -
并通过联系 GBase 技术支持。
-43379 Updates to primary key are not allowed.
Updating a table's primary key is not allowed.
不允许更新表的主键。
ACTION
First, delete the row and then attempt to insert a new row with the
new primary key.
行动
首先，删除该行，然后尝试使用新主键插入新行。
-43383 Unable
to
update
timestamp
to
for
action
number
None
无
ACTION
Ask your database administrator to repair the data.
行动
请数据库管理员修复数据。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2492 -
-43384 Creating %1 to allow restore %2
missing chunks
缺少 chunk
ACTION
Creating missing chunks
行动
创建所需的 chunk。
-43386 Storage space was not backed up so it cannot be restored/verified.
None
无
ACTION
None
行动
无
-43387 Unable to determine if is a dbspace or dbslice: %2
An error occurred while trying to convert a dbslice to its list
of dbspaces. Most likely there is a typographical error or a
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2493 -
coserver failed to respond.
尝试将 dbslice 转换为其 dbspace 列表时发生错误。很可能是排版错误或协同服务
器无法响应。
ACTION
Verify that all coservers are in the correct state (on-line or quiescent
for a backup or warm restore and micro-kernel for cold restore).
行动
验证所有协同服务器是否处于正确状态（联机或热恢复的联机或静态以及微内核的冷恢复
状态）。
-43396 Logstream does not exist.
ACTION
Verify the logstream exists in this database server.
行动
验证日志流在数据库服务器中存在。
-43397 Storage space does not exist.
ACTION
Verify the storage space exists in this database server and retry the
backup or restore.
行动
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2494 -
验证此数据库服务器中是否存在存储空间，然后重试备份或还原。
-83336 The
warm
restore
failed
because
the
dbspace
number
is
full.
A warm restore operation requires space in a temporary dbspace to write
the temporary logical logs to be restored. The specified dbspace is now full and
the warm restore cannot continue.
热恢复操作需要临时 dbspace 中的空间来写入要恢复的临时逻辑日志。指定的 dbspace
已满，
并且热恢复无法继续。
ACTION
Free space in the dbspace or specify another dbspace and restart the restore.
行动
释放 dbspace 中的可用空间或指定另一个 dbspace 并重新启动还原。
-26097 Operation is not valid on a secondary server.
The above operation is not valid on the secondary server.
Attempt such operations only on the primary node in the HDR pair or cluster.
上述操作在辅助服务器上无效。仅在 HDR 对或群集中的主节点上尝试此类操作。
-43083 System call stat() or fstat() failed on file , error number errno>.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2495 -
An operating system error prevented information from being returned for the
specified the file.
操作系统错误导致无法为指定的文件返回信息。
ACTION
Correct the error and retry your command.
行动
更正错误并重试命令。
-43084 Error while writing data to file .
An error occurred while writing to the file. The file system might be running out
of space.
写入文件时发生错误。文件系统可能空间不足。
ACTION
Contact GBase Software support.
行动
联系 GBase 软件支持。
-83380 An archive checkpoint could not be completed in the secondary server.
An archive checkpoint was attempted on a secondary server but we failed. Possible
causes include the LOG_STAGING_DIR configuration parameter not being set, or not
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2496 -
receiving a checkpoint from the primary server within the time interval specified
by the BAR_CKPSEC_TIMEOUT configuration parameter
在辅助服务器上尝试了归档检查点，但是失败了。可能的原因包括没有设置
LOG_STAGING_DIR
配置参数，或者未在 BAR_CKPSEC_TIMEOUT 配置参数指定的时间间隔内从主服务器接收检
查点。
ACTION
Check the online message log for more information and correct the problem.
If the checkpoint timed out you can increase the value of the BAR_CKPTSEC_TIMEOUT
configuration parameter.
行动
检查联机消息日志以获取更多信息并更正问题。如果检查点超时，则可以增加
BAR_CKPTSEC_TIMEOUT 配置参数的值。
-83353 Attempt to reopen a parallel whole system backup failed with
return code ..
This is an internal error.
这是一个内部错误。
ACTION
Retry the parallel whole system backup. If it fails again, contact
GBase Software Support.
行动
重试并行整个系统备份。如果再次失败，请与 GBase 软件支持联系。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2497 -
-43141 The edition of GBase 8s Dynamic Server currently running restricts
the number of parallel backup or restore processes to
Resetting BAR_MAX_BACKUP to .
将 BAR_MAX_BACKUP 重置为
Some editions of GBase 8s Dynamic Server limit the number of parallel
backup or restore processes and this limit has been exceeded.
某些版本的 GBase 8s Dynamic Server会 限制并行备份或还原过程的数量，并且已超出此
限制。
ACTION
The BAR_MAX_BACKUP configuration parameter has been dynamically reset
to the maximum number processes that are allowed for this edition.
行动
BAR_MAX_BACKUP 配置参数已动态重置为此版本允许的最大数量进程。
-83974 This edition of GBase 8s Dynamic Server supports only
nodes in a cluster. Stopping connection attempt.
Some editions of GBase 8s Dynamic Server limit the number of nodes in a cluster.
某些版本的 GBase 8s Dynamic Server 限制了群集中的节点数。
ACTION
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2498 -
Keep the number of nodes under the allowed value.
Ensure that the number of nodes in the cluster does not exceed the maximum number
of nodes supported by the edition.
行动
将节点数保持在允许的值下。确保群集中的节点数不超过版本支持的最大节点数。
-83975 This edition of GBase 8s Dynamic Server does not support
nodes in a cluster. Stopping connection attempt.
Some editions of GBase 8s Dynamic Server limit the type of secondary nodes that
can be added to the cluster.
某些版本的 GBase 8s Dynamic Server 限制了可以添加到群集的辅助节点的类型。
ACTION
Avoid adding non-allowed node types to the cluster.
行动
避免将非允许的节点类型添加到群集。
-26401 Cannot connect to accelerator server.
Connecting to the accelerator server failed.
Possible reason can be:
- The accelerator server is not running.
- The connectivity information (a group entry in the sqlhosts file with the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2499 -
name of the accelerator) is outdated or invalid.
- The database contains stale meta information (AQTs) of data marts that
no longer exist.
连接到加速器服务器失败。
可能的原因可能是：
- 加速器服务器未运行。
- 连接信息（sqlhosts 文件中的加速器名称的组条目）已过期或无效。
- 数据库包含不再存在的数据集市的陈旧元信息（AQT）。
ACTION
Check if the accelerator server is operational.
Log on to the computer as either user root or as user gbasedbt, and then run
this command: ondwa status
行动
检查加速器服务器是否正常运行。以 root 用户或用户 gbasedbt 身份登录计算机，
然后运行以下命令：ondwa status
Check the sqlhosts file to find the group entry with the name of the
accelerator. If the entry is considered correct, it is possible that the
authentication token is outdated. It may be necessary to renew the entry
by removing the accelerator and setting up the initial connection anew, as
described in the manual. If the accelerator is shared with another GBase 8s
server instance (e.g. in a HA environment), it may be necessary to get an
up-to-date copy of the sqlhosts entry from one of the sharing GBase 8s server
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2500 -
instances.
检查 sqlhosts 文件以查找具有加速器名称的组条目。如果该条目被认为是正确的，则认
证令牌
可能已过时。如手册中所述，可能需要通过移除加速器并重新设置初始连接来更新条目。
如果加速
器与另一个 GBase
8s 服 务器实例共享（例如在 HA 环境中），则可能需要从共享 GBase
8s
服务器获取 sqlhosts 条目的最新副本实例。
The meta information for data marts (AQTs) are special views in the system
catalog table systables of a database, with a name beginning with "aqt".
After removing data marts when connected to a different database, or after
setting up the accelerator server from scratch, it is possible that stale
AQTs are left over. Stale AQTs should be removed manually using the
"DROP VIEW ..." command.
数据集市（AQT）的元信息是数据库的系统目录表 systables 中的特殊视图，名称以"aqt"
开头。
在连接到不同数据库时删除数据集市后，或者在从头开始设置加速器服务器之后，可能会
遗留过时
的 AQT。应使用"DROP VIEW ..."命令手动删除旧的 AQT。
-26402 The dynamic SQL operation failed to run on the accelerator server.
The dynamic SQL operation failed on the accelerator server during the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2501 -
PREPARE, OPEN, FETCH, or CLOSE phase.
在 PREPARE、OPEN、FETCH 或 CLOSE 阶段，加速器服务器上的动态 SQL 操作
失败。
ACTION
Note all the circumstances including the complete error message and
contact GBase Software Support.
行动
请注意所有情况，包括完整的错误消息，并与 GBase 软件支持联系。
-26403 An SQDWA error occurred.
The query cannot be accelerated due to an internal error that was detected
in the SQDWA component.
由于在 SQDWA 组件中检测到内部错误，无法加速查询。
ACTION
Note all the circumstances including the complete error message and contact
GBase Software Support.
行动
请注意所有情况，包括完整的错误消息并联系 GBase 软件支持。
-26404 The query cannot be accelerated. Fallback to running the query on
the database server is disabled.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2502 -
Is is not possible to accelerate the query and the query cannot be sent to
the database server for processing.
无法加速查询，也无法将查询发送到数据库服务器进行处理。
ACTION
To enable the query to run on the database server, run the following
statement and then run the query again: set environment use_dwa 'fallback on'
行动
要使查询在数据库服务器上运行，请运行以下语句，然后再次运行查询：
set environment use_dwa 'fallback on'
-26406 Opening multiple cursors to an accelerator server is not allowed.
Opening multiple cursors to an accelerator server from a single session
is not allowed.
不允许从单个会话向加速器服务器打开多个游标。
ACTION
Close the previous cursor before opening a new cursor to the same accelerator
server.
行动
在将新光标打开到同一个加速器服务器之前关闭上一个光标。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2503 -
-26407 Changing
the
data
type
for
the
host
variables
is
not
allowed
in
an
accelerated
query.
Changing the data type of host variables is not allowed during query
acceleration.
在查询加速期间，不允许更改主机变量的数据类型。
ACTION
Prepare the SQL statement again using the new host variables, and then run the
query again.
行动
使用新的主机变量再次准备 SQL 语句，然后再次运行查询。
-26408 Arithmetic operation resulted in an overflow
The value is too large, and an overflow has occurred.
该值太大，发生溢出。
ACTION
You either sent an arithmetic expression in an SQL statement or prepared
statement to a database server, or a database server returned an arithmetic
expression. This expression caused an overflow. Change the arithmetic
expression so that it does not cause an overflow.
行动
要么将 SQL 语句中的算术表达式或预处理语句发送到数据库服务器，
要么数据库服务器返
回
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2504 -
算术表达式。这个表达式引起了溢出。更改算术表达式，以便它不会导致溢出。
-21528 Defragment: The partition does not require defragmentation.
ACTION
No action required.
行动
不需任何操作。
-21529 Defragment:
Could
not
find
a
large
enough
extent
to
cover
2
or
more
extents.
ACTION
Add
another
chunk
to
the
dbspace
or
delete
some
partitions
to
create
more
free
space.
行动
将另一个 chunk 添加到 dbspace 或删除一些分区以创建更多可用空间。
-21530 Defragment: Defragmentation is not supported on secondary servers.
ACTION
Defragment on the primary server. Changes will be replicated to the
secondary servers.
行动
主服务器上的分片整理。更改将复制到辅助服务器。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2505 -
-21531 Defragment: A partition that contains a partition header page table cannot
be defragmented.
ACTION
Do not attempt to run the defragmenter on the partition header page table - this
is not allowed.
行动
不要试图在分区标题页表上运行分片整理程序-这是不允许的。
-21532 Defragment: The partition is in the wrong state or an incompatible type
ACTION
If a conflicting action is occurring on the partition, run defragmentation
later. Otherwise the partition is a type that cannot be defragmented. See the
GBase 8s Data Server Administrator's Reference for information on
defragmentation restrictions.
行动
如果分区上发生冲突操作，请稍后运行分片整理。否则，分区是无法进行分片整理。
有关分片整理限制的信息，请参阅《GBase 8s 数据服务器管理员参考》。
-21533 Defragment: A defragmentation task is already in progress on this dbspace.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2506 -
ACTION
Run one defragmentation task on a dbspace at a time.
行动
在 dbspace 上一次运行一个分片整理任务。
-21534 Defragment: Internal error - cannot map the logical page number.
ACTION
Contact GBase Software Support.
行动
联系 GBase 软件支持。
-21535 Defragment: Internal error - cannot free the old chunk extent.
ACTION
Contact GBase Software Support.
行动
联系 GBase 软件支持。
-21536 Defragment: Internal error - cannot have two destination extents.
ACTION
Contact GBase Software Support.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2507 -
行动
联系 GBase 软件支持。
-21537 Defragment: This command cannot be run while a defragmentation is in
progress.
ACTION
Rerun the command after defragmentation is complete.
行动
分片整理完成后重新运行命令。
-21539 Defragment: You can't run this command on catalog/pseudo/temp tables
ACTION
Run defragment on a regular table/partition
行动
在常规表/分区上运行分片整理。
-21541 The total amount of storage space for the list of dbspaces, blobspaces, and
sbspaces exceeds the TENANT_LIMIT_SPACE property setting for the tenant database.
ACTION
To resolve the discrepancy between the total size of the current storage spaces
and
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2508 -
the configured storage limit, you can take at least one of these actions:
1. Increase the value of the TENANT_LIMIT_SPACE property,
2. or change the list of storage spaces,
3. or reduce the size of one or more of the storage spaces.
行动
要解决当前存储空间的总大小与配置的存储限制之间的差异，
可以至少执行以下操作之一：
1.增加 TENANT_LIMIT_SPACE 属性的值，
2.或更改存储空间列表，
3.或减小一个或多个存储空间的大小。
-21551 Tenant PIT Restore Generic Error
ACTION
This is a Tenant PIT Restore Generic Error.
行动
这是租户PIT恢复通用错误。
-26451 STATCHANGE can take values in the range of 0 to 100.
ACTION
STATCHANGE specifies a percentage of how much a table distribution
can change before it is considered stale. Set STATCHANGE to an integer
value in the range from 0 to 100.
行动
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2509 -
STATCHANGE 指定表分布在被视为过时之前可以更改的百分比。将 STATCHANGE 设置
为 0 到 100 之间的整数值。
-26452 You cannot specify the STATLEVEL as FRAGMENT for non-fragmented tables.
ACTION
You can set the STATLEVEL attribute to the FRAGMENT option only for
fragmented tables. Specify the TABLE or AUTO options for non-fragmented
tables.
行动
只能为分片表将 STATLEVEL 属性设置为 FRAGMENT 选项。为非分片表指定 TABLE 或
AUTO 选项。
-26454 Cannot specify both a PRIMARY KEY constraint and a NULL constraint
for the same column.
The database server issues this error when the CREATE TABLE or ALTER TABLE
statement attempts to define a table schema that includes a column definition
with contradictory specifications regarding NULL values.
- The PRIMARY KEY constraint prevents the database server from storing NULL
values in this column.
- The NULL constraint allows the database server store NULL values in this
column.
当 CREATE TABLE 或 ALTER TABLE 语句试图定义表架构时，数据库服务器会发出此错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2510 -
语句尝试
定义一个表模式，该表模式包含具有关于 NULL 值的矛盾规范的列定义。
- PRIMARY KEY 约束阻止数据库服务器在此列中存储 NULL 值。
- NULL 约束允许数据库服务器在此列中存储 NULL 值。
To avoid this error, revise the column definition so that it does not include
both PRIMARY KEY and NULL specifications on the same column.
- If you want this column to be the primary key of this table, you must drop
the NULL specification in the column definition.
- If you want to allow NULL values in this column, you must drop the PRIMARY
KEY specification in the column definition.
要避免此错误，请修改列定义，使其在同一列上不包含 PRIMARY KEY 和 NULL 规范。
- 如果希望此列成为此表的主键，则必须在列定义中删除 NULL 规范。
- 如果要在此列中允许NULL值，则必须在列定义中删除 PRIMARY KEY 规范。
-26455 Cannot
specify
both
a
NOT
NULL
constraint
and
a
NULL
constraint
for
the
same
column.
The database server issues this error when the CREATE TABLE or ALTER TABLE
statement attempts to define a table schema that includes a column definition
with contradictory specifications regarding NULL values.
- The NOT NULL constraint prevents the database server from storing NULL
values in this column.
- The NULL constraint allows the database server store NULL values in this
column.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2511 -
当 CREATE TABLE 或 ALTER TABLE 语句尝试定义包含具有关于 NULL 值的矛盾规范的列定
义的
表模式时，数据库服务器会发出此错误。
- NOT NULL 约束阻止数据库服务器在此列中存储 NULL 值。
- NULL 约束允许数据库服务器在此列中存储 NULL 值。
To avoid this error, revise the column definition so that it does not include
both NOT NULL and NULL specifications on the same column.
- If you want to prohibit NULL values in this column, you must drop the
NULL specification in the column definition.
- If you want to allow NULL values in this column, you must drop the NOT
NULL specification in the column definition.
要避免此错误，请修改列定义，使其在同一列上不包含 NOT NULL 和 NULL 规范。
- 如果要禁止此列中的 NULL 值，则必须在列定义中删除 NULL 规范。
- 如果要在此列中允许 NULL 值，则必须在列定义中删除 NOT NULL 规范。
-26456 The authorization ID %s is not defined for the trusted context.
Authorization name attempted to reuse a trusted connection
using trusted context. The trusted context name can not be used under the
The switch user failed.
授权名称 尝试使用可信上下文重用可信连接。无法在
下使用可信上下文名称。交换机用户失败。
This error can also occur for one of the following reasons:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2512 -
出于以下原因之一，也可能发生此错误：
- The authorization ID is allowed to use the trusted context, but
authentication is required and the request to switch users did not
include the authentication token
允许授权标识使用互信上下文，但需要进行身份验证，并且切换用户的请求不包括
身份验证令牌
- The authorization ID is allowed to use the trusted context, but the
trusted context is disabled
允许授权标识使用互信上下文，但禁用互信上下文
- The system authorization ID attribute of the trusted context object
associated with the trusted connection has been changed
已更改与互信连接关联的互信上下文对象的系统授权标识属性
- The trusted context object associated with the trusted connection
has been dropped
已删除与互信连接关联的互信上下文对象
The attempt to reuse the trusted connection fails. The trusted connection is
in an unconnected state.
尝试重用互信连接失败。互信连接处于未连接状态。
-26457 The trusted context already exists.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2513 -
The context name is already defined in the database. For CREATE TRUSTED CONTEXT
or ALTER TRUSTED CONTEXT statement, a trusted context with the specified name
already exists. Verify that you have specified the correct context name and that
you are in the correct database.
已在数据库中定义上下文名称。对于 CREATE
TRUSTED
CONTEXT 或 ALTER
TRUSTED
CONTEXT
语句，已存在具有指定名称的互信上下文。验证是否指定了正确的上下文名称，以及是否
在正确的
数据库中。
-26458 The trusted context specified authorization ID
which is already specified for another trusted context.
A CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement for specified
SYSTEM AUTHID , but this authorization ID is already
defined to use a different trusted context. A system authorization ID
that is defined as the SYSTEM AUTHID for a trusted context cannot be
associated with any other trusted context as the SYSTEM AUTHID.
为指定的 SYSTEM AUTHID 创建 CREATE TRUSTED CONTEXT
或 ALTER TRUSTED CONTEXT 语句，但此授权标识已定义为使用不同的互信上下文。定义为
互信上下文的 SYSTEM AUTHID 的系统授权标识不能作为 SYSTEM AUTHID 与任何其他互信
上下文关联。
Use the following query to determine which trusted context is already
using the authorization ID:
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2514 -
使用以下查询确定哪个互信上下文已在使用授权标识：
SELECT CONTEXTNAME FROM SYSUSER.SYSTRUSTEDCONTEXT
WHERE AUTHID =
To correct this error change the authorization ID for the trusted context
and reissue the CREATE or ALTER statement.
要更正此错误，请更改互信上下文的授权标识，然后重新发出 CREATE 或 ALTER 语句。
-26459 The trusted context does not exist.
The specified trusted context does not exist in the database.
Verify that you have specified the correct trusted context name.
数据库中不存在指定的互信上下文 。验证是否指定了正确的互信上
下文名称。
-26460 Attribute with value cannot be dropped or altered
because it is not part of the definition of trusted context.
Attribute was specified for a trusted context, but the
trusted context is not defined with an attribute with this name. The statement
could not be processed.
为互信上下文指定了属性 ，但未使用具有此名称的属性定义互信上下文。
无法处理该语句。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2515 -
To correct this error remove the name of the unsupported attribute and
re-issue the statement.
要更正此错误，请删除不支持的属性的名称，然后重新发出该语句。
-26461 Attribute with value is not unique for trusted context.
During the CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT a duplicate
value was specified for the attribute. Each pair of attribute name
and value must be unique for a trusted context. The statement cannot be processed.
在 CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT 期间，为属性指定了重复值
。对于互信上下文，每对属性名称和值必须是唯一的。无法处理此语句。
To correct this error remove the non-unique specification of
and and re-issue the statement.
要更正此错误，请删除 的非唯一规范，然后重新发出该语句。
-26462 User cannot be dropped or altered because it is not part
of the definition of trusted context
User was specified for a trusted context, but the
trusted context is not defined with an user with this name. The statement
could not be processed.
已为互信上下文指定了用户 ，但未使用具有此名称的用户定义互信上下文。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2516 -
无法处理此语句。
To correct this error remove the name of the undefined user and
re-issue the statement.
要更正此错误，请删除未定义用户的名称并重新发出该语句。
-26463 User is not unique for trusted context.
During the CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT a duplicate
value of user was specified in the WITH USE FOR clause.
The statement cannot be processed.
在 CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT 期间，在 WITH USE FOR
子句中指定了用户 的重复值。无法处理此语句。
To correct this error remove the non-unique specification of user name
and and re-issue the statement.
要更正此错误，请删除用户名的非唯一规范，然后重新发出该语句。
-26464 A CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT statement specified
%s more than once or the trusted context is already defined to be used by
this authorization ID or PUBLIC.
The statement specified that be allowed to use the trusted
context, but the specified authorization ID or PUBLIC is already defined to use
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2517 -
the trusted context, or the authorization ID was specified more than once in
the statement. The authorization ID or PUBLIC must not already be allowed to use
the trusted context, and it can only be specified once within a statement for a
trusted context. The statement could not be processed.
该语句指定 允许使用互信上下文，但指定的授权 ID 或 PUBLIC
已定义
为使用互信上下文，或者在语句中多次指定授权 ID。不能允许授权 ID 或 PUBLIC 使用互
信上下文，
并且只能在互信上下文的语句中指定一次。无法处理该语句。
If the authorization ID or PUBLIC was specified more than once, remove the extra
specifications of , and re-issue the statement. If an ALTER
TRUSTED CONTEXT statement that contained an ADD USE FOR clause, and the trusted
context already was defined for use by that authorization ID or PUBLIC, use the
REPLACE USE FOR clause instead to redefine the usage characteristics for the
specified users to use the trusted context.
如果多次指定授权 ID 或 PUBLIC，请删除 的额外规范，然后重新
发出该语句。如果包含 ADD USE FOR 子句的 ALTER TRUSTED CONTEXT 语句以及已定义可
供该授权 ID 或 PUBLIC 使用的互信上下文，请使用 REPLACE USE FOR 子句重新定义指定
用
户的使用特性以使用该信任上下文。
-26465 An ALTER TRUSTED CONTEXT statement for specified %s but the trusted
context is not currently defined to be used by this authorization ID or PUBLIC.
An ALTER TRUSTED CONTEXT statement for attempted to replace or remove the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2518 -
ability for to use the trusted context, but the specified
authorization ID or PUBLIC is not currently defined to use the trusted context.
The statement could not be processed.
ALTER TRUSTED CONTEXT 语句，用于尝试替换或删除 使用互信上
下文的功能，但当前未定义指定的授权 ID 或 PUBLIC 以使用互信上下文。无法处理该语
句。
If an ALTER TRUSTED CONTEXT statement that contained a REPLACE USE FOR clause,
and the trusted context was not already was defined for use by that authorization
ID or PUBLIC, use the ADD USE FOR clause instead to define the trusted context to
be used by the specified users. If the ALTER TRUSTED CONTEXT statement contained
the DROP USE FOR clause, none of the specified authorization IDs or PUBLIC were
currently defined to use the trusted context.
如果包含 REPLACE USE FOR 子句的 ALTER TRUSTED CONTEXT 语句以及尚未定义互信上下
文以供该授权 ID 或 PUBLIC 使用，请使用 ADD USE FOR 子句来定义指定用户要使用的互
信
上下文。如果 ALTER TRUSTED CONTEXT 语句包含 DROP USE FOR 子句，则当前未定义任何
指定的授权 ID 或 PUBLIC 以使用互信上下文。
-26466 ENCRYPTION attribute %s cannot be specified more than once.
Specify only one ENCRYPTION attribute in a statement. Alternatively, specify one
WITH ENCRYPTION attribute for each ADDRESS attribute.
在语句中仅指定一个 ENCRYPTION 属性。
或者，
为每个 ADDRESS 属性指定 WITH
ENCRYPTION
属性。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2519 -
-26468 A DBSECADM users cannot create a trusted context for themselves.
The statement (CREATE TRUSTED CONTEXT or ALTER TRUSTED CONTEXT) was not
processed because the specified SYSTEM AUTHID matched that of the DBSECADM
user who ran the statement.
未处理语句（CREATE TRUSTED CONTEXT 或 ALTER TRUSTED CONTEXT），因为指定的
SYSTEM AUTHID 与运行该语句的 DBSECADM 用户的系统匹配。
Specify a different authorization ID or run the statement as a different
DBSECADM user.
指定其他授权 ID 或将语句作为不同的 DBSECADM 用户运行。
-26469 A trusted connection was not established because the trusted context
is not enabled.
Ensure that the trusted context is correctly defined and enabled, and then try
to establish a trusted connection.
确保正确定义并启用了互信上下文，然后尝试建立互信连接。
-26470 The database specified ('database name') is not associated with the
trusted context.
Specify the correct database for the trusted context associated with
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2520 -
the current trusted connection or establish a regular connection to the database.
为与当前可信连接关联的互信上下文指定正确的数据库，或者建立与数据库的一般连接。
-26471 Internal
Function
(%s):
Unable
to
send
or
receive
from
the
Session
Manager.
This error indicates that the server was able to establish connection to the
Session Manager but failed to send or receive data.
If you cannot find a direct cause for this internal error, note
all circumstances and contact GBase Software Support.
此错误表示服务器能够建立与会话管理器的连接但无法发送或接收数据。如果找不到此内
部错误
的直接原因，请记录所有情况并联系 GBase 软件支持。
-26472 Internal Error occurred during a BLOB operation in function %s.
If you cannot find a direct cause for this internal error, note
all circumstances and contact GBase Software Support.
如果找不到此内部错误的直接原因，请记录所有情况并与 GBase 软件支持联系。
-26473 Internal Error occurred. The required parameter %s is NULL.
If you cannot find a direct cause for this internal error, note
all circumstances and contact GBase Software Support.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2521 -
如果找不到此内部错误的直接原因，请记录所有情况并与 GBase 软件支持联系。
-26474 Internal Error occurred during codeset conversion in function %s.
If you cannot find a direct cause for this internal error, note
all circumstances and contact GBase Software Support.
如果找不到此内部错误的直接原因，请记录所有情况并与 GBase 软件支持联系。
-26475 Function (%s): Unable to connect to the Session Manager.
This error indicates that the server is unable to connect to the Session Manager
which is necessary for debugging the SPL routine. Verify that the Session Manager
is running in the specified host system at the specified port number. Also make
sure that the Session Manager host and the port can be accessed from the host
system where the server is running.
此错误表示服务器无法连接到调试 SPL 例程所需的会话管理器。
验证会话管理器是否在指
定端口号
的指定主机系统中运行。还要确保可以从运行服务器的主机系统访问会话管理器主机和端
口。
-26476 Can not create temp table with ERKEY
It is illegal to create a temp table with ERKEY
使用 ERKEY 创建临时表是非法的。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2522 -
-26477 Illegal usage of ERKEY
Your usage of ERKEY is not legal
ERKEY 的用法不合法。
-26478 Can not add ERKEY when table already has ERKEY
You attempted to alter a table to include the ERKEY attribute when that table
already had the ERKEY attribute.
该表已具有 ERKEY 属性时，您试图更改表以包含 ERKEY 属性。
-26479 Can not drop ERKEY when table does not have ERKEY
You attempted to alter a table to drop the ERKEY when the table did not
have the ERKEY attribute.
当表没有 ERKEY 属性时，试图更改表以删除 ERKEY。
-26480 Illegal usage of ifx_replcheck
You attempted to use the ifx_replcheck column in an illegal manner.
试图以非法的方式使用 IFX_PLECHECK 列。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2523 -
-26481 Cannot perform this operation through a grid
Renaming replicated database is not supported through a grid.
Manually rename the replicated database at all grid servers outside
of the grid context.
不支持通过网格重命名复制数据库。在网格上下文之外的所有网格服务器上手动重命名复
制的数据库。
-26482 Cannot alter a replicated table in a grid outside of the same grid context
The ALTER TABLE statement on a replicated table that was created through
a grid must be executed within the same grid context and with
replication enabled by setting the ER_enable argument to 1.
通过网格创建的复制表上的 ALTER TABLE 语句必须在同一网格上下文中执行，并通过将
ER_enable 参数设置为 1 来启用复制。
-26483 Grid or Region is not defined
A SET ENVIRONMENT GRID_SELECT command was issued using a non-existant
grid or region name.
使用不存在的网格或区域名称发出了 SET ENVIRONMENT GRID_SELECT 命令。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2524 -
-26484 SQL error encountered on a SET ENVIRONMENT GRID_SELECT command
Examine the message log file for more detailed information.
检查消息日志文件以获取更多详细信息。
-26491 JDBC method (%s) not supported with this server.
A Java UDR invoked a method from the JDBC API that is not supported
by J/Foundation in this version of the server. See the GBase 8s release
notes for more information about JDBC compliance.
Java UDR 在此版本的服务器中调用了 J/Foundation 不支持的 JDBC API 方法。
有关 JDBC 合规性的更多信息，请参阅 GBase 8s 发行说明。
-26500 Query offloading is turned OFF
This query was not accelerated because query offloading is turned off.
To turn on query offloading, use the following statement:
SET ENVIRONMENT use_dwa '1'
此查询未加速，因为关闭了查询卸载。要打开查询卸载，请使用以下语句：
SET ENVIRONMENT use_dwa '1'
-26501 Subquery matching is not supported
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2525 -
This subquery was not accelerated because accelerating a subquery is not
supported yet.
此子查询未加速，因为尚不支持加速子查询。
-26502 Contradictory filters in where clause will not produce any rows
This query was not accelerated because the where clause have contradictory
filters which will result in no rows. Hence there is no need to off-load this
query to accelerator.
此查询未加速，因为 where 子句具有相互矛盾的过滤器，这将导致没有行。因此，
无需将此查询卸载到加速器。
-26503 Statement is not a SELECT or SELECT INTO statement
This statement was not accelerated because it is not a SELECT or
INSERT INTO ... SELECT ... statement.
此语句未加速，因为它不是 SELECT 或 INSERT INTO ... SELECT ...
语句。
-26504 Query containing FOR UPDATE is unsupported for offloading
This query was not accelerated, because it contains a FOR UPDATE clause.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2526 -
此查询未加速，因为它包含 FOR UPDATE 子句。
-26505 Query contains a pseudo table
This query was not accelerated, because it contains a pseudo table.
此查询未加速，因为它包含伪表。
-26506 Query contains a temporary table
This query was not accelerated, because it contains a temporary table.
此查询未加速，因为它包含临时表。
-26507 Query contains a table which is not a real table
This query was not accelerated, because it contains a table which is not a real
table (e.g. view, external table, sequence, synonym).
此查询未加速，因为它包含的表不是真正的表（例如视图、外部表、序列、同义词）。
-26508 Query contains a system catalog table
This query was not accelerated, because it contains a system catalog table.
此查询未加速，因为它包含系统目录表。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2527 -
-26509 Query contains a table in remote database
This query was not accelerated because it contains a table that does not reside
in the database to which the user is connected.
此查询未加速，因为它包含的表不驻留在用户所连接的数据库中。
-26510 Cannot identify fact table
This query was not accelerated because the fact table cannot be identified.
For outer joins, the fact table is the leftmost table in the query.
For inner joins, the fact table is the table containing most rows.
此查询未加速，因为无法识别事实表。
对于外连接，事实表是查询中最左侧的表。
对于内连接，事实表是包含大多数行的表。
-26511 Cannot access the AQT dictionary
This query was not accelerated because an error occurred when trying to access
the AQT dictionary cache.
Note all circumstances and contact GBase Software Support.
此查询未加速，因为尝试访问 AQT 字典缓存时发生错误。请注意所有情况并联系 GBase
软件支持。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2528 -
-26512 No data marts are defined on this database
This query was not accelerated because no data marts are defined on the current
database.
此查询未加速，因为当前数据库上未定义任何数据集市。
-26513 Data mart is virtual but the AVOID_EXECUTE directive is not set
This query was not accelerated because the data mart it matches to is a virtual
data mart. To match against virtual data marts, the AVOID_EXECUTE optimizer
directive or explain setting must be set.
此查询未加速，因为它匹配的数据集市是虚拟数据集市。要与虚拟数据集市匹配，
必须设置 AVOID_EXECUTE 优化器指令或说明设置。
-26514 Query contains more tables than data mart reference definitions
This query was not accelerated because it contains more tables than the number
of references in the data mart definitions. GBase 8s offloads only queries fully
contained in a single data mart.
此查询未加速，因为它包含的表多于数据集市定义中的引用数。
GBase 8s 仅卸载完全包含在单个数据集市中的查询。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2529 -
-26515 Query does not contain a fact table of any data mart
This query was not accelerated because it does not contain a fact table of any
data mart defined on this database.
此查询未加速，因为它不包含此数据库上定义的任何数据集市的事实表。
-26516 Query contains combination of tables not contained in any data mart
This query was not accelerated because it uses a set of tables that is not
contained in any data mart definition. Check the tables and references used in
your data mart definitions.
此查询未加速，因为它使用了一组不包含在任何数据集市定义中的表。
检查数据集市定义中使用的表和引用。
-26520 ON clause contains a non-equality join between columns
This query was not accelerated because it contains an OUTER join with a
non-equality join predicate between two columns. Query acceleration is only
possible on equality join predicates of two columns.
此查询未加速，因为它包含一个 OUTER 连接，两个列之间具有不相等的连接谓词。
查询加速仅适用于两列的等式连接谓词。
-26525 OUTER join with in-join filter (extends NULLs)
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2530 -
The query was not accelerated because it contains an OUTER join with
in-join filter.
The ON clause of an ANSI OUTER join query must not contain other expressions
than equality joins between columns (e.g. non-equality filters or table filter).
The WHERE clause of an GBase 8s OUTER join query must not contain non-equality
filters or table-level filters on subservient tables.
查询未加速，
因为它包含具有 in-join 过滤器的 OUTER 连接。
ANSI
OUTER 连接查询的 ON
子句
不能包含除列之间的等值连接之外的其他表达式
（例如，
非相等过滤器或表过滤器）
。
GBase
8s OUTER
连接查询的 WHERE 子句不得在子服务表上包含不相等的过滤器或表级过滤器。
For example, the following queries cannot be accelerated.
ANSI outer join queries :
例如，以下查询无法加速。
ANSI 外连接查询：
SELECT * FROM f left join d ON (f.col1 = d.col1 AND f.col2 > d.col2)
SELECT * FROM f left join d ON (f.col1 = d.col1 AND f.col2 > 0)
SELECT * FROM f left join d ON (f.col1 = d.col1 AND d.col2 > 0)
GBase 8s outer join queries :
GBase 8s 外连接查询：
SELECT * FROM f outer d WHERE f.col1 = d.col1 AND f.col2 > d.col2
SELECT * FROM f outer d WHERE f.col1 = d.col1 AND d.col2 > 0
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2531 -
-26528 OR clause contains joins between different tables
This query was not accelerated because it contains an OR clause with equality
join predicates that refer to more that two tables.
此查询未加速，因为它包含具有等值连接谓词的 OR 子句，该子句引用多个表。
-26529 OR clause contains joins between different columns
This query was not accelerated because it contains an OR clause with equality
join predicates that refer to more that two columns.
此查询没有加速，因为它包含一个 OR 子句，该子句具有相等的联接谓词，该谓词引
用的列超过两列。
-26530 Query contains a full join
This query was not accelerated because it contains a full OUTER join.
Full OUTER joins are not eligible for query acceleration.
此查询未加速，因为它包含完整的 OUTER 连接。
Full OUTER 连接不符合查询加速的条件。
-26532 ON clause of LEFT OUTER refers to more than two tables
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2532 -
This query was not accelerated because it contains a LEFT OUTER join with an
ON clause that refers to more than two tables.
此查询未加速，因为它包含 LEFT OUTER 连接，其中 ON 子句引用两个以上的表。
-26534 INNER join must be on first level of joins
This query was not accelerated because it contains an INNER join that is not
on the first level of joins. Query acceleration on INNER joins is only possible
if the INNER join in on the first join level.
此查询未加速，因为它包含不在第一级联接的 INNER 连接。仅当 INNER 在第一个连接级
别加入时，
才能在 INNER 连接上进行查询加速。
-26536 INNER join contains a non-equality join between columns
This query was not accelerated because it contains an INNER join with a
non-equality join predicate between two columns. Query acceleration is only
possible on equality join predicates of two columns.
此查询未加速，因为它包含一个 INNER 连接，两个列之间具有不相等的连接谓词。
查询加速仅适用于两列的等式连接谓词。
-26537 INNER join refers to more than two tables
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2533 -
This query was not accelerated because it contains an INNER join with an
ON clause that refers to more than two tables.
此查询未加速，因为它包含带有 ON 子句的 INNER 连接，该子句引用两个以上的表。
-26538 Joins do not form a star or snowflake scheme
This query was not accelerated because it does not join the contained tables
in a star or snowflake scheme. The number of joins must be one less than the
number of tables.
此查询未加速，因为它未加入星形或雪花模式中包含的表。连接数必须比表的数量少一个。
-26540 Table cannot be fact table, it is used by query with different aliases
This query was not accelerated because it contains the fact table more than
once. The fact table is used by the query with different aliases.
此查询未加速，因为它不止一次包含事实表。事实表由具有不同别名的查询使用。
-26543 Query does not contain an equality join from the data mart definition
and none of the columns in the equality join has a unique index
This query was not accelerated because it does not contain an equality join that
is present in the data mart definition, and none of the columns in the equality
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2534 -
join has a unique index. If a reference in the data mart definition is not
reflected by the corresponding equality join predicates in the query, then these
equality join predicates can be omitted from the query only if at least one of
the columns has defined a unique index on it. Otherwise, the accelerator does
not preserve the correct number of rows.
此查询未加速，因为它不包含数据集市定义中存在的等值连接，并且等于连接中的所有列
都没有唯一索引。
如果查询中的相应等值连接谓词没有反映数据集市定义中的引用，则只有在其中至少一个
列已在查询上定
义了唯一索引的情况下，才能从查询中省略这些相等连接谓词。否则，加速器将不保留正
确的行数。
-26544 Query does not contain a table from the data mart definition
and there is no unique index defined on that table
This query was not accelerated because it does not contain a table that is
present in the data mart definition with a reference defined on it, and there
is no unique index defined on that table. If a reference in the data mart
definition contains a table that is not present in the query, this table can be
omitted from the query only if there is a unique index defined on it. Otherwise,
the accelerator does not preserve the correct number of rows.
该查询未加速，因为它不包含数据集市定义中存在的具有定义了引用的表，而且该表上也
没有定义唯一的索引。
如果数据集市定义中的引用包含查询中不存在的表，则只有在该表上定义了唯一索引的情
况下，才能从查询中
省略此表。否则，加速器将不保留正确的行数。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2535 -
-26546 Query contains equality joins that are not present in the data mart
definition
This query was not accelerated because it contains equality joins that are not
defined as references in the data mart definition.
此查询未加速，因为它包含未在数据集市定义中定义为引用的等值连接。
-26547 Query does not contain an equality join from the data mart definition
and none of the columns in the equality join from the data mart
definition have a unique index
This query was not accelerated because it does not contain an equality join that
is present in the data mart definition and none of the columns in the equality
join of the data mart definition have a unique index. If a reference in the data
mart definition is n:m, then this reference needs to be reflected by an equality
join in the query.
此查询未加速，因为它不包含数据集市定义中存在的等值连接，并且数据集市定义的相等
连接中的任何列
都没有唯一索引。 如果数据集市定义中的引用为 n:m，则此引用需要由查询中的等值连接
反映。
-26552 Column is not contained in the data mart definition
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2536 -
This query was not accelerated because it refers to a column that is not
contained in the definition of the data mart.
此查询未加速，因为它引用了未包含在数据集市定义中的列。
-26555 Expression is not supported
This query was not accelerated because it contains an expression that is not
supported by the accelerator.
此查询未加速，因为它包含加速器不支持的表达式。
-26557 Data type is not supported
This query was not probed successfully because it contains a column whose
data type is not supported by the accelerator.
此查询未加速，因为它包含加速器不支持的数据类型列。
-26558 Query contains implicit column
This query was not accelerated or probed successfully because it contains
an implicit column. Tables contain implicit columns if they are created or
altered using the following options:
此查询未成功加速或检测，因为它包含隐式列。如果使用以下选项创建或更改表，
则表包含隐式列：
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2537 -
option | implicit columns
-----------------+--------------------------------------
WITH CRCOLS | cdrserver, cdrtime
WITH REPLCHECK | ifx_replcheck
WITH VERCOLS | ifx_insert_checksum, ifx_row_version
WITH ERKEY | ifx_erkey_1, ifx_erkey_2, ifx_erkey_3
WITH ROWIDS | rowid
-26559 Query does not explicitly contain columns
This query was not probed successfully because it does not explicitly contain
columns. E.g. a query like "select count(*) from t" does not select specific
columns.
未成功探测此查询，因为它未明确包含列。例如。像“select count(*) from t”这样的
查询不会选择特定的列。
-26560 Cannot find synonym for table.
This query was not probed successfully because it contains a table that does
not reside in the current database and no synonym is defined on this table.
此查询未成功探测，因为它包含一个不驻留在当前数据库中的表，并且未在此表上定
义同义词。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2538 -
-26561 Default GBase 8s sqlcode returned for not matched ISAO server sqlcode.
This query returned a error from the accelerator in drda sqlcode and
drda sqlstate form. This error did not match any of the existing IDS sqlcode.
So IDS server gives this default sqlcode error.
此查询从 drda sqlcode 和 drda sqlstate 表单中的加速器返回错误。此错误与任何现有
IDS sqlcode 都不匹配。所以 IDS 服务器给出了这个默认的 sqlcode 错误。
-26563 The query cannot be accelerated because the unary function with expression
is not supported on the accelerator.
The query contains unary function with expressions as argument. If the data types
in the expression are non-numeric types then the accelerator returns error. So
such queries need to be prevented from off-loading to the accelrator.
该查询包含带表达式作为参数的一元函数。如果表达式中的数据类型是非数字类型，则加
速器返回错误。
因此，需要防止此类查询卸载到加速器。
-26564 The Query containing windowed aggregates is unsupported for offloading
This query was not accelerated, because it contains a windowed aggregates.
此查询未加速，因为它包含窗口化聚合。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2539 -
-26565 Row type cannot be used as an OUT/INOUT parameter in a C UDR when the
routine is invoked by another SPL routine.
-26700 User () was not found.
The specified user name is not registered in the database server. This error
occurred when the ALTER, RENAME, or DROP statement was run. Verify the user name
and then rerun the statement. It is also possible that the user was previously
removed or renamed.
未在数据库服务器中注册指定的用户名。
运行 ALTER、
RENAME 或 DROP 语句时发生此错误。
验证用户名，
然后重新运行该语句。用户之前也可能被删除或重命名。
-26701 User () was not created because it already exists.
Verify the user name. If you want to create a user, specify a unique user name
that is not registered in the database server. If you want to change the
properties of a user account, you can use either the DROP USER or RENAME USER
statement and then rerun the CREATE USER statement. You can also use the ALTER
USER statement to change the properties of an existing user.
验证用户名。如果要创建用户，请指定未在数据库服务器中注册的唯一用户名。如果要更
改用户账户的属性，
可以使用 DROP USER 或RENAME USER 语句，然后重新运行 CREATE USER 语句。您还可以
使用 ALTER USER
语句更改现有用户的属性。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2540 -
-26702 User () cannot connect to the database server because the user
account is locked.
To unlock the user account, run the ALTER USER statement with the ACCOUNT UNLOCK
option. Only a database server administrator (DBSA) can manage user accounts.
In a non-root installation, the DBSA is the user who installed the product.
Log in as the user who installed this database server to modify user accounts.
要解锁用户账户，请使用 ACCOUNT UNLOCK 选项运行 ALTER USER 语句。只有数据库服务
器管理员
（DBSA）才能管理用户账户。在非 root 用户安装中，DBSA 是安装产品的用户。以安装此
数据库服务
器的用户身份登录以修改用户账户。
-26703 User
()
is
not
authorized
to
create,
alter,
drop,
or
rename
users.
Only a database server administrator (DBSA) can manage user accounts. In a
non-root installation, the DBSA is the user who installed the product. Log in as
the user who installed this database server to modify user accounts.
只有数据库服务器管理员（DBSA）才能管理用户账户。在非 root 用户安装中，DBSA 是安
装产品的
用户。以安装此数据库服务器的用户身份登录以修改用户账户。
-26704 User name () exceeds the maximum length.
Specify a user name that is not longer than 32 characters.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2541 -
-26705 The password specified for user () is not valid.
Specify a password that contains 6 - 32 characters.
-26706 Cannot add a password to the user (%s) because a password already exists.
Use the MODIFY option instead of the ADD option.
An ALTER USER operation can only add a password for a user if that user does not
have a
password. If you want to change the password, use the MODIFY option in the ALTER
statement.
If you want to drop the password, use the DROP option in the ALTER statement.
ALTER
USER 操作只能为用户添加密码
（如果该用户没有）
。
如果要更改密码，
请使用 ALTER
语句中的 MODIFY 选项。
如果要删除密码，请使用 ALTER 语句中的 DROP 选项。
-26707 User () cannot be created because the user is not mapped to any
properties.
When you create a user for a non-root installation, you must use the PROPERTIES
option with the CREATE USER statement. You can exclude the PROPERTIES option in
the CREATE USER statement if the user has operating-system properties on the
host computer. Also, you can exclude the PROPERTIES option if default properties
exist on the database server.
为非 root 用户安装创建用户时，
必须将 PROPERTIES 选项与 CREATE
USER 语句一起使用。
如果用户在主机上具有操作系统属性，则可以在 CREATE
USER 语句中排除 PROPERTIES 选
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2542 -
项。
此外，如果数据库服务器上存在默认属性，则可以排除 PROPERTIES选项。
-26708 Incorrect old password supplied for user ().
-26709 The new password specified for user (%s) is not valid. Specify a password
that contains 6 - 32 characters.
-26710 PUBLIC is a reserved word. You cannot create, drop, alter, or rename a user
with the name PUBLIC.
-26711 The default user was not found.
The default user is not registered in the database server. This error occurred
when the ALTER, RENAME, or DROP statement was run. Verify the default user is
registered and then rerun the statement. It is also possible that the default
user was previously removed or renamed.
默认用户未在数据库服务器中注册。运行 ALTER、RENAME 或 DROP 语句时发生此错误。
验证默认用户是否已注册，然后重新运行该语句。可能是之前删除或重命名了缺省用户。
-26712 The default user was not created because it already exists.
If you want to change the properties of the default user, you can use the ALTER
DEFAULT USER
statement.
Alternatively,
you
can
run
the
DROP
DEFAULT
USER
statement
and
then
rerun
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2543 -
the
CREATE DEFAULT USER statement with different properties.
如果要更改缺省用户的属性，可以使用 ALTER DEFAULT USER 语句。或者，您可以运行
DROP DEFAULT USER 语句，然后使用不同的属性重新运行 CREATE DEFAULT USER 语句。
-26713 Do not specify a password while creating the default user.
The default user can have properties, but it cannot have a password.
User accounts associated with the default user have the same properties.
缺省用户可以有属性，但不能有密码。与缺省用户关联的用户账户具有相同的属性。
-26714 An internal error occurred while hashing the password.
Record all circumstances prior to the error and contact GBase Software Support.
-26715 Cannot alter the user () because only one USER or UID property
is allowed.
A user must have either one USER property or one UID property. The ALTER operation
failed
because it would not have resulted in one USER or UID property.
用户必须具有一个 USER 属性或一个 UID 属性。 ALTER 操作失败，因为它不会产生一个
USER 或 UID 属性。
-26716 Cannot
alter
the
user
to
add
groups
because
the
number
of
groups
would
exceed
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2544 -
the maximum limit ().
The
total
number
of
groups
after
the
ALTER
USER
operation
cannot
exceed
the
maximum
number
of allowed groups (16).
ALTER USER 操作后的组总数不能超过允许的最大组数（16）。
-26717 An internal error occurred while performing an ALTER operation. Note all
circumstances and contact GBase Software Support.
-26718 Cannot alter the user () to add a home directory because
the
property
value
already
exists.
Use
the
MODIFY
option
instead
of
the
ADD
option.
An ALTER USER operation can only add a home directory if no home directory exists.
If you want to modify the home directory, use the MODIFY option in the ALTER
statement.
如果主目录不存在，ALTER USER 操作只能添加主目录。如果要修改主目录，
请使用 ALTER 语句中的 MODIFY 选项。
-26719 The ALTER statement specified an incorrect authorization value
().
The valid values for the AUTHORIZATION option are "dbsa", "dbsso", "aao", and
"bargroup".
AUTHORIZATION 选项的有效值是“dbsa”、“dbsso”、“aao”和“bargroup”。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2545 -
-26720 Cannot change a property value more than once in the same ALTER statement.
In a single ALTER statement a property can only be changed once.
在单个ALTER语句中，属性只能更改一次。
-26721 Cannot drop the password for the user () because the password
is
specified.
Do
not
include
a
value
for
the
PASSWORD
property
with
the
DROP
option.
When dropping password for the user, the password value cannot be specified.
删除用户的密码时，无法指定密码值。
-26722 The surrogate user name () exceeds the maximum length of 32
characters.
Specify a user name that has 32 characters or fewer.
-26723 The value of the surrogate property HOMEDIR exceeds the maximum length.
Specify a value that is less that 255 bytes.
-26724 Cannot drop the HOMEDIR property for the user () because
a value is specified. Do not include a value for the HOMEDIR property with the
DROP option.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2546 -
In an ALTER USER operation to drop a specified property, a value should be
supplied only when the property is GROUP or AUTHORIZATION. For all other
properties, a property value cannot be specified.
在删除指定属性的 ALTER USER 操作中，仅当属性为 GROUP 或 AUTHORIZATION 时才应提
供值。
对于所有其他属性，不能指定属性值。
-26725 Cannot drop the UID property for the user () because a value
is specified. Do not include a value for the UID property with the DROP option.
In
an
ALTER
USER
operation
to
drop
a
specified
property,
a
value
should
be
supplied
only
when the property is GROUP or AUTHORIZATION. For all other properties, a property
value
cannot be specified.
在删除指定属性的 ALTER USER 操作中，仅当属性为 GROUP 或 AUTHORIZATION 时才应提
供值。
对于所有其他属性，不能指定属性值。
-26726 Cannot drop the USER property for the user () because a value
is specified. Do not include a value for the USER property with the DROP option.
In
an
ALTER
USER
operation
to
drop
a
specified
property,
a
value
should
be
supplied
only
when the property is GROUP or AUTHORIZATION. For all other properties, a property
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2547 -
value
cannot be specified.
在删除指定属性的 ALTER USER 操作中，仅当属性为 GROUP 或 AUTHORIZATION 时才应提
供值。
对于所有其他属性，不能指定属性值。
-26727 The SQL statement cannot assign operating system properties to the user
().
The specified user account is an operating system user account and it is managed
by
the operating system administrator. You can use the CREATE USER and ALTER USER
statements only to grant administrative database server privileges to this user
account. Use the AUTHORIZATION keyword with a valid authorization property: DBSA
(Database Server Administrator), DBSSO (Database System Security Officer),
AAO (Audit Analysis Officer), or BARGROUP (authority to execute ONBar commands).
由操作系统管理员管理。只能使用 CREATE USER 和 ALTER USER语句向此用户账户授予管
理数据库
服务器权限。
使用带有有效授权属性的授权关键字：
DBSA(数据库服务器管理员)、
DBSSO(数
据库系统
安全员)、AAO(审计分析员)或 BARGROUP (执行 ONBar 命令的权限)。
-26728 The uid %s is not in the /etc/gbasedbt/allowed.surrogates file or in the
cache.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2548 -
You must add the uid before it can be a surrogate.
在代理之前必须添加 uid。
-26729 The user %s is not in the /etc/gbasedbt/allowed.surrogates file or in the
cache.
You must add the user before it can be a surrogate.
必须先添加用户才能成为代理。
-26730 The gid %s is not in the /etc/gbasedbt/allowed.surrogates file or in the
cache.
You must add the gid before it can be a surrogate.
您必须添加 gid 才能成为代理程序。
-26731 The group %s is not in the /etc/gbasedbt/allowed.surrogates file or in the
cache.
You must add the group before it can be a surrogate.
必须先添加该组才能成为代理。
-26732 The USERMAPPING feature is disabled. The USERMAPPING configuration
parameter must be set to BASIC or ADMIN.
-26733 A gridtable can only be altered, renamed or dropped
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2549 -
within a grid context.
You must Connect to the appropriate grid prior to issueing the alter or
drop table statement.
在发出 alter 或 drop 表语句之前, 必须连接到相应的网格。
-26734 A database containing gridtables can only be droppen within a grid context
You must Connect to the appropriate grid prior to dropping the database
必须在发出 alter 或 drop table 语句之前连接到相应的网格。
-26735 Invalid parameter for CLUSTER_TXN_SCOPE. The only allowed values are
DEFAULT, SESSION, SERVER, and CLUSTER
-84221 Server name () already exists with a different
definition in the source's SQLHOSTS file.
The server name specified as target for the snapshot copy operation already exists
in the SQLHOST file of the source server and it points to a different TCP/IP port
and/or machine.
指定为快照复制操作的目标的服务器名称已存在于源服务器的 SQLHOST 文件中，
并且它指
向不同的
TCP/IP 端口和/或计算机。
Fix the SQLHOSTS files and retry the operation.
修复 SQLHOST 文件并重试此操作。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2550 -
-84502 XA transactions are not supported on read-only secondary servers
An XA transaction was run on a read-only secondary server.
ACTION
Modify your application to prevent the xa start() function from running on a
read-only
secondary server. Or, make the secondary server updatable using the
UPDATABLE_SECONDARY
configuration parameter.
行动
修改应用程序以防止 xa start() 函数在只读辅助服务器上运行。或者，使用
UPDATABLE_SECONDARY
配置参数使辅助服务器可更新。
-26801 Cannot reference an external database that is not case sensitive.
This statement refers to a database other than the current database.
However, the current database is a case sensitive database, and the
external one is not. This action is not supported, because the databases
that are used in a single distributed transaction either must all be case
sensitive, or else must all be case insensitive.
此语句引用当前数据库以外的数据库。但是，当前数据库是区分大小写的数据库，而外部
数据库不是。
不支持此操作，因为在单个分布式事务中使用的数据库必须都区分大小写，否则必须都不
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2551 -
区分大小写。
-26802 Cannot reference an external database that is case sensitive.
This statement refers to a database other than the current database.
However, the current database is a case insensitive database, and the
external one is not. This action is not supported, because the databases
that are used in a single distributed transaction must all be case
sensitive, or else must all be case insensitive.
此语句引用当前数据库以外的数据库。但是，当前数据库是不区分大小写的数据库，而外
部数据库不是。
不支持此操作，因为在单个分布式事务中使用的数据库必须都区分大小写，否则必须全都
区分大小写。
-33488 The options specified require a C++ compiler, but one could not be
found.
The options passed to the ESQL/C compiler require that the application be linked
with a C++ compiler. Ensure that a C++ compiler is installed on your system and
that the PATH environment variable contains the location of your C++ compiler.
传递给 ESQL/C 编译器的选项要求应用程序与 C++ 编译器链接。
确保在系统上安装了 C++
编译器，
并且 PATH 环境变量包含 C ++ 编译器的位置。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2552 -
-33489 The GL_USEGLU environment variable setting requires a C++ compiler,
but one could not be found.
The
GL_USEGLU
environment
variable
setting
requires
that
the
application
be
linked
with a C++ compiler. Ensure that a C++ compiler is installed on your system and
that the PATH environment variable contains the location of your C++ compiler.
If ICU support is not required by your program, unset the variable.
GL_USEGLU 环境变量设置要求应用程序与 C ++ 编译器链接。确保系统上安装了 C ++ 编
译器，
并且 PATH 环境变量包含 C
++ 编译器的位置如果程序不需要 ICU 支持，
请取消设置变量。
-26901 An alias cannot represent another alias.
The statement failed because the alias definition specified that the alias
represented another alias instead of a real table name.
A table can have multiple aliases, but an alias cannot have an alias.
Rerun the statement with a real table name before the AS keyword in the alias
definition.
该语句失败，因为别名定义指定别名表示另一个别名而不是实际表名。表可以有多个别名，
但别名不能有别名。
在别名定义中的AS关键字之前，使用实际表名重新运行该语句。
-26902 [Internal] Client decimal buffer size mismatch
A client application has sent the incorrect buffer size for a field that has a
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2553 -
decimal
or
numeric
data
type.
This
can
lead
to
a
loss
of
precision
or
the
truncation
of digits of the decimal value.
客户端应用程序为具有十进制或数字数据类型的字段发送了错误的缓冲区大小。
这可能导致精度损失或截断十进制数字的位数。
ACTION
If you are using GBase 8s JDBC driver versions 3.50.JC8, 3.70.JC2, or earlier,
upgrade to the
latest version of the GBase 8s JDBC driver.
行动
如果您使用的是V3.50.JC8,3.70.JC2 或更早版本的 GBase 8s JDBC 驱动程序，
请升级到最新版本的 GBase 8s JDBC 驱动程序。
If you want to ignore this error, set the database server environment variable
IFMX_TEMP_CQ00225490 to 1 and restart the database server.
如果要忽略此错误，
请将数据库服务器环境变量 IFMX_TEMP_CQ00225490 设置为 1 并重新
启动数据库服务器。
-26903 Multiple execution of a CREATE TABLE statement that was prepared once
is not allowed.
A CREATE TABLE statement that was prepared only one time cannot be executed
multiple times.
只能准备一次的 CREATE TABL E语句不能多次执行。
ACTION
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2554 -
Either set the AUTO_REPREPARE configuration parameter to 1 in the onconfig file
or include the FREE statement after the PREPARE CREATE TABLE and EXECUTE
statements.
行动
在 onconfig 文件中将 AUTO_REPREPARE 配置参数设置为 1，或者在 PREPARE CREATE
TABLE
和 EXECUTE 语句之后包含 FREE 语句。
-26904 Attached, non-vanilla or interval fragmented compressed indexes are not
supported.
Compressed indexes must be detached indexes but not interval fragmented or
non-vanilla.
压缩索引必须是分离索引，但不能是间隔分片或非分片。
-26905 The procedure was not created because its definition has more than 341
parameters
The maximum number of parameters in a procedure definition is 341. Reduce the
number of parameters to 341 or fewer and retry the CREATE PROCEDURE statement.
过程定义中的最大参数数为 341。将参数数量减少到 341 或更少，然后重试 CREATE
PROCEDURE 语句。
-26907 Routine creation failed because a collection variable was defined as a
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2555 -
global variable.
A variable that is based on a collection data type cannot be declared as a
global variable.
基于集合数据类型的变量不能声明为全局变量。
-26950 Clustered compressed indexes are not supported.
Compressed indexes must be non-clustered indexes. After you create a
clustered index, you can compress it using an SQL admin API command.
压缩索引必须是非聚簇索引。创建聚簇索引后，可以使用 SQL admin API 命令对其进行压
缩。
-26951 The grid query failed to run. Contact GBase Software Support.
-26952 The statement failed because the grid query contained a server name.
Server names are not valid when a GRID clause is used. Remove any
reference to a specific server from the query and run the statement again.
使用 GRID 子句时，服务器名称无效。从查询中删除对特定服务器的任何引用，然后再次
运行该语句。
-26953 The statement failed because the grid or region does not exist.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2556 -
The specifid grid or region is not defined. Include an existing grid or
region name in the GRID clause and run the statement again.
未定义特定网格或区域。在 GRID 子句中包含现有网格或区域名称，然后再次运行该语句。
-26954 The statement failed because the grid query contained a UNION or UNION ALL
operator.
Statements that include the GRID clause cannot contain the UNION or UNION ALL
operators.
Remove
the
UNION
and
UNION
ALL
operators
from
the
query
and
run
the
statement
again.
包含 GRID 子句的语句不能包含 UNION 或 UNION ALL 运算符。从查询中删除 UNION 和
UNION ALL 运算符，
然后再次运行该语句。
-26955 The statement failed because of an invalid value for the SET ENVIRONMANT
GRID_NODE_SKIP statement
The valid values for the GRID_NODE_SKIP option are DEFALULT, 'on', or 'off'.
Run the statement again with one of the valid values.
GRID_NODE_SKIP 选项的有效值为 DEFALULT、'on' 或 'off'。
使用其中一个有效值再次运行该语句。
-26956 Cannot run the SET ENVIRONMENT SELECT_GRID or SELECT_GRID_ALL statement.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2557 -
There was not enough memory to execute the command.
没有足够的内存来执行命令。
-26957 The statement failed because the grid query cannot connect to a server.
One of the servers in the grid is not currently available. Wait until the
server is available, or run the SET ENVIRONMENT GRID_NODE_SKIP 'on'
statement and then run the statement again.
网格中的一个服务器当前不可用。等到服务器可用，或运行 SET ENVIRONMENT
GRID_NODE_SKIP 'on'
语句，然后再次运行该语句。
-26958 The
statement
failed
because
the
grid
query
contained
one
or
more
subqueries.
Satatements that include the GRID clause cannot contain subqueries.
Remove all subqueries from the query and run the statement again.
包含 GRID 子句的语句不能包含子查询。从查询中删除所有子查询并再次运行该语句。
-26959 The statement failed because the syntax for the grid query is incorrect.
Fix the grid query syntax and run the statement again.
修复网格查询语法并再次运行该语句。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2558 -
-26960 The statement failed because the grid query contained a table that is not
a grid table.
Make the table available for a grid query by running the
cdr change gridtable command or by using OAT. Then run the statement again.
通过运行 cdr change gridtable 命令或使用 OAT 使表可用于网格查询。然后再次运行该
语句。
-26961 The statement failed because a table in the grid query is in the process
of being altered.
A table that is being altered cannot be included in a grid query until
the alter operation has propagated to all nodes in the grid.
在 alter 操作传播到网格中的所有节点之前，不能将正在更改的表包含在网格查询中。
-26962 The statement failed because the grid query contained coorelated joins.
包含 GRID 子句的语句不能包含相关联接。从查询中删除所有相关联接，然后再次运行该
语句。
-26963 The statement failed because the grid or region has no members.
Specify a different grid or region in the GRID clause, or add members to the
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2559 -
grid or region, and then run the statement again.
在 GRID 子句中指定不同的网格或区域，或将成员添加到网格或区域，然后再次运行该语
句。
-26964 Cannot connect to a shard node.
A SELECT statement was made to a sharded table but the server containing
one of the shards is currently unavailable.
对切分表执行了 SELECT 语句，但包含其中一个分片的服务器当前不可用。
-26965 Sharded query failed because it does not contain a sharded table.
The remote query path generated by optimizer must contain sharded table.
Contact GBase Software Support.
优化程序生成的远程查询路径必须包含分片表。联系 GBase 软件支持。
-26966 Sharded query included unsupported extended data types.
The query contains one or more SQL data types that are not supported in
sharded queries.
该查询包含分片查询不支持的一种或多种 SQL 数据类型。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2560 -
-26967 A connection to a shard node could not be established
Examine which node was not available and then retry the query.
Verify the SHARD_ID and node names are all unique.
检查哪个节点不可用，然后重试查询。验证 SHARD_ID，节点名称都是唯一的。
-26968 A connection to a shard node was lost
Correct the reason for the lost of the network connection and then
retry the query. Verify that all the shard nodes are online.
更正丢失网络连接的原因，然后重试查询。验证所有分片节点是否在线。
-26969 Parallel Sharded Queries Not active
Parallel Sharded Queries is not active on the local server.
本地服务器上的并行共享查询不处于活动状态。
-26970 Parallel Sharded Queries not available on shard node
Parallel Sharded Queries does not exist on a shard node.
Verify the SHARD_ID is valid and unique.
分片节点上不存在并行分片查询。验证 SHARD_ID 是否有效且唯一。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2561 -
-26971 Sharding connection Connect Error.
The shard cluster could not connect to one of the remote shard servers.
分片群集无法连接到其中一个远程分片服务器。
-26972 Sharding Internal Error.
Parallel Sharded Queries encountered an internal error. Contact GBase Software
Support.
并行共享查询遇到内部错误。联系 GBase 软件支持。
-26973 Triggers are not supported in sharded queries.
The query includes triggers or trigger body statements that are not supported
in sharded queries.
查询包括分片查询中不支持的触发器或触发器主体语句。
-26974 Sharded tables are not supported inside procedure or function.
You cannot include a sharded table in a procedure or function.
不能在过程或函数中包含分片表。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2562 -
-26975 Cannot
include
a
FOR
UPDATE
clause
in
a
SELECT
statement
on
a
sharded
table.
A SELECT statement that operates on a sharded table cannot contain a FOR UPDATE
clause.
在分片表上运行的 SELECT 语句不能包 含FOR UPDATE 子句。
Edit the SELECT statement or the cursor declared and remove this clause.
编辑 SELECT 语句或声明的游标并删除此子句。
-26976 The
statement
failed
because
it
attempted
to
move
rows
between
shard
servers.
The statement contains an update to a shard key that requires the row to move
to another shard server. This type of update is not allowed.
该语句包含对分片键的更新，该分片键需要将行移动到另一个分片服务器。不允许此类更
新。
To update the shard key of a row, delete the row and then insert it with the
new values.
若要更新行的分片键，请删除该行，然后使用新值插入该行。
-26977 Sharded queries are not supported within an XA environment.
Sharded queries are not supported within an XA environment.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2563 -
XA 环境中不支持共享查询。
-26991 The query failed because the FROM clause includes more than one sharded
table.
A SELECT statement cannot include more than one sharded table in the FROM clause.
SELECT 语句不能在FROM子句中包含多个分片表。
-26992 The sharded query failed because of an internal error.
The query on a sharded table encountered an internal error. If this error
recurs, note all circumstances and contact GBase Software Support.
分片表上的查询遇到内部错误。如果再次出现此错误，请记录所有情况并联系 GBase 软件
支持。
-26993 Cannot alter the table to shard collection table.
Collection table can only be altered to shard collection table.
集合表只能更改为分片集合表。
-32519 Passwords are only allowed in SET SESSION AUTHORIZATION statements
for a trusted connection using a trusted context.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2564 -
A SET SESSION AUTHORIZATION statement with a password, was executed outside
of a trusted connection.
在可信连接的中间执行带有密码的 SET SESSION AUTHORIZATION 语句、
-88001 C-ISAM function returned error .
The C-ISAM processor returned an error.
C-ISAM 处理器返回错误。
Check the C-ISAM error code and correct the situation.
检查 C-ISAM 错误代码并更正情况。
-88002 Memory allocation error.
An attempt to allocate memory from the system failed.
尝试从系统分配内存失败。
Release some memory and retry the operation.
释放一些内存并重试该操作。
-88003 Cannot create a file or directory at .
GBase 8s PSM attempted to create a file or directory but the attempt failed.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2565 -
GBase 8s PSM 尝试重命名文件或目录，但尝试失败。
Check the associated operating system error and correct the situation.
检查相关的操作系统错误并更正情况。
-88004 Cannot rename a file or directory to .
GBase 8s PSM attempted to rename a file or directory but the attempt failed.
GBase 8s 尝试重命名文件或目录，但尝试失败。
Check the associated operating system error and correct the situation.
检查相关的操作系统错误并更正情况。
-88006 An unspecified error occurred,
A generic, unexpected error happened.
发生了一般性的意外错误。
Check additional errors and the configuration and contact GBase Support if the
problem persist.
检查其他错误和配置，如果问题仍然存在，请类型 GBase 支持。
-88008 The specified path is not a directory or does not exists.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2566 -
GBase 8s PSM Attempted to open a directory that does not exist.
GBase 8s PSM 尝试打开不存在的目录。
Correct the situation and attempt to run the command again.
纠正这种情况并尝试再次运行该命令。
-88014 When creating a new device, a device type is needed.
When creating a new device, a device type is needed.
创建新设备时，需要设备类型.
Provide a device type (either FILE or TAPE) and retry the operation.
提供设备类型（FILE 或 TAPE）并重试该操作。
-88015 A block size must be specified for device type %s.
The specified device type requires a block size.
指定的设备类型需要 block 大小。
Provide a block size and retry the operation.
提供 blcok 大小并重试该操作。
-88016 An empty pool was provided.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2567 -
A valid pool name is needed for the operation.
操作需要有效的池名称。
Provide a valid pool name and retry the operation.
提供有效的池名称并重试该操作。
-88017 Invalid pool specified
The specified pool is not known.
不知道指定的池。
Provide a valid value for the pool.
请为该池提供一个有效值。
-88018 Invalid device type specified.
The specified type of device is not known.
指定的设备类型未知。
Provide a valid value for the device type.
请为该设备类型提供一个有效值。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2568 -
-88019 Invalid block size for device .
The block size specified for the device is not correct.
为设备指定的 block 大小不正确。
Fix the block size and retry the operation.
修复 block 大小并重试该操作。
-88020 nvalid media size for device .
The media size specified for the device is not correct.
为设备指定的介质尺寸不正确。
Fix the media size and retry the operation.
修复介质尺寸并重试操作。
-88021 Cannot update the device because it is in use.
NONE
无
NONE
无
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2569 -
-88022 Error -88022: Cannot delete the device because it is in use.
GBase 8s PSM Failed to delete the named device because it is in use.
GBase 8s PSM 无法删除指定的设备，因为它正在使用中。
Wait until the device is idle and retry the operation.
等到设备空闲并重试操作。
-88023 Error -88023: Cannot open the device definition file .
Attempt to open a GBase 8s PSM device definition file failed.
尝试打开 GBase 8s PSM 设备定义文件失败。
Check the associated operating system error code.
检查关联的操作系统错误代码。
-88035 No Device is available to mount in pool .
The storage manager was asked to mount a volume for a specified
pool, but no device was found.
要求存储管理器为指定的池装入卷，但未找到任何设备。
Be sure that a device has been created for the specified pool.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2570 -
Also be sure that the devices for the given pool are available.
确保已为指定的池创建了设备。还要确保给定池的设备可用。
-88056 The device requested in the operation () does not exist.
You tried to perform an operation on a device that does not exist.
For example you tried to delete a device that does not exist.
您试图在不存在的设备上执行操作。例如，尝试删除不存在的设备。
Resubmit the command with the correct device or pool.
使用正确的设备或池重新提交命令。
-88057 The specified device does not belong to the specified pool.
Either the device or the pool is incorrect
设备或池不正确
Correct the device or pool provided.
更正提供的设备或池。
-88058 The specified device cannot be deleted.
An error prevented the storage manager from deleting the specified device.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2571 -
错误导致存储管理器无法删除指定的设备。
Check the accompanying error and fix the situation.
检查随附的错误并修复情况。
-88101 Cannot create catalog tables
Check the GBase 8s PSM catalog directory pointed by the GBase 8s PSM_CATALOG
configuration
parameter ($GBS_HOME/etc/psm by default) for access permissions.
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查 GBase 8s PSM_CATALOG 配置参数（缺省情况下为 $GBS_HOME/etc/psm）指向的
GBase 8s PSM 目录以获取访问权限。检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88102 GBase 8s PSM catalog creation failed at .
GBase 8s PSM attempted to create the GBase 8s PSM catalog tables in the specified
directory, but
failed.
GBase 8s PSM 尝试在指定目录中创建 GBase 8s PSM 目录表，但失败了。
Check associated error messages and resolve the issues.
Check
the
value
of
the
GBase
8s
PSM_CATALOG
configuration
parameter
or
environment
variable for the catalog location.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2572 -
检查相关的错误消息并解决问题。检查 GBase 8s PSM_CATALOG 配置参数或目录位置的环
境变量的值。
-88103 Error -88103: Cannot open catalog table .
An attempt to open a catalog table failed with either an C-ISAM error
number or an operating system error number.
尝试打开目录表失败，出现 C-ISAM 错误号或操作系统错误号。
Check the accompanying error numbers and correct the situation
before trying the command again.
在再次尝试命令之前，请检查随附的错误编号并更正情况。
-88104 Error -88104: Cannot close catalog table descriptor for
table .
An attempt to close a catalog table failed with either an C-ISAM error
number or an operating system error number.
尝试关闭目录表失败，出现 C-ISAM 错误号或操作系统错误号。
Check the accompanying error numbers and correct the situation
before trying the command again.
在再次尝试命令之前，请检查随附的错误编号并更正情况。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2573 -
-88105 Error -88105: Cannot lock catalog table .
An attempt to lock a catalog table failed with either an C-ISAM error
number or an operating system error number.
One reason for this error is that the lock timeout set for GBase 8s PSM
is either too short or not long enough.
尝试锁定目录表失败，出现 C-ISAM 错误号或操作系统错误号。此错误的一个原因是
GBase 8s PSM 的锁定超时设置太短或不够长。
Check the accompanying error numbers and correct the situation
before trying the command again.
Try to make the configuration parameter GBase 8s PSM_TIMEOUT longer if the
associated C-ISAM error is ELOCKED or EFLOCKED.
在再次尝试命令之前，请检查随附的错误编号并更正情况。如果关联的 C-ISAM 错误是
ELOCKED
或 EFLOCKED，请尝试使配置参数 GBase 8s PSM_TIMEOUT 更长。
-88106 Error -88106: Cannot build a new index for catalog table .
The storage manager attempted to build an index for the specified catalog table,
but
encountered an error.
存储管理器尝试为指定的目录表构建索引，但遇到错误。
Check the associated operating system and or C-ISAM errors and correct the
situation.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2574 -
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88107 Error -88107: Cannot insert record into catalog table .
The
storage
manager
attempted
to
insert
one
or
more
records
to
the
specified
catalog
table, but
encountered an error.
存储管理器尝试为指定的目录表构建索引，但遇到错误。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88108 Error -88108: Cannot delete records from catalog table .
The storage manager attempted to delete one or more records from the specified
catalog table, but
encountered an error.
存储管理器尝试将一个或多个记录插入指定的目录表，但遇到错误。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2575 -
-88109 Cannot update to catalog table .
The
storage
manager
attempted
to
update
one
or
more
records
in
the
specified
catalog
table, but
encountered an error.
存储管理器尝试更新指定目录表中的一个或多个记录，但遇到错误。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88110 Cannot read from catalog table .
The storage manager attempted to read one or more records in the specified catalog
table but
encountered an error.
存储管理器尝试从指定的目录表中读取一个或多个记录，但遇到错误。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88111 Cannot get index information for catalog table .
GBase 8s PSM attempted to obtain index information for a table, but failed.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2576 -
GBase 8s PSM 尝试获取表的索引信息，但失败了。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查
相关的操作系统和/或 C-ISAM 错误并更正情况。
-88112 Cannot demote the 'HIGHEST' priority device in the pool .
GBase
8s
PSM
attempted
to
demote
the
device
identified
as
having
the
HIGHEST
priority
in the pool to priority 'HIGH', but an error was returned.
GBase 8s PSM 尝试将标识为池中具有最高优先级(HIGHEST)的设备降级为优先级“HIGH”，
但返回了错误。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88113 Catalog table is not present.
An attempt to open a catalog table failed because the table is missing.
尝试打开目录表失败，因为缺少表。
Check the accompanying error numbers and correct the situation
before trying the command again.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2577 -
在再次尝试命令之前，请检查随附的错误编号并更正情况。
-88114 The GBase 8s PSM catalog is missing
The GBase 8s PSM catalog is not present in the specified directory
指定的目录中不存在 GBase 8s PSM。
GBase 8s PSM will try to create the catalog.
GBase 8s PSM 会尝试创建目录。
-88115 The GBase 8s PSM catalog is corrupted.
The GBase 8s PSM catalog is corupted. Either there are missing tables, or the
existing tables are damaged.
GBase 8s PSM 目录已被破坏。缺少表，或现有表已损坏。
Manaully inspect that there are no missing tables in the GBase 8s PSM_CATALOG_PATH
directory.Run 'onGbasedbt PSM -C check' command. If this does not solve the issue,
import the catalog back.
手动检查 GBase
8s
PSM_CATALOG_PATH 目录中是否有丢失的表。运行 'onGbasedbt
PSM
-C
check' 命令。
如果这不能解决问题，请重新导入目录。
-88116 The Catalog import operation was aborted.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2578 -
Multiple problems can cause this problem including an already existing catalog.
多个问题可能导致此问题，包括一个已经存在的目录。
Check Associated errors, correct the sittuation and re-run the operation.
请检查关联错误，更正情况并重新运行此操作。
-88117 Attempt to load table failed.
GBase 8s PSM attempted to load a catalog table but encontered an error.
GBase 8s PSM 尝试加载目录表但是输入了错误。
Check associatted errors.
检查相关的错误。
-88118 Attempt to erase table failed.
GBase 8s PSM attempted to erase a catalog table but encontered an error.
GBase 8s PSM 试图擦除目录表但是出现了错误。
Check associatted errors.
检查相关的错误。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2579 -
-88119 The import file has incorrect number of columns in line .
The
unload
file
being
used
to
load
a
catalog
table
has
an
incorrect
number
of
columns.
用于加载目录表的卸载文件的列数不正确。
Check the file for corruption and fix it or use another load file.
检查文件是否损坏并修复它或使用其他加载文件。
-88130 Error -88130: GBase 8s PSM initialization failed.
The storage manager attempted to obtain index information for a table, but failed.
存储管理器尝试获取表的索引信息，但失败了。
Check the associated operating system and or C-ISAM errors and correct the
situation.
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88131 Error -88131: The environment variable 'GBS_HOME' is not set.
The storage manager attempted to obtain index information for a table, but failed.
存储管理器尝试获取表的索引信息，但失败了。
Check the associated operating system and or C-ISAM errors and correct the
situation.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2580 -
检查相关的操作系统和/或 C-ISAM 错误并更正情况。
-88132 Error -88132: An attempt to allocate memory to store the value of the
'GBS_HOME'
environment variable failed.
The value of the environment variable might be invalid or corrupted.
Your system might be extremely low in memory.
环境变量的值可能无效或已损坏。您的系统内存可能非常低。
Check the value of the 'GBS_HOME' environment variable.
Check that your system is not low in memory.
检查'GBS_HOME'环境变量的值。检查您的系统内存是否不足。
-88133 Error -88133: An attempt to allocate memory to store the value of the
'ONCONFIG'
environment variable failed.
The value of the environment variable might be invalid or corrupted.
Your system might be extremely low in memory.
环境变量的值可能无效或已损坏。您的系统内存可能非常低。
Check the value of the 'ONCONFIG' environment variable.
Check that your system is not low in memory.
检查'ONCONFIG'环境变量的值。检查您的系统内存是否不足。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2581 -
-88134 Error -88134: An attempt to allocate memory to store the value of the
'PSMCONFIG'
environment variable failed.
The value of the environment variable might be invalid or corrupted.
Your system might be extremely low in memory.
环境变量的值可能无效或已损坏。您的系统内存可能非常低。
Check the value of the 'PSMCONFIG' environment variable.
Check that your system is not low in memory.
检查'PSMCONFIG'环境变量的值。检查您的系统内存是否不足。
-88150 Warning -88150: The BAR_BSALIB_PATH configuration parameter is not set.
The BAR_BSALIB_PATH parameter is not set in the onconfig file. Therefore ON-Bar
and allutilities related to it are using the default path that changes from system
to
system.This
can
lead
to
problems
identifying
the
location
of
the
library
to
use.
未在 onconfig 文件中设置 BAR_BSALIB_PATH 参数。因此，ON-Bar 和与其相关的所有实
用程序都使用从
系统更改为系统的默认路径。这可能导致识别要使用的库的位置时出现问题。
You
must
set
the
BAR_BSALIB_PATH
configuration
parameter
to
specify
the
XBSA
library
to
be
used
by
ON-Bar
and
related
utilities.
You
must
set
this
explicitly
in
the
onconfig
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2582 -
file.
必须设置 BAR_BSALIB_PATH 配置参数以指定 ON-Bar 和相关实用程序要使用的 XBSA 库。
您必须在 onconfig 文件中明确设置它。
-88151 Warning
-88151:
The
XBSA
shared
library
at
cannot
be
loaded.
The XBSA library at the specified location cannot be loaded.
无法加载指定位置的 XBSA 库。
Check the accompanying system error and correct the situation.
检查随附的系统错误并更正情况。
-88152 Error -88152: The XBSA shared library at does not seem to
be for the
GBase 8s Primary Storage Manager.
The XBSA library at the specified location is not the for the Primary Storage
Manager.
指定位置的 XBSA 库不是主存储管理器。
Check the BAR_BSALIB_PATH configuration parameter and the default location of the
ON-Bar shared library in your system.
检查 BAR_BSALIB_PATH 配置参数以及系统中 ON-Bar 共享库的默认位置。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2583 -
-88160 The converted string cannot be for in an INT4 integer.
We are trying to convert a string to INT4 but the value is too big.
我们正在尝试将字符串转换为 INT4，但值太大。
Correct the values and retry the operation.
请更正值并重试操作。
-88161 The length for the string is too big to fit in bytes.
The
value
that
we
want
to
assign
to
a
string
exceeds
the
size
of
the
string
variable.
要分配给字符串的值超过字符串变量的大小。
Correct the values and retry the operation in the correct format.
请更正值并以正确的格式重试操作。
-88162 The system cannot insert the specified device in the GBase
8s PSM catalog.
The device specified in the operation or command could not be inserted into the
GBase 8s PSM catalog.
无法将操作或命令中指定的设备插入 GBase 8s PSM 目录中。
Check the associated errors for more information related to this problem.
检查相关错误以获取与此问题相关的更多信息。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2584 -
-88163 The pool specified is invalid.
The pool specified is not valid.
指定的池无效。
Recheck the information that you need and then specify valid values for pools.
重新检查所需的信息，然后为池指定有效值。
-88164 The device type specified is invalid.
The device type specified is not valid.
指定的设备类型无效。
Review device-type information and specify a valid value for the device type.
查看设备类型信息并指定设备类型的有效值。
-88165 The device path is longer than bytes.
The device path specified is too long.
指定的设备路径太长。
Specify a valid value for the full path of the device.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2585 -
为设备的完整路径指定有效值。
-88166 The priority specified for the device is invalid.
The priority specified for the device is invalid.
为设备指定的优先级无效。
Specify a valid value for the priority of the device.
指定设备优先级的有效值。
-88167 The device specification file has a syntax error at line .
Incorrect syntax in the device specification file.
设备规范文件中的语法不正确。
The offending part of the syntax has been ignored.
Correct the syntax and run the command again.
语法的违规部分已被忽略。更正语法并再次运行该命令。
-88168 Loading devices from the device specification file failed.
The
operator
attempted
to
create
a
set
of
devices
from
a
device
specification
file,
but
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2586 -
the operation failed.
操作员尝试从设备规范文件创建一组设备，但操作失败。
Check the accompanying messages and correct the situation.
检查随附的消息并更正情况。
-88180 Existing in the catalog is different from
.
The GBase 8s PSM catalog was created with a different version of the Primary
Storage Manager, so processing cannot continue.
GBase 8s PSM 目录是使用不同版本的主存储管理器创建的，因此无法继续处理。
Recreate the catalog with the current GBase 8s PSM release.
使用当前版本的 GBase 8s PSM 重新创建目录。
-88181 Devices of type are not supported in this platform.
Some device types are not supported in all platforms. For example, in the Windows
operating system, tape devices are not supported.
并非所有平台都支持某些设备类型。例如，在 Windows 操作系统中，不支持磁带设备。
Refer to the product documentation and use a supported type of device.
请参阅产品文档并使用支持的设备类型。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2587 -
-88182 The XBSA Resource Type is unknown.
The XBSA Resource Type that was specified is unknown to the system.
指定的 XBSA 资源类型对系统是未知的。
Refer to the product documentation and use a supported XBSA Resource Type.
请参阅产品文档并使用受支持的 XBSA 资源类型。
-88183 Cannot Acquire a next sequential ID for the object.
GBase 8s PSM tried to generate a serial number to insert a new record in a table
but an error happened
GBase 8s PSM 尝试生成序列号以在表中插入新记录但发生错误
Retry the action and contact GBase Support if the problem persist.
如果问题仍然存在，请重试该操作并联系 GBase 技术支持。
-88184 The pool name already exist in the system.
An attempt was made to create a pool that already exist in the system.
尝试创建系统中已存在的池。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2588 -
Delete the existing pool or try the action again or change the name of the pool
that you wnat to create.
删除现有池或再次尝试操作或更改要创建的池的名称。
-88185 An error happened attempting to create a new pool.
The creation of the pool failed.
创建池失败。
See the associated errors and correct the situation.
查看相关错误并更正。
-88186 A defect in the program was found. Contact GBase Support.
A programming error was found in the program. This error should never happen.
在程序中发现了编程错误。永远不会发生此错误。
Take note of all circumstances of the error and contact GBase Support immediately.
记下错误的所有情况，并立即联系 GBase 支持。
-88187 The pool that you attempted to delete does no exist.
The pool that you are trying to delete from the system does not exist.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2589 -
尝试从系统中删除的池不存在。
Check the list of existing pools, verify the spelling and syntax and retry the
operation.
检查现有池列表，验证拼写和语法并重试该操作。
-88188 The specified pool type is invalid.
An incorrect pool type was provided for the requested operation.
为请求的操作提供了错误的池类型。
Check the manual for a list of valid pool types.
查看手册以获取有效池类型的列表。
-88189 Close the GBase 8s PSM session failed.
An error happened while trying to close a GBase 8s PSM session.
尝试关闭 GBase 8s PSM 会话时发生错误。
Check the errors and contact GBase Support.
检查错误并联系 GBase 支持。
-88190 Failed to open a GBase 8s PSM session.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2590 -
An error happened while trying to open a GBase 8s PSM session.
尝试关闭 GBase 8s PSM 会话时发生错误。
Check the errors and contact GBase Support.
检查错误并联系 GBase 支持。
-88191 Failed to generate the list of pools in the system
An error happened while trying to create a list of pools in the system
尝试在系统中创建池列表时发生错误。
Check the errors and contact GBase Support.
检查错误并联系 GBase 支持。
-88192 Failed to add a pool to the system
An error happened while trying to add a pool to the system
尝试将池添加到系统时发生错误。
Check the errors and contact GBase Support.
检查错误并联系 GBase 支持。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2591 -
-88193 Failed to delete a pool from the system
An error happened while trying to delete a pool from the system
尝试从系统中删除池时发生错误。
Check the errors and contact GBase Support.
检查错误并联系 GBase 支持。
-88194 System Pools cannot be deleted.
An attempt was made to delete a system pool.
尝试删除系统池。
Check the list of system pools in the manual, they cannot be deleted or modified.
检查手册中的系统池列表，不能删除或修改它们。
-88195 Pools with devices cannot de deleted.
An attempt was made to delete a pool that has devices on it.
试图删除其上有设备的池。
Delete the devices that are under the pool and retry the operation.
删除池下的设备并重试该操作。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2592 -
-88196 The device cannot be modified.
An attempt was made to modify a device, but the operation returned an error.
尝试修改设备，但操作返回错误。
Check that the combination of device path and pool exist in the system,
orrect any errors, and resubmit the command; or check the additional errors.
检查系统中是否存在设备路径和池的组合，
更正错误，
然后重新提交命令;或检查其他错误。
-88250 The function received an invalid handle
This is an internal error, a function received an invalid handler and we
cannot continue. This error should not happen.
这是一个内部错误，一个函数收到了一个无效的处理程序，不能继续。不应发生此错误。
Contact GBase Support.
联系 GBase 支持。
-88300 The current user does not have authorization to run this utility.
The current user is not authorized to perform the current action.
当前用户无权执行当前操作。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2593 -
The action must be performed by an authorized user.
该操作必须由授权用户执行。
-88301 The requested action is not valid for the current menu or is an
incorrect action.
You tried to perform an invalid action for the current menu (such as "add" while
using the catalog menu),
or the attempted action requested is not valid.
您尝试对当前菜单执行无效操作(例如，在使用目录菜单时执行“add”)，或者请求的尝试
操作无效。
Check information on command line options and specify the correct information.
检查命令行选项的信息并指定正确的信息。
-88302 Duplicated instances of option are not allowed.
An attempt to have multiple instances of the same option was made,
for example, to specify multiple pools for a single device.
例如，尝试具有相同选项的多个实例，以便为单个设备指定多个池。
Correct the command line information and retry the operation.
更正命令行信息并重试该操作。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2594 -
-88303 Not enough arguments for option .
The selected option requires more arguments than those that were provided.
所选选项需要的参数多于提供的参数。
Check command line information and fix the command line.
检查命令行信息并修复命令行。
-88304 No more arguments were expected for the action .
You provided more arguments that were expected.
您提供了更多预期的参数。
Check command line information and fix the command line.
请检查命令行信息并修复命令行。
-88305 The flag is not valid in the current context.
The specified flag is not valid for the current action.
指定的标志对当前操作无效。
Check command line information and fix the command line.
请检查命令行信息并修复命令行。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2595 -
-88306 Cannot mix the following flags :
An attempt was made to specify mutually exclusive flags.
尝试指定互斥标志。
Check command line information and fix the command line.
检查命令行信息并修复命令行。
-88307 The provided string for the argument is longer than
bytes.
An
attempt
was
made
to
provide
a
string
that
is
longer
than
what
the
program
supports.
试图提供一个比程序支持的字符串更长的字符串。
Use a string of the correct size.
使用正确大小的字符串。
-38602 Server failed to start in recovery mode within an expected time duration.
The server instance started, but did not move into recovery mode in the
allowable time.
服务器实例已启动，但未在允许的时间内进入恢复模式。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2596 -
ACTION
行动
Check the GBase 8s online log for messages about problems that occurred. Take
the necessary steps to fix those problems, and then rerun the restore utility.
If the problem persists, or no other problems are reported in the online log,
the server might need more time to move into recovery mode.
检查 GBase 8s 联机日志，查看有关发生的问题的消息。采取必要步骤修复这些问题，然
后重新运行
还原实用程序。如果问题仍然存在，或者联机日志中没有报告其他问题，服务器可能需要
更多时间进入
恢复模式。
The restore utility waits 5 minutes, which is 5 times the default value of the
MAX_CONNECT_TRY_RESTORE environment variable. Set the environment variable to
a value greater than 60 seconds, and run the restore utility.
还原实用程序等待 5 分钟，这是 MAX_CONNECT_TRY_RESTORE 环境变量缺省值的 5 倍。
将环境变量设置为大于 60 秒的值，并运行 RESTORE 实用程序。
-9659 The
server
does
not
support
the
specified
UPDATE
operation
on
JSON
documents
Use successive SELECT, DELETE and INSERT operations to update JSON documents
使用连续的 SELECT、DELETE 和 INSERT 操作来更新 JSON 文档。
-9660 The database server operation failed due to an invalid JSON document.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2597 -
Replace the invalid JSON document with a valid JSON document. To prevent the
problem from occurring in the future, ensure that the client inserts valid and
uncorrupted JSON documents into the database.
用有效的 JSON 文档替换无效的 JSON 文档。为防止将来出现此问题，请确保客户端将有
效且未损坏的
JSON 文档插入数据库。
-9661 The statement failed because constraint (%s) cannot be enabled with
NOVALIDATE option.
Only foreign key constraints are allowed to be enabled with NOVALIDATE option.
Examine the sysconstraints.constrtype entry for this constraint in the system
catalog. Unless the value for this constraint is R, it is not a referential
constraint. Remove the NOVALIDATE keyword from the statement.
只允许使用 NOVALIDATE 选项启用外键约束。检查系统目录中此约束的
sysconstraints.constrtype
条目。除非此约束的值为 R，否则它不是参照约束。从语句中删除 NOVALIDATE 关键字。
-9662 No user permission for %s
The user/tenant in multitenancy mode is restricted to use only the
resources provided by the application provider. These resources can
be dbspaces, blobspaces, sbspaces, temp dbspaces, temp sbspaces etc..
In this case, the user/tenant is not permitted to use the resource.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2598 -
多租户模式下的用户/租户仅限于使用应用程序提供商提供的资源。这些资源可以是
dbspace、blobspace、sbspace、temp dbspace、temp sbspace 等。在这种情况下，
不允许用户/租户使用该资源。
-9663 Cannot %s tenant database.
A tenant database can only be dropped using the Admin API task('tenant
drop',..) statement. A tenant database may not be renamed.
只能使用 Admin API 任务（'tenant drop'，..）语句删除租户数据库。
租户数据库可能无法重命名。
-9664 Session limit exceeded; transaction aborted or session aborted.
A session limit has been exceeded. The current transaction has been
aborted. The current session may also be terminated depending on the
limit exceeded.
已超出会话限制。当前事务已中止。根据超出的限制，也可以终止当前会话。
-9665 Cannot
create
attached
indexes
on
boolean,
lvarchar,
user
defined
data
types
and fragmented tables.
Specifying IN TABLE as the storage option for create index statement,
creates a legacy attached index.
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2599 -
将 IN TABLE 指定为 create index 语句的存储选项，将创建旧的附加索引。
-9666 No connections are allowed while a tenant restore is in progress.
You cannot access the database that this statement requests because a tenant
restore is still in progress for this database spaces.
无法访问此语句请求的数据库，因为对于此数据库空间，tenant 还原仍在进行中。
-------
---------
# GBase 版权所有 2004-2018，保留所有权利。
GBase 8s 错误消息
南大通用数据技术股份有限公司 - 2600 -