![]() An extra row has been added to the USER_TAB_STATISTICS view with the NOTES column set to "STATS_ON_CONVENTIONAL_DML".This value is only changed when new statistics are gathered using the DBMS_STATS package. The NUM_ROWS column in the USER_TABLES view is not amended by this action.We see the impact of the real-time statistics. TAB1 ID 1 1885 11 STATS_ON_CONVENTIONAL_DML We check some basic statistics for the TAB1 table. ![]() We flush the monitoring information to the dictionary.ĮXEC DBMS_STATS.flush_database_monitoring_info 'Description of ' || level AS description We reset the test data and run a conventional path INSERT. The first test will have some extra detail, but subsequent tests will be less verbose. ![]() TABLE_NAME COLUMN_NAME LOW_VALUE HIGH_VALUE SAMPLE_SIZE NOTES UTL_RAW.cast_to_number(high_value) AS high_value, UTL_RAW.cast_to_number(low_value) AS low_value, LOW_VALUE and HIGH_VALUE of ID column from USER_TAB_COL_STATISTICS. Don't use this on a real instance or you will be breaking your license agreement. There is a workaround for testing by enabling the " _exadata_feature_on" initialisation parameter. This feature is currently restricted to Enterprise Edition on Engineered Systems, like Exadata and Exadata Cloud Service, as described here.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |