Database DataWarehousing (MOSC)

MOSC Banner

Partitioning strategy for index - LOCAL or GLOBAL

edited Jun 3, 2013 9:13PM in Database DataWarehousing (MOSC) 3 commentsAnswered

Hi,
We are converting one of our heap tables (TRX_TAB) into a partitioned one

The table has 2 B-tree indices and one Primary Key Constraint

FIrst index is based on a single column - TRX_ID
Second index is a composite index consisting of 2 columns; 1. CUST_ID and 2. TRX_DATE (in that order)
Primay Key is based on a single column - TRX_SEQ (this is based on oracle sequence)
There are 40 other columns which are varchar2 data type and couple of DATE data type

The database os OLTP and the table is used to store transactional data, dating back to year 2002

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

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center