Update to writing Oracle CLOBS / LOBS.

If you use my implementation of writing large objects to oracle make sure you monitor the way your sessions behave incase they may get left open even though in oracle they are clearly seen as inactive and that .Close() was explicitly called on the OracleConnection.

We ran into this eventually causing a connection saturation of our pool. Presently I have no known solution to preventing this, however if oracle is configured correctly to use connection pooling this should not be an issue. Since oracle at my employment can’t seem to be configured to use connection sharing correctly all the time I spent on this was pointless…

I’ve said it once, I’ll say it again, I really hate you Oracle.

BloggingContext.ApplicationInstance.CompleteRequest();

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s