$G Is Present In The Failed Mapping Table Entry (Doc ID 2407653.1)

Last updated on MAY 06, 2021

Applies to:

Symptoms

While testing a configuration change on a development system, the following scenario was noticed:

When a recipient is found in the 'general.txt' file, the mapping successfully adds the desired conversion tag and everything works the way it is expected.

However, the slave debug logs show that when the user is not in the 'general.txt' file, the source channel name gets added as a conversion tag while it shouldn't.

Example from the slave log of tcp_local_*.log-nnnnn:

As expected, "visexempt|uid_2@example2.com" did not exist in the 'general.txt', and so the ${ } lookup failed.

But why did it add conversion tag "tcp_scanner"?

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.