try this
This problem occurs when you use the Microsoft Oracle provider and passing more than 32k of data to a CLOB parameter of an Oracle Stored Procedure.
There are a couple of ways to work around this problem:
1) Instead of calling a stored procedure to insert into a clob field, use inline SQL to insert/update the field
2) Rewrite your logic to use Oracle Data Provider for .NET (ODP.NET) version 9.2, here is a sample code
In your project, you would need to reference the following dll: Oracle.DataAccess.dll
VB.NET
Imports Oracle.DataAccess.Client
Dim conn As OracleConnectionDim cmd As OracleCommand
conn = New OracleConnection("Database Connection String")
cmd = New OracleCommand("Stored Procedure Name", conn)
cmd.CommandType = CommandType.StoredProcedure
cmd.Parameters.Add("ClobData", OracleDbType.Clob, CLOB_DATA, ParameterDirection.Input)
conn.Open()
cmd.ExecuteNonQuery()
cmd.Dispose()
conn.Close()