-
Title
Poster: 15022 - Error posting ODR_INSERT1 to table -
Description
Post stopped as follows when the target was resync'd using Oracle data pump while SP_OCT_REPLICATE_ALL_DDL was set to 1:
sp_ctrl (rtluseoradb02:2100)> show log reverse
Error 2013-12-13 01:46:12.644013 445 2261878624 Poster stopped: Internal error encountered; cannot continue (posting from SID1, queue queue_name, to SID2)
Error 2013-12-13 01:46:12.643209 445 2261878624 Poster: PreProcessLobMsg: object <id> not found (posting from SID1, queue queue_name, to SID2) [module opo]
Notice 2013-12-13 01:30:52.517409 32713 3181045504 s:2 Poster: Oracle error: ORA-00942: table or view does not exist. rowid:AABASQAABAABcL+AAA (posting from SID1, queue queue_name, to SID2) [module opo]
Warning 2013-12-13 01:30:52.516427 32713 3181045504 s:2 Poster: 15022 - Error posting ODR_INSERT1 to table "<owner>.<table_name>". (posting from SID1, queue queue_name, to SID2) [module opo]
-
Cause
The object "<owner>.<table_name>" does not exist on target. -
Resolution
Call Support for help in readreleasing (removing) messages pertaining to the problem object using qview utility. In future set SP_OCT_REPLICATE_ALL_DDL to 0 if application permits.
-
Additional Information
Enabling the parameter SP_OPO_DISABLE_OBJECT_NUM to ignore the problem object does not help. Setting SP_OPO_CONT_ON_ERR to 1 and configuring the file oramsglist to ignore ORA-00942 does not help either. Being a temporary object, it does not exist for long so it is not possible to create that object on target for Post to resume processing as its structure is not known anymore.