I got No active extraction maps on Goldengate while running Extract or Replicat Stats.
No active extraction maps
Details of error are as follows.
GGSCI (msdbadm01 as GGS_ADMIN19C@MSDB) 62> stats EMSDB01
Sending STATS request to EXTRACT EMSDB01 ...
No active extraction maps.
no active replication/extraction maps
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 <replicat group> "no active replication maps" GGSCI> STATS <extract group> "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.