Skip Headers
Oracle® Database Error Messages
11g Release 1 (11.1)

B28278-02
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
Mobi · ePub

70 O2U-00200 to O2U-00212

O2U-00200: Internal error in OTT facility O2U
Cause: An internal OTT error occurred in the O2U facility of OTT.
Action: Contact ORACLE customer support.
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.
Action: Contact ORACLE customer support.
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 the end user.
Action: Contact ORACLE customer support.
O2U-00203: Type to be declared must be an object type or a named collection type
Cause: You have asked OTT 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.
Action: You are probably asking OTT to declare a built-in type, or, if you are generating Java code, a named collection type. Do not ask OTT to generate a declaration for this type.
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).
Action: A name is translated first from the database character set to the client character set, and then from the client character set to the compiler character set. The client character set is specified in a platform-dependent manner (On UNIX platforms, the client character set is specified by setting the NLS_LANG environment variable.) Use a client character set that includes the character set of the INTYPE file and can be translated to the compiler character set. The database character set is one such character set. Specify synonyms in the INTYPE file for any names of database objects that cannot be successfully translated to the client character set.
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.
Action: Specify an explicit translation for the type name in the INTYPE file.
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.
Action: Specify an explicit translation for the type name in the INTYPE file, or just use the translated type name with added underscores.
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.
Action: Specify an explicit translation for the attribute name in the INTYPE file.
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.
Action: Specify explicit translations for the affected attribute names in the INTYPE file, or just use the translated attribute names with added underscores.
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.
Action: Make sure that the name is spelled correctly, and is the name of an attribute or function defined in the current type.
O2U-00210: Unable to allocate memory
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
O2U-00211: A type without attributes was translated
Cause: OTT translated a type without attributes. The corresponding C-type will be a struct without any components, which is not legal C. The empty type in the database may be the result of an error during type creation. Additionally, incomplete types may be used temporarily in the creation of types that reference one another.
Action: Re-create a full version of the type in the database and then re-run OTT.
O2U-00212: An error occurred for which no message is available
Cause: The cause of this error was not reported.
Action: Contact ORACLE customer support.