My Oracle Support Banner

Oracle Database Provider For DRDA - DB2 FOR Z/OS NEEDS A STATIC SYNCLOG (Doc ID 2206049.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database Provider for DRDA - Version 12.1.0.1 to 12.2.0.1 [Release 12.1 to 12.2]
Information in this document applies to any platform.

Symptoms

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.

Cause

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
Symptoms
Cause
Solution
References


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