Re: dbimport failed - IDS 9.30 UC3
On Mon, 06 Oct 2003 03:39:12 -0400, Hari Gupta wrote:
This may not be a dbexport/dbimport problem but an engine problem. Check the
trigger text in systrigbody and see if the stored procedure call there is
missing the NULL's for the second and third arguments to procedure
sp_stop_clock. There have been other problems with the engine mucking with
trigger text before saving it (the last was a tendency to add so many layers of
redundant parenthesis that the trigger text output by dbschema or dbexport
could not be executed to recreate the trigger without editing it). This may be
something similar. However, if the trigger text looks OK in systrigbody you
can use my dbschema replacement utility with its -l option to output a dbimport
compatible schema file which you can use to import the database, in general, or
just edit the schema and add the missing args manually.
Myschema is included in the package utils2_ak available from the IIUG Software
Repository.
Art S. Kagel
> Hi,
>
> I have recently installed IDS 9.30 UC3 on Linux 7.3. Done a dbexport with -ss
> and started dbimport with -d <dbspace-name>. After about 5 hrs, dbimport
> failed with following error:
>
> ------------------------------------
> *** prepare sqlobj
> 201 - A syntax error has occurred.
> ------------------------------------
>
> The statement just above where dbimport failed was a "create trigger" as
> below:
>
> ------------------------------------------------------------------- create
> trigger "auth".trg_altask_del delete on "auth".aualtask
> referencing old as old
> for each row
> (
> execute procedure "auth".sp_stop_clock('D' , , ,old.doc_typ
> ,old.doc_yer ,old.doc_num ,old.doc_prt ,old.wrk_typ ,old.seq_num , , ,
> ,old.mdu_ref ));
>
> *** prepare sqlobj
> 201 - A syntax error has occurred.
> -------------------------------------------------------------------
>
> Pl. note that after this create statement, all statement were update stats. So
> what I did, created trigger seperately and ran update stats based upon
> dbexport SQL file using dbaccess.
>
> I did read few archives about this error but none of them reported above error
> followed by 201 error.
>
> There was an issues similar to this with dbimport in earlier verson of IDS but
> I don't think it will be still an known bug with IDS 9.30 UC3.
>
> Can some guru help me about this please ?
>
> Pl. let me know if onconfig or some other info. is needed.
>
> TIA
>
> Hari