One, the source side
Sourceistable
Sourcedb Oracle
Rmthost 127.0.0.1, Mgrport 7820
Rmtfile D:\ogg\oracle\dirdat\i1
Table Dbo.t_v;
Table dbo.t_t;
Two, Target side
Specialrun
End RUNTIME
Setenv (Nls_lang =american_america. ZHS16GBK)
UserID Ogg,password Xifenfei
Extfile D:\ogg\oracle\dirdat\i1
Sourcedefs D:\ogg\oracle\dirdef\t_v.def
Discardfile D:\ogg\oracle\dirtmp\repsz.dsc,append,megabytes 100
MAP "Dbo.t_v", Target mssql.t_v;
MAP "dbo.t_t", Target mssql.t_t
, Colmap (id = id, text_t = @binary (T_text));
Third, the implementation
Extract Paramfile DIRPRM\EINIT1.PRM reportfile dirrpt\einit1.rpt
Replicat paramfile DIRPRM\RINIT1.PRM reportfile dirrpt\rinit1.rpt
Iv. Test Instructions
More Wonderful content: http://www.bianceng.cn/database/Oracle/
If the large segment of the database is too long, such as the type of text field here is too long, there is data in the L1, but there is no corresponding data in the target database, the initial analysis may be:
1, the Defgen definition file determines the length of the file to cause
2, target-side coding and CLOB column related restrictions (unlikely)
3, goldengate software inherent mechanism, but also need to thoroughly read the official website documents
4, now as if to the target end of the final length of 4000byte (according to the database encoding different Chinese characters, letters, numbers), in this test, if the source end of the use of Ntext,target can only receive 1000 characters, if the text type, Can accept 1333 Chinese characters.
5, test Environment Description: SQL Server to Oracle 11g,source end table (ID int primary key auto,t_text text), Target side (ID number primary key,text_t Clob
-An unexpected cause has been found (February 22, 2011 23:27:51)
When the size of a large object exceeds 4 K, Oracle Goldengate stores the "data in segments within" Oracle Goldengate TRA Il. The 4K is stored in the base segment, and the rest are stored in a series of 2K segments. Oracle Goldengate does not support the filtering, column mapping, or manipulation of large to this size. Full Oracle goldengate functionality can is used for objects that are 4K or smaller.
The general meaning is that when the content is more than 4k, you cannot use filtering, column mapping, or the operation of large characters, when the content is equal to or less than 4k, all the goldengate functions can be used. The problem is that when the T_text content is greater than 4k, large object operations cannot be performed.
Question: What to do when there is more data than 4k
-Test test (February 23, 2011 23:34:13)
After initialization, when synchronizing a database, heterogeneous databases have different column types (for example, text in MSSQL to CLOB in Oracle), and you must use Sourcedefs to convert a column type using the appropriate function (for example: Colmap (id = id, t_lob = @ Binary (T_lob)), for data larger than 4k, or as initialization cannot be processed. The problem waits for a solution
Author: 51cto Oracle small-mixed son