Assembly: System.Data.OracleClient (in system.data.oracleclient.dll)
The desired length of the current OracleLob stream in bytes. For CLOB and NCLOB data types, this must be an even number.
A value specified in the value parameter for a CLOB or NCLOB data type is not even.
A value specified in the value parameter is less than zero or greater than 4 gigabytes.
The operation is not within a transaction, the OracleLob object is null, or the connection is closed.
The object was closed or disposed.
An Oracle error has occurred.
An attempt to increase the length of the OracleLob stream fails, and returns "Message: ORA-22926: specified trim length is greater than current LOB value's length" from the Oracle server.
A stream must support both writing and seeking for SetLength to function.
The .NET Framework Data Provider for Oracle handles all CLOB and NCLOB data as Unicode. Therefore, when accessing CLOB and NCLOB data types, you are always dealing with the number of bytes, where each character is 2 bytes. For example, if a string of text containing three characters is saved as an NCLOB on an Oracle server where the character set is 4 bytes per character, and you perform a SetLength operation, you specify the length of the string as 6 bytes, although it is stored as 12 bytes on the server.
To write to the LOB, you must have retrieved the LOB using the FOR UPDATE clause in the SQL SELECT statement, and you must have a local transaction started.
A write operation to a read-only LOB might succeed, but does not update the LOB on the server. In this case, however, the local copy of the LOB is updated. Therefore, later read operations on the OracleLob object might return the results of the write operation.
Windows 98, Windows Server 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter EditionThe Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.