6
Oracle 10g Tablespace Enhancements By Jim Czuprynski Synopsis. Oracle 10g's daunting array of new features like extended FLASHBACK technology, Automated Storage Management, and Grid Computing sometimes overshadow the more mundane -- yet no less impressive! - improvements to its logical storage capabilities. This article illustrates several enhancements to Oracle's already robust logical storage structures, including the SYSAUX tablespace, BIGFILE tablespaces, tablespace groups, and tablespace renaming. Oracle's highest-level logical container for data, the tablespace, is a lot like an orphaned, lonely child. Tablespaces live in that lonely place between the physical raw data contained in their datafiles and the myriad logical objects whose structure they organize, manage, and control: tables, indexes, and LOBs, to name just a few. I was heartened to see that Oracle 10g has made some significant improvements to tablespaces that considerably extend the size, manageability, and cohesiveness of an Oracle database. I will dive right into what I believe is the most impressive new feature in this group: the BIGFILE tablespace. Size Does Matter: BIGFILE Tablespaces I fondly remember buying my first IBM XT clone PC in the late 1980s because it came with my first-ever hard drive. I recall telling my co-workers that I would never need to buy another PC because the new machine had a huge amount of storage -- 20MB - and had cost me only an extra $400.00. (This machine's case is now a concrete-filled boat anchor somewhere in northern Wisconsin. I filled up the hard drive in about six months.) As the quality and quantity of storage media continues to grow, Oracle 10g has kept pace as well. One of the major improvements in Oracle 10g is the introduction of new tablespace storage capacity. A tablespace is limited to a maximum of 65,536 (64K) datafiles, but each datafile's size had been limited by the maximum OS file size. The new BIGFILE tablespace overcomes this limitation by allowing the creation of a tablespace with only one datafile - but what a datafile! A BIGFILE tablespace's datafile can now hold up to 4,294,967,296 (yes, you read that correctly - the multiplier is over 4 billion) blocks of data storage space. This means that a tablespace could conceivably hold up to 128 TB of data if the maximum Oracle tablespace block size of 32K is used. Oracle does recommend that Automatic Segment Space Management (ASSM) should be enabled. In addition, if the BIGFILE tablespace's datafile is sized at its maximum of

Oracle 10g Tablespace Enhancements

Embed Size (px)

DESCRIPTION

gg

Citation preview

Oracle 10g Tablespace EnhancementsBy Jim CzuprynskiSynopsis. Oracle 10g's daunting array of new features like extended FLASHBACK tecnology! Auto"ated Storage #anage"ent! and $rid Co"%uting so"eti"es o&ersadow te "ore "undane '' yet no less i"%ressi&e( ' i"%ro&e"ents to its logical storage ca%a)ilities* +is article illustrates se&eral enance"ents to Oracle's already ro)ust logical storage structures! including te S,SA-. ta)les%ace! B/$F/L0 ta)les%aces! ta)les%ace grou%s! and ta)les%ace rena"ing*Oracle's highest-level logical container for data, the ta)les%ace, is a lot like an orphaned, lonely child. Tablespaces live in that lonely place between the physical raw data contained intheir datafiles and the myriad logical objects whose structure they organize, manage, and control tables, inde!es, and "O#s, to name just a few. $ was heartened to see that Oracle %&g has made some significant improvements to tablespaces that considerably e!tend the size, manageability, and cohesiveness of an Oracle database. $ will dive right into what $ believe is the most impressive new feature in this group the B/$F/L0 ta)les%ace.Size Does atter! B"#$"%E Tablespaces$ fondly remember buying my first $#' (T clone )* in the late %+,&s because it came with my first-ever hard drive. $ recall telling my co-workers that $ would never need to buy another )* because the new machine had a huge amount of storage -- -&'# - and had costme only an extra ./&&.&&. 0This machine's case is now a concrete-filled boat anchor somewhere in northern 1isconsin. $ filled up the hard drive in about si! months.23s the 4uality and 4uantity of storage media continues to grow, Oracle %&g has kept pace aswell. One of the major improvements in Oracle %&g is the introduction of new tablespace storage capacity. 3 tablespace is limited to a ma!imum of 56,675 05/82 datafiles, but each datafile's size had been limited by the ma!imum O9 file size. The new #$:;$"< tablespace overcomes this limitation by allowing the creation of a tablespace with only one datafile - but wat a datafile=3 #$:;$"< tablespace's datafile can now hold up to /,-+/,+5>,-+5 0yes, you read that correctly - the multiplier is over / )illion2 blocks of data storage space. This means that a tablespace could conceivably hold up to %-, T# of data if the ma!imum Oracle tablespace block size of 7-8 is used. Oracle does recommend that Auto"atic Seg"ent S%ace #anage"ent 1ASS#2 should be enabled. $n addition, if the #$:;$"< tablespace's datafile is sized at its ma!imum of %-,T#, then the ?@$;OA' e!tent management method will most likely yield better performance, especially when a large e!tent size is chosen.#$:;$"< tablespaces 0also known as #;Ts2 are therefore obviously aimed at 9torage 3rea @etwork 093@2 environments on which Oracle's new Auto"atic Storage #anage"ent 1AS#2 feature has been enabled. 0$ will cover the use of #$:;$"< tablespaces in the 39' environment more e!tensively in an upcoming article.2 The resulting increase in a database's potential size is staggering $f enough disk space is available, Oracle can now handle up to eigt exa)ytes of data 056,675 #$:;$"< datafiles ! %-,T# per datafile2.9ince #$:;$"< tablespaces are allowed to own only one datafile, there is now a one-to-one correspondence between tablespace and datafile, and database space management actually becomes much simpler because all space management operations that were only limited to datafiles now e!tend automatically to #$:;$"< tablespaces. ;or e!ample, $ can now resize a #$:;$"< tablespace just by issuing the &%TE' T&B%ES(&CE )b*t+name, 'ES"-E )ne.+size,/ command - $ don't have to worry about resizing its datafile0s2 separately.'igrating segments to a #$:;$"< tablespace is accomplished using the same methods already available to move tables and inde!es to different tablespaces. To migrate a table, the B#3 only has to issue the &%TE' T&B%E )table+name, O0E )b*t+name,/ command. $ssuing the &%TE' "1DE2 )in3e4+name, T&B%ES(&CE )b*t+name, 'EB5"%D O1%"1E/ command will migrate an inde! to a #$:;$"< tablespace.;inally, note that a pre-Oracle %&g CnormalC tablespace is now called a 9'3"";$"< tablespace, and that by default Oracle will continue to create 9'3"";$"