In VLDB databases, there is a common willing in using a tablespace naming convention that includes seasonal information of data within tablespace, such as CHURN_2008M01 or SALE_2008W50. This has various benefits in terms of ILM (Information Life Cycle) management. By just looking the name of a tablespace, the DBA can have a pretty good idea about the tablespace and segments within that tablespace. Nevertheless, prior to 10g this convention can cause significant degeneration in system catalog performance if data windowing is used. In other words, if you periodically need to drop old tablespaces and add new ones, Oracle catalog starts to blow up. In this paper, you will find a tricky way of solving this problem by Oracle 10g.
This post consists of my article published in IOUG “Oracle Technology Best Practices” booklet delivered in Oracle Open World 2008.
As I’ve promised, I publish my presentation I held on Tuesday in Oracle Open World. It was a really challanging experience for me to perform a presentation in such a great event. Moreover one of the Oracle experts, Julian Dyke, I really like to read attented to my presentation. And I am very proud of hearing his positive feedbacks about my presentation. Thanks a lot Julian. Hope to see you in Birmingham…
I also want to thank to Reiner Zimmermann from Oracle, all my collegues and managers in Turkcell, and Hasan Tonguc Yilmaz for their supports and ideas in preparing this presentation.