Oracle Support will typically enter problems like this into the TAR system (Technical Assistance Requust) -- which feeds into the Oracle developers' bug database. The key is, you want to provide a minimal testcase using OCI.

Fortunately, DBD::Oracle has a feature for exactly this purpose, that turns on OCI-level tracing. You can then trivially make a C program that sends the exact OCI calls to Oracle to demonstrate the problem. All you need to do, is put the following immediately after use DBD::Oracle; in your script:

use DBI;
use DBD::Oracle;
DBI->trace(6,"trace_oci.txt");
[download]

Try and make the smallest possible script that demos the problem, and make a SQL script that creates the minimal server-side schema required. Your DBA can then send these two files to Oracle Support.

Think of it this way -- if someone sends you exactly what you need to be able to reproduce the problem in your own environment and on your own desktop, you're likely to fix that bug much more quickly than one where you need to install a specific version of some software which you may or may not be familiar with (imagine if you had to fix a bug in Mozilla's XPCOM.....)

Good Luck...

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.