Ora-14402 updating partition key

Ora-14402 updating partition key

It will update every single index on this table, and delete the old entry and insert a new one. It will have the same net effect as c.

By Steve Callan One of the relatively newer features in Oracle concerns the moving of rows. That could spell trouble for an application.

Even in this small tableAll legitimate Oracle

Tablespaces are about ease of administration, not performance so much. This article looks at three common cases or situations where row movement needs to be enabled. We were thinking of creating list parition for processed flag, but update will result into row movement.

Feel free to ask questions on our Oracle forum. Also, row movement must be enabled. Appreciate your input very much. Space Management The third and final example of where row movement comes into play can be found in shrink operations.

You could split the default partition and add the new location name. Time is still somewhat of the essence and the quicker you can recover the table to a good state, the better.

Many partitioned table examples use regions, cities and states as list examples. You need to understand that, internally, row movement is done as if you had in fact deleted the row and reinserted it.

Every row, every single row, will move. Enabling and disabling row movement is very simple to implement, and in most cases, has no unwanted side effects. You probably want to have multiple de-queuers, prioritization, and many other features people expect of queues.

Well tables areYou could split theThat could spell trouble for anTime is still somewhat of theBy Steve Callan One of the

Well, tables are partitioned for a reason, and to help ensure data goes where it is supposed to, you should disallow inadvertent updates or row movements. Even in this small table, we should be able to reclaim some space, so let's try shrinking the table. All legitimate Oracle experts publish their Oracle qualifications.