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

## 00301-00326 Object Type Translator Type File Messages

##### O2F-00301: error attempting to read from the INTYPE file

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.

##### O2F-00302: unable to allocate memory

Cause: OTT was unable to allocate memory.

Action: Contact ORACLE customer support.

##### O2F-00303: no INTYPE file was specified

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.

##### O2F-00304: invalid filename for the INTYPE 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.

##### O2F-00305: error opening the INTYPE file for reading

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.

##### O2F-00306: unable to close the INTYPE 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.

##### O2F-00307: unable to read the INTYPE 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.

##### O2F-00308: no type specifications were seen in the INTYPE file

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.

##### O2F-00309: name of user-defined type is illegal or missing

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.

##### O2F-00310: illegal or missing identifier name

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.

##### O2F-00311: illegal or missing file name

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.

##### O2F-00312: illegal or missing type version string

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.

##### O2F-00313: illegal or missing attribute 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.

##### O2F-00314: AS expected but not seen in the INTYPE file

Cause: Incorrect syntax in the INTYPE file.

Action: Make sure your TYPE file syntax is correct.

##### O2F-00315: an attribute of a type is listed twice in a type specification

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.

##### O2F-00316: an unexpected token was seen at the end of a type specification

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.

##### O2F-00317: error opening the ERRTYPE file for writing

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.

##### O2F-00318: error writing to the OUTTYPE 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.

##### O2F-00319: no OUTTYPE file specified

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.

##### O2F-00320: invalid filename for the OUTTYPE 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.

##### O2F-00321: error opening the OUTTYPE file for writing

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.

##### O2F-00322: unable to close the OUTTYPE 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.

##### O2F-00323: internal error in OTT facility O2F

Cause: An internal OTT error occurred in the O2F component of OTT.

Action: Contact ORACLE customer support.

##### O2F-00324: 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 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.

##### O2F-00325: none of the characters in a name were legal identifier characters

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.

##### O2F-00326: some characters in this name were not legal identifier characters

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.

##### O2F-00327: CASE option has an illegal value

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.

##### O2F-00328: illegal INITFUNC name

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.

##### O2F-00329: type or option specification expected

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.

##### O2F-00330: name exceeds 265 bytes in length

Cause: A name seen in the INTYPE file exceeds 265 bytes in length.

Action: Choose a shorter name.

##### O2F-00331: a syntactically illegal name was seen in the INTYPE file

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.

##### O2F-00332: a database link may not appear in the name of a user-defined type

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.

##### O2F-00333: an unexpected token appeared where a keyword was expected in the INTYPE file

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.

##### O2F-00334: a user-defined type is listed more than once in the INTYPE file

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.

##### O2F-00335: internal error in O2F component of OTT

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.

##### O2F-00336: error reported by subsystem:\n

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.

##### O2F-00337: error unparsing schema. Schema empty or no connection to Oracle

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.

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