Data Dictionary
>
FPSAPP Tables
> FPSAPP.CFG_SESSIONS_TO_KILL
Table FPSAPP.CFG_SESSIONS_TO_KILL"
Configuration settings that determine what sessions are considered hung based on username, osuser, and module from v$session. At least one of these must be specified and the others must be listed as ANY. The order of precedence is module, then osuser, then username. Settings do not overlap so whichever rows is deemed the most relevant will its settings applied and no others.
-
Schema: FPSAPP
-
Tablespace: FPSDATA
-
Primary key: USERNAME_OR_ANY, OSUSER_OR_ANY, MODULE_OR_ANY
|
Column |
Type |
Nullable |
Comment |
|---|---|---|---|
|
USERNAME_OR_ANY |
VARCHAR2(64) |
N |
USERNAME from v$session or the word ANY which signifies any USERNAME. |
|
OSUSER_OR_ANY |
VARCHAR2(30) |
N |
OSUSER from v$session or the word ANY which signifies any OSUSER. |
|
MODULE_OR_ANY |
VARCHAR2(128) |
N |
MODULE from v$session or the word ANY which signifies any MODULE. |
|
IS_AUTO_KILL_ALLOWED |
CHAR(1) |
Flag indicating whether the session is allowed to be killed automatically. |