Post to SQL Server stops with the following error in the Target event_log file:
Error 2025-12-08 19:38:50.639641 899233 3219834624 Poster: [SP-OPX01001] Errors on target table SCHEMA.TABLE_NAME at seqno/offset 1754/104641364. <CAUSE> error=0 state=HY104 msg=[Microsoft][ODBC Driver 18 for SQL Server]Invalid precision value. <ADVICE> Please see event_log and open target log files for more details. See 'http://advice.shareplex.com/SP-OPX01001' for additional advice and support. (posting from o.SOURCE_DB, queue test_queue, to r.TARGET_DB) [module opx]
The Target Post log file will contain the following:
xpst 2025-12-08 19:41:53.478444 899667 987248384 error_code=0 state=HY104 msg=[Microsoft][ODBC Driver 18 for SQL Server]Invalid precision value
xpst 2025-12-08 19:41:53.478499 899667 987248384 ora_type=96,c_type=1 sql_type=1, col_size=0 data=0x7fa33400b7f0,data_len=0, nchar_col_size=0
xpst 2025-12-08 19:41:53.478503 899667 987248384 buf=0x7fa33400b7f0 buf_sz=1 yes
xpst 2025-12-08 19:41:53.478506 899667 987248384 ind_ptr_8 0x7fa33401e910 ind_sz_8 = 39 buf=0x7fa33400b7f0 buf_sz=1 yes
xpst 2025-12-08 19:41:53.478513 899667 987248384 precision=1 scale=0 lob_hdr=0
xpst 2025-12-08 19:41:53.478515 899667 987248384 col_id=0 charset_id=873 charset_form=1 unicode=yes fractional_secs= -1
This can occur when a column in both the Source and Target databases is defined as a CHAR(1) data type.
The Source database is Oracle, and the Target database is SQL Server.
The resolution is to upgrade to SharePlex 12.2, where the issue does not occur.
A workaround is to define the column on the Target SQL Server databae as VARCHAR(1).
