Database Administration (MOSC)

MOSC Banner

Need more explanation about Doc ID 238519.1 (Updating a Row with More Than 255 Columns Causes Row Ch

edited Sep 1, 2017 10:55AM in Database Administration (MOSC) 5 commentsAnswered ✓

Is there any document that explains more on Doc ID 238519.1.

I don't understand the fixes suggested. Here is the fixes posted:

"

fix:

Ensure both rowpieces are populated when the row is initially inserted: this

prevents the migration when the NULL columns are populated.

Fix1

~~~~

Ensure the last column is populated on insert

Fix2

~~~~

Add an additional dummy column at the end that can be populated.

"

Currently my table has has 291 columns.

Does the author mean that I will not get row chaining when doing row(s) update/insert if I add to the end a dummy non-null column (auto fill default value)?

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