The following error shows up in target event log:
Warning 2015-07-20 12:36:32.117552 3895 18 s:2 Poster: 15022 - Error posting ODR_UPDATE1 to table "TARGET_OWNER1"."TARGET_TABLE". (posting from SID1, queue queue_name, to SID2) [module opo]
Notice 2015-07-20 12:36:32.119967 3895 18 s:2 Poster: Oracle error: ORA-01410: invalid ROWID. rowid:AAAgpOABpAAA5LJAAj (posting from SID1, queue queue_name, to SID2) [module opo]
TROUBLESHOOTING:
To verify if this is indeed the case, set the debug on Post as follows:
sp_ctrl>set param sp_opo_debug_flag queue <queue_name> 0x1f000085
sp_ctrl>stop post
sp_ctrl>start post
Once it stops due to error, reset the debug by:
sp_ctrl>reset param sp_opo_debug_flag queue <queue_name>
Then examine the latest *opo* log in /vardir/log directory to see if errors like below show up:
opo 2015-07-21 22:25:07.784694 29957 1 StDispatch
opo 2015-07-21 22:25:07.784757 29957 1 StDispatch: 126(0).67748-3(74823067) ODR_UPDATE1 "TARGET_OWNER2"."TARGET_TABLE" 133710 AAAgpOABfAAEGJOAAB 91737/20811280 14131600537187 2487502663384 fwd:1
opo 2015-07-21 22:25:07.784781 29957 1 StDispatch
opo 2015-07-21 22:25:07.784810 29957 1 StDispatch: 126(0).67748-3(74823067) ODR_UPDATE1 "TARGET_OWNER1"."TARGET_TABLE" 133710 AAAgpOABfAAEGJOAAB 91737/20811280 14131600537187 2487502663385 fwd:1
opo 2015-07-21 22:25:07.784831 29957 1 StDispatch
That would be indicative of the same source table replicating to two different target tables in same named post queue. This is not supported. It indicates that post send the same message twice but with different target schema owner and same offset and same source rowid. That would cause the ORA-1410 since we updated to a different table with same source rowid message and the next update tried to use a target rowid that belongs to a different table which is invalid rowid.
RESOLUTION:
To fix the problem, carry out the following steps:
Make a copy of the currently active config file
Edit it to move one of the target tables via a different named Post queue
Activate the copy
Sync the table that is out of sync due to ORA-01410
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center