Illegal Stored Procedure Entry" message

--0-1812285848-1104274518=:69443 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, When I running a : dbexport DB-name I get allways a "Illegal Stored Procedure Entry" message without reference to Store Procedure. what can i do, for get a full dbexport database? --------------------------------- Do You Yahoo!? Yahoo! Net: La mejor conexi'n a internet y 25MB extra a tu correo por $100 al mes. --0-1812285848-1104274518=:69443 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit <DIV> <DIV>Hi,<BR><BR>When I running a :<BR><BR>dbexport DB-name<BR><BR>I get allways a "Illegal Stored Procedure Entry" message without reference to Store Procedure.<BR><BR>what can i do, for get a full dbexport database?<BR><BR></DIV></DIV><p><br><hr size=1><b>Do You Yahoo!?</b><br> <a href="http://net.yahoo.com.mx"><b>Yahoo! Net</b></a>: La mejor conexi'n a internet y 25MB extra a tu correo por <a href="http://net.yahoo.com.mx/">$100 al mes</a>.<br> --0-1812285848-1104274518=:69443-- sending to informix-list

Cesae Cruz wrote: PLEASE don't post MIME to this newsgroup. > > Hi, > > When I running a : > dbexport DB-name > I get allways a "Illegal Stored Procedure Entry" message without reference to Store Procedure. > what can i do, for get a full dbexport database? If you upgraded from a 7.xx engine to a 9.xx engine in place, there is a system delivered stored procedure which is replaced during the upgrade with a new one with a different interface but the same name. Due to changes in the system catalogues the old one would not work anymore. However, because the engine has to be able to revert back to 7.xx the old procedure is simply renamed to a name that is illegal. Looks like your dbexport is trying to export the procedure's definition to the schema file and recognizes that the name is invalid. The procedure is " oldsystdist" - note the leading space in the name. You can query sysprocedures to see if there is a records with that procname to determine if this is the problem. You can try using my dbexport/dbimport replacement utility, myexport, to perform the export. It uses my dbschema replacement utility, myschema, to create the schema and either Jonathan Leffler's sqlcmd utility or onpload to perform the actual data extracts. It's very fast with some nice enhancements to dbexport/dbimport. Once myexport completes you can edit the schema file and remove any unwanted procedures including any like ' systdist' that cannot be reloaded. Myexport and myimport are completely compatible with dbexport/dbimport so the export from one can be reloaded with the other. To use myexport you'll need three packages from the IIUG Software Repository: utils2_ak, myexport, and sqlcmd (most recent version is best). Art S. Kagel