DBD::Oracle test failure under DBI 1.49

2005-12-09 Thread Michael Gray
DBD::Oracle 1.16 fails a test for me when building under DBI 1.49. All was fine with the identical build under DBI 1.48. This is on SuSE Linux 9.3, 32-bit Athlon. In a nutshell: Can't bind a reference (DBI::st=HASH(0x82df350)) at t/50cursor.t line 91. A full transcript is attached, please

DBI:Oracle failure ORA-12154

2005-12-09 Thread Claude
I run locally a client script which fails with the following message: ORA-12154: TNS:could not resolve service name (DBD ERROR: OCIServerAttach) at ... DBI::connect('DBI','dbi:Oracle:abc','batman','secret','HASH(0x82d7910)') called at ... The datasource seems ok to me, and I checked from

Re: DBI:Oracle failure ORA-12154

2005-12-09 Thread Jeffrey Seger
Is $ORACLE_HOME set to the correct path? If the tnsnames.ora is not in $ORACLE_HOME/network/admin/, is $TNS_ADMIN set to the actual location of the file? On 09 Dec 2005 15:37:33 +0200, Claude [EMAIL PROTECTED] wrote: I run locally a client script which fails with the following message:

Re: problems using DBI:Proxy

2005-12-09 Thread Scott T. Hildreth
On Thu, 2005-12-08 at 14:25 +0200, Claude wrote: I have problems using DBI:Proxy / DBI:Proxyserver with an Oracle database. In fact, I am not sure that I start the proxy properly. I'd like to connect to a remote Oracle database (called 'abc') running on machine A (ip=1.2.3.4), port 1521.

RE: Oracle failure ORA-12154

2005-12-09 Thread Reidy, Ron
Can you connect to this database using SQL*Plus in the same manner? From the error docs: $ oerr ora 12154 12154, 0, TNS:could not resolve service name // *Cause: The service name specified is not defined correctly in the // TNSNAMES.ORA file. // *Action: Make the following checks and

Re: DBD::Oracle test failure under DBI 1.49

2005-12-09 Thread Tim Bunce
On Fri, Dec 09, 2005 at 11:45:44AM +, Michael Gray wrote: DBD::Oracle 1.16 fails a test for me when building under DBI 1.49. All was fine with the identical build under DBI 1.48. This is on SuSE Linux 9.3, 32-bit Athlon. In a nutshell: Can't bind a reference

Re: DBD::Oracle 2nd insert of row into table with 2 CLOBs hangs

2005-12-09 Thread Jared Still
On Tue, 2005-12-06 at 15:43 -0800, Joe Slagel wrote: Hi Tim Folks, We've found a interesting problem when inserting multiple rows into a table containing two CLOB columns. The second execute() hangs and Oracle never responds. The execute() hangs only when the character sizes of the two

RE: Oracle 10g and DBD::Oracle

2005-12-09 Thread Reidy, Ron
This does not look the same. Where are the bind variables? -Original Message- From: Peter Santos [mailto:[EMAIL PROTECTED] Sent: Friday, December 09, 2005 7:32 AM To: Reidy, Ron Cc: dbi-users@perl.org Subject: Re: Oracle 10g and DBD::Oracle No this issue is not repeatable in SqlPlus.

Re: Oracle 10g and DBD::Oracle

2005-12-09 Thread Peter Santos
No this issue is not repeatable in SqlPlus. Here is the test case for sqlplus. First I updated the table to include 3 records with distinct date_left columns. Just to make it easier to test. DATE_LEFT === 11/28/05 12:13 11/29/05 15:30 11/30/05 19:22 Then I setup my test script which I

DBI::Oracle questions

2005-12-09 Thread Daryl Pietrocarlo
I know you are probably swamped with dumb questions, I will try to be brief and to the point. Any help would be appreciated. 1. I would like to install a PRECOMPILED version of the DBD package for Windows? Does such a thing exist - I looked at Oracle and saw nothing. I read groups

Re: Oracle 10g and DBD::Oracle

2005-12-09 Thread Peter Santos
The bind variable is x.dt which will contain 3 different values for every iteration of the loop. I'll be more explicit.. Here is what I have in the database: --select to_char(date_left,'MMDD')dt from test_t1; 20051129 20051130 20051128 Now for the sql script... ---START-OF-SCRIPT--- var

DBI::db and invisibility

2005-12-09 Thread Ed Peschko
hey, I've been writing a DBD plugin for DBI, and was wondering why the DBI::db object that I've been creating doesn't show its contents either via Dumper or via 'x' in the database. Is this a consequence of how DBI is programmed? Would it be easy to change to remove this limitation? After