> > > > Jeff, > > > > I upgraded to perl 5.8.3 and installed both the DBI and the > > DBD::Oracle modules from your site. As you suspected, that > > did not fix the problem. > > Unfortunately :( > > > > When I was running the dumpbin utility, I realized that in my > > previous email I mis-typed the error message that I was > > getting. It's not the OCILobAppend function, it's > > OCILobWriteAppend (if that makes any difference). Never the > > less, The OCILobWriteAppend function is not exported from my > > OCI.dll file (the other one is). I suspected that the > > software I have installed was outdated, I guess this confirms > > it. So I suppose I need to get some different software > > loaded on my PC. > > Ok -- good news and bad news. That function is in the > 8.1.7.4 client lib, > but I can't tell you if it was in the 8.1.7. It seems pretty > obvious that > it's not in the 8.1.6.x that you have. > > > > > My next question is going to demonstrate my ignorance, but I > > need to ask it. Exactly what should I be asking my IT > > department to load onto my machine? I've asked them for the > > "Oracle Client" software, but they don't seem to understand > > what I'm asking for. They gave me this "Oracle Developer" > > software and told me that the client software is included in > > it. I doubt that's true though because it doesn't have any > > of the directories/files that I would need to build the DBD > > module myself (\LIB, \OCI, ...), so I'm assuming that there > > must be something else available. I have near zero Oracle > > experience, so it's possible I'm just not using the right > > terminology, on the other hand, maybe they're just playing dumb. > > Ok -- in order to build directly, you will need the client > libs and the OCI > libs. They are correct that the client libs are included and they may > (probably) have the option to install the OCI libs too when > they do install > it. Usually, you have to go into custom install or do a > "full" install. > > That said, it's possible that with a version with out that, > you'll have to > back off a rev or two in DBD::Oracle to avoid that function. > > I would suggest that you ask them for the 8.1.7 client > install and if that > doesn't work (i.e. that function is not in 8.1.7 directly), > then you can > patch it to 8.1.7.4, I'm sure. If you have a valid license > of Oracle, the > 8.1.7 client should be downloadable still somewhere on > Oracle's site. If > not, the 9x client should work, too. > > Regards, > > Jeff >
FWIW I am using 8.1.7 which was good to build last time - I'll guess 9 months ago, but now long.t fails with a bunch of (eg): ... ok 151 ok 152 # failed test 153 at line 328. not ok 153 error: ORA-24801: illegal parameter value in OCI lob function (DBD ERROR: OCILobWriteAppend) If you're using Oracle < 8.1.7 then the OCILobWriteAppend error is probably due to Oracle bug #886191 and is not a DBD::Oracle problem 41 locator: OCILobLocatorPtr=SCALAR(0x1ca48dc) ok 154 ... A quick google brings up thread: http://www.mail-archive.com/[EMAIL PROTECTED]/msg20034.html which may be enlightening. Or at least offer some more insight... And BTW Ron since you're planning threads, are you aware of the warning on building DBI: CPAN.pm: Going to build T/TI/TIMB/DBI-1.41.tar.gz *** You are using a perl configured with threading enabled. *** You should be aware that using multiple threads is *** not recommended for production environments. -Lynn.
