Release 8.0
A54625_01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
This chapter lists messages generated by the Object Type Translator. The likely cause(s) of the event(s) generating the message and recommended corrective action are also presented.
The error code consists of a prefix, severity code, and sequence number. The prefix O2 shows that the error was issued by Object Type Translator. An additional letter indicated whether the error was caused by the interface, a file read, or unparsing:
| Prefix | Meaning |
|---|---|
|
O2I |
interface error |
|
O2F |
file read error |
|
O2U |
unparsing error |
There are four severity codes, described in the following table.
Cause: The value supplied for the USERID parameter is not a legal<username>/<password>[@<databasename>] string.
Action: Set the USERID option to the correct <username>/<password> or <username>/<password>@<database name> combination to use when connecting to the database. If you have an OPS$ account, you may instead omit the USERID option, in which case OTT will attempt to connect to the database using the userid OPS$<username>. The USERID option may be specified on the command line or in a CONFIG file.
Cause: OTT could not connect to Oracle with the username, password, and, if applicable, database link that was supplied. Either the USERID option value was incorrect, or, if the USERID was not supplied, the userid OPS$<username> was not accepted.
Action: Check that the username and password are current and correct. Run another program that connects to Oracle to verify that you can connect using that username and password.
Cause: Two different file names have been used in the INTYPE file to refer to the same HFILE file, or different file names have been used to refer to the same HFILE file on the command line and in the INTYPE file.
Action: Consistently refer to each HFILE file using the same file name.
Cause: An internal OTT error occurred in the O2I component of OTT.
Action: Contact ORACLE customer support.
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
Cause: An operating system error occurred when attempting to write to the HFILE file.
Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.
Cause: The HFILE file to which declarations generated by OTT are written was not specified.
Action: Specify the global HFILE option on the command line or in a CONFIG file. You may choose a different HFILE for a particular type by specifying a different HFILE in the INTYPE file entry describing the type. If every INTYPE file entry specifies an HFILE, and if none of the types in the HFILE require declarations of types not mentioned there, the global HFILE option may be omitted. An INTYPE file generated by a previous invocation of OTT satisfies these conditions.
Cause: The HFILE specified filename is not syntactically correct.
Action: Make sure the HFILE filename is spelled correctly.
Cause: An operating system error occurred while attempting to open the HFILE file for writing.
Action: Make sure the HFILE filename is spelled correctly. Try creating or modifying the HFILE to make sure you have write access to the file.
Cause: An operating system error occurred while attempting to close the HFILE file.
Action: Try creating or modifying the HFILE file to make sure you are able to access the file.
Cause: The message file for the internal OTT component O2U was not found. OTT may not be correctly installed.
Action: Contact ORACLE customer support.
Cause: A user-defined type specified in the INTYPE file was not found in the database.
Action: Make sure the name of the type is spelled correctly. Make sure the type is actually declared in the database.
Cause: A subsystem invoked by OTT reported a warning. This warning immediately follows the "Warning reported by subsystem" message.
Action: Examine the warning reported by the subsystem to determine its cause.
Cause: A subsystem invoked by OTT reported an error. This error immediately follows the "Error reported by subsystem" message.
Action: Examine the error message reported by the subsystem to determine its cause.
Cause: The required CODE option was not specified on the command line or in a configuration file.
Action: Specify the CODE option on the command line or in a configuration file. Currently, the following values of the CODE option are supported: CODE=ANSI_C, CODE=KR_C, CODE=C.
Cause: The filename specified for the INITFILE file is not syntactically correct.
Action: Make sure the filename of the INITFILE file is spelled correctly.
Cause: An operating system error occurred while attempting to close the INITFILE file.
Action: Try opening the INITFILE file with an editor to make sure the file can be accessed.
Cause: An operating system error occurred while attempting to open the INITFILE file for writing.
Action: Make sure the INITFILE filename is spelled correctly. Try creating or modifying the INITFILE file to make sure you have write access to the file.
Cause: An operating system error occurred when attempting to write to the INITFILE file.
Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.
Cause: A request was made in the option SCHEMA_NAMES=FROM_INTYPE that schema names be written to the OUTTYPE file as given in the INTYPE file. However, an INTYPE file was not specified.
Action: Either supply the name of an INTYPE file, or specify the SCHEMA_NAMES option ALWAYS or IF_NEEDED.
Cause: An internal OTT error occurred in the O2U facility of OTT.
Action: Contact ORACLE customer support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
Cause: An operating system error occurred while attempting to read from the INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file.
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
Cause: The required option INTYPE was not specified.
Action: Set the INTYPE option to the name of the file containing names of types for OTT to translate. The INTYPE option may be specified on the command line or in a CONFIG file.
Cause: The filename specified for the INTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the INTYPE file correctly.
Cause: An operating system error occurred while attempting to open the INTYPE file.
Action: Make sure the filename of the INTYPE file is spelled correctly. Try opening the INTYPE file with an editor to make sure you have access to the file.
Cause: An operating system error occurred while attempting to close the INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file.
Cause: The first token of the INTYPE file was not read. Either an operating system error occurred while attempting to read from the INTYPE file, or all lines of the INTYPE file are blank lines or comment lines.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file. Make sure the INTYPE file contains one or more type specifications.
Cause: Either there are no type specifications in the INTYPE file, or the first type specification could not be read due to a previously reported error.
Action: Fix any previously reported errors. Make sure there are one or more type specifications in the INTYPE file.
Cause: The name of a user-defined type is expected following the keyword TYPE at the beginning of a type specification. No legal type name was seen.
Action: Make sure that the type specification is syntactically correct, and that the type name is spelled correctly.
Cause: A legal C or C++ identifier was expected following AS, but was not seen.
Action: Use a legal C or C++ identifier, consisting of letters, digits, and underscores not beginning with a digit.
Cause: A legal file name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct file name.
Cause: A type version name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct version name.
Cause: An attribute name was expected in the INTYPE file, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct attribute name.
Cause: Incorrect syntax in the INTYPE file.
Action: Make sure your TYPE file syntax is correct.
Cause: An attribute of a user-defined type is listed twice in a type specification in the INTYPE file. The second occurrence is ignored.
Action: Remove one of the two occurrences of the attribute.
Cause: There is a syntax error in the INTYPE file.
Action: Check your documentation to make sure the type specifications in your INTYPE file are syntactically correct.
Cause: An operating system error occurred while attempting to open the ERRTYPE file for writing.
Action: Make sure you spelled the ERRTYPE filename correctly. Try creating or modifying the ERRTYPE file to make sure you have write access to the file.
Cause: An operating system error occurred when attempting to write to the OUTTYPE file.
Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.
Cause: The required option OUTTYPE was not specified.
Action: Set the OUTTYPE option to the name of the file to which the TYPE file produced by OTT should be written. The OUTTYPE option may be specified on the command line or in a CONFIG file.
Cause: The filename specified for the OUTTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the OUTTYPE file correctly.
Cause: An operating system error occurred while attempting to open the OUTTYPE file.
Action: Make sure you spelled the filename of the OUTTYPE file correctly. Make sure you have operating system permission to open the file.
Cause: An operating system error occurred while attempting to close the OUTTYPE file.
Action: Try opening the OUTTYPE file with an editor to make sure you are able to access the file.
Cause: An internal OTT error occurred in the O2F component of OTT.
Action: Contact ORACLE customer support.
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 can be translated to the compiler character set. The compiler character set itself 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.
Cause: None of the characters in the name of a database entity 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 name in the INTYPE file.
Cause: One or more characters in the name of a database entity 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: Make sure that the name is spelled correctly, and that it is terminated by a blank, the end of a line, or an equals sign ("="). You may use the translated name with added underscores, or you may specify an explicit translation for the name in the INTYPE file.
Cause: The value given for the CASE option in the INTYPE file is not legal.
Action: Change the value given for the CASE option to one of the following legal values: SAME, LOWER, UPPER, or OPPOSITE.
Cause: The function name given for the INITFUNC option in the INTYPE file is not a legal C or C++ identifier.
Action: Change the name of the INITFUNC function to a legal C or C++ identifier.
Cause: A type or option specification was expected in the INTYPE file, but was not seen.
Action: Check the INTYPE file for syntax errors. Supply a type or option specification. A type specification begins with the word TYPE. An option specification begins with the word CASE, INITFILE, or INITFUNC.
Cause: A name seen in the INTYPE file exceeds 265 bytes in length.
Action: Choose a shorter name.
Cause: A syntactic error, such as mismatched or incorrectly placed quotes, occurred in a name used in the INTYPE file.
Action: Make sure that the name is either quoted in full or not quoted at all. If the name is quoted, make sure that both the opening quote and the closing quote are present.
Cause: A database link was seen in the name of a user-defined type. This feature is not yet supported.
Action: Declare the user-defined type in the database to which OTT connects.
Cause: A keyword such as TYPE was expected in the INTYPE file, but an incorrect or misspelled keyword was seen.
Action: Verify that your TYPE specification obeys the syntax described in your documentation. Verify that your keyword is spelled correctly.
Cause: The same name of a user-defined type appears in more than one type specification. The duplicate specifications of the type name will be ignored.
Action: Put all of the information about the type, including all type name and attribute name translations, in a single TYPE specification, and eliminate the duplicate TYPE specifications.
Cause: A request was made that all types in the database schema are to be unparsed. An internal error occurred when initiating access to the database.
Action: Unparse from an INTYPE file. Contact ORACLE customer support.
Cause: A request was made that all types in the database schema are to be unparsed. An error occurred in a subsystem when accessing the database.
Action: Examine the error message reported by the subsystem to determine its cause. Unparse from an INTYPE file.
Cause: A request was made that all types in the database schema are to be unparsed. Either OTT cannot connect to the Oracle database, or the database contains no user types that may be unparsed.
Action: Ensure that a login/password string was specified for OTT and that the Oracle database can be accessed with it. Ensure that the USER_TYPES table in the database contains at least one row.
