-
Titre
Post stopped due to "Poster: ORA-12096: error in materialized view log on.." -
Description
The following errors are observed in the target event_log when Post is stopped due to ORA-12096:
Error 2019-07-18 17:51:42.659536 121621 3722688256 s:5 Poster: que/seq = 5/ 28353 seqno/offset = 210/392608552 Unexpected Oracle error: ORA-12096: error in materialized view log on "TABLE_OWNER"."TABLE_NAME" ORA-01843: not a valid month ORA-06512: at "TRIGGER_OWNER”.”TRIGGER_NAME", line 325 ORA-04088: error during execution of trigger “TRIGGER_OWNER”.”TRIGGER_NAME” (object name: "TABLE_OWNER"."TABLE_NAME") (posting from o.SOURCESID, queue QUEUE_NAME, to o.TARGETSID) [module opo]
Info 2019-07-18 17:51:43.612906 101181 383715168 Poster exited with code=1, pid = 121621 (posting from o.SOURCESID, queue QUEUE_NAME, to o.TARGETSID)
-
Cause
The trigger named above is enabled on the target database. -
Résolution
The trigger “TRIGGER_OWNER”.”TRIGGER_NAME” is enabled on the target. This is resulting in the error in materialized view log. Post will stop due to any Oracle error on the target except for those that are listed by default in oramsglist file.
To resolve the issue:
1.Disable the trigger “TRIGGER_OWNER”.”TRIGGER_NAME” on the target database. You can do so by:
SQL>ALTER TRIGGER <trigger_name> DISABLE;
2.Alternatively, you can also run the script sp_add_trigger.sql located in /proddir/util subdirectory (where proddir refers to SharePlex’s Product Directory). The script disables all the triggers on target database for the action of Post process. See SharePlex Reference Guide for details.
-
Informations supplémentaires
Here is the description of the Oracle error: ORA-12096: error in materialized view log on “”string“”.””string“” Cause: There was an error originating from this materialized view log. One possible cause is that schema redefinition has occurred on the master table and one or more columns in the log is now a different type than corresponding master column(s). Another possible cause is that there is a problem accessing the underlying materialized view log table. Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop the materialized view log and recreate it.