This topic describes the error messages for Oracle tenants in OceanBase Database.
Applicability
This topic applies only to OceanBase Database Enterprise Edition. OceanBase Database Community Edition provides only the MySQL mode.
Value ranges of error codes in OceanBase Database:
Error messages indicated by the preceding error codes are compatible with those in Oracle databases. For more information about error messages in Oracle databases, see Database Error Messages.
Format of error messages
For Oracle tenants in OceanBase Database, error messages are returned in the format of prefix+numeric code.
Like in an Oracle database, for an error that originates from the database, an error message prefixed with ORA is returned. For an error that originates from a stored procedure, an error message prefixed with PLS is returned.
The format of error messages is as follows:
ORA-<err_num>: <err_msg>
PLS-<err_num>: <err_msg>
The parameters are described as follows:
err_num: the error code that is compatible with Oracle databases.err_msg: the error message.
Variables in error messages
OceanBase Database integrates parameters into error messages to help you locate and fix errors. These parameters are displayed as percent signs (%).
Here is an example:
ORA-00910: specified length too long for column '%s' (max = %d byte)
The preceding error message may appear as the following message:
ORA-00910: specified length too long for column 'fruit' (max = 32767 byte)
About ORA-00600
In Oracle databases, ORA-00600 indicates an internal error, which is a Catchall internal error message for Oracle program exceptions. It indicates that the process encounters a low-level or unexpected error.
In Oracle tenants of OceanBase Database, for errors that are incompatible with Oracle databases, this error code is returned in the following format:
ORA-00600: internal error code, arguments: %d, %s
Here, %d indicates an error code in OceanBase Database, and %s indicates the error message in OceanBase Database.