If you are getting

" DBD::Oracle::st execute failed: ORA-01008: not all variables bound (DBD ERROR: OCIStmtExecute) " errors on 10

it is a know a bug in Oracle.

http://forums.oracle.com/forums/thread.jspa?messageID=1668176


----- Original Message ----- From: "Kai Schwermann" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, April 03, 2007 1:31 PM
Subject: DBD::Oracle crashes non-deterministic


Hi Folks,

we have strange behaviour on several of our programs written with perl
5.6.1,DBI 1.35 and Oracle DBD::1.14 on Linux.

I know it's old, but we can't update it easily yet.

The Oracle Client is 9i and 9i R2, Databases are having trouble beginning
with the latest 9er Releases and 10.2.

Our Perl-Module crashes completely on undeterministic parts of the
software and sometimes immediately, sometimes even NOT. (Same Data, of
course)

The modules usually have large queries and few updates/inserts into
different tables, it makes no difference if the statements are prepared or
not.

One difference we have found is that if we are targetting a 9i R2 Database
it happens only if more than ONE Connection from the same user is working
on the database, on 10.2 it seems to happen everytime.

The latest time it happened was when a customers database was moved to a
different machine, but stayed on the 9i Rx release. Unfortunately the
database guys "did not change anything",
so i have no clue until now what is different.
At least on this installation it happens only when more than one process
is working on the database.

Does anyone have a clue on whats happening? It seems to be that something
client/session-dependent changes from 9i to 9i Rx / 10.x, but until now
nothing helped, updating the client to latest
9iR2, latest DBI and latest DBD did not help.

Switching to perl 5.8 is no option for the customers until now...

Hope you can help us

Bye for now
Kai
--
Kai Schwermann, Geschäftsführer
bill-X GmbH
Möserstr. 34          49074 Osnabrück, Germany
Tel. +49-541-71008-0   Fax +49-541-71008-499
http://www.bill-X.de    [EMAIL PROTECTED]
____________________________________________________________________________

Reply via email to