Hi,

It appears that my original message was longer than 5000 lines, so mailer rejected it. 
I am resending this without DBI and DBD make logs. If you can help please let me know 
so I can mail you the logs as well if needed.

Much appreciated!

Srdjan Nikolic

>  -----Original Message-----
> From:         Nikolic, Srdjan  
> Sent: Saturday, 15 February 2003 1:39 PM
> To:   '[EMAIL PROTECTED]'
> Subject:      DBI/DBD Oracle dumps core on Solaris 8 when 
> reference cursor returned untouched
> 
> Hi,
> 
> Here is the problem summary:
> 
> Versions:
>       Perl: 5.6.1
>       DBI: 1.32
>       DBD-Oracle: 1.12
>       Operating System: Solaris 5.8
>       Oracle version: 8.1.7
> 
> Description:
>       When DBI/DBD executes a PL/SQL stored procedure which 
> returns a reference cursor, and that cursor has been touched 
> by the procedure, the whole works fine. However, if the 
> cursor was untouched, for example if there is a piece of code 
> that raises an exception before the cursor was used in the 
> procedure, the program dumps core. The error message is:
> 
> OCIErrorGet after OCIAttrGet OCI_ATTR_PARAM_COUNT (er1:ok): 
> -1, 24338: ORA-24338: statement handle not executed
> !! ERROR: 24338 'ORA-24338: statement handle not executed 
> (DBD ERROR: OCIAttrGet OCI_ATTR_PARAM_COUNT)'
> DBD::Oracle::st execute failed: ORA-24338: statement handle 
> not executed (DBD ERROR: OCIAttrGet OCI_ATTR_PARAM_COUNT) at 
> ./bug.pl line 40.
> 
> Note that the execution is successful also if the cursor 
> statement did not have any rows returned. The program fails 
> ONLY if the cursor is untouched.
> 
> Attachments:
>       bug.sql - creates the example tables and packages (run 
> 'sqlplus user/password @bug.sql' to install).
>       bug.pl - the sample perl script (use './bug.pl MR' for 
> success or './bug.pl GG' to get it to dump core).
>       DBImake.log - verbose log of the DBI-1.32 make and installation
>       DBDmake.log - verbose log of the DBD-1.12-Oracle make 
> and installation
>       success.log - verbose log of a successful execution of bug.pl
>       failure.log - verbose log of a failed execution (with core dump)
>       Unfortunately I was unable to recompile everything to 
> convince gdb backtrace to produce any sane output. All I have 
> is number of hex pointers... Sorry.
> 
> The complicating factor is that I am not allowed to modify 
> the stored procedure code to ensure the cursor gets touched 
> every time. That would be the most obvious solution. The 
> reason for this is that the perl code we are executing is 
> used to performance test some 15 complex functions in a 
> package, so any modification would cause lengthy regression testing.
> 
> I have seen only one reference to this issue on the Net (and 
> that appears to have been unanswered). I would appreciate any 
> feedback from developers.
> 
>  <<bug.pl>>  <<bug.sql>>  <<failure.log>>  <<success.log>> 
> 
> 
> 
> Regards,
> 
> Srdjan Nikolic
> Senior Performance Analyst
> 
> Telstra Corporation           Phone:  03-9634-1715
> Infrastructure Services               Fax:    03-9634-1710
> Hosting & Internet                    Mobile: 04-1110-9334
> Test and Operational Deployment       e-mail: 
> [EMAIL PROTECTED]
> Operational Architecture
> Performance Testing Lab
> 

Attachment: bug.pl
Description: bug.pl

Attachment: bug.sql
Description: bug.sql

Attachment: failure.log
Description: failure.log

Attachment: success.log
Description: success.log

Reply via email to