Alter of system generated index Post failing with ORA-01418: specified index does not exist. (4370306)

Alter of system generated index Post failing with ORA-01418: specified index does not exist.

When Posting an alter statement to a system generated index, fails with ORA-01418: specified index does not exist.

Notice 2023-01-22 00:46:35.204619 30345 3489658624 s:2 Poster: ORA-01418: specified index does not exist (posting from o.splexrac, queue SPLEX, to o.splexrac) [module osp]
Error 2023-01-22 00:46:35.207329 30345 3489658624 s:2 Poster: [SP-OPO01002] Post process stopped due to DDL error ORA-01418: specified index does not exist on SQL alter index "schema"."SYS_C0041310" rebuild tablespace T.... <CAUSE> Post received a DDL error from the target database. Message:[subque/seq 2/1938 seqno/offset 11192/638240004]. <ADVICE> 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 0 before starting Post. See 'http://advice.shareplex.com/SP-OPO01002' for additional advice and support. (posting from o.splexrac, queue SPLEX, to o.splexrac) [module opo]
Info 2023-01-22 00:46:35.332696 30310 2887940032 Poster exited with code=1, pid = 30345 (posting from o.splexrac, queue SPLEX, to o.splexrac)
 

When the system generated index is initially created on Source the name is generated by Oracle.
The create DDL statement is replicated to Target and the index is created under a different name generated by Oracle.
If the Source index is then altered, it is altered under the Source index name which is different to the Target index name, and hence the reason why Post cannot locate the index on Target.
 

The system generated index will need to be manually altered on Target.
Restart Post to ignore the DDL error and to allow for posting to continue.