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

## 00101-00126: Object Type Translator Initialization Messages

##### O2I-00101: invalid value for the USERID parameter

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.

##### O2I-00102: unable to connect to Oracle

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.

##### O2I-00103: two file names refer to the same HFILE file in the INTYPE file

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.

##### O2I-00110: internal error in OTT component O2I

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

Action: Contact ORACLE customer support.

##### O2I-00111: unable to allocate memory

Cause: OTT was unable to allocate memory.

Action: Contact ORACLE customer support.

##### O2I-00112: unable to write to the HFILE file

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.

##### O2I-00113: no HFILE specified

Cause: The HFILE file to which C 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.

##### O2I-00114: invalid HFILE file name

Cause: The HFILE specified filename is not syntactically correct.

Action: Make sure the HFILE filename is spelled correctly.

##### O2I-00115: error opening the HFILE file

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.

##### O2I-00116: unable to close the HFILE 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.

##### O2I-00117: internal error: No message file for component O2U

Cause: The message file for the internal OTT component O2U was not found. OTT may not be correctly installed.

Action: Contact ORACLE customer support.

##### O2I-00118: this user-defined type was not found in the database

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.

##### O2I-00119: warning reported by subsystem:\n

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.

##### O2I-00120: error reported by subsystem:\n

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.

##### O2I-00121: no value was specified for the CODE option

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.

##### O2I-00122: invalid filename for the INITFILE file

Cause: The filename specified for the INITFILE file is not syntactically correct.

Action: Make sure the filename of the INITFILE file is spelled correctly.

##### O2I-00123: unable to close the INITFILE file

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.

##### O2I-00124: error opening the INITFILE file for writing

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.

##### O2I-00125: error writing to the INITFILE 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.

##### O2I-00126: you must specify an INTYPE file with SCHEMA_NAMES=FROM_INTYPE

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.

##### O2I-00127: illegal INITFUNC name

Cause: The name of the INITFUNC function is not a legal C or C++ identifier.

Action: Specify the name of the INITFUNC function as a legal C or C++ identifier. This name may be given in the INTYPE file, given on the command line, or derived from the INITFILE name.

##### O2I-00128: unable to write to the Java file

Cause: An operating system error occurred when attempting to write to a Java source file.

Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.

##### O2I-00129: no Java file specified

Cause: The file to which Java declarations generated by OTT are written was not specified.

Action: This message should never be seen, because Java files are named after the classes declared within them. Contact ORACLE customer support.

##### O2I-00130: invalid Java file name

Cause: A Java file name was specified that is not syntactically correct.

Action: Make sure the Java filename is spelled correctly.

##### O2I-00131: error opening a Java file

Cause: An operating system error occurred while attempting to open a Java file for writing.

Action: Make sure the filename is spelled correctly. Try creating or modifying the file to make sure you have write access to the file.

##### O2I-00132: unable to close a Java file

Cause: An operating system error occurred while attempting to close a Java file.

Action: Try creating or modifying the Java file to make sure you are able to access the file.

##### O2I-00133: an error occurred for which no message is available

Cause: The cause of this error was not reported.

Action: Contact ORACLE customer support.

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