Return-Path: Delivered-To: apmail-db-ddlutils-user-archive@www.apache.org Received: (qmail 56632 invoked from network); 13 Dec 2006 17:22:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Dec 2006 17:22:41 -0000 Received: (qmail 83965 invoked by uid 500); 13 Dec 2006 17:22:18 -0000 Delivered-To: apmail-db-ddlutils-user-archive@db.apache.org Received: (qmail 83570 invoked by uid 500); 13 Dec 2006 17:22:11 -0000 Mailing-List: contact ddlutils-user-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ddlutils-user@db.apache.org Delivered-To: mailing list ddlutils-user@db.apache.org Received: (qmail 82845 invoked by uid 99); 13 Dec 2006 17:22:05 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Dec 2006 09:22:01 -0800 X-ASF-Spam-Status: No, hits=2.8 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST,DNS_FROM_RFC_WHOIS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [66.163.178.159] (HELO web34410.mail.mud.yahoo.com) (66.163.178.159) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 13 Dec 2006 09:21:35 -0800 Received: (qmail 45292 invoked by uid 60001); 13 Dec 2006 17:20:27 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding; b=n+nTyIWXhgQzv8+DMho+CBdSirIaUJ9lnWxXbFWoeDb6YQCg+nX+jfxDfpfBbD1KlYhak/y64IGb3KvT8H9/7G46VFepB7wip0bJ10REB6wa5ueUNTfvybd53YFwxg8qQHmVQC1krnv12SWfOKK6Fs/rR8NOY7gb0ZrB05bkwxQ= ; Message-ID: <20061213172027.45290.qmail@web34410.mail.mud.yahoo.com> Received: from [82.122.218.150] by web34410.mail.mud.yahoo.com via HTTP; Wed, 13 Dec 2006 09:20:27 PST Date: Wed, 13 Dec 2006 09:20:27 -0800 (PST) From: Laurent ROCHE Subject: Re : Not much info with: "Could not parse or write data file" To: ddlutils-user@db.apache.org Cc: "Jean T. Anderson" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi,=0A=0AYes, the file does exist.=0AI should have said that I have managed= to make it work previously with a tiny version of the database, but as soo= n as I take the full db, the import fails. =0AAlso DB-unit manages to impor= t the data without failing.=0A=0AThere's no error message in derby.log, las= t line is:=0AChargeur de classe de la base de donn=E9es d=E9marr=E9 - derby= .database.classpath=3D''=0A(excuse my French ;-) ! )=0A=0AThe schema makes = sense in dblook, Cloudscape Workbench, Squirrel, ...=0A=0AI still need a wa= y to find out what the IMPORT error is !=0A=0A =0ACheers,=0AL@u=0AThe Compu= ting Froggy=0A=0A=0A----- Message d'origine ----=0ADe : Jean T. Anderson =0A=C0 : ddlutils-user@db.apache.org=0AEnvoy=E9 le : Mer= credi, 13 D=E9cembre 2006, 17h51mn 06s=0AObjet : Re: Not much info with: "C= ould not parse or write data file"=0A=0ALaurent ROCHE wrote:=0A> Hi,=0A> = =0A> I am exporting a database from PostgreSQL into Derby, using the ant ta= sks.=0A> =0A> The schema has been generated OK.=0A> So it seems, anyway: I = had the following messages:=0A> [ddlToDatabase] INFO: Executed 190 SQL comm= and(s) with 0 error(s)=0A> [ddlToDatabase] Written schema to database=0A> = =0A> But then the data import (I guess) fails with the following messages:= =0A> BUILD FAILED=0A> C:\apps\Ddlutils-test\build.xml:35: Could not parse o= r write data file C:\apps\Ddlutils-test\data.xml=0A=0ADoes that data.xml fi= le actually exist in C:\apps\Ddlutils-test\data.xml ?=0A=0A> It will be nic= e to get an line number where the import fails and also the SQL error (as = I suppose, it fails because of some SQL problems).=0A> Like this it makes i= t really hard to know what's going wrong ... particularly considering the d= ata are exported from an identical PG db (so there should be no problems).= =0A=0AIf a SQL error is involved, a message might have been written to the= =0ADerby log file. Assuming that you created the Derby database in=0AC:\app= s\Ddlutils-test, check C:\apps\Ddlutils-test\derby.log.=0A=0ADoes the Derby= schema "make sense"? After creating the schema in Derby=0Ayou can check i= t with this Derby command ('dbname' is the name of your=0Adatabase and this= assumes you're executing this command in=0AC:\apps\Ddlutils-test):=0A=0Aja= va org.apache.derby.tools.dblook -d jdbc:derby:dbname -o dbname.sql=0A=0ATh= ese database locations and urls assume you're using the embedded jdbc=0Adri= ver and that the database was created in C:\apps\Ddlutils-test.=0AOtherwise= you can give it the full path to the database [1]:=0A=0A jdbc:derby:C:/F= ull/Path/to/Databases/dbname=0A=0Athe URL would need to be tweaked for the = client jdbc driver.[2]=0A=0A -jean=0A=0A[1] http://wiki.apache.org/db-derby= /DatabaseNamesRelativeAbsolute=0A[2] http://db.apache.org/derby/docs/10.2/a= dminguide/cadminappsclient.html=0A=0A=0A=0A=0A=0A=0A=0A=09=0A=0A=09=0A=09= =09=0A_____________________________________________________________________= ______ =0AD=E9couvrez une nouvelle fa=E7on d'obtenir des r=E9ponses =E0 tou= tes vos questions ! =0AProfitez des connaissances, des opinions et des exp= =E9riences des internautes sur Yahoo! Questions/R=E9ponses =0Ahttp://fr.ans= wers.yahoo.com