pg.ddx.ioUniversity INGRES on Usenet (1985-1995): threads about Berkeley INGRES, QUEL and EQUEL from comp.databases.ingres, comp.databases and net.database
From: mack@ips.cs.tu-bs.de
Subject: Re: iiud.scr problem
Date: 1995/11/21
Message-ID: <DIEHJG.1MG@ips.cs.tu-bs.de> (raw)
References: <Pine.SOL.3.91.951116003148.4299A-100000@iglou>
In article <Pine.SOL.3.91.951116003148.4299A-100000@iglou>,
Lucky Leavell <ris@iglou.com> wrote:
>I am attempting to unload a 6.4/04 database and reload it into an
>OpenIngres 1.1 database. I ran unloaddb -c <dbname> and executed the
>unload.ing script. Before executing the reload.ing script on the OI
...
>bombs on the following dummy column def in the copy command:
>
> dummy1= "d0\\",
>
>with an E_US16C7 COPY: Column 'dummy1', bad delimiter'\\'.
>error. (The same dummy column exists in the 6.4 version of iiud64.scr also.
>
Yes, we had the same problem here - actually, I was never able
to create a backslash delimiter on OI 1.1, so I changed the
copy statement in iiud64.scr to:
...
\quel
copy iiud_64temp (
drop= d1,
sp= d1,
table_name= char(0),
dummy1= "d0;",
nl= d1
)
into "ii_copy.tmp"
\go
/* If no rows copied, error. */
...
This got rid of the necessity to copy backslashes into ii_copy.tmp
and it worked for us. But CA support told us some different work
around - I do not remember, as we reached them _after_ we had
successfully copied the databases.
This was on SunOS 4.1.3...
Thomas Mack
TU Braunschweig, Abt. Datenbanken