When shareplex replicates all ddls, poster exits on 9i ddl error due to "ORA-01843" not a valid month when the ddl statement has date column.
For example, this is a partial statement of a successfull ddl statement from source.
from r474 a
where a.tr_erech = '31 dec 2010'
and a.kod_hishtatfut <>0
and a.kod_buza_shiaruch <> 999
When shareplex processes (capture, reader, and poster) log into shareplex, the first thing it does is "alter session set nls_date_format = "MMDDYYYYHH24MISS";". As the result, they will expect date column to have a correct format: "MMDDYYYYHH24MISS".
Unlike DML statements which shareplex processes will capture, parse, and reconstruct them in the correct syntax, shareplex captures DDL statements as they are and send down to target. As the result, any DDL statements that does not have correct date format "MMDDYYYYHH24MISS", depending on the setting of SP_OPO_STOP_ON_DDL_ERR either poster exits or reports the error and moves forward.
1. on SOURCE prior to issue DDL, issue this command "alter session set nls_date_format = "MMDDYYYYHH24MISS" and use the right syntax for date.
2. on TARGET sp_ctrl> set param SP_OPO_STOP_ON_DDL_ERR 0
This instructs poster to not stop when a ddl error occur, and it is applies to all ddl statements.
this may also apply to invalid date, invalid day, invalid year.
Note: This will cause the table to be out of sync.
