goldengate extract process abending caused by nologging DDL

I use goldengate(for oracle) to do a SCHEMA synchronized,include DDL operrations. when the the EXTRACT process was running to capture the changes ,then if you try do a DDL such as "alter table t_a no logging" on the capture table will cause EXT process ABENDING, I hit these errors today.
ogg version:
Oracle GoldenGate Command Interpreter for Oracle
Version 11.2.1.0.1 OGGCORE_11.2.1.0.1_PLATFORMS_120423.0230_FBO
Linux, x64, 64bit (optimized)

# vi ggserr.log
"
2013-01-30 14:25:45 WARNING OGG-00455 Oracle GoldenGate Capture for Oracle, ext1.prm: Problem in resolving [HYSH.NCME_MAP]: Failed to validate table HYSH.
NCME_MAP. The table is created with the NOLOGGING option, which is not supported. Extract may not be able to capture data from it., try to fix this issue in
order to avoid possible fatal error.
2013-01-30 14:25:45 INFO OGG-00476 Oracle GoldenGate Capture for Oracle, ext1.prm: Gathering metadata for [HYSH.NCME_MAP] not successful even though ob
ject was resolved, retrying [4] times with 1 second interval.
2013-01-30 14:25:46 WARNING OGG-00455 Oracle GoldenGate Capture for Oracle, ext1.prm: Problem in resolving [HYSH.NCME_MAP]: Failed to validate table HYSH.
NCME_MAP. The table is created with the NOLOGGING option, which is not supported. Extract may not be able to capture data from it., try to fix this issue in
order to avoid possible fatal error.
2013-01-30 14:25:46 INFO OGG-00476 Oracle GoldenGate Capture for Oracle, ext1.prm: Gathering metadata for [HYSH.NCME_MAP] not successful even though ob
ject was resolved, retrying [3] times with 1 second interval.
2013-01-30 14:25:47 WARNING OGG-00455 Oracle GoldenGate Capture for Oracle, ext1.prm: Problem in resolving [HYSH.NCME_MAP]: Failed to validate table HYSH.
NCME_MAP. The table is created with the NOLOGGING option, which is not supported. Extract may not be able to capture data from it., try to fix this issue in
order to avoid possible fatal error.
2013-01-30 14:25:47 INFO OGG-00476 Oracle GoldenGate Capture for Oracle, ext1.prm: Gathering metadata for [HYSH.NCME_MAP] not successful even though ob
ject was resolved, retrying [2] times with 1 second interval.
2013-01-30 14:25:48 WARNING OGG-00455 Oracle GoldenGate Capture for Oracle, ext1.prm: Problem in resolving [HYSH.NCME_MAP]: Failed to validate table HYSH.
NCME_MAP. The table is created with the NOLOGGING option, which is not supported. Extract may not be able to capture data from it., try to fix this issue in
order to avoid possible fatal error.
2013-01-30 14:25:48 INFO OGG-00476 Oracle GoldenGate Capture for Oracle, ext1.prm: Gathering metadata for [HYSH.NCME_MAP] not successful even though ob
ject was resolved, retrying [1] times with 1 second interval.
2013-01-30 14:25:49 WARNING OGG-00455 Oracle GoldenGate Capture for Oracle, ext1.prm: Problem in resolving [HYSH.NCME_MAP]: Failed to validate table HYSH.
NCME_MAP. The table is created with the NOLOGGING option, which is not supported. Extract may not be able to capture data from it., try to fix this issue in
order to avoid possible fatal error.
2013-01-30 14:25:49 ERROR OGG-00521 Oracle GoldenGate Capture for Oracle, ext1.prm: Object was resolved, however in the same resolution call both DDL hi
story and database metadata resolution failed, cannot recover, SCN [3631144], object id [56605].
2013-01-30 14:25:49 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, ext1.prm: PROCESS ABENDING.
....
2013-01-30 15:01:46 WARNING OGG-01961 Oracle GoldenGate Capture for Oracle, ext1.prm: NOLOGGING option is detected on table HYSH.NCME_MAP. Redo for this t
able is not available for capture by Extract.
"

SQL> select force_logging from v$database;
FOR
---
YES
SQL> select objectid,optime,startscn,metadata_text from GGMGR.GGS_DDL_HIST where objectname='NCME_MAP' and fragmentno=1 order
  2  by 3
  3*
SQL> /
  OBJECTID OPTIME                STARTSCN METADATA_TEXT
---------- ------------------- ---------- --------------------------------------------------
     56605 2013-01-30 14:25:29    3631129 ,G1='ALTER TABLE ncme_map nologging
                                           ',
     56605 2013-01-30 14:27:38    3631185 ,G1='ALTER TABLE ncme_map logging
                                           ',
     56605 2013-01-30 14:30:27    3631252 ,G1='ALTER TABLE ncme_map LOGGING
                                           ',
     56605 2013-01-30 14:30:28    3631271 ,G1='ALTER TABLE ncme_map LOGGING
                                           ',

TIP:
MY OGG MANAGER user is GGMGR,capture hysh schema change.
at 2013-01-30 14:25:29,a nologging DDL operation on the tablle.when force logging option was introduced on database level . then Oracle Database ignores any NOLOGGING setting on table level until the database is taken out of force logging mode.
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.
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.

GGSCI () 2> edit params ext1
--Add the following parameter 
DBOPTIONS ALLOWNOLOGGING
GGSCI () 1> start ext ext1
GGSCI () 1> info all
Program     Status      Group       Lag at Chkpt  Time Since Chkpt
MANAGER     RUNNING                                           
EXTRACT     RUNNING     EXT1        00:00:00      00:00:08   

extend read:

skip a transaction in goldengate(跳过一个事务OGG)