Hi,
I've just spent a long time tracking down a bug in an Oracle procedure
because DBI's execute method returned success even though the procedure
raised an exception. Shouldn't exceptions raised in procedures cause
execute to fail?
Here is an example:
use DBI;
use strict;
use warnings;
begin proctest(?); end;
is the more desirable syntax for calling oracle procedures. It's an
anonymous pl/sql block. I personally had never seen the call proctest()
syntax used in Oracle. It's valid syntax, but it doesn't appear to be doing
what you want it to do.
According to the Oracle
If you can connect via ssh (not SSL, that's an additional layer inside
application protocols), you could use port forwarding.
For a basic setup, try running one of the following commands:
ssh [EMAIL PROTECTED] -L 1521:remote.machine:1521
ssh [EMAIL PROTECTED] -L 1521:127.0.0.1:1521
This will
I need to connect to an Oracle db on a remote machine, on the local network,
that only supports ssl connections. Is there a way to do this using
DBD::Oracle? Is there some other way to do this?
Any assistance appreciated.
Tim Hester
Not that I am offering you a solution, but with Oracle I have found the
error messages are sometimes misleading. For example I was helping a
co-worker with code. He wanted to call a stored procedure, so I sent
him some example code that I had which called a function. The function
I was
John Scoles wrote:
I sort if expected that for the exec it is usualy only used withing SP
perhaps
begin; exec(user.package.proctest(?)); end; ?? who knows
same problem as without exec:
PLS-00302: component 'PACKAGE' must be declared
The next error is usually a permission problem on the
John Scoles wrote:
That is an odd one, I will check with the DBAs here to see if this is
normal Oracle behavior
Well the error id correct but and on my box an error is thrown that I catch
I did change my code over to
begin track.proctest(?) end;
what version of DBI and DBD are you using??
Thanks Jared for the info.Kim
Jared Still wrote:
On Dec 5, 2007 8:02 PM, John Scoles [EMAIL PROTECTED] wrote:
DBI and DBD::Oracle 1.19 should be compatiable with any version of Oracle
going right back to 7. It is more a matter of which Oracle Client you
complile DBD::Oracle against.
I sort if expected that for the exec it is usualy only used withing SP
perhaps
begin; exec(user.package.proctest(?)); end; ?? who knows
The next error is usually a permission problem on the Oracle side.
Either the use who is calling the SP dose not have execute permission
for the package
Wow I go one right for once.
Not 100% sure on why that is? Me thinks when you use 'Begin End' it
forces OCI to take it as an pseudo 'stored procedure' and runs in the
current OCI client.
I think using call just executes as a thread off the present client and
in the background someplace??
That is an odd one, I will check with the DBAs here to see if this is
normal Oracle behavior
Well the error id correct but and on my box an error is thrown that I catch
I did change my code over to
begin track.proctest(?) end;
what version of DBI and DBD are you using??
cheers
Martin
John Scoles wrote:
Wow I go one right for once.
Not 100% sure on why that is? Me thinks when you use 'Begin End' it
forces OCI to take it as an pseudo 'stored procedure' and runs in the
current OCI client.
I think using call just executes as a thread off the present client and
in the
12 matches
Mail list logo
