DYNAMICRESOLUTION | NODYNAMICRESOLUTION

Sometimes it is slow to start the OGG process. It may be because too many tables need to be synchronized. Before enabling the process, OGG creates a record for the table to be synchronized and stores it to the disk, this takes a lot of time. OGG also provides the DYNAMICRESOLUTION | NODYNAMICRESOLUTION parameter to solve this problem. For details, refer to the official descriptions:

Sometimes it is slow to start the OGG process. It may be because too many tables need to be synchronized. Before enabling the process, OGG creates a record for the table to be synchronized and stores it to the disk, this takes a lot of time. OGG also provides the DYNAMICRESOLUTION | NODYNAMICRESOLUTION parameter to solve this problem. For details, refer to the official descriptions:

Sometimes it is slow to start the OGG process. It may be because too many tables need to be synchronized. Before enabling the process, OGG creates a record for the table to be synchronized and stores it to the disk, this takes a lot of time. OGG also provides the DYNAMICRESOLUTION | NODYNAMICRESOLUTION parameter to solve this problem. For details, refer to the official descriptions:

DYNAMICRESOLUTION | NODYNAMICRESOLUTIONValid for Extract and ReplicatUse the DYNAMICRESOLUTION and NODYNAMICRESOLUTION parameters to control how tablenames are resolved. use DYNAMICRESOLUTION to make processing start sooner when there is a large number oftables specified in TABLE or MAP statements. by default, whenever a process starts, OracleGoldenGate queries the database for the attributes of the tables and then builds an objectrecord for them. the record is maintained in memory and on disk, and the process ofbuilding 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 atonce. A table's attributes are added to the record the first time its object ID enters thetransaction log, which occurs with the first extracted transaction on that table. recordbuildingfor other tables is deferred until activity occurs. DYNAMICRESOLUTION is the same asWILDCARDRESOLVE DYNAMIC. NODYNAMICRESOLUTION causes the object record to be built at startup. this option is notsupported for Teradata. NODYNAMICRESOLUTION is the same as wildcardresolve immediate. for more information about WILDCARDRESOLVE, see page 389.