Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 00200-00210: Object Type Translator Unparser Messages

##### 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: A type specified in the INTYPE file was not an object type or a named collection type. OTT will only generate declarations for these types.

Action: You are probably asking OTT to declare a built-in type. Because this type is predefined, no declaration is required. 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 may 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 may 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: Use the translated type name with added underscores, or specify an explicit translation for the type name in the INTYPE file.

##### 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 begins 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 attribute names contained illegal 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. This type has one or more such attributes. To find the affected 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: You can use the data member names that have extra underscores if you want, or you can specify an explicit translation for the affected attribute names in the INTYPE file.

##### 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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index