Oninit cdi / Archive
Talk to an expert →

Re: DBEXPORT failed with *** prepare unldobj & 201 - A syntax error

Posted in 2005

Topics: Storage & Space Management, Connectivity: ESQL/C, 4GL & Embedded SQL, Security, Permissions & Auditing, Migration, Import/Export & Data Conversion, Platform-Specific Issues, Versions, Editions & End-of-Life

Fnu Gaurav — — source: Usenet: comp.databases.informix

--0__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A Content-type: multipart/alternative; Boundary="1__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A" --1__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: quoted-printable Hi, 9.40.UC7 on Solaris create database checkdb; create table tab1(case int); create table tab2(ref int); I did a dbexport, dropped the database and did dbimport. No problems. I= do not believe that such problem can be platform specific so it would be f= are to say that the problem has been fixed in latest version. Thanks and Regards, Gaurav = Ben Thompson = <ben@nomonitorsof = tspam.com> = To Sent by: informix-list@iiug.org = owner-informix-li = cc st@iiug.org = Subj= ect Re: DBEXPORT failed with *** = 01/04/2005 06:18 prepare unldobj & 201 - A syntax= AM error = = = Please respond to = Ben Thompson = = = Hari Gupta wrote: > -------------------------------------------- > A VERY HAPPY NEW YEAR - 2005 TO ALL OF YOU > -------------------------------------------- > > IDS 9.40.UC3 > RHL 7.3 > > dbexport is failing over with following error: > > -----------------------------------------------------------------------= -------- > { TABLE "auth".syscolformats row size =3D 875 number of columns =3D 1= 6 index size =3D > 204 } > { unload file name =3D sysco00773.unl number of rows =3D 0 } > > create table "auth".syscolformats > ( > owner char(32), > tabname char(32), > colname char(32), > extowner char(32), > priority smallint, > typeface char(64), > fontsize smallint, > fontstyle smallint, > fontcolor integer, > aidfa char(30), > formatmask char(256), > format4gl char(128), > align char(1), > case char(1), > ruletype char(1), > checktext char(256) > ) extent size 16 next size 16 lock mode row; > revoke all on "auth".syscolformats from "public";> > *** prepare unldobj > 201 - A syntax error has occurred. > -----------------------------------------------------------------------= ------- > > dbexport by: > > dbexport -d <database name> -ss> > - There is no row in this table (syscolformats). > - Last night onchecks did not report any thing unusual. > > Question: > > 1. Root cause of this error and can it be prevented ? I have reproduced your problem by creating a test database and creating= this table in it. The problem is because you have a column called 'case= ' which appears to be a reserved word. There is a bug in dbexport where i= f there is a column name that is a reserved word it will fail like this. = A favourite of mine is 'ref' - if you have a column of this name it will fail as well. I don't think I have raised this bug with technical support as I can work around it (see below) but if anyone is listening and would like to= fix it, then it's easy to reproduce and I would be grateful. > 2. Is it safe to drop this system table ? Is this a system table? I know its name starts with 'sys' but it doesn'= t exist in any database I have. Can anyone else verify this? > 3. If yes, should it be dropped first and continue dbexport; recreate= it after > dbexport is over ? > OR > Drop and recreate the table and then start dbexport ? Rename the column case to case1 as follows, provided you are sure this is NOT a system table - do not take my word for it: rename column syscolformats.case to case1; Do the dbexport. Rename it back using a similar SQL statement: rename column syscolformats.case1 to case; Edit the dbexport unload file and change the column name back to what i= t was. Dbimport has no problems with reserved words. Ben. = --1__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A Content-type: text/html; charset=US-ASCII Content-Disposition: inline Content-transfer-encoding: quoted-printable <html><body> <p>Hi,<br> <br> 9.40.UC7 on Solaris<br> <br> create database checkdb;<br> create table tab1(case int);<br> create table tab2(ref int);<br><br> I did a dbexport, dropped the database and did dbimport. No problems. I= do not believe that such problem can be platform specific so it would = be fare to say that the problem has been fixed in latest version.<br> <br> Thanks and Regards,<br> Gaurav<br> <img src=3D"cid:10__=3D09BBE512DFF2022A8f9e8a93df938@us.ibm.com" width=3D= "16" height=3D"16" alt=3D"Inactive hide details for Ben Thompson &lt;be= n@nomonitorsoftspam.com&gt;">Ben Thompson &lt;ben@nomonitorsoftspam.com= &gt;<br> <br> <br> <table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">= <tr valign=3D"top"><td style=3D"background-image:url(cid:20__=3D09BBE51= 2DFF2022A8f9e8a93df938@us.ibm.com); background-repeat: no-repeat; " wid= th=3D"40%"> <ul> <ul> <ul> <ul><b><font size=3D"2">Ben Thompson &lt;ben@nomonitorsoftspam.com&gt;<= /font></b><font size=3D"2"> </font><br> <font size=3D"2">Sent by: owner-informix-list@iiug.org</font> <p><font size=3D"2">01/04/2005 06:18 AM</font> <table border=3D"1"> <tr valign=3D"top"><td width=3D"168" bgcolor=3D"#FFFFFF"><div align=3D"= center"><font size=3D"2">Please respond to<br> Ben Thompson</font></div></td></tr> </table> </ul> </ul> </ul> </ul> </td><td width=3D"60%"> <table width=3D"100%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">= <tr valign=3D"top"><td width=3D"1%" valign=3D"middle"><img src=3D"cid:3= 0__=3D09BBE512DFF2022A8f9e8a93df938@us.ibm.com" border=3D"0" height=3D"= 1" width=3D"58"

↪ replying to Fnu Gaurav
Ben Thompson — — source: Usenet: comp.databases.informix

Fnu Gaurav wrote: > --0__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A > Content-type: multipart/alternative; > Boundary="1__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A" > > --1__=09BBE512DFF2022A8f9e8a93df938690918c09BBE512DFF2022A > Content-type: text/plain; charset=US-ASCII > Content-transfer-encoding: quoted-printable > > > > > > > Hi, > > 9.40.UC7 on Solaris > > create database checkdb; > create table tab1(case int); > create table tab2(ref int);> > I did a dbexport, dropped the database and did dbimport. No problems. I= > do > not believe that such problem can be platform specific so it would be f= > are > to say that the problem has been fixed in latest version. Well that's good news. I did not know UC7 was out. How do others find out when a new release is out? I tested on SuSE 9.0 running IDS 9.40.UC5. Ben.

Glossary