Databases
StackOverflow2013
Postsdbo
PODoes Oracle occi have any memory bugs when writing blobs using stored procedures via stream?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODoes Oracle occi have any memory bugs when writing blobs using stored procedures via stream?
    primarykey
    data
    text
    <p>The function below will produce some kind of memory corruption that will cause an exception (which cannot be identified since memory is corrupted) while doing another call:</p> <pre><code>{ ora::Statement stmt(__cn); string sql("BEGIN Pckg.Sp_procA(:1, :2, :3, :4, :5, :6, :7, :8, " ":9, :10, :11, :12, :13, :14, :15, :payload); END;"); occi::Blob payload(__cn.getConnection()); occi::Environment* tempEnv = occi::Environment::createEnvironment(); occi::Timestamp reportTime(tempEnv); reportTime.fromText(__report.report_time), "yyyy-mm-ddH24:mi:ss.ff"); stmt.setSQL(sql); stmt.setString (1, ""); stmt.setString (2, ""); stmt.setString (3, __report.varA); stmt.setString (4, __report.varB); stmt.setInt (5, __report.varC); stmt.setString (6, __report.varD); stmt.setString (7, __report.varE); stmt.setString (8, __report.varF); stmt.setTimestamp(9, reportTime); stmt.setNull (10, occi::OCCITIMESTAMP); stmt.setString (11, __report.varG); stmt.setString (12, __report.varH); stmt.setString (13, __report.varI); stmt.setString (14, __report.varK); stmt.setString (15, __report.varX); stmt.setBinaryStreamMode(16, __report.payload.Size(), true); stmt.executeUpdate(); occi::Stream* streamedData = stmt.getStream(16); streamedData-&gt;writeLastBuffer(__report.payload.GetPtr(), __report.payload.Size()); stmt.closeStream(streamedData); occi::Environment::terminateEnvironment(tempEnv); return true; } </code></pre> <p>The function below works perfectly unless the code above is executed and looks like this:</p> <pre><code>{ ora::Statement stmt(__cn); string sql("BEGIN " "Pckg.Sp_procB(:1, :2, :3, :4, :5, :6, :7, :8, :9, :10, :11); END;"); occi::Environment* tempEnv = occi::Environment::createEnvironment(); occi::Timestamp reportTime(tempEnv); reportTime.fromText(__report.report_time, "yyyy-mm-dd HH24:mi:ss.ff"); stmt.setSQL(sql); stmt.setString (1, ""); stmt.setString (2, ""); stmt.setString (3, __report.varA); stmt.setString (4, __report.varB); stmt.setInt (5, __report.varB); stmt.setString (6, __report.varD); stmt.setString (7, __report.varE); stmt.setString (8, __report.varF); stmt.setString (9, __report.varG); stmt.setTimestamp(10, reportTime); stmt.setNull (11, occi::OCCITIMESTAMP); stmt.executeUpdate(); occi::Environment::terminateEnvironment(tempEnv); return true; </code></pre> <p>}</p> <p>I got the blob insert example from Oracle's documentation and can't see anything wrong with it. The second function also seems to be ok which got me thinking that Oracle's occi might have some kind of bug that corrupts memory. Anyone knows anything about this or has done anything similar?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USSalsa
    1. USSalsa
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. CO[`select isn't broken`](http://pragprog.com/the-pragmatic-programmer/extracts/tips); If the question is as presented, it should go on the Oracle Forums / Bug tracker.
      singulars
      1. PODoes Oracle occi have any memory bugs when writing blobs using stored procedures via stream?
      1. USsehe
    2. COTrue. Thanks...
      singulars
      1. PODoes Oracle occi have any memory bugs when writing blobs using stored procedures via stream?
      1. USSalsa
    3. COWhat error do you actually see? I wonder if `__report.payload` is initialised, otherwise `.Size()` might bomb out. Or since it's an out parameter, and `Size` is presumably zero before you start, maybe you need to give the max size you might see returned instead so Oracle doesn't try to write to memory it isn't allocated? Having `:payload` in the proc call looks like a fix attempt; mixing named and positional parameters might be asking for pain later but probably doesn't matter right now. I don't see the `occi::Blob payload` being used though, but I might be missing something...
      singulars
      1. PODoes Oracle occi have any memory bugs when writing blobs using stored procedures via stream?
      1. USAlex Poole
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload