SharePlex 10.2.1 - Installation and Setup Guide

Continue to post when there is a DML error

SharePlex provides a way for Post to continue processing after it encounters a DML error, rather than stop.

Continue posting on Oracle and SharePlex errors

Valid for Oracle targets

When SharePlex posts to an Oracle target, you can configure Post to ignore specific Oracle DML errors and specific SharePlex error messages and continue processing. Post determines which messages to ignore based on the list in the oramsglist file. The file is installed with a small list of errors by default, but you can remove any of them as desired.

When Posts ignores an error, it writes the error to the SharePlex Event Log. Post also logs the error and the SQL statements that caused the error to the Error log. This log is named SID_errlog.sql log file and is stored in the data directory in the SharePlex variable-data directory. For more information, see View events and errors.

Note: There are certain errors that Post will not ignore, and it will stop for those messages even if they are listed in the oramsglist file.

Important: Use caution when using this feature. It could result in hidden out-of-sync conditions. Enable this parameter only if your target users cannot tolerate replication lag and it is acceptable to have some out-of-sync data. Check the SID_errlog.sql log frequently to see if there were errors that could cause replication problems.

To configure Post to continue on errors

1. On the target system, change directories to the data sub-directory of the SharePlex variable-data directory.

2. Find the oramsglist file.

3. If replication is not active, open the file in a text editor. If replication is active, make a copy of the file and then open the copy in the editor.

4. Increase the number on the first line by the number of errors that you are adding. This number must be equal to the total number of errors that are in the file. For example, in the following file there are 10 errors listed.

   ora@sys1dad > vi oramsglist
   10
   604
   900
   902
   908
   909
   910
   911
   932
   960
   1026

5. Starting at the end of the file, add the number of each Oracle or SharePlex error, one per line as shown in the preceding example. The messages need not be in numerical order.

6. Save and close the file.

7. Stop Post (if running).

   sp_ctrl> stop post

8. If you edited a copy of the oramsglist file, save the copy to the original name of oramsglist.

9. Change the value of the SP_OPO_CONT_ON_ERR parameter to 1. Or change the value to 2 to also continue posting on table errors listed in the oramsglist file. See the SharePlex Reference Guide for a description of the SP_OPO_CONT_ON_ERR parameter.

   sp_ctrl> set param SP_OPO_CONT_ON_ERR 1

10. Start Post.

    sp_ctrl> start post

Continue posting on ODBC errors

Valid for Open Target

When SharePlex posts to an Open Target target, you can configure Post to ignore ODBC errors and continue processing. Post writes the error to the SharePlex Event Log. Post also logs the error and the SQL statements that caused the error to the Error log. This log is named ID_errlog.sql log file, where ID is the database identifier. The file is stored in the data directory in the SharePlex variable-data directory. For more information, see View events and errors.

Important: Use caution when using this feature. It could result in hidden out-of-sync conditions. Enable this parameter only if your target users cannot tolerate replication lag and it is acceptable to have some out-of-sync data. Check the SID_errlog.sql log frequently to see if there were errors that could cause replication problems.

To configure Post to continue on errors

1. On the target system, change directories to the data sub-directory of the SharePlex variable-data directory.

2. Look for one of the following files, depending on the database. These files are installed empty.

   File name	Supported database
   postgresmsglist	Postgres
   sqlservermsglist	Microsoft SQL Server
   mysqlmsglist	Oracle MySQL

   Note: There are certain errors for which Post will stop, even if you list those errors in the message file.

3. If replication is not active, open the file in a text editor. If replication is active, make a copy of the file and then open the copy in the editor.

4. Starting at the end of the file, add the number of each error, one per line as shown in the example. The messages need not be in numerical order.

   Example:

   sqlservermsglist:

   8102

   8180

   544

   2627

   3621

5. Save and close the file.

6. Stop Post (if running).

   sp_ctrl> stop post

7. If you copied the original file, save it back to its original name.

8. Change the value of the SP_OPX_CONT_ON_ERR parameter to 1.

   sp_ctrl> set param SP_OPX_CONT_ON_ERR 1

9. Start Post.

   sp_ctrl> start post