RE: Using dostats after upgrade to 9.2x in place

Hi Brian, Marco beat you to the answer by about five minutes. Thanks guys. Unfortunately, although this environment variable allows me to send this SQL statement to the engine, it returns "-389 No DBA permission.". But 'informix' is the database owner ??? Any pointers ? Andy Jarman -----Original Message----- From: Brian Wilkins [mailto:brianw@informix.com] Sent: 22 September 2000 15:51 To: Jarman, Andy Cc: informix-list@iiug.org; 'kagel@bloomberg.net' Subject: Re: Using dostats after upgrade to 9.2x in place Hi Andy, Long time no hear. If there is a leading space you can have the environment variable DELIMIDENT=1, then put double quotes round the procedure name. Brian W. "Jarman, Andy" wrote: > Art, > > Any ideas on how to delete this redundant SP? It seems to have a leading > space. > Makes it somewhat difficult to delete through the normal syntax (DROP > PROCEDURE...) > > Andy Jarman > > -----Original Message----- > From: Art S. Kagel [mailto:kagel@bloomberg.net] > Sent: 21 September 2000 16:15 > To: informix-list@iiug.org > Subject: Using dostats after upgrade to 9.2x in place > > NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE > > Note that if you upgrade an existing 7.xx server to 9.2x in place the DBA > stored procedure systdist will be renamed oldsystdist and a new version > installed. There are objects referenced in oldsystdist that have changed > sufficiently to prevent it from re-optimizing/compiling which will cause > dostats to report the error and exit without updating stats for other > stored procedures in that database. This procedure exists in each and > every database. The fix is to DROP PROCEDURE oldsystdist; in each database. > > Art S. Kagel