A shared/technical IFS account gets stuck showing 'IFS Account is already logged in by <other user>' after a forced disconnection (e.g. the session hung and had to be killed), even though the session doesn't appear in the Database Sessions screen and the other user can still log in fine from their own machine — how is this cleared manually rather than waiting for it to time out?

Q: A shared/technical IFS account gets stuck showing 'IFS Account is already logged in by ' after a forced disconnection (e.g. the session hung and had to be killed), even though the session doesn't appear in the Database Sessions screen and the other user can still log in fine from their own machine — how is this cleared manually rather than waiting for it to time out?

Query FND_CLIENT_LOGON_TAB directly and use the DIRECTORY_ID and OS_USER columns to find the specific stale session record for the affected account/user combination, then delete that row and commit — for example: DELETE FROM FND_CLIENT_LOGON_TAB WHERE DIRECTORY_ID = ' ' AND OS_USER = ' ' AND PROGRAM = 'Ifs.Fnd.Explorer.exe'; COMMIT;. This clears the stuck 'already logged in' state immediately, rather than waiting for it to clear automatically after an HTTP session timeout.

Answer

Query FND_CLIENT_LOGON_TAB directly and use the DIRECTORY_ID and OS_USER columns to find the specific stale session record for the affected account/user combination, then delete that row and commit — for example: DELETE FROM FND_CLIENT_LOGON_TAB WHERE DIRECTORY_ID = '<account>' AND OS_USER = '<domain\username>' AND PROGRAM = 'Ifs.Fnd.Explorer.exe'; COMMIT;. This clears the stuck 'already logged in' state immediately, rather than waiting for it to clear automatically after an HTTP session timeout.

← Browse Security and access questions