How to start DBimport from the point of failure
Q: can dbimport be restarted from where it failed, or skip a failing statement? Answer: there's no built-in restart option. The suggested workaround is to drop/clean up the partially loaded last table, then edit the <dbname>.sql schema file in the .exp directory to delete everything up to the comment block preceding the CREATE TABLE for that table, and run the remainder with dbaccess (setting logging mode appropriately, e.g. no logging during load then back to unbuffered). The poster noted rerunning dbimport itself fails with "database already exists", and no further resolution is recorded.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Hi, Anyway to start DBimport from the point of failure in case it failed in the middle? Or Have any way to skip the failure & continue with the next line? rgd schillache
SCHIL ACHE wrote: > Hi, > > Anyway to start DBimport from the point of failure in case it failed in the > middle? Or Have any way to skip the failure & continue with the next line? No. -- Cheers, Obnoxio The Clown http://obotheclown.blogspot.com I will now proceed to pleasure myself with this fish. -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.
Hello,
just remove what's already done from your sql file, and execute the rest with
"dbaccess db db.sql"
You probably have to activate a logging mode first
Best regards,
Jacques Lapeire
-----Original Message-----
From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of SCHIL
ACHE
Sent: Thursday, February 04, 2010 8:44 AM
To: ids@iiug.org
Subject: How to start DBimport from the point of failure [18900]
Hi,
Anyway to start DBimport from the point of failure in case it failed in the
middle? Or Have any way to skip the failure & continue with the next line?
rgd
schillache
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
Check the last table you successfully imported. Remove the table 1 up to the table you successfully imported the data from the .exp/filename.sql.... change the logging mode to "No Logging" and rerun the import again. turn on the logging mode set to "U".
The only way would be to drop the partially loaded last table and edit the
<databasename>.sql schema file to remove everything above the comments that
precede the 'create table' statement for that table. Then you should be
able to run dbimport and it will start from whatever is at the top of the
schema file.
Art
Art S. Kagel
Advanced DataTools (www.advancedatatools.com)
IIUG Board of Directors (art@iiug.org)
See you at the 2010 IIUG Informix Conference
April 25-28, 2010
Overland Park (Kansas City), KS
www.iiug.org/conf
Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Advanced DataTools, the IIUG, nor any other
organization with which I am associated either explicitly, implicitly, or by
inference. Neither do those opinions reflect those of other individuals
affiliated with any entity with which I am affiliated nor those of the
entities themselves.
On Thu, Feb 4, 2010 at 2:43 AM, SCHIL ACHE <penfriend5@yahoo.co.uk> wrote:
> Hi,
>
> Anyway to start DBimport from the point of failure in case it failed in the
> middle? Or Have any way to skip the failure & continue with the next line?
>
> rgd
> schillache
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--000325556656b5b8b5047ec4b642
dbimport will fail with the error database already exists.