CLOB to Oracle DB Target (large string causes issues)

[Ted Cooper]

When inserting a large string message to Oracle from a C# application, we encounter a known Oracle issue:

ORA-01460 - unimplemented or unreasonable conversion requested

This problem occurs with strings over 4000 characters.  In ODP.NET you can beat it with some creative methods to call the database, per this link:

http://stackoverflow.com/questions/3557995/issues-calling-stored-procedure-from-c-sharp-with-large-clob

The suggested fix is to do the following: "Set the parameter value when BeginTransaction has already been called on the DbConnection."

However, with the DB configured as a target, I don't get this level of fine control to tweak how we call the stored procedure.

Similar to the person in the link, I'm trying to send a large amount of string data as XML to the DB for processing.

Is this something we could build into nLog, either as an optional parameter on the target for Oracle calls, or automatic based on the type of connection?

[Kim Christensen]

You could create a custom target which solves this problem. Unfortunately there are no way to perform this workaround in NLog

[Steven Orvis]

I have a pull request for this same issue. Even if they don't merge the code you could create a custom DatabaseTarget and use the code from the pull request.

https://github.com/NLog/NLog/pull/1194