Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the DBD-Oracle CPAN distribution.

Report information
The Basics
Id: 66853
Status: resolved
Priority: 0/
Queue: DBD-Oracle
People
Owner: Nobody in particular
Requestors: peter.dermek [...] uptime.at
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 1.27
Fixed in: (no value)

History Show all quoted text
  Thu Mar 24 06:03:51 2011 peter.dermek [...] uptime.at - Ticket created
Subject: ORA-03124: two-task internal error (DBD ERROR: OCIStmtExecute)
Hi there, I have encountered the error ORA-03124: two-task internal error (DBD ERROR: OCIStmtExecute) when executing the below code using DBD::Oracle version 1.27. The query worked at the very first time, and failed on second time and onwards. Oracle server is 11.2g and client is also 11.2g. OS info: Linux 2.6.18-194.11.3.el5 # x86_64 x86_64 x86_64 GNU/Linux Perl info: v5.8.8 built for x86_64-linux-thread-multi use DBI; use Data::Dumper; $dbh = DBI->connect_cached( "DBI:Oracle:sid=mydbsid;host=mydbhost;port=1521;SERVER=POOLED", "crm", "crm"); $sth = $dbh->prepare("SELECT * FROM django_content_type WHERE id=?"); if ($sth->execute(1)) { $res = $sth->fetchall_arrayref; warn Dumper($res); } Note, that when SERVER=POOLED is removed it does work fine. Any idea as what went wrong or how to tweak to get it working? cheers, Peter
  Thu Mar 24 06:31:48 2011 bohica [...] ntlworld.com - Correspondence added
On Thu Mar 24 06:03:51 2011, peterd wrote: Show quoted text
> Hi there, > > I have encountered the error ORA-03124: two-task internal error (DBD > ERROR: OCIStmtExecute) when executing the below code using DBD::Oracle > version 1.27. The query worked at the very first time, and failed on > second time and onwards. Oracle server is 11.2g and client is also
11.2g. Show quoted text
> > OS info: Linux 2.6.18-194.11.3.el5 # x86_64 x86_64 x86_64 GNU/Linux > Perl info: v5.8.8 built for x86_64-linux-thread-multi > > use DBI; > use Data::Dumper; > > $dbh = DBI->connect_cached( > "DBI:Oracle:sid=mydbsid;host=mydbhost;port=1521;SERVER=POOLED", > "crm", "crm"); > > $sth = $dbh->prepare("SELECT * FROM django_content_type WHERE id=?"); > if ($sth->execute(1)) { > $res = $sth->fetchall_arrayref; > warn Dumper($res); > } > > Note, that when SERVER=POOLED is removed it does work fine. > > Any idea as what went wrong or how to tweak to get it working? > > > > cheers, > Peter
I've no real idea but a google on that error shows loads of people have hit it and in some cases it was a bug in Oracle or Oracle supplied code. I doubt it is DBD::Oracle issue and posts like the following from John (who maintains DBD::Oracle) suggest that also: http://cpanforum.com/posts/11341 Martin -- Martin J. Evans Wetherby, UK
  Thu Mar 24 06:31:50 2011 The RT System itself - Status changed from 'new' to 'open'
  Sun Jun 24 07:37:34 2012 bohica [...] ntlworld.com - Status changed from 'open' to 'resolved'