DYNAMICRESOLUTION | NODYNAMICRESOLUTION

有时候开启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, Oracle

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 389.