Use the NAMEMATCH parameters to control the behavior of fallback name mapping. Fallback name mapping is enabled by default when the source database is case-sensitive and the target database supports both case-sensitive and case-insensitive object names, such as Oracle, DB2 and SQL/MX.
By default (NAMEMATCHIGNORECASE) fallback name matching works as follows: When a source table name is case-sensitive, Oracle GoldenGate applies case-sensitive wildcard mapping on the target database to find an exact match. If the target database does not contain the exact target table name, including case, fallback name mapping performs a case-insensitive target table mapping to find a name match.
NAMEMATCHIGNORECASEPerforms a case-insensitive target table mapping to find a name match when the target database does not contain the exact target table name, including case.
NAMEMATCHNOWARNINGOutputs a warning message to the report file when fallback name matching is used.
NAMEMATCHEXACTDisables fallback name mapping. If an exact, case-sensitive match is not found, Oracle GoldenGate returns an error and abends.