About OGG & quot; LoadingdatafromfiletoReplicat & quot; key parameters for synchronizing partial records containing the lob field table
Key parameters for synchronizing partial records containing the lob field table in OGG "Loading data from file to Replicat"
First, describe one point:
The Loading data with an Oracle GoldenGate direct load method is unavailable for tables containing the following data types:
LOBs, LONGs, user-defined types (UDT), or any other large data type that is greater than 4 KB in size.
Therefore, you have to use the OGG "Loading data from file to Replicat" method to do the following:
1. the db version is 10gR2 (the test environment in this article is 10.2.0.5), because the impdp of 10gR2 does not have the remap_table Function
2. For a table (t1) containing the lob field, a part of data is synchronized to the same user (specifically, the same user in the database), but the table name (t1_temp) is changed)
Of course, the above requirements can also be implemented using hvr data synchronization software. The advantages of hvr are as follows:
Hvr can directly insert the row to be synchronized to the t1_temp table without generating a landing file (not a file that falls on the file system.
OGG "Loading data from file to Replicat" is first formed by the extract process of OGG to form a landing file (to form a file on the file system ), then, these files are read by the replicat process of OGG, converted into SQL statements, and executed in the database.
Of course, you can also use OGG "Loading data from file to database utility.
The key parameter mentioned in this article is the extract process parameter of OGG:
table test.t1_temp, SQLPREDICATE "where xh= '11'"
It can also be written in this way.
table test.t1_temp, SQLPREDICATE "where xh in (select xh from test.highgo_sync_row_xh)"
Test. highgo_sync_row_xh saves the xh value to be synchronized.