EAR4 - Gathering Statistics, unusable indexes and more

Hi,
Some feedback on statistics:
1. When choosing a table -> Statistics -> gather Statistics, the minimum is to have a CASCADE option (so all the indexes will be analyzed too). I think it should be the deafult! This way there is a chance that the developers will have good statistics...
As a bonus, an advanced tab with the rest of the options might be nice, when you have time.
2. When choosing to gather statistics on an index, you should you dbms_stats and not ALTER INDEX... COMPUTE STATISTICS which is a deprecated syntax.
And about indexes:
1. When looking at the index tab of a table, unusable indexes should be visibly different - maybe just color the status column. Well, any color-coding can help to gain more infomation very fast (index types and index status). Well, I guess the same goes for disabled triggers, disabled constraints etc...
2. When right-clicking an index in an index tab of a table, the only option is export, which makes no sense. Could you replace it with the six relevant index options, just like when we right click an index in the side bar (drop, rebuild, rename, make unusable...)
Well, same goes for the triggers tab of a table - when right-clicking a trigger give us the trigger actions(enable/disable, drop...), not export.
my two cents,
Ofir

When Choose a partitioned table from the tables list (tree view on the left), I have many tabs with details (Columns, data, indexes,etc).
1. The last tab, SQL, doesn't generate any CREATE TABLE sql at all for the simple partition table I created (10g Release 2 on windows 2000, raptor 4.1, a table with a single partition).
2. There is no way to see the partitions definitions - for example, the list of partitions and their ranges (or list values). I would like to have another tab for partitioned table with that information (from all_tab_partitions). Also, how can I easily see the type of partitioning and the partition key of the table?
3. Also in the builtin reports, there is no way to get that data. The only report about partitioned tables that I see is Table -> Organization -> Partitioned -> Partitioned Tables, that only provide owner, table_name, maybe tablespace and logging (blank in my case).. I think:
a. You should rewrite the report to use dba/all_part_tables - with columns like partitioning_type, subpartitioning_type, partition_count etc.
b. add a report about the partition key columns per partitioned table from dba_part_key_columns.
4. When adding an index to a partitioned table, I can't choose local/global index. The index is always created as a global index. For example, can't create bitmap index on partitioned tables because they must be local.
Ofir

Similar Messages

Gathering statistics on partitioned and non-partitioned tables

Hi all,
My DB is 11.1
I find that gathering statistics on partitioned tables are really slow.
TABLE_NAME                       NUM_ROWS     BLOCKS SAMPLE_SIZE LAST_ANALYZED PARTITIONED COMPRESSION
O_FCT_BP1                        112123170     843140    11212317 8/30/2011 3:5            NO                    DISABLED
LEON_123456                      112096060     521984    11209606 8/30/2011 4:2           NO                   ENABLED
O_FCT                           115170000     486556      115170 8/29/2011 6:3            YES
SQL> SELECT COUNT(*) FROM user_tab_subpartitions
2 WHERE table_name =O_FCT'
3 ;
COUNT(*)
       112I used the following script:
BEGIN
DBMS_STATS.GATHER_TABLE_STATS(ownname          => user,
                                tabname          => O_FCT',
                                method_opt       => 'for all columns size auto',
                                degree           => 4,
                                estimate_percent =>10,
                                granularity      => 'ALL',
                                cascade          => false);
END;
/It costs 2 mins for the first two tables to gather the statistics respectively, but more than 10 mins for the partitioned table.
The time of collecting statistics accounts for a large part of total batch time.
And most jobs of the batch are full load in which case all partitions and subpartitions will be affected and we can't just gather specified partitions.
Does anyone have some experiences on this subject? Thank you very much.
Best regards,
Leon
Edited by: user12064076 on Aug 30, 2011 1:45 AM

Hi Leon
Why don't you gather stats at partition level? If your partitions data is not going to change after a day (date range partition for ex), you can simply do at partition level
GRANULARITY=>'PARTITION' for partition level and
GRANULARITY=>'SUBPARTITION' for subpartition level
You are gathering global stats every time which you may not require.
Edited by: user12035575 on 30-Aug-2011 01:50

How to Gather Statistics of Tables and Indexes

Hi all,
Plz help me in Gathering Statistics of Tables and Indexes.
Thanks

for tables
exec dbms_stats.gather_table_stats('SCOTT', 'EMPLOYEES');
for indexes
exec dbms_stats.gather_index_stats('SCOTT', 'EMPLOYEES_PK');
check this link for detail
http://nimishgarg.blogspot.com/2010/04/oracle-dbmsstats-gather-statistics-of.html

DB Statistics & BI Indexes

Hi All,
I have been going through a lot of threads related to DB Statistics & BI Indexes and I am confused.
1) How do I come to know that the DB Statistics and BI Indexes for a cube are active or created?
Is it through RSDDSTAT where the status is X means stats are active? Is there another way to find out?
What about BI Indexes?
2) How do I create DB Statistics?
3) Does creatting DB statistics for query help the query performance or creating DB statistics on cube helps the Query performance or is it both?
4) I understand primary indexes are created while creating the cube.However, when we try to create secondary indexes through performance tab in which table the details are stored? Can it be deleted later?
5) Is there another way to create BI Indexes other than performance tab?

P.S: the formatting went nuts... I added *** before each of my replies... COME ON SAP!! Cant you fix this???
Hi.
1) How do I come to know that the DB Statistics and BI Indexes for a cube are active or created?
Is it through RSDDSTAT where the status is X means stats are active? Is there another way to find out?
What about BI Indexes?
In addition to the performance tab where you got the traffic lights, you can check the indexes through tcode SE11. Just input the table name and on the next sceen click the button reading "Indexes...". A popup will show you the indexes that exist for the table you are looking at. Doubleclicking any of the indexes will take you to the details.
You can also define a new, secondary index here. You might have to go to DB02->missing indexes to have it created on the database, even though it says it exists and is active in se11... get your basis guy in on all of this.
2) How do I create DB Statistics?
Through Performance tab or step in process chain, but you should schedule db stats at least once a week in that DB-maintenance-calendar-thingy you can get to with a tcode I cannot remember... DBxx where xx is two numbers...ask your basis guy.
3) Does creatting DB statistics for query help the query performance or creating DB statistics on cube helps the Query performance or is it both?
You cannot create statistics for a query. You can collect statistics about the query use. This is the statistics stuff you can activate from bct; the "statistics-cubes" and all that. They store the info you collect and this is then called BI Statistics. It is of absolutely no use whatsoever with regards to performance. You can learn a lot about your system by analysing this, but starting to collect the BI Statistics wont help your slow running queries.
You can create statistics for cubes. This is the DB Stats and the effect of creating it is that the system will know how the data is distributed in the cube and because of that, it will have a better chance of reading data according to your selections faster. Much faster in some cases! This goes for both queries and loads (a load is just a special kind of query, where results are not put on the screen but in another table). Try to keep your DB Stats as up to date as you can - I always update the stats after each load and compression... It is especially important on transactional cubes, because data is more volatile here than when you only load every second day or so.
4) I understand primary indexes are created while creating the cube.However, when we try to create secondary indexes through performance tab in which table the details are stored? Can it be deleted later?
I dont know the tables this is stored in, but you can delete any index using SE11as mentioned above. Secondary indexes will need to be re-defined in SE11 when your system has been taken down... or if you activate the cube. In that case, only the hardwired primary indexes are created.
5) Is there another way to create BI Indexes other than performance tab?
I think you can only create/define an index in SE11, but you can refresh it from the Performance tab or in a process chain.
Regards,
Jacob
Edited by: Jacob Jansen on Aug 10, 2010 9:56 PM

Gathering statistics on interMedia indexes and tables

Has anyone found any differences (like which one is better or worse) between using the ANALYZE sql command, dbms_utility package, or dbms_stats package to compute or estimate statistics for interMedia text indexes and tables for 8.1.6? I've read the documentation on the subject, but it is still unclear as to which method should be used. The interMedia text docs say the ANALYZE command should be used, and the dbms_stats docs say that dbms_stats should be used.
Any help or past experience will be grateful.
Thanks,
jj

According to the Support Document "Using statistics with Oracle Text" (Doc ID 139979.1), no:
Q. Should we gather statistics on the underlying DR$/DR# tables? If yes/no, why?
A. The recommendation is NO. All internal recursive queries have hints to fix the plans that are deemed most optimal. We have seen in the past that statistics on the underlying DR$ tables may cause query plan changes leading to serious query performance problems.
Q. Should we gather statistics on Text domain indexes ( in our example above, BOOKS_INDEX)? Does it have any effect?
A: As documented in the reference manual, gathering statistics on Text domain index will help CBO to estimate selectivity and costs for processing a CONTAINS() predicate. If the Text index does not have statistics collected, default selectivity and cost will be used.
So 'No' on the DR$ tables and indexes, 'yes' on the user table being indexed.

Performance Problems - Index and Statistics

Dear Gurus,
I am having problems lossing indexes and statistics on cubes ,it seems my indexes are too old which in fact are not too old just created a month back and we check indexes daily and it returns us RED on the manage TAB.
please help

Dear Mr Syed ,
Solution steps I mentioned in my previous reply itself explains so called RE-ORG of tables;however to clarify more on that issue.
Occasionally,ORACLE Cost-Based Optimizer may calculate the estimated costs for a Full Table Scan lower than those for an Index Scan, although the actual runtime of an access via an index would be considerably lower than the runtime of the Full Table Scan,Some Imperative points to be considered in order to perk up the performance and improve on quandary areas such as extensive running times for Change runs & Aggregate activate & fill ups.
Performance problems based on a wrong optimizer decision would show that there is something serious missing at Database level and we need to RE_ORG the degenerated indexes in order to perk up the overall performance and avoid daily manual (RSRV+RSNAORA)activities on almost similar indexes.
For Re-organizing degenerated indexes 3 options are available-
1) DROP INDEX ..., and CREATE INDEX 
2)ALTER INDEX <index name> REBUILD (ONLINE PARALLEL x NOLOGGING)
3) ALTER INDEX <index name> COALESCE [as of Oracle 8i (8.1) only]
Each option has its Pros & Cons ,option 2 seems to be having lot of advantages to
Advantages- option 2
1)Fast storage in a different table space possible
2)Creates a new index tree
3)Gives the option to change storage parameters without deleting the index
4)As of Oracle 8i (8.1), you can avoid a lock on the table by specifying the ONLINE option. In this case, Oracle waits until the resource has been released, and then starts the rebuild. The "resource busy" error no longer occurs.
I would still leave the Database tech team be the best to judge and take a call on these.
These modus operandi could be institutionalized for all fretful cubes & its indexes as well.
However,I leave the thoughts with you.
Hope it Helps
Chetan
@CP..

ORA-01502 error in case of unusable unique index and bulk dml

Hi, all.
The db is 11.2.0.3 on a linux machine.
I made a unique index unusable, and issued a dml on the table.
Howerver, oracle gave me ORA-01502 error.
In order to avoid ORA-01502 error, do I have to drop the unique index ,and do bulk dml, and recreate the index?
Or Is there any other solution without re-creating the unique index?
create table hoho.abcde as
select level col1 from dual connect by level <=1000
10:09:55 HOHO@PD1MGD>create unique index hoho.abcde_dx1 on hoho.abcde (col1);
Index created.
10:10:23 HOHO@PD1MGD>alter index hoho.abcde_dx1 unusable;
Index altered.
Elapsed: 00:00:00.03
10:11:27 HOHO@PD1MGD>delete from hoho.abcde where rownum < 11;
delete from hoho.abcde where rownum < 11
ERROR at line 1:
ORA-01502: index 'HOHO.ABCDE_DX1' or partition of such index is in unusable stateThanks in advance.
Best Regards.

Hi. all.
The following is from "http://docs.oracle.com/cd/E14072_01/server.112/e10595/indexes002.htm#CIHJIDJG".
Is there anyone who can show me a tip to avoid the following without dropping and re-creating an unique index?
•DML statements terminate with an error if there are any unusable indexes that are used to enforce the UNIQUE constraint.
Unusable indexes
An unusable index is ignored by the optimizer and is not maintained by DML. One reason to make an index unusable is if you want to improve the performance of bulk loads. (Bulk loads go more quickly if the database does not need to maintain indexes when inserting rows.) Instead of dropping the index and later recreating it, which requires you to recall the exact parameters of the CREATE INDEX statement, you can make the index unusable, and then just rebuild it. You can create an index in the unusable state, or you can mark an existing index or index partition unusable. The database may mark an index unusable under certain circumstances, such as when there is a failure while building the index. When one partition of a partitioned index is marked unusable, the other partitions of the index remain valid.
An unusable index or index partition must be rebuilt, or dropped and re-created, before it can be used. Truncating a table makes an unusable index valid.
Beginning with Oracle Database 11g Release 2, when you make an existing index unusable, its index segment is dropped.
The functionality of unusable indexes depends on the setting of the SKIP_UNUSABLE_INDEXES initialization parameter.
When SKIP_UNUSABLE_INDEXES is TRUE (the default), then:
•DML statements against the table proceed, but unusable indexes are not maintained.
•DML statements terminate with an error if there are any unusable indexes that are used to enforce the UNIQUE constraint.
•For non-partitioned indexes, the optimizer does not consider any unusable indexes when creating an access plan for SELECT statements. The only exception is when an index is explicitly specified with the INDEX() hint.
•For a partitioned index where one or more of the partitions are unusable, the optimizer does not consider the index if it cannot determine at query compilation time if any of the index partitions can be pruned. This is true for both partitioned and non-partitioned tables. The only exception is when an index is explicitly specified with the INDEX() hint.
When SKIP_UNUSABLE_INDEXES is FALSE, then:
•If any unusable indexes or index partitions are present, any DML statements that would cause those indexes or index partitions to be updated are terminated with an error.
•For SELECT statements, if an unusable index or unusable index partition is present but the optimizer does not choose to use it for the access plan, the statement proceeds. However, if the optimizer does choose to use the unusable index or unusable index partition, the statement terminates with an error.Thanks in advance.
Best Regards.

SQL Loader direct path loads and unusable indexes

sorry about all the questions. I am researching several issues. I am reading the Utilities document. It says that in certain circumstances indexes will become unusable. I have some questions about my scenario.
1. tables partitioned by range
2. local indexes
3. all tables have 1 primary key and other indexes are non-unique
4. all sql loads will go into the most recent partition
5. users will be querying tables while sql loader is occurring
6. only one sql loader session will run per table
7. no foreign keys, triggers, or other constrants other than primary keys.
The docs are not clear. Do I have a concern about unusable indexes with direct path loads? Will indexes function while the sql loader direct path is occurring(this I can't test since I have small data files now and they load fast, but I will have larger ones in production).
My understanding is that Extertnal tables using Insert append is exactly the same as sql loader direct path load. Is this true?

if you dont have anything productive to say how about you don't post at all? you have made ignorant posts like this for years.
as far as reading the docs what do you think "the docs are not clear" means? By the docs I am referring to the utilities document.
As far as version number its 10.2 and I forgot that. However, it does not appear that sql loader has really changed all that much over the last few versions.
Finally I plan on testing it out and its more than a 2 minute test. I wanted to make sure I don't miss anythng in my tests.
don't respond to any threads or posts I make from now on.

Which Event Classes i should use for finding good indexs and statistics for queries in SP.

Dear all,
I am trying to use pro filer to create a trace,so that it can be used as workload in
"Database Engine Tuning Advisor" for optimization of one stored procedure.
Please tel me about the Event classes which i should use in trace.
The stored proc contains three insert queries which insert data into a table variable,
Finally a select query is used on same table variable with one union of the same table variable, to generate a sequence for records based on certain condition of few columns.
There are three cases where i am using the above structure of the SP, so there are three SPS out of three , i will chose one based on their performance.
1) There is only one table with three inserts which gets into a table variable with a final sequence creation block.
2) There are 15 tables with 45 inserts , which gets into a tabel variable with a final
sequence creation block.
3)
There are 3 tables with 9 inserts , which gets into a table variable with a final
sequence creation block.
In all the above case number of record will be around 5 lacks.
Purpose is optimization of queries in SP
like which Event Classes i should use for finding good indexs and statistics for queries in SP.
yours sincerely

"Database Engine Tuning Advisor" for optimization of one stored procedure.
Please tel me about the Event classes which i should use in trace.
You can use the "Tuning" template to capture the workload to a trace file that can be used by the DETA. See
http://technet.microsoft.com/en-us/library/ms190957(v=sql.105).aspx
If you are capturing the workload of a production server, I suggest you not do that directly from Profiler as that can impact server performance. Instead, start/stop the Profiler Tuning template against a test server and then script the trace
definition (File-->Export-->Script Trace Definition). You can then customize the script (e.g. file name) and run the script against the prod server to capture the workload to the specified file. Stop and remove the trace after the workload
is captured with sp_trace_setstatus:
DECLARE @TraceID int = <trace id returned by the trace create script>
EXEC sp_trace_setstatus @TraceID, 0; --stop trace
EXEC sp_trace_setstatus @TraceID, 2; --remove trace definition
Dan Guzman, SQL Server MVP, http://www.dbdelta.com

Index and statistics

for infoprovider, what is the problem to run the indicex, but not statistics them?

Statistics tell the optimizer things like how many values there, how similar or unique the values are, etc. The database optimizer uses the index and table statistics to make decisions about how best to execute the query, e.g. perform indexed reads of the table or a full table scan, or what order to read tables. The CBO (Cost Based Optimzer) is generally trying to find the execution plan that requires the fewest system resources, generally the fewest IOs (but there are other factors in the mix). It may examine hundreds or thousands of different execution plans to find wht it thinks is best.
Without any / good statistics the CBO may make bad choices about how to execute the query, that are not the most efficient.
When you drop and rebuild the indices, you lose the statistics which could easily result in bad choices by the CBO (Cost Based Optimizer).

Indexes and BW statistics

hello all,
What is meaning of Indexes and BW statistics?
Sneha

Please search the forum...these have been discussed in details.

Relation between computing and gathering statistics

Hi gurus,
What is the relation between computing and gathering statistics for a database object.Are they mutually dependent or one doesn't have anything to do with the other?How they affect performance of a database??
plz dont redirect..just bottom lines are expected(be specific)
Thanks in advance
anirban

computing term used to collect 100% statistics along with analyze command.
gather stats is a new package provided by the oracle, also recommend to use this instead of analyze. You can also take 100% stats, like compute with analyze command, in gather stats pacakge, parameter estimate_percent=>null.
exec dbms_stats.gather_table_stats('SCHEMA',TABLE',cascade=>true,estimate_percent=>NULL);
Jaffar

How to add blayers in Photoshop I get INDEX and then no more l;ayers

I am trying to do an exercise I cannot follow it since whenever I open a New Item my Layer turns into INDEX and after that I am not able to add any new layers

Indexed mode does not support layers. If you need to reduce bit depth for the final output, work in RGB until the image is finished, then reduce to Indexed mode, and save as GIFF (or format of choice).
You should save as PSD before setting Indexed mode if you want to keep a copy of the layered document.

Unusable system (graphical glitches and more)

Sorry for the quite unspecific title, but I'm not really sure how to describe this problem...
So, I came back from a threeweek long vacation yesterday and did a "pacman -Syu". Everything went smooth and there was nothing on the Arch news or the forum that seemed serious to me, so I thought everything was good.
After booting today, I experience pretty bad graphical glitches which make the system unusable. urxvtc (and lxterminal) don't even start anymore, one of my conkys hogs a core at 100% and chromium and gvim look like this:
Screenshot: http://i.imgur.com/jKnZUHs.png
Sakura, xterm, dwb, firefox and thunderbird seem to work fine, as far as I can tell. Haven't really tested things in deep, but there's nothing obvious. Logs (dmesg or journalctl) also look plain to me, but I can post them anyway if necessary.
pacman.log is here. As you can see, I tried downgrading some packages that seemed relevant to me, but no success so far.
[2014-08-20 12:33] [PACMAN] starting full system upgrade
[2014-08-20 12:44] [PACMAN] upgraded xorg-xrandr (1.4.2-1 -> 1.4.3-1)
[2014-08-20 12:44] [PACMAN] upgraded arandr (0.1.7.1-2 -> 0.1.7.1-3)
[2014-08-20 12:44] [PACMAN] upgraded attica-qt5 (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded bash (4.3.018-3 -> 4.3.022-1)
[2014-08-20 12:44] [PACMAN] upgraded cabextract (1.4-2 -> 1.4-3)
[2014-08-20 12:44] [PACMAN] installed pyqt5-common (5.3.1-1)
[2014-08-20 12:44] [PACMAN] installed python2-pyqt5 (5.3.1-1)
[2014-08-20 12:44] [PACMAN] installed python2-html5lib (0.999-4)
[2014-08-20 12:44] [PACMAN] upgraded calibre (1.40.0-1 -> 1.206.1-1)
[2014-08-20 12:44] [PACMAN] upgraded chromium (36.0.1985.125-1 -> 36.0.1985.143-1)
[2014-08-20 12:44] [PACMAN] upgraded cmake (3.0.0-3 -> 3.0.1-1)
[2014-08-20 12:44] [PACMAN] upgraded convertlit (1.8-6 -> 1.8-7)
[2014-08-20 12:44] [PACMAN] upgraded cpupower (3.15-1 -> 3.16-1)
[2014-08-20 12:44] [PACMAN] upgraded cracklib (2.9.0-2 -> 2.9.1-1)
[2014-08-20 12:44] [PACMAN] upgraded cups-filters (1.0.55-1 -> 1.0.57-1)
[2014-08-20 12:44] [PACMAN] upgraded deadbeef (0.6.1-2 -> 0.6.2-1)
[2014-08-20 12:44] [PACMAN] upgraded device-mapper (2.02.106-2 -> 2.02.109-1)
[2014-08-20 12:44] [PACMAN] upgraded dhcpcd (6.4.2-1 -> 6.4.3-1)
[2014-08-20 12:44] [PACMAN] upgraded libutil-linux (2.24.2-1 -> 2.25-3)
[2014-08-20 12:44] [PACMAN] upgraded e2fsprogs (1.42.10-1 -> 1.42.11-1)
[2014-08-20 12:44] [PACMAN] upgraded util-linux (2.24.2-1 -> 2.25-3)
[2014-08-20 12:44] [PACMAN] upgraded fakeroot (1.20-1 -> 1.20.1-1)
[2014-08-20 12:44] [PACMAN] upgraded gsm (1.0.13-7 -> 1.0.13-8)
[2014-08-20 12:44] [PACMAN] upgraded libx264 (1:142.20140311-4 -> 1:142.20140311-6)
[2014-08-20 12:44] [PACMAN] upgraded ffmpeg (1:2.3.1-1 -> 1:2.3.3-1)
[2014-08-20 12:44] [PACMAN] installed wxgtk (3.0.1-2)
[2014-08-20 12:44] [PACMAN] upgraded libidn (1.28-2 -> 1.29-1)
[2014-08-20 12:44] [PACMAN] upgraded sqlite (3.8.5-1 -> 3.8.6-1)
[2014-08-20 12:44] [PACMAN] upgraded filezilla (3.8.1-1 -> 3.9.0.3-1)
[2014-08-20 12:44] [PACMAN] upgraded flashplugin (11.2.202.394-1 -> 11.2.202.400-1)
[2014-08-20 12:44] [PACMAN] upgraded geoip-database (20140702-1 -> 20140806-1)
[2014-08-20 12:44] [PACMAN] upgraded openssl (1.0.1.h-1 -> 1.0.1.i-1)
[2014-08-20 12:44] [PACMAN] upgraded git (2.0.3-1 -> 2.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded gnupg (2.0.25-1 -> 2.0.26-1)
[2014-08-20 12:44] [PACMAN] upgraded gperf (3.0.4-4 -> 3.0.4-5)
[2014-08-20 12:44] [PACMAN] upgraded gpgme (1.5.0-1 -> 1.5.1-1)
[2014-08-20 12:44] [PACMAN] upgraded gstreamer0.10-ugly (0.10.19-11 -> 0.10.19-12)
[2014-08-20 12:44] [PACMAN] upgraded gstreamer0.10-ugly-plugins (0.10.19-11 -> 0.10.19-12)
[2014-08-20 12:44] [PACMAN] upgraded vim-runtime (7.4.383-1 -> 7.4.404-1)
[2014-08-20 12:44] [PACMAN] upgraded gvim (7.4.383-1 -> 7.4.404-1)
[2014-08-20 12:44] [PACMAN] upgraded handbrake (0.9.9-6 -> 0.9.9-7)
[2014-08-20 12:44] [PACMAN] upgraded handbrake-cli (0.9.9-6 -> 0.9.9-7)
[2014-08-20 12:44] [PACMAN] upgraded mesa (10.2.4-1 -> 10.2.5-1)
[2014-08-20 12:44] [PACMAN] upgraded mesa-libgl (10.2.4-1 -> 10.2.5-1)
[2014-08-20 12:44] [PACMAN] upgraded intel-dri (10.2.4-1 -> 10.2.5-1)
[2014-08-20 12:44] [PACMAN] upgraded inxi (2.1.28-1 -> 2.1.29-1)
[2014-08-20 12:44] [PACMAN] upgraded solid (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded karchive (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kcoreaddons (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kwidgetsaddons (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kjobwidgets (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kglobalaccel (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kconfig (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kcompletion (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded ki18n (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kwindowsystem (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kcrash (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kdbusaddons (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kservice (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kauth (5.0.0-2 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kcodecs (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kguiaddons (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kconfigwidgets (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kitemviews (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kiconthemes (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded sonnet (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded ktextwidgets (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kxmlgui (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kbookmarks (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded knotifications (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kwallet (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kio (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kactivities-frameworks (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded kbd (2.0.1-1 -> 2.0.2-1)
[2014-08-20 12:44] [PACMAN] upgraded kdeclarative (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded krb5 (1.12.1-1 -> 1.12.2-1)
[2014-08-20 12:44] [PACMAN] upgraded kdelibs (4.13.3-2 -> 4.13.3-3)
[2014-08-20 12:44] [PACMAN] upgraded plasma-framework (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded threadweaver (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded krunner (5.0.0-1 -> 5.1.0-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-flashplugin (11.2.202.394-1 -> 11.2.202.400-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-gettext (0.19.1-1 -> 0.19.2-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-mesa (10.2.4-1 -> 10.2.5-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-mesa-libgl (10.2.4-1 -> 10.2.5-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-intel-dri (10.2.4-1 -> 10.2.5-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-krb5 (1.12.1-1 -> 1.12.2-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-libcups (1.7.4-1 -> 1.7.5-1)
[2014-08-20 12:44] [PACMAN] upgraded xcb-proto (1.10-2 -> 1.11-1)
[2014-08-20 12:44] [PACMAN] upgraded libxcb (1.10-3 -> 1.11-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-libxcb (1.10-3 -> 1.11-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-openssl (1.0.1.h-1 -> 1.0.1.i-1)
[2014-08-20 12:44] [PACMAN] upgraded tdb (1.3.0-1 -> 1.3.0-2)
[2014-08-20 12:44] [PACMAN] upgraded lib32-tdb (1.2.12-1 -> 1.3.0-1)
[2014-08-20 12:44] [PACMAN] upgraded lib32-util-linux (2.24.2-1 -> 2.25-1)
[2014-08-20 12:44] [PACMAN] upgraded libbsd (0.6.0-2 -> 0.7.0-1)
[2014-08-20 12:44] [PACMAN] upgraded libedit (20140213_3.1-1 -> 20140620_3.1-1)
[2014-08-20 12:44] [PACMAN] upgraded libmariadbclient (10.0.12-2 -> 10.0.13-1)
[2014-08-20 12:44] [PACMAN] upgraded libunrar (1:5.1.6-1 -> 1:5.1.7-1)
[2014-08-20 12:44] [PACMAN] upgraded libva-vdpau-driver (0.7.4-1 -> 0.7.4-2)
[2014-08-20 12:44] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-08-20 12:44] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Starting build: 3.16.1-1-ARCH
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [autodetect]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Starting build: 3.16.1-1-ARCH
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [base]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [udev]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [modconf]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [block]
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [filesystems]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [keyboard]
[2014-08-20 12:44] [ALPM-SCRIPTLET] -> Running build hook: [fsck]
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-08-20 12:44] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-08-20 12:44] [PACMAN] upgraded linux (3.15.7-1 -> 3.16.1-1)
[2014-08-20 12:45] [PACMAN] upgraded linux-headers (3.15.7-1 -> 3.16.1-1)
[2014-08-20 12:45] [ALPM] warning: /etc/lirc/lircd.conf installed as /etc/lirc/lircd.conf.pacnew
[2014-08-20 12:45] [ALPM-SCRIPTLET] :: lirc.service and lircm.service have been replaced
[2014-08-20 12:45] [ALPM-SCRIPTLET] by the upstream unit files lircd.service and
[2014-08-20 12:45] [ALPM-SCRIPTLET] lircmd.service.
[2014-08-20 12:45] [PACMAN] upgraded lirc-utils (1:0.9.0-75 -> 1:0.9.1.a-3)
[2014-08-20 12:45] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-08-20 12:45] [PACMAN] upgraded lirc (1:0.9.0-75 -> 1:0.9.1.a-3)
[2014-08-20 12:45] [PACMAN] upgraded lvm2 (2.02.106-2 -> 2.02.109-1)
[2014-08-20 12:45] [PACMAN] upgraded mariadb-clients (10.0.12-2 -> 10.0.13-1)
[2014-08-20 12:45] [PACMAN] upgraded mariadb (10.0.12-2 -> 10.0.13-1)
[2014-08-20 12:45] [PACMAN] upgraded menu-cache (0.5.1-2 -> 0.6.0-1)
[2014-08-20 12:45] [PACMAN] upgraded mirage (0.9.5.2-1 -> 0.9.5.2-2)
[2014-08-20 12:45] [PACMAN] upgraded mplayer (37224-1 -> 37224-2)
[2014-08-20 12:45] [PACMAN] upgraded mpv (0.4.2-1 -> 0.5.0-1)
[2014-08-20 12:45] [PACMAN] upgraded openresolv (3.5.6-1 -> 3.5.7-1)
[2014-08-20 12:45] [PACMAN] upgraded netctl (1.8-1 -> 1.9-1)
[2014-08-20 12:45] [PACMAN] upgraded openconnect (1:5.03-1 -> 1:6.00-1)
[2014-08-20 12:45] [PACMAN] upgraded networkmanager-openconnect (0.9.8.6-2 -> 0.9.10.0-1)
[2014-08-20 12:45] [PACMAN] upgraded nitrogen (1.5.2-1 -> 1.5.2-2)
[2014-08-20 12:45] [PACMAN] upgraded numix-themes (2.2.3-1 -> 2.3-1)
[2014-08-20 12:45] [PACMAN] upgraded opencv (2.4.9-1 -> 2.4.9-3)
[2014-08-20 12:45] [PACMAN] upgraded parted (3.1-4 -> 3.2-1)
[2014-08-20 12:45] [PACMAN] installed perl-xml-namespacesupport (1.11-3)
[2014-08-20 12:45] [PACMAN] installed perl-xml-sax-base (1.08-3)
[2014-08-20 12:45] [PACMAN] installed perl-xml-sax (0.99-4)
[2014-08-20 12:45] [PACMAN] installed perl-xml-sax-expat (0.51-2)
[2014-08-20 12:45] [PACMAN] upgraded perl-xml-simple (2.20-2 -> 2.20-3)
[2014-08-20 12:45] [PACMAN] upgraded ponymix (2-2 -> 3-1)
[2014-08-20 12:45] [PACMAN] upgraded python-setuptools (1:5.4.1-1 -> 1:5.7-1)
[2014-08-20 12:45] [PACMAN] upgraded python2-cryptography (0.5.2-1 -> 0.5.3-1)
[2014-08-20 12:45] [PACMAN] upgraded python2-setuptools (1:5.4.1-1 -> 1:5.7-1)
[2014-08-20 12:45] [PACMAN] upgraded python2-tornado (4.0.0-1 -> 4.0.1-1)
[2014-08-20 12:45] [PACMAN] upgraded qscintilla (2.8.3-3 -> 2.8.3-4)
[2014-08-20 12:45] [PACMAN] upgraded reflector (2014-4 -> 2014.8-1)
[2014-08-20 12:45] [PACMAN] upgraded s-nail (14.7.4-1 -> 14.7.6-1)
[2014-08-20 12:45] [PACMAN] upgraded screenfetch (3.2.2-1 -> 3.6.0-1)
[2014-08-20 12:45] [PACMAN] upgraded zenity (3.12.1-1 -> 3.12.1-2)
[2014-08-20 12:45] [PACMAN] upgraded steam (1.0.0.47-2 -> 1.0.0.48-1)
[2014-08-20 12:45] [PACMAN] upgraded taglib-extras (1.0.1-2 -> 1.0.1-3)
[2014-08-20 12:45] [PACMAN] upgraded transcode (1.1.7-14 -> 1.1.7-15)
[2014-08-20 12:45] [PACMAN] upgraded unrar (1:5.1.6-1 -> 1:5.1.7-1)
[2014-08-20 12:45] [PACMAN] upgraded vimpager (1.8.9-1 -> 1.8.9-2)
[2014-08-20 12:45] [ALPM-SCRIPTLET]
[2014-08-20 12:45] [ALPM-SCRIPTLET] Creating symlink /var/lib/dkms/vboxhost/4.3.14/source ->
[2014-08-20 12:45] [ALPM-SCRIPTLET] /usr/src/vboxhost-4.3.14
[2014-08-20 12:45] [ALPM-SCRIPTLET]
[2014-08-20 12:45] [ALPM-SCRIPTLET] DKMS: add completed.
[2014-08-20 12:45] [ALPM-SCRIPTLET] ==> To build and install your modules run: dkms install vboxhost/4.3.14
[2014-08-20 12:45] [ALPM-SCRIPTLET] ==> To do this automatically at startup run: systemctl enable dkms.service
[2014-08-20 12:45] [PACMAN] upgraded virtualbox-host-dkms (4.3.14-2 -> 4.3.14-3)
[2014-08-20 12:45] [ALPM-SCRIPTLET] In order to use the new version, reload all virtualbox modules manually.
[2014-08-20 12:45] [PACMAN] upgraded virtualbox-host-modules (4.3.14-3 -> 4.3.14-5)
[2014-08-20 12:45] [PACMAN] upgraded virtualbox (4.3.14-2 -> 4.3.14-3)
[2014-08-20 12:45] [ALPM-SCRIPTLET] 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[2014-08-20 12:45] [ALPM-SCRIPTLET] 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
[2014-08-20 12:45] [PACMAN] upgraded virtualbox-ext-vnc (4.3.14-2 -> 4.3.14-3)
[2014-08-20 12:45] [ALPM-SCRIPTLET]
[2014-08-20 12:45] [ALPM-SCRIPTLET] Creating symlink /var/lib/dkms/vboxguest/4.3.14/source ->
[2014-08-20 12:45] [ALPM-SCRIPTLET] /usr/src/vboxguest-4.3.14
[2014-08-20 12:45] [ALPM-SCRIPTLET]
[2014-08-20 12:45] [ALPM-SCRIPTLET] DKMS: add completed.
[2014-08-20 12:45] [ALPM-SCRIPTLET] ==> To build and install your modules run: dkms install vboxguest/4.3.14
[2014-08-20 12:45] [ALPM-SCRIPTLET] ==> To do this automatically at startup run: systemctl enable dkms.service
[2014-08-20 12:45] [PACMAN] upgraded virtualbox-guest-dkms (4.3.14-2 -> 4.3.14-3)
[2014-08-20 12:45] [PACMAN] upgraded weechat (0.4.3-2 -> 1.0-1)
[2014-08-20 12:45] [PACMAN] upgraded wildmidi (0.3.6-1 -> 0.3.7-1)
[2014-08-20 12:45] [PACMAN] upgraded wine (1.7.23-1 -> 1.7.24-1)
[2014-08-20 12:45] [PACMAN] upgraded wxgtk2.8 (2.8.12.1-1 -> 2.8.12.1-2)
[2014-08-20 12:45] [PACMAN] upgraded x264 (1:142.20140311-4 -> 1:142.20140311-6)
[2014-08-20 12:45] [PACMAN] upgraded xf86-video-intel (2.99.914-3 -> 2.99.914-4)
[2014-08-20 12:45] [PACMAN] upgraded xfce4-mixer (4.10.0-2 -> 4.10.0-3)
[2014-08-20 12:45] [PACMAN] upgraded xfsprogs (3.2.0-1 -> 3.2.1-1)
[2014-08-21 17:49] [PACMAN] Running 'pacman -U intel-dri-10.2.4-1-x86_64.pkg.tar.xz mesa-10.2.4-1-x86_64.pkg.tar.xz mesa-libgl-10.2.4-1-x86_64.pkg.tar.xz'
[2014-08-21 17:49] [PACMAN] downgraded mesa (10.2.5-1 -> 10.2.4-1)
[2014-08-21 17:49] [PACMAN] downgraded mesa-libgl (10.2.5-1 -> 10.2.4-1)
[2014-08-21 17:49] [PACMAN] downgraded intel-dri (10.2.5-1 -> 10.2.4-1)
[2014-08-21 17:53] [PACMAN] Running 'pacman -U libxcb-1.10-3-x86_64.pkg.tar.xz xcb-proto-1.10-2-any.pkg.tar.xz'
[2014-08-21 17:53] [PACMAN] downgraded xcb-proto (1.11-1 -> 1.10-2)
[2014-08-21 17:53] [PACMAN] downgraded libxcb (1.11-1 -> 1.10-3)
[2014-08-21 17:53] [PACMAN] Running 'pacman -U libva-vdpau-driver-0.7.4-1-x86_64.pkg.tar.xz'
[2014-08-21 17:53] [PACMAN] downgraded libva-vdpau-driver (0.7.4-2 -> 0.7.4-1)
[2014-08-21 17:54] [PACMAN] Running 'pacman -U xf86-video-intel-2.99.914-3-x86_64.pkg.tar.xz'
[2014-08-21 17:54] [PACMAN] downgraded xf86-video-intel (2.99.914-4 -> 2.99.914-3)
Any ideas?

Thanks for the help, but neither switching to uxa nor to glamor did help. Downgrading the kernel, intel-dri, mesa and xf86-video-intel didn't do anything, either... not sure what else to do.

Best practices for gathering statistics in 10g

I would like to get some opinions on what is considered best practice for gathering statistics in 10g. I know that 10g has auto statistics gathering, but that doesn't seem to be very effective as I see some table stats are way out of date.
I have recommended that we have at least a weekly job that generates stats for our schema using DBMS_STATS (DBMS_STATS.gather_schema_stats). Is this the right approach to generate object stats for a schema and keep it up to date? Are index stats included in that using CASCADE?
Is it also necessary to gather system stats? I welcome any thoughts anyone might have. Thanks.

Hi,
Is this the right approach to generate object stats for a schema and keep it up to date? The choices of executions plans made by the CBO are only as good as the statistics available to it. The old-fashioned analyze table and dbms_utility methods for generating CBO statistics are obsolete and somewhat dangerous to SQL performance. As we may know, the CBO uses object statistics to choose the best execution plan for all SQL statements.
I spoke with Andrew Holsworth of Oracle Corp SQL Tuning group, and he says that Oracle recommends taking a single, deep sample and keep it, only re-analyzing when there is a chance that would make a difference in execution plans (not the default 20% re-analyze threshold).
I have my detailed notes here:
http://www.dba-oracle.com/art_otn_cbo.htm
As to system stats, oh yes!
By measuring the relative costs of sequential vs. scattered I/O, the CBO can make better decisons. Here are the data items collected by dbms_stats.gather_system_stats:
No Workload (NW) stats:
CPUSPEEDNW - CPU speed
IOSEEKTIM - The I/O seek time in milliseconds
IOTFRSPEED - I/O transfer speed in milliseconds
I have my notes here:
http://www.dba-oracle.com/t_dbms_stats_gather_system_stats.htm
Hope this helps. . . .
Don Burleson
Oracle Press author
Author of “Oracle Tuning: The Definitive Reference”
http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

EAR4 - Gathering Statistics, unusable indexes and more

Similar Messages

Maybe you are looking for