Ora 14402 updating partition key column

27-Sep-2020 12:57

First, let's get a record of the current ROWIDs for each office and then delete two rows.Interestingly enough, the ROWIDs for the two remaining rows are different from their original IDs before the delete statement.Or two offices in the same city (from different groups or business units within the same company) merge into one location?You could split the default partition and add the new location name.Further, a shrink operation (without the COMPACT option) can invalidate open cursors. We looked at three major operations where row movement is required: partition key value change, flashback and space management.Enabling and disabling row movement is very simple to implement, and in most cases, has no unwanted side effects. Does a row move to another table, or is row movement constrained to the row's container (i.e., a table)?This article looks at three common cases or situations where row movement needs to be enabled.

ora 14402 updating partition key column-90

A list partition where the partition key is a specific value is a good example of this.

I find it handy to keep the flashback syntax around in an easily (and quickly) identifiable location, and that is chiefly because I don't use timestamps that much in my applications.

Time is still somewhat of the essence and the quicker you can recover the table to a good state, the better.

Let's create a quick partitioned table example and see how moving a row works.

2 ( 3 OFFICE_NUMBER NUMBER NOT NULL, 4 CITY_ID VARCHAR2(12) NOT NULL, 5 OFFICE_NAME VARCHAR2(30) NOT NULL 6 ) 7 PARTITION BY LIST (CITY_ID) 8 ( 9 PARTITION P282 VALUES ('282'), 10 PARTITION P283 VALUES ('283'), 11 PARTITION P284 VALUES ('284')); Table created.

A list partition where the partition key is a specific value is a good example of this.I find it handy to keep the flashback syntax around in an easily (and quickly) identifiable location, and that is chiefly because I don't use timestamps that much in my applications.Time is still somewhat of the essence and the quicker you can recover the table to a good state, the better.Let's create a quick partitioned table example and see how moving a row works.2 ( 3 OFFICE_NUMBER NUMBER NOT NULL, 4 CITY_ID VARCHAR2(12) NOT NULL, 5 OFFICE_NAME VARCHAR2(30) NOT NULL 6 ) 7 PARTITION BY LIST (CITY_ID) 8 ( 9 PARTITION P282 VALUES ('282'), 10 PARTITION P283 VALUES ('283'), 11 PARTITION P284 VALUES ('284')); Table created.Using ROWIDs to perform DML on records can be wicked fast, and is virtually the fastest way to access a row.