Symptoms

The Microsoft Service for Distributed Relational Database Architecture (DRDA) trace log listener may repeatedly write an error message in the trace log file when certain errors occur. After the error message is written to the trace log file, the trace log listener does not log messages for any new transactions that are processed by the Microsoft Service for DRDA.

The following is an example excerpt of a trace log that shows an error message that is written repeatedly:

Information:3:3:[date time] Request: SYNCCTL, SyncType=SYNCTYPE_FORGET
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected
Information:3:3:[ date time] Client 10 disconnected


Resolution

Cumulative update information

The fix that resolves this problem is included in Cumulative Update 1 for Microsoft Host Integration Server 2013.

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

This problem may occur when the following conditions are true:

  • An IBM DB2 database sends a fully qualified quoted identifier such as "SCHEMA1.TABLE1."

  • An SQL synonym is not defined for the DB2 alias in the Microsoft Service for DRDA configuration.

Under these conditions, the SQL transformer in the Microsoft Service for DRDA converts the fully qualified quoted identifier to a quoted SQL schema name only, such as "SCHEMA1," because of the missing SQL synonym. This results in an error because the SQL table name is missing and therefore the SQL table cannot be located. At this point, the trace log listener problem is encountered because one of the messages is repeatedly written to the trace log file.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Any additional feedback? (Optional)

Thank you for your feedback!

×