Oracle Call Interface (OCI) Errors

OCI errors appear onscreen. These messages are also written to the log file. If tracing is enabled, these messages are captured in the trace file. See Log and Trace Files.

OCI errors are prefixed by the time stamp hh:mm:ss, where hh is hours, mm is minutes, and ss is seconds. In addition, each of the OCI errors is followed by the error message text in the following form:

Error Text: text

where text is the error text returned by the OCI. The text may sometimes be several lines long, especially if more than one error has occurred. The text starts with ORA-xxx, where xxx is the Oracle error number. Explanations are in your Oracle documentation.

OCI errors typically precede many of the errors listed in the section, Error Messages. You can typically find the problem when you look up the OCI message. If the error involves a stored procedure, you must search through line numbers and stored procedure names to find the error.

The following OCI error is most likely to occur with the DATABridge Client for Oracle.

OCI ERROR: err_code = nnnn for <ocifunction>

where <ocifunction> is the name of the OCI function involved in the error. The following is a list of possible OCI functions.

OCIAttrGet
OCIAttrSet
OCIDefineByPos
OCIEnvCreate
OCIEnvInit
OCIHandleAlloc
OCIHandleFree
OCIServerAttach
OCIServerDetach
OCISessionBegin
OCISessionEnd
OCIStmtExecute
OCIStmtFetch
OCIStmtPrepare
OCITransCommit
OCITransRollback

For more details, see your Oracle documentation.