Database Tuning (MOSC)

MOSC Banner

Extended Data Types and chained rows

in Database Tuning (MOSC) 5 commentsAnswered ✓

Hi,

One of applications running on our database stores its data in a huge number of tables, most of which have a small number of rows. Developers want it badly to have many varchar2(32000) columns in these tables. Most part of these columns are business attributes, and their length should not be more than 100, but developers say that they want to store in tables any incoming information, even garbage entered by mistake, so they extend length of columns. In reality 'garbage' is a very small number of rows, in a very small number of tables.

Extended data types create implicit LOBs and DBA does not have control over initial size of these LOBs. So for many tables database stores 64k table segment, 64k LOB index segment and 1m LOB segment.

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