My Oracle Support Banner

OID Log Error: ORA-02399: Exceeded Maximum Connect Time, You Are Being Logged Off. (Doc ID 1561211.1)

Last updated on JANUARY 10, 2019

Applies to:

Oracle Internet Directory - Version 10.1.2 to 11.1.1 [Release 10gR2 to 11g]
Information in this document applies to any platform.


1. Follow messages reported in the oid log files showing that OID server lost connection to Oracle database.

- ORA-02399: exceeded maximum connect time, you are being logged off.

2. The database connections have a timeout of 15 minutes except for the schemas listed in the previously posted solution. I am wondering if there is anything else that needs to be changed with the timeout settings in order for this not to happen.

[2013-06-04T09:40:49-05:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:] [pid: 22301] [tid: 11] [ecid: 004r_KHEptF1ba9srciOPm0005ST00001M,0] ServerWorker (REG):[[
ConnID:62 mesgID:28 OpID:27  OpName:modify ConnIP:::ffff: ConnDN:cn=orcladmin
INFO * gslsbmccCallCatalog: The attribute sudocommand has been indexed
[2013-06-04T13:16:47-05:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:] [pid: 22301] [tid: 1] StatsCollector: ERROR * gslsmujGetInstInfo * ORA-2399:ORA-02399: exceeded maximum connect time, you are being logged off

[2013-06-04T13:16:47-05:00] [OID] [NOTIFICATION:16] [] [OIDLDAPD] [host:] [pid: 22301] [tid: 1] StatsCollector: ERROR * StatsCollector * Failed to get instances' status                     info





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

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