RE: sanity check...

From: Sonja Sehovic <sonja.sehovic_at_pbz.hr>
Date: Thu, 5 May 2005 13:46:05 +0200
Message-ID: <B3772712305A314CAB52855AF8F2739613BAA1EB@ksdcexc01.sit.pbz.hr>

This is how we gather statistics on some of the schemas (9.2.0.6):

DBMS_STATS.GATHER_SCHEMA_STATS('SCHEMA_NAME',NULL,FALSE,'FOR ALL INDEXED = COLUMNS SIZE 1',4,'DEFAULT',TRUE,NULL,NULL,'GATHER'); HTH,
Sonja

-----Original Message-----
From: oracle-l-bounce_at_freelists.org =
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of zhu chao Sent: Thursday, May 05, 2005 1:41 PM
To: shrekdba_at_gmail.com
Cc: oracle-l
Subject: Re: sanity check...

You can export the statistics and import back after you import the = actual d=3D
ata.
While doing import, the ANALYZE=3D3DY should also do the analyze.

On 5/5/05, bill thater <shrekdba_at_gmail.com> wrote:
> solaris 9
> 9.2.0.6

>=3D20

> OK i have several development databases here. the production ones are
> someplece else and they're not my concern yet. a lot of the
> evelopment here consists of truncating and reloading tables in a
> couple of schemas on the databases, adding data, importing data. most
> of the schemas are static. this leads to developers showing up at my
> cube and <whiney voice> "bill, the database is slow again.</whiney
> voice>. most of this can be fixed by just gathering stats on those
> schemas.

>=3D20

> so what i'm looking for is pointers to TFM, white papers, best
> pratices, your favorite method of gathering stats on just those
> schemas so i can write a script to be chroned to run against them.

>=3D20

> thanks.

>=3D20

> --=3D3D20
> --
> Bill "Shrek" Thater ORACLE DBA =3D3D20
> shrekdba_at_gmail.com=3D3D20
> =

---

> om mani padme hum
> --
> http://www.freelists.org/webpage/oracle-l
>=3D20

--=3D20
Regards
Zhu Chao
www.cnoug.org

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l

Received on Thu May 05 2005 - 07:52:31 CDT