idError » ORADB-O2U

O2U-00200 Internal error in OTT facility O2U

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00200 Internal error in OTT facility O2U

Cause:
An internal OTT error occurred in the O2U facility of OTT.

O2U-00201 Illegal arguments to function o2upt()

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00201 Illegal arguments to function o2upt()

Cause:
Illegal arguments were passed to the function O2UPT(). This is an internal error that should not be encountered by an end user.

O2U-00202 Invalid data passed to function

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00202 Invalid data passed to function

Cause:
Arguments with incorrect values were passed to the function O2UPT(). This is an internal error that should not be encountered by an end user.

O2U-00203 Type to be declared must be an object type or a named collection type

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00203 Type to be declared must be an object type or a named collection type

Cause:
OTT was asked to generate code for a type it does not support. When generating Java code, OTT will only generate code for object types. When generating C declarations, OTT will only generate declarations for object types and named collection types.

O2U-00204 Unable to convert from the database character set to the compiler character set

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00204 Unable to convert from the database character set to the compiler character set

Cause:
The name of a type, attribute, or method cannot be converted from the client character set in effect when OTT was invoked to the compiler character set (typically ASCII or EBCDIC).

O2U-00205 None of the characters in a type name were legal identifier characters

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00205 None of the characters in a type name were legal identifier characters

Cause:
None of the characters in the name of a user-defined type could be translated to a character that can begin a C or C++ identifier, such as a letter or an underscore.

O2U-00206 Some characters in a type name were not legal identifier characters

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00206 Some characters in a type name were not legal identifier characters

Cause:
One or more characters in the name of a user-define type could not be translated to a character that can appear in a C or C++ identifier, such as a letter, an underscore, or a digit. The characters that could not be translated were replaced with underscores.

O2U-00207 None of the characters in an attribute name were legal identifier characters

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00207 None of the characters in an attribute name were legal identifier characters

Cause:
None of the characters in the name of an attribute of a type could be translated to a character that can begin a C or C++ identifier, such as a letter or an underscore. To find the affected attribute, look in the declaration generated for this type for data member names that are obviously incorrect.

O2U-00208 One or more characters in an attribute name were not legal identifier characters

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00208 One or more characters in an attribute name were not legal identifier characters

Cause:
If an attribute name contains one or more characters that can not be translated to a legal C or C++ identifier character, the characters that can not be translated are replaced with underscores. To find the affected attribute or attributes, look in the declaration generated for this type for data member names that have extra underscores not present in the original attribute names.

O2U-00209 Attribute or function name to be translated was not found

admin — Fri, 20 Mar 2009 13:46:27 +0000

Description:
O2U-00209 Attribute or function name to be translated was not found

Cause:
This name, for which a translation was requested, is not the name of an attribute or a function of the current type.