My Oracle Support Banner

Alert.Log Entries Caused by DG4DRDA , (DG4DB2), DG4ODBC, DG4SYBASE, DG4MSQL, DG4IFMX and DG4TERA Gateway IDLE Timeout (Doc ID 1127160.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database Gateway for DRDA - Version 11.2.0.1 and later
Oracle Database Gateway for SQL Server - Version 11.2.0.1 and later
Oracle Database Gateway for Sybase - Version 11.2.0.1 and later
Oracle Database Gateway for Informix - Version 11.2.0.1 and later
Oracle Database Gateway for Teradata - Version 11.2.0.1 and later
Information in this document applies to any platform.

Symptoms

Starting with the 11.2 gateway release a gateway idle timeout is introduced. The gateway IDLE timeout (configuration parameter HS_IDLE_TIMEOUT=<time in minutes>) will end idle gateway sessions after the configured time. The next access of this session through the gateway will then fail with ORA-28511 and add entries to the alert.log file.

Changes

Enabling gateway idle timeout using the parameter HS_IDLE_TIMEOUT with a value not equal to 0.

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
Changes
Cause
Solution
 Case 1:
 


Case 2:
 SUMMARY:
References

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