Re: DBI BLOB Insert Issue - Database out of space

[FloydATC]

First off: I'm assuming you've already passed the Oracle error message on to the DBA since that's not a Perl/DBI problem per se. Google has plenty of helpful pointers on that particular error message.

About the AutoCommit vs. manual commit/rollback: Without seeing the actual code we can only speculate, but generally speaking AutoCommit means you forego the whole "roll back in the event of failure" mechanism by committing each query as you go. How this ends up inserting a record with an empty field is hard to say.

If you simply inserted a single record with a number of fields, I'm tempted to say it SHOULD be an "all or nothing" thing; either the entire record makes it into the database with all fields intact or the single insert query should fail completely and leave no trace. This should be the case with or without AutoCommit.

On the other hand, if you insert and then update with AutoCommit, you'll end up with a partial if the update fails. This is what AutoCommit means.

Note that I have no way of knowing your proficiency level, please don't be offended if you know all of this perfectly well :-)