Database DataWarehousing (MOSC)

MOSC Banner

Interval Range Partition Table - Problem with round-robin store in clause - tablespace management

edited Oct 27, 2011 3:54AM in Database DataWarehousing (MOSC) 2 commentsAnswered
Setting up a new 11.2 database.  Our current database is 10.2.  Trying to use range interval partitioning on a large partitioned table.  The internal partition field is ID, with an  interval of 25,000.  The ID in the table is the unique primary key. The table holds blob data, medial record attachments, typically image files.   Relatively speaking, the blobs are large. Each partition has its OWN DEDICATED tablespace.   Each partition/tablespace ends up with as stated already, 25,000 entries. Currently each partition/tablespace holds about 2 days worth of rows, then we move to the next partition/tablespace It’s of primary importance that each partition has its OWN tablespace. In Oracle 10.2 this have been a very manual

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center