Re: FW: FW: Explain (more is better?)

Yup, exported the other day, recalculated extent sizes based on current table size and expected growth, dumped the DB's and imported again. Thats where we ran into the problem with a field called 'user' brett Obnoxio The Clown wrote: > > In the year of Our Lord Tue, 12 Dec 2000 10:02:36 +0200, "Dirk Moolman" > <dirkm@reach.co.za> broke a vow of silence to utter: > > >If we do, everyone else also missed it. We have a case (related to > >performance) open with Tech Support now for about 4 months. We've looked at > >HP patches, configuration changes, kernel parameters - the works ....... > > Mmmmm....well, I've run plenty of different OLTP systems on HP using OPTCOMPIND > 0, and never had a problem. > > Have you guys ever done a full dbexport/initialise/dbimport? > > >-----Original Message----- > >From: owner-informix-list@iiug.iiug.org > > > >In the year of Our Lord Mon, 11 Dec 2000 10:22:04 +0200, "Dirk Moolman" > ><dirkm@reach.co.za> broke a vow of silence to utter: > > > >> > >>OPTCOMPIND = 0 proved to be VERY bad on our system, and we run OLTP. We > >>made some onconfig changes, but after changing OPTCOMPIND to 2, we had a > >>very drastic improvement in speed. > > > >Oh? Sounds like you might be missing something... > > > >>-----Original Message----- > >>From: owner-informix-list@iiug.iiug.org > >>[mailto:owner-informix-list@iiug.iiug.org]On Behalf Of David Williams > >>Sent: Monday, December 11, 2000 3:59 AM > >>To: informix-list@iiug.org > >>Subject: Re: Explain (more is better?) > >> > >> > >>In article <fApY5.29470$eT4.2358818@nnrp3.clara.net>, John Berry > >><johnberry@clara.net> writes > >>>We have a large number of tables > 700 with a large majority in the > >range > >>>of > 1GB > >>> > >>>Some of the queries on the database can take a number of minutes > >especially > >>>when > >>>multiple joins are being performed. > >>> > >>>Now I have always assumed the lower the cost of query the better :-) > >>> > >>>However I am starting to doubt this when I run a low cost query on a > >>number > >>>of frequent hit tables it can take upto 2 mins to return data > >>>If I re-structure the query the cost goes up to 2500 but data is returned > >>in > >>>seconds ? > >>> > >> > >> Run you run the full update statistics? Perhaps the stat are out of > >> date. > >> > >>>Would I be right in assuming the cost is based on use of indexes and > >amount > >>>of data retrieved and not a lot else so a high cost query is not always > >>bad. > >>> > >>>and if so what about OPTCONF hmm 0,1 or 2 > >>> > >> > >> OPTCOMPIND = 0 favors indexes and should be used on OLTP systems. > >> > >>>:-) > >>> > >>> > >> > >>-- > >>David Williams > >> > > -- ----------------------------------------------------------------- Brett's 10th law of UNIX administration... rm is forever ----------------------------------------------------------------- Brett Geer - UNIX Admin/Analyst/Programmer - Intratex Holdings. Tel. +27 31 717 4000 Direct. +27 31 717 4146 Fax. +27 31 717 4001 ----------------------------------------------------------------- The little voices are talking to me again, telling me to reach for a keyboard and type rm -rf /* last week they had me rm -rf `echo $MANPATH | sed 's/:/ /g'` now I fear I have no answers -----------------------------------------------------------------

Brett Geer wrote: > > Yup, exported the other day, recalculated extent sizes based on > current table size and expected growth, dumped the DB's and imported > again. > > Thats where we ran into the problem with a field called 'user' > > brett dbexport/dbimport seem to be horribly broken. We've had all sorts of problems trying to dbimport something that was dbexported: Stored procedures with literal ? characters, e.g ... if some_var = '?' then ... break it, as do other things which I can't remember. dbaccess can import the same commands correctly... Chris -- ************************************************************** Chris Hall Email: Chris.Hall@OrbisUK.com Orbis Tel: +44 208 742 1600 http://www.OrbisUK.com Fax: +44 208 742 2649

Try my dbexport/dbimport replacement utilities. Myimport is compatible with dbexport output and dbimport is compatible with myexport output. You will need three free packages from the IIUG Software Repository: myexport utils2_ak sqlcmd Myexport/myimport is fully compatible with dbexport/dbimport for disk based export/import and provides several nice additional features including large file support. Art S. Kagel Chris Hall wrote: > > Brett Geer wrote: > > > > Yup, exported the other day, recalculated extent sizes based on > > current table size and expected growth, dumped the DB's and imported > > again. > > > > Thats where we ran into the problem with a field called 'user' > > > > brett > > dbexport/dbimport seem to be horribly broken. We've had all sorts of > problems trying to dbimport something that was dbexported: > > Stored procedures with literal ? characters, e.g > > ... > if some_var = '?' then > ... > > break it, as do other things which I can't remember. > > dbaccess can import the same commands correctly... > > Chris > -- > ************************************************************** > Chris Hall Email: Chris.Hall@OrbisUK.com > Orbis Tel: +44 208 742 1600 > http://www.OrbisUK.com Fax: +44 208 742 2649

Where do I get these packages ?? Thanks -- Paulo Roberto Marelli de Amorim TS&0 Consulting Brasil In article <3A3FB51D.54F3D64C@bloomberg.net>, kagel@bloomberg.net wrote: > Try my dbexport/dbimport replacement utilities. Myimport is compatible with > dbexport output and dbimport is compatible with myexport output. You will > need three free packages from the IIUG Software Repository: > > myexport > utils2_ak > sqlcmd > > Myexport/myimport is fully compatible with dbexport/dbimport for disk based > export/import and provides several nice additional features including large > file support. > > Art S. Kagel > > Chris Hall wrote: > > > > Brett Geer wrote: > > > > > > Yup, exported the other day, recalculated extent sizes based on > > > current table size and expected growth, dumped the DB's and imported > > > again. > > > > > > Thats where we ran into the problem with a field called 'user' > > > > > > brett > > > > dbexport/dbimport seem to be horribly broken. We've had all sorts of > > problems trying to dbimport something that was dbexported: > > > > Stored procedures with literal ? characters, e.g > > > > ... > > if some_var = '?' then > > ... > > > > break it, as do other things which I can't remember. > > > > dbaccess can import the same commands correctly... > > > > Chris > > -- > > ************************************************************** > > Chris Hall Email: Chris.Hall@OrbisUK.com > > Orbis Tel: +44 208 742 1600 > > http://www.OrbisUK.com Fax: +44 208 742 2649 > Sent via Deja.com http://www.deja.com/

Paulo Amorim wrote: > > Where do I get these packages ?? Go to the International Informix Users Group WEB Site: www.iiug.org select SOFTWARE from the top menu, select Index from the text, then Full Index, then use the alphabet tabs to get myexport from the 'M' section, sqlcmd57 or later from the 'S' section, and utils2_ak from the 'U' section. All files should be Shell Archives and the utils2_ak contains an ar archive (System V format) containing the source for myschema which myexport uses. If your ar utility is not compatible (AIX's is still BSD format) you can get GNU ar source from any GNU site or my own ar2 package which is also in the IIUG Repository and use either to extract the archive (myschema.source.ar). Art S. Kagel > Thanks > -- > Paulo Roberto Marelli de Amorim > TS&0 Consulting > Brasil > > In article <3A3FB51D.54F3D64C@bloomberg.net>, > kagel@bloomberg.net wrote: > > Try my dbexport/dbimport replacement utilities. Myimport is > compatible with > > dbexport output and dbimport is compatible with myexport output. You > will > > need three free packages from the IIUG Software Repository: > > > > myexport > > utils2_ak > > sqlcmd > > > > Myexport/myimport is fully compatible with dbexport/dbimport for disk > based > > export/import and provides several nice additional features including > large > > file support. > > > > Art S. Kagel > > > > Chris Hall wrote: > > > > > > Brett Geer wrote: > > > > > > > > Yup, exported the other day, recalculated extent sizes based on > > > > current table size and expected growth, dumped the DB's and > imported > > > > again. > > > > > > > > Thats where we ran into the problem with a field called 'user' > > > > > > > > brett > > > > > > dbexport/dbimport seem to be horribly broken. We've had all sorts of > > > problems trying to dbimport something that was dbexported: > > > > > > Stored procedures with literal ? characters, e.g > > > > > > ... > > > if some_var = '?' then > > > ... > > > > > > break it, as do other things which I can't remember. > > > > > > dbaccess can import the same commands correctly... > > > > > > Chris > > > -- > > > ************************************************************** > > > Chris Hall Email: Chris.Hall@OrbisUK.com > > > Orbis Tel: +44 208 742 1600 > > > http://www.OrbisUK.com Fax: +44 208 742 2649 > > > > Sent via Deja.com > http://www.deja.com/