Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Statspack consolidation

RE: Statspack consolidation

From: Post, Ethan <Ethan.Post_at_ps.net>
Date: Fri, 29 Apr 2005 15:17:35 -0500
Message-ID: <E5D2567DDF0D03428A15664A78CA473C489174@pscdalpexch02.perotsystems.net>


OK, maybe I missed this but why are they doing this? What expected gains/reporting ability/monitoring ability etc...do they need to achieve by doing this? Or is this another way we DBA's find to waste time (I am guilty of this also), let's face it we love to tinker.

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Tim Gorman Sent: Friday, April 29, 2005 3:09 PM
To: Oracle-L
Subject: FW: Statspack consolidation

Table compression can only help if you are using "direct-path" inserts. The
standard STATSPACK package does "conventional" (i.e. not direct-path) inserts, as does the IMP utility, so data loaded from either would not compress.

Table compression would only help if one was transferring data using INSERT
/*+ APPEND */ selecting from a database link or loading data using SQLLDR
DIRECT=3DTRUE.

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Apr 29 2005 - 16:22:32 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US