About OGG "Loading data from File to Replicat" synchronizing key parameters for partial records containing LOB field tables

About OGG "Loading data from File to Replicat" synchronizing key parameters for partial records containing LOB field tables

Let's start by stating:
Loading data with an Oracle GoldenGate direct load This method is not available for table with the following data types:

LOBs, LONGs, user-defined types (UDT), or any other large the data type is greater than 4 KB in size.

Therefore, when encountering the following requirements, we have to use OGG "Loading data from file to Replicat" This method to do:

1. DB version is 10GR2 (test environment for this article is 10.2.0.5) because 10GR2 IMPDP has no remap_table function

2. The table containing the LOB field (T1), synchronizes a portion of the data to the same user (exactly the same user in the database), just a table name (T1_TEMP)

Of course, such as the requirements, you can also use HVR data synchronization software to do. At this point, the advantages of HVR are shown:
HVR does not form a landing file (does not form a file that falls on the file system), you can insert the row you need to synchronize directly into the T1_temp table.

Ogg "Loading data from the file to Replicat" This method is first by the Ogg extract process to form a floor file (to form a file on the file system), and then by the Ogg Replicat process read these files, into SQL statements, Execute these statements in the database.

Of course, you can also use Ogg "Loading data from the file to the database utility" to do.

The key parameters described in this article are the parameters of the Ogg extract process:

You can write it like that.

Table Test.t1_temp, Sqlpredicate "where XH in (select XH from Test.highgo_sync_row_xh)"

Where Test.highgo_sync_row_xh saves the values of the XH that need to be synchronized.

About OGG "Loading data from File to Replicat" synchronizing key parameters for partial records containing LOB field tables