Accumulation of problems in ogg oracle synchronization to PG

1 Scenario: ORACLE----PG source end has done an UPDATE operation, and if this record happens to be not in the corresponding table of the target end (various situations: deleted, not synchronized, etc.), if table A has three fields: aa, bb, cc SQL: update A table only modifies the aa field, and bb, cc fields have non-null constraints, then in this case, the error message of the R process, only the aa field will have a value, and the bb, cc fields are both Is set to null, then it will report a violation of the non-empty constraint

 解决办法：  dblogin
                         add trandata xxx.a ALLCOLS
                                             info trandata xxx.a

2 Scene: ORACLE----PG

      OGG  R 进程日志报  invalid byte sequence for encoding "UTF8"  \0x00

            解决办法：

            在 /opt/goldengate/dirprm中增加一个文件：char.txt
            文件内容为：
            SOURCECHARSET UTF-8
            TARGETCHARSET  UTF-8
            \x00 \x20

            在R进程的配置文件里增加一行：
            CHARMAP  /opt/goldengate/dirprm/char.txt

3 dblogin PG database in OGG

   export LD_LIBRARY_PATH=/opt/pgsql/lib:/opt/goldengate/lib
         export ODBCINI=/opt/goldengate/odbc/odbc_lych.ini
         cd /opt/goldengate
         ./ggsci
         dblogin sourcedb  xxx,userid xxx,password xxx