DBI Proxy + transactions

2011-10-05 Thread Borissov Pavel
Hi! Tell me, please, how can I use db transactions ( $dbh-begin_work() ... $dbh-commit() ) with DBI Proxy ? -- With regards, Borissov Pavel

RE: DBI Proxy + transactions

2011-10-05 Thread John Scoles
I would hope it would depend on which type of DB you are trying to proxy to. If the DB at the other end of the proxy does not support 'begin_work' and 'commit' or 'transactions' then DBI Proxy will not magically enable it. What flavour of DB is behind the proxy?? I have never used it for

DBD::ODBC fails, SQL*Plus works

2011-10-05 Thread Scott Stansbury
Folks, I could use a tip or lead with the following issue: I have a Windows Server 2008 R2 box with Oracle Instant Client 11.2, with the SQL*Plus and ODBC modules installed. No other Oracle software is installed. I am connecting to an Oracle 10g instance. The following SQL*Plus works:

Re: :ODBC fails, SQL*Plus works

2011-10-05 Thread Scott Stansbury
I'm sorry - that was just fat fingers on the cut/paste... In actuality it is $oracle_host = 192.168.15.200:1535 On Oct 5, 2011, at 12:13 PM, Nelson, Erick [HDS] wrote: Your $oracle_host Perl var looks like it has more that just the host ip address and port in it. What is the 10.128 ?

Re: :ODBC fails, SQL*Plus works

2011-10-05 Thread tiger peng
You passed the full description to SQL*Plus. Try to assign it to your $dsnorCheck where is the tnsnames.ora (and sqlnet.ora)?  what is the valuess for env varialbles ORACLE_HOME and TNS_ADMIN Why use ODBC driver instead of Oracle? From: Scott Stansbury

Re: :ODBC fails, SQL*Plus works

2011-10-05 Thread Scott Stansbury
On Oct 5, 2011, at 1:00 PM, Kong, Alan wrote: Since you are using DBI::ODBC, you should create an ODBC data source pointing to your Oracle database first, and then calling the connect function by passing the data source name you just created for ODBC data source. That's our standard config,

Re: DBD::ODBC fails, SQL*Plus works

2011-10-05 Thread Bruce Johnson
On Oct 5, 2011, at 9:09 AM, Scott Stansbury wrote: It returns (after a few seconds) with an ORA-12154 error: TNS:could not resolve the connect identifier specified ( SQL-08004). Basic questions: the script is running in an environment where the env variables $ORACLE_HOME and $TNS_ADMIN

Re: :ODBC fails, SQL*Plus works

2011-10-05 Thread Scott Stansbury
On Oct 5, 2011, at 1:47 PM, Kong, Alan wrote: It is different than typing the whole connection description in the command prompt as it will bypass tnsnames.ora entry. ODBC is looking for the tnsnames.ora entry for connection description, so using the above connection method, I bet it will

Re: DBD::ODBC fails, SQL*Plus works

2011-10-05 Thread Scott Stansbury
On Oct 5, 2011, at 1:53 PM, Bruce Johnson wrote: Basic questions: the script is running in an environment where the env variables $ORACLE_HOME and $TNS_ADMIN are available? Your tnsnames.ora file is present and correct? I did have the env variables configured, and the tnsnames.ora is now

Re: :ODBC fails, SQL*Plus works

2011-10-05 Thread Bill Ward
Am I the only one amused by the fact that in a thread about Oracle we have a thread with writers Scott and Tiger? On Wed, Oct 5, 2011 at 9:41 AM, tiger peng tigerpeng2...@yahoo.com wrote: You passed the full description to SQL*Plus. Try to assign it to your $dsnorCheck where is the

RE: DBD::ODBC fails, SQL*Plus works

2011-10-05 Thread John Scoles
Why even use DBD::ODBC? Why not use DBD::Oracle? Cheers John Subject: Re: DBD::ODBC fails, SQL*Plus works From: john...@pharmacy.arizona.edu Date: Wed, 5 Oct 2011 10:53:48 -0700 CC: dbi-users@perl.org On Oct 5, 2011, at 9:09 AM, Scott Stansbury wrote: It returns (after a