Being re-constituted from the old website; if you can’t find what you’re seeking, please let me know via email and I’ll get it re-posted as soon as possible…
Presentation: RDBMS Forensics - Troubleshooting Using ASH
This was presented at the OTN China Tour 2013 in Beijing on 18-Nov 2013, as well as Oracle Open World 2013 in San Francisco on 22-Sep 2013, at Collaborate 2013 in Denver on 11-April 2013, at Oracle Open World 2012 in San Francisco on 02-Oct 2012, at the Utah Oracle Users Group “Training Days 2011” in Sandy UT on 30-March 2011, at RMOUG “Training Days 2011” in Denver CO on 13-Feb 2011 and at the Hotsos Symposium 2011 in Irving TX on 08-Mar 2011.
This is based on two (and a half) case studies illustrating how Active Session History (ASH) can be used as the next best thing to trace files when diagnosing complex problems in the Oracle RDBMS. ASH is not just for performance tuning, it can also provide vital information for the forensic analysis following a specific problem.
White Paper: Scaling To Infinity - Partitioning Data Warehouses using Oracle Database
This paper was presented at the Oracle Open World conference in 2011, 2010, 2009 and 2007 in San Francisco CA, and at the RMOUG Training Days conference in 2010, 2009, 2006, and 2005 in Denver CO, and has been presented numerous times at other Oracle users group conferences and as a 1-day and 2-day training seminar. It is being presented once again at the IOUG forum of Collaborate 2013 in Denver CO on 08-April 2013.
This paper explains why using the EXCHANGE PARTITION operation during ETL leads a data warehouse onto the virtuous cycle of effective use of advanced features and easy living. Not using EXCHANGE PARTITION during ETL relegates a data warehouse onto the dreaded death spiral where life becomes progressively more difficult and ROI shrinks to zero.
Presentation: Scaling To Infinity - Partitioning Data Warehouses on Oracle
Presentation slides to accompany the white paper.
White paper: Compression in Oracle Database
This paper was presented at the RMOUG Training Days conference in 2013 in Denver CO in February 2013, at the UTOUG Training Days conference in Salt Lake City UT in March 2013, and at the IOUG forum of Collaborate 2013 in Denver CO in April 2013.
This paper explains the three types of table data compression available in Oracle database: BASIC/OLTP de-duplication, hybrid-columnar compression (HCC), and the often-overlooked "trailing NULL columns" form of compression. The paper reviews all of the features of Oracle that have combined to implement the first two compression features, paying particular attention to reviewing row formats and block formats within Oracle database, using blocks dumps and diagrams as illustration.
Presentation: Compression in Oracle Database
Presentation slides to accompany the white paper.
Can I get a copy of your paper “The Search for Intelligent Life in Oracle’s cost-based optimizer.
Thanks
Ron,
My apologies for being so slow in reconstituting my website since migrating to WordPress. I will get everything re-posted for download soon, and I would be glad to share the white paper with you via email, with one huge caveat…
…and that caveat is that the white paper was written for Oracle8.0 and Oracle8.1 only, and it has been effectively obsolete since Oracle9i, for almost 10 years now. So please bear in mind that using the OPTIMIZER_INDEX_CACHING and OPTIMIZER_INDEX_COST_ADJ parameters for any version of Oracle greater than Oracle8i is dangerous and will cause more problems than it resolves. Please consider using the GATHER_SYSTEM_STATS procedure within the DBMS_STATS package to set appropriate values within the SYS.AUX_STATS$ table for the CPU model of the cost-based optimizer. I strongly recommend reading up on gathering statistics using information posted by Maria Colgan at “http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/1354477.pdf” and Kimberly Floss at “http://www.oracle.com/technetwork/issue-archive/2005/05-jan/o15tech-tuning-090612.html”.
If this is acceptable, then please let me know and I’ll send the white paper.
Thanks!
-Tim