OTL 4.0, OTL defined exceptions

OTL defined exceptions

The following OTL exceptions can be raised by the OTL stream functions:

Code=32000: Incompatible data types in stream ope ration

Cause: The data type of a variable used in the current stream operation is not compatible with the declared stream format
Action: Check placeholders and declarations of their data types

Code=32001: Row must be full for flushing output stream

Cause: Stream is open for output and has a format of output rows. An output row is a tuple of all output variables put together. The current output row is not filled yet but the flush function is invoked. The stream buffer cannot be flushed until the current row of the output buffer is full.
Action: Fill the row first, then flush the stream.

Code=32003: Not all input variables have been initialized

Cause: stream has input variables but not all the variables have been initialized. An attempt to read data from the stream was made.
Action: Assign all input variables first.

Code=32004: No input variables have been defined in SQL statement

Cause: Stream has no input variables. An attempt to write objects into the stream via one of the operator << was made.
Action: Do not call the operator << for streams which have no input variables defined.

Code=32005: Input string value is too large to fit into the buffer

Cause: Stream is open for output, e.g. an INSERT statement. The actual string value is larger than the buffer size, e.g. "123456789" is the string and the placeholder was defined as :f2<char[5]>
Action: Truncate the input string or increase the size of the buffer of the placeholder <char[10]>

Code=32006: Input otl_long_string value is too large to fit into the buffer

Cause: Stream is open for output, e.g. an INSERT statement. The actual otl_long_string is larger than the buffer size, defined by set_max_long_size(), e.g. "123456789" is the long string and the following function call was made set_max_long_size(5).
Action: Truncate the input long string or increase the size of the max long size: set_max_long_size(100)

Code=32007: PL/SQL table size is too large (>32767)

Cause: Size of PL/SQL.table to be declared in otl_stream is too large.
Action: The maximum size of PL/SQL table is limited to 32767 elements.

Code=32008: Writing CLOB/BLOB in stream mode: actual size is greater than specified

Cause: Actual number of bytes to be written into the LOB stream is greater than specified in the otl_lob_stream::set_len() function.
Action: Actual number of bytes to be written into the LOB stream should match the number, specified in the set_len() function.

Code=32009: Closing CLOB/BLOB in stream mode: actual size is not equal to specified size

Cause: When otl_lob_stream::close() is called, it turns out that the number of bytes, written into the LOB stream, does not match the number of bytes, specified in otl_lob_stream::set_len().
Action: Actual number of bytes to be written into the LOB stream should match the number, specified in the set_len() function

Code=32010: CLOB/BLOB stream is not open for writing

Cause: An attempt was made to write into the LOB stream, which was not initialized for writing.
Action: LOB stream that is not open for writing, cannot be used for writing.

Code=32011: CLOB/BLOB stream is not open for reading

Cause: An attempt was made to read from the LOB stream, which was not initialized for reading.
Action: LOB stream that is not open for reading, cannot be used for reading.

Code=32012: First session must be started with session_begin()

Cause: An attempt to call otl_connect::session_reopen() was made, before calling session_begin().
Action: Change the logic of the program to call session_begin() first, and only after that to call session_reopen().

Code=32013: Invalid bind variable declaration

Cause: There was a typo in the bind variable declaration, e.g. :var<date>, instead of :var<timestamp>.
Action: Correct the typo and try again.

Code=32014: No stored procedure was found

Cause: Stored procedure name, being passed into otl_stream::create_stored_proc_call, cannot be found in the Oracle data dictionary.
Action: Correct the stored procedure name, and try again.

Code=32015: Unsupported data type

Cause: Datatype of parameter of the stored procedure, specified in otl_stream::create_stored_proc_call, is unsupported.
Action: PL/SQL tables, as stored procedure parameters, are not supported by create_stored_proc_call(). Also, if a stored procedure, which returns a reference cursor as an output parameter, has INOUT, or OUT parameters, is not supported by create_stored_proc_call(). What is supported by create_stored_proc_call() is as follows: (1) stored procedures with scalar input/output paramaters; (2) a stored procedure with scalar input parameters only, which returns a reference cursor as an output parameter, or as a stored function, returning a reference cursor as a return value.

Code=32016: Unsupported procedure type

Cause: Stored procedure name, being passed into otl_stream::create_stored_proc_call, is of unsupported type..
Action: F.or more detail, see this.

Prev Contents Go Home

Permission to use, copy, modify and redistribute this document for any purpose is hereby granted without fee, provided that the above copyright notice appear in all copies.