OGG不抽取或不应用数据No active extraction maps 或 No active replication maps

0    125    1

👉 本文共约1937个字,系统预计阅读时间或需8分钟。

No active extraction maps.

现象

感觉extract进程不工作,所有进程也不报错,使用stats统计时返回No active extraction maps.

解决

1、若是SQL Server数据库,则所有进程的参数文件配置中,表名前不能加数据库名。

例如:

错误写法:TABLE testing.dbo.*;

正确写法:TABLE dbo.*;

2、尝试做UPDATE和DELETE等DML操作。

3、尝试添加DYNAMICRESOLUTION 参数。

4、尝试查询select count(*) from DBA_GOLDENGATE_SUPPORT_MODE;视图。如果查询很久都不能出结果,那么,可能碰到数据库的bug了,需要修改该视图的定义。

我的情况是,Oracle 11.2.0.4的环境,业务表大约有2万个表,但是查询该视图很久不能出结果。解决办法,使用sys执行如下代码:

然后查询select count(*) from DBA_GOLDENGATE_SUPPORT_MODE;视图可以秒出。

该问题耗费了我3天时间,具体可以参考:https://www.xmmup.com/shitudba_goldengate_support_modeyinqidejichengmoshioggbutongbuwentipaichaguocheng.html

No active replication maps

解决

1、源端是cdb,而目标端是非cdb,那么修改如下修改:

2、检查dump或extract的trail文件是否有内容生成

3、尝试重启replicate进程

Replicat Is Not Applying Changes To Database (文档 ID 2648750.1)

APPLIES TO:

Oracle GoldenGate - Version 12.3.0.1.4 and later
Information in this document applies to any platform.

SYMPTOMS

Configured a new GG setup. The extract/pump are up and running at the source and the replicat is up and running at the target. The extract is picking transactions from the source Database and the pump is sending it to the target server as appropriate. However, Replicat is reading the trail file sent by the Pump but not applying the changes to the target database.

CAUSE

Source database is multitenant but target is not multitenant. Below has been mentioned in replicat parameter file

SOLUTION

Please remove below parameter

--> SOURCECATALOG

and mention like below in replicat

--> MAP .., TARGET .;

本人提供Oracle、MySQL、PG等数据库的培训和考证业务,私聊QQ646634621或微信db_bao,谢谢!

DYNAMICRESOLUTION参数

Sometimes the OGG process is slower. It may be because there are too many tables to be synchronized. OGG will create a record and save it to disk before the process is started. This takes a lot of time. Use this parameter to resolve this issue.

有时候开启OGG进程的时候较慢,可能是因为需要同步的表太多,OGG在开启进程之前会将需要同步的表建立一个记录并且存入到磁盘中,这样就需要耗费大量的时间。OGG同时也提供了DYNAMICRESOLUTION | NODYNAMICRESOLUTION参数来解决这个问题,看官方如何描述的:

DYNAMICRESOLUTION | NODYNAMICRESOLUTION

Valid for Extract and Replicat
Use the DYNAMICRESOLUTION and NODYNAMICRESOLUTION parameters to control how table names are resolved.

Use DYNAMICRESOLUTION to make processing start sooner when there is a large number of
tables specified in TABLE or MAP statements. By default, whenever a process starts,
GoldenGate queries the database for the attributes of the tables and then builds an object
record for them. The record is maintained in memory and on disk, and the process of
building it can be time-consuming if the database is large.

DYNAMICRESOLUTION causes the object record to be built one table at a time, instead of all at
once. A table’s attributes are added to the record the first time its object ID enters the
transaction log, which occurs with the first extracted transaction on that table. Recordbuilding
for other tables is deferred until activity occurs. DYNAMICRESOLUTION is the same as
WILDCARDRESOLVE DYNAMIC.

NODYNAMICRESOLUTION causes the object record to be built at startup. This option is not
supported for Teradata. NODYNAMICRESOLUTION is the same as WILDCARDRESOLVE IMMEDIATE.
For more information about WILDCARDRESOLVE, see page 368.

STATS COMMAND Displays "No Active Replication/Extraction Maps" (文档 ID 967319.1)

APPLIES TO:

Oracle GoldenGate - Version 4.0.0 and later
Information in this document applies to any platform.

GOAL

Provide additional information to the user on why the STATS COMMAND Displays "no Active Replication/extraction Maps".

SOLUTION

Issue:

STATS COMMAND displays "no active replication/extraction maps"

Solution Summary:

This internal mapping table used by the extract and/or replicat process to build statistics must be created.

Solution Description:
GGSCI> STATS
"no active replication maps"

GGSCI> STATS
"no active extraction maps"

Directly related to the usage of the DYNAMICRESOLUTION parameter

During normal (without DYNAMICRESOLUTION parameter) start-up for extract and replicat the processes query the database for the attributes of the tables that are being processed. i.e.the list of tables in the include files that you have in your parameter files and builds an internal mapping table. The DYNAMICRESOLUTION parameter prevents this from happening at start-up.

The mapping table is not built in extract until the object ID of a table in the parameter file is read from the transaction log. If no transaction log records have been read and processed by the extract process, the internal mapping table has not been built.

In the replicat process, the internal mapping table is built when a record is read from the input trail that matches one of the tables in the parameter file. If there are no records on the replicat input trail or there are records but they do not match the tables in the map/target parameter statements the internal mapping table has not been built.

This internal mapping table is used by the extract and/or replicat process to build statistics. If this table is not built, there is nothing for the STATS command to use to create the statistics report.

The message that is displayed indicates that nothing has been processed in the extract or replicat that contains a DYNAMICRESOLUTION parameter. Once data for the tables in the extract and replicat are processed (captured from or applied to DB) the STATS command produces processing statistics.

总结

1、bug问题

2、进程参数配置问题

标签:

头像

小麦苗

学习或考证,均可联系麦老师,请加微信db_bao或QQ646634621

您可能还喜欢...

发表回复

您的电子邮箱地址不会被公开。 必填项已用*标注

4 × 3 =

 

嘿,我是小麦,需要帮助随时找我哦
  • 18509239930
  • 个人微信

  • 麦老师QQ聊天
  • 个人邮箱
  • 点击加入QQ群
  • 个人微店

  • 回到顶部
返回顶部