Golden Gate Replicates Abends -Error With Default Mapping. No Matching Fields Found In Source And Target
(Doc ID 2788401.1)
Last updated on JANUARY 04, 2024
Applies to:
Oracle Utilities Advanced Spatial and Operational Analytics - Version 2.7.0.0.0 and laterInformation in this document applies to any platform.
Goal
On : 2.7.0.0.0 version, System Wide
Golden gate replicates abends -Error with default mapping. No matching fields found in source and targat
Ex:-
OGG-02756 The definition for table CISADM.W1_STOCK_TRANS is obtained from the trail fil
021-05-26 10:47:03 INFO OGG-05520 Input trail file encryption: AES128.
2021-05-26 10:47:03 INFO OGG-03522 Setting session time zone to source database time zone 'GMT'.
2021-05-26 10:47:03 INFO OGG-03506 The source database character set, as determined from the trail file, is UTF-8.
2021-05-26 10:47:03 INFO OGG-06505 MAP resolved (entry CISADM.F1_EXT_LOOKUP_VAL): map "CISADM"."F1_EXT_LOOKUP_VAL", TARGET WAM1REP.F1_EXT_LOOKUP_VAL , KEYCOLS (BUS_OBJ_CD,F1_EXT_LOOKUP_VALUE) ,UPDATEDELE
TES ,OVERRIDEDUPS ,COLMAP ( USEDEFAULTS ,JRN_FLAG = @STRSUB( @GETENV('GGHEADER','OPTYPE'), 'INSERT', 'I', 'SQL COMPUPDATE', 'U', 'DELETE', 'D','PK UPDATE','P' ) ,JRN_SLICING_TS = @DATENOW() ,JRN_SCN = @GETEN
V('TRANSACTION' , 'CSN') ,JRN_UPDATE_DTTM = @TOKEN('tk-commit-ts') ).
2021-05-26 10:47:29 WARNING OGG-06439 No unique key is defined for table F1_EXT_LOOKUP_VAL. All viable columns will be used to represent the key, but may not guarantee uniqueness. KEYCOLS may be used to define the key.
2021-05-26 10:47:29 INFO OGG-02756 The definition for table CISADM.F1_EXT_LOOKUP_VAL is obtained from the trail file.
Using the following default columns with matching names:
Error with default mapping. No matching fields found in the source and target
The following target columns were not mapped:
BUS_OBJ_CD
F1_EXT_LOOKUP_VALUE
F1_EXT_LOOKUP_USAGE_FLG
BO_DATA_AREA
These days the GOlden gate keeps crashing for changes on the source system. This is not consistent as we have observed, it is happening with only a few tables-related replicates that have failed with the error above when there are inserts or updates on these tables. we are not sure what inserts /updates would impact and cause this failure, as we have observed it is not occurring for all inserts/updates on these tables.
STOCK_ITEM_DTL_BIN
STOCK_ITEM_DTL
F1_EXT_LOOKUP_VAL
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |