OTL knowledge point and execution exception error handling

1.OTL_SQL_HANDLE.GET_RPC ():

Meaning: The parameters have been removed or inserted several times. Note: When you delete, it is always 0.

2. Set the field to the same size.

such as: user_id Varchar2[5], the operation, User_id<char[6]>, and the input suserid[6] size is 6. namely otl_stream_handle<<suserid;

OTL exceptions are typically ORACLE errors:

Special: When the card is dead, it is generally not enough to set the cache size.

OTL Library Execution exception [32000]:

WORKAROUND: The Out parameter type does not match. such as <double>, datatype in operator <</>>: CHAR, variable int, the actual requirement is long, as a conversion.

OTL Library execution exception [32001]:row must is full for flushing output stream

FIX: Dynamic variable name.

OTL Library Execution exception [933]:

WORKAROUND: The SQL statement is incorrect, cannot be executed, or does not conform to the OTL format, as compared to the normal statement.

OTL Library execution exception [32005]:

Input string value is too large to fit into the buffer

Resolution: The size of the cache setting when open;

Statement usage type is inconsistent with field actual type. When the character length setting such as char[4] is consistent with the error, note that the last character set is "OK."

OTL Library execution exception [904]:

FIX: Field names are inconsistent.

OTL Library execution exception [926]:

WORKAROUND: The INSERT statement is incorrect.

OTL Library execution exception [917]:

FIX: Oracle error, missing comma

OTL Library Execution exception [1861]:

FIX: oralce1861 errors, inconsistent field properties, such as Date type, insert string type data.

OTL Library execution exception [1438]:

Resolution: oracle1438, inconsistent accuracy required

OTL Library execution exception [947]:

Resolution: The number of fields is inconsistent.

OTL Library execution exception [1013]:

Resolution: ORA-01013: The user requested to cancel the current operation

OTL Library execution exception [1756]:

Resolution: The string in Oracle 1756 quotes does not end correctly

OTL knowledge point and execution exception error handling