A long-running database session (visible in the application's own Database Sessions screen and in FND_SESSION_RUNTIME/v$session) can't be killed — the application's own RMB > Kill Session fails, the session doesn't even appear in SQL Developer's Monitor Sessions, and running `ALTER SYSTEM KILL SESSION '<sid>,<serial#>'` from a regular client tool returns 'ORA-00026: missing or invalid session ID.' How is a session like this actually terminated?

All FAQ questions / Platform, Aurena, and customization

Answer

Log on to the database server itself (not remotely through a client tool) and run the kill command locally through SQL*Plus, connected AS SYSDBA: sqlplus / as sysdba then ALTER SYSTEM KILL SESSION '<sid>,<serial#>';. Running the identical command locally on the server as SYSDBA has succeeded in cases where the same command failed with ORA-00026 when run remotely through a client tool like SQL Developer — the session then clears from v$session once Oracle's PMON background process catches up.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions