Last updated on NOVEMBER 21, 2016
Applies to:Oracle Database Provider for DRDA - Version 220.127.116.11 to 18.104.22.168 [Release 12.1]
Information in this document applies to any platform.
DB2 keeps every synclog it's ever encountered *in memory* and that eventually causes DB2 to crash with an out-of-memory condition, requiring a restart and purge of old synclogs.
Oracle DP4DRDA creates a unique synclog (logstamp varies) on every session, and DB2 eventually chokes on the sheer number of synclogs it tries to remember over time.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms