APPLIES TO:
Oracle GoldenGate - Version 10.4.0.78 and later
Information in this document applies to any platform.
SYMPTOMS:
1. When using SAMFS file system replicat may abend incompatible record error or Bad column Index error
Oracle GoldenGate (OGG) replicat abends with error about incompatible record
GGS ERROR 190 Incompatible record (101)
Checking the affected trail, the data looks good in the physical file
Re-starting replicat on an earlier RBA might help to overcome the issue
2.Replicat abend with Bad column Index
ERROR OGG-01161 Bad column index (##) specified for table <schema>.<table_name>,max columns = ##.
CAUSE:
The above said issues can occur any time the target file system uses AsyncIO. This includes the SAMFS file system.
OGG does not support any file system with async IO writes.
SOLUTION:
If an AsyncIO file system is used, caching should be disabled. If the problem persists, try disabling async io.
Note : This has not been tested for performance impact. Please check with your system administrator for the mount options.
Other workaround, is to change the file system to regular UFS filesystem. UFS filesystem does not need any specific mount options.
Incompatilbe record error can happen when trails are stored on NFS mounted file system. To avoid this please refer Doc ID 1232303.1 for the Mount options when configuring Oracle GoldenGate
REFERENCES:
BUG:10306932 - RFE: ADD SUPPORT FOR SAMFS
3-5543766031
=====================================
小結：OGG-01161很多問題是由於數據庫主備兩端的表結構發生該表導致，但是在某些情況下並非如此。例如此次事件就是由於備庫開啓了異步IO，解決此問題有兩種方式，（1）開啓異步IO，同事關閉cache。（2）使用同步IO。針對數據庫操作系統更傾向於第一種方式。
----thank you & best regards