Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: oracledump.pl works on Oracle 8i, fails on Oracle 7.3.4

Re: oracledump.pl works on Oracle 8i, fails on Oracle 7.3.4

From: Ron Reidy <rereidy_at_indra.com>
Date: Sat, 04 Jan 2003 06:16:52 -0700
Message-ID: <3E16DEC4.9080905@indra.com>


P. Bianchi wrote:
> Trying to mirror Oracle data onto Mysql, using oracledump.pl perl script
> (great utility, a big thanks! to the author).
>
> Oracledump succeeds in dumping tables from a O8i database (residing on the
> same linuxbox).
>
> It fails in dumping tables from a 7.3.4 production database (placed on a
> different unix server) with the following output:
>
> ============================
> Checking table structure for table TBLCONFREPARTI
> Fetching keys for table TBLCONFREPARTI
> Fetching indexes for table TBLCONFREPARTI
> Printing CREATE TABLE statement for table TBLCONFREPARTI
>
> CREATE TABLE TBLCONFREPARTI (, PRIMARY KEY (STRIDREPARTO,BYTVERSIONE) );
> Preparing SELECT statement to fetch data from table TBLCONFREPARTI
>
> Can't call method "execute" on an undefined value at ./oracledump.pl line
> 274.
> =============================
>
> Linux RH7.3, Kernel 2.4.18.10, Perl 5.6.1, DBI unknown, DBD-Oracle 1.12,
> Oracledump "may 2001", Oracle 7.3.4 on an IBM AIX server.
>
> Any hint why the script oracledump, after having accessed and read the
> source database over the network, fails to write down the output?
>
> TIA
> P. Bianchi
>
>
>
>
>
>
>

Well, I've never heard of this script, but I do know the error message indicates the statement handle used to fetch data from the table was not opened correctly (there is probably no error handling in the code at this point).

Also, looking at the output you posted, the 'CREATE TABLE' statement looks suspect (actually wrong).

Some things to look at:

  1. the output of 'perl -V' at the command line.
  2. The #! line in the begining of the script compared to the output in #1.
  3. Look at using the perl debugger to step through the code and find out what is going on.
  4. Contact the author and see what is going on.
Received on Sat Jan 04 2003 - 07:16:52 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US