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.
1
2
3
4
5
6
7
8
9
10
11
12
13
GGSCI>stats<replicat_name>
SendingSTATSrequesttoREPLICAT<replicat_name>...
Noactivereplicationmaps.
IntegratedReplicatStatistics:
Totaltransactions0.00
Redirected0.00
Replicatedprocedures0.00
DDLoperations0.00
Storedprocedures0.00
Datatypefunctionality0.00
Eventactions0.00
Directtransactionsratio0.00%
CAUSE
Source database is multitenant but target is not multitenant. Below has been mentioned in replicat parameter file
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.
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.
