[SP OPO01002] Post process stopped due to DDL error ORA 10631: SHRINK clause should not be specified (4268102)

[SP OPO01002] Post process stopped due to DDL error ORA 10631: SHRINK clause should not be specified

s:4 Poster: [SP-OPO01002] Post process stopped due to DDL error ORA-10631: SHRINK clause should not be specified for this object on SQL ALTER TABLE "TABLE_OWNER"."TABLE_NAME" shrink space . Post received a DDL error from the target database. Message:[subque/seq 4/953960355 seqno/offset 304/429579576]. While Post is stopped, fix the problem so that this error does not occur again. Then, manually execute the correct DDL on the target and restart Post. (Note: On restart, Post will skip the original DDL that caused the error.) To configure Post to continue processing after it receives a DDL error, set the SP_OPO_STOP_ON_DDL_ERR parameter to 1 before starting Post. See 'http://advice.shareplex.com/SP-OPO01002' for additional advice and support. (posting from HOSTNAME, queue queueame, to HOSTNAME) [module opo]

ORA-10631:SHRINK clause should not be specified for this object

This is an Oracle error, the error is due to the fact that an object you are trying to shrink has an “function-based” index on it. Objects with function-based indexes cannot be shrunk. To reclaim the space you need to drop and re-add the function-based index after shrinking the object.

1. Issue the DDL in the correct sequence on source.
2. For example:

• drop index TABLE_OWNER.IDX_TABLE_OWNER_UPDATEDATE;
• alter table TABLE_OWNER.TABLE_NAME enable row movement;
• alter table TABLE_OWNER.TABLE_NAME shrink space;
• CREATE INDEX "TABLE_OWNER"."IDX_TABLE_OWNER_UPDATEDATE ON "TABLE_OWNER"."TABLE_NAME" (TRUNC("UPDATEDDATE"));