64 O2F-00301 to O2F-00341
- O2F-00301: Error attempting to read from the INTYPE file
-
Cause: An operating system error occurred while attempting to read from the INTYPE file.
- O2F-00302: Unable to allocate memory
-
Cause: OTT was unable to allocate memory.
- O2F-00303: No INTYPE file was specified
-
Cause: The required option INTYPE was not specified.
- O2F-00304: Invalid filename for the INTYPE file
-
Cause: The filename specified for the INTYPE file is not syntactically correct.
- O2F-00305: Error opening the INTYPE file for reading
-
Cause: An operating system error occurred while attempting to open the INTYPE file.
- O2F-00306: Unable to close the INTYPE file
-
Cause: An operating system error occurred while attempting to close the INTYPE 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.
- 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.
- 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.
- O2F-00310: Illegal or missing identifier name
-
Cause: A legal C or C++ identifier was expected following AS, but was not seen.
- O2F-00311: Illegal or missing file name
-
Cause: A legal file name was expected, but was not seen.
- O2F-00312: Illegal or missing type version string
-
Cause: A type version name was expected, but was not seen.
- O2F-00313: Illegal or missing attribute name
-
Cause: An attribute name was expected in the INTYPE file, but was not seen.
- O2F-00314: AS expected but not seen in the INTYPE file
-
Cause: Incorrect syntax in the INTYPE file.
- 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.
- O2F-00316: An unexpected token was seen at the end of a type specification
-
Cause: There is a syntax error in the INTYPE file.
- O2F-00317: Error opening the ERRTYPE file for writing
-
Cause: An operating system error occurred while attempting to open the ERRTYPE file for writing.
- O2F-00318: Error writing to the OUTTYPE file
-
Cause: An operating system error occurred when attempting to write to the OUTTYPE file.
- O2F-00319: No OUTTYPE file specified
-
Cause: The required option OUTTYPE was not specified.
- O2F-00320: Invalid filename for the OUTTYPE file
-
Cause: The filename specified for the OUTTYPE file is not syntactically correct.
- O2F-00321: Error opening the OUTTYPE file for writing
-
Cause: An operating system error occurred while attempting to open the OUTTYPE file.
- O2F-00322: Unable to close the OUTTYPE file
-
Cause: An operating system error occurred while attempting to close the OUTTYPE file.
- O2F-00323: Internal error in OTT facility O2F
-
Cause: An internal OTT error occurred in the O2F component of OTT.
- 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).
- 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.
- 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.
- O2F-00327: CASE option has an illegal value
-
Cause: The value given for the CASE option in the INTYPE file is not legal.
- 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.
- O2F-00329: Type or option specification expected
-
Cause: A type or option specification was expected in the INTYPE file, but was not seen.
- O2F-00330: Name exceeds 265 bytes in length
-
Cause: A name seen in the INTYPE file exceeds 265 bytes in length.
- O2F-00331: A syntactically illegal name was seen in the INTYPE file
-
Cause: A syntax error occurred in a name used in the INTYPE file.
- 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.
- 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.
- 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.
- O2F-00335: Internal error in O2F component of OTT
-
Cause: A request was made that all types in the database schema are to database.
- O2F-00336: Error reported by subsystem:\n
-
Cause: A request was made to generate declarations for all the types in a database schema. An error occurred in a subsystem when accessing the database.
- O2F-00337: Schema not found, or no types found in schema
-
Cause: A request was made to generate declarations for all the types in a database schema. Either the schema was not found, no user-declared types were found in the schema, or unable to connect to Oracle.
- O2F-00338: Illegal or missing package name
-
Cause: A legal Java package name was expected following IN or PACKAGE or IN PACKAGE, but was not seen.
- O2F-00339: CODE option has an illegal value
-
Cause: The value given for the CODE option in the INTYPE file is not legal.
- O2F-00340: Name was null
-
Cause: A name had a length of 0 characters.
- O2F-00341: An error occurred for which no message is available
-
Cause: The cause of this error was not reported.