在部署OGG的时候遇到OGG-01960错误，OGG版本为ogg112101_fbo_ggs_Linux_x64_ora10g_64bit，数据库版本为10.2.0.4.0 for linux X86_64。

2013-04-19 15:21:54  ERROR   OGG-01960  Failed to validate table FMIS0200.ZWITEMSYW. The table is created with the NOLOGGING option, which is not supported.

Extract may not be able to capture data from it.

数据库应打开了force logging和SUPPLEMENTAL LOG，而且修改表的属性为logging后，问题依然存在。查看MOS(OGG Extract 11.2 abends with ERROR OGG-01960 Failed to validate table The table is created with the NOLOGGING option, which is not supported. [ID 1465720.1])，发现这是11.2及之后版本的OGG才有的问题，以下是该文章的描述。

Applies to:

Oracle GoldenGate - Version 11.2.1.0.1 and later

Information in this document applies to any platform

Symptoms

On : 11.2.1.0.1 version, EXTRACT executable

When starting the extract, the following error occurs:

ERROR

-----------------------

ERROR OGG-01960 Failed to validate table MSC.MSC_SUPPLIES. The table is created with the NOLOGGING option, which is not supported. Extract may not be able to capture data from it.

Cause

Prior to v11.2 extract logs a warning message and keeps the extract running which can cause data loss. When user upgrades from v11.1.1.1.x to 11.2, an extract abended with "ERROR OGG-01960 Failed to validate table." From OGG version 11.2 onward, the default behavior is to make the extract abend when it encounters a table/partition created with nologging option.

Solution

Workaround:

As a temporary workaround, DBOPTIONS ALLOWNOLOGGING can be added after USERID parameter in the extract parameter file. This parameter will cause the extract to log a warning message and continue to run. However, there is a chance for data loss. Resync in required.

To get the extract running:

1. edit params

2. Add the following parameter after USERID parameter

DBOPTIONS ALLOWNOLOGGING

3. Restart the extract

Note: However post the code change in bug 14158453 the parameter DBOPTIONS ALLOWNOLOGGING is no longer valid. Extract no longer relies on the table metadata (logging/ nologging) and instead uses special records in the redo log to detect missing data and when detected it would error as below indicating the object id of the table in question. 2012-08-02 09:10:09 ERROR OGG-01965 The redo record indicates data loss on object 167,946

Workaround:

The table can be excluded from the extract, enable logging at the table/ partition/ tablespace level and include it back in the extract if it needs to be replicated across.

Solution:

Change the table/partition created with NOLOGGING option to LOGGING option and resync the source and target tables.

ORACLE给出的解决方法是在EXTRACT进程的配置文件里加上DBOPTIONS ALLOWNOLOGGING参数，允许表是NOLOGGING属性，增加DBOPTIONS ALLOWNOLOGGING参数后，问题得到解决但这种方法是否存在其他潜在问题就不知道了。

由于客户有的应用系统已经部署过11.1.1.1.2版本的OGG，最终客户决定使用11.1.1.1.2版本的OGG而没有使用11.2版本的OGG，而11.1版本的OGG没有这个问题。

本文固定链接: http://www.dbdream.com.cn/2013/05/ogg-01960%e9%94%99%e8%af%af/ | 信春哥，系统稳，闭眼上线不回滚！