Ok that narrows it down for me nicely.
hopefully I will get some time to look at it soon
might just be a simple var miss match
cheers
John Scoles
Charles Jardine wrote:
On 07/10/09 12:23, John Scoles wrote:
could be a bug
I would try the latest Trunk version of DBD::Oracle there were some
fixes put in there to the Object model way back in July.
you can find it at
http://svn.perl.org/modules/dbd-oracle/trunk
Sadly this doesn't fix the problem. It does, however, change the symptom.
Rather than a segfault, I am now getting
OCI-21500: internal error code, arguments: [kocgpn129], [2], [], [],
[], [], [], []
which matches Martin Evans's report.
I have narrowed the problem down to a single line of code - in the
trunk it
is line 1837 of oci8.c, which reads
OCITypeByRef_log_stat(fbh->imp_sth->envhp,fbh->imp_sth->errhp,type_ref,&tdo,status);
Beyond that, I am out of my depth.
I will see if I ever get any free time in the near future if I can
get 1.24 (the Beer) with a fix for this out by Christmas
I would be more than happy to test release candidates for 1.24.
Charles Jardine wrote:
On 07/10/09 11:47, Martin Evans wrote:
Charles Jardine wrote:
I have encountered a problem with the 'extended' support for
objects in DBD::Oracle. Specifically, if $dbh->{ora_objects}
is true, any attempt to fetch a nested table of objects
causes perl to crash with a segmentation fault.
Versions:
OS: SLES10 SP2 (64bit)
Oracle: 10.2.0.4 (64bit)
Perl: 5.10.0 (64bit)
DBI: 1.609
DBD::Oracle: 1.23
[details snipped - see original post]
Same for me but I am using an Oracle client older than the Oracle
server
- are you? Have you tried using a client that matches the server? I
cannot tell if you are running to a local or remote oracle. In the
past
when I have got "OCI-21500: internal error code, arguments:
[kocgpn129]"
errors it has been down to attempting to use a new feature in Oracle
with an old client.
My tests were run on the server, using the bequeather. I have just
reproduced it using a local TNS style connection. In bot cases the
server and client are using the same ORACLE_HOME. There is no
version mismatch
I forgot to mention that the script works correctly with
$dbh->{ora_objects} set to 0. This leads me to believe that the
problem is probably in DBD::Oracle itself.
