Observation 1: Stay in the same app(e.g. WO), user keep active.
user continues working in the same app, select some items or switch
TABs inside the same application (e.g. WO), the TEMP was not released.
Observation 1.1: Stay in the same app, user inactive:
If user stay idle in the same app, the TEMP was released after a session timeout (default 30 minutes).
Observation 2: GOTO other apps;
After switch to another application, (e.g. from WO to ASSET), the TEMP was released.
Observation 3: Normal log out:
After a normal log out, the TEMP is released.
Observation 4: User Close the Browser:
user close the browser directly, the application has no idea if the
user finished using the result set. So it will wait for a session
timeout and cleanup the TEMP.
doubt that the best way is to avoid using Temp, pure in-memory
operations have the best performance. But if your Oracle database
doesn't have enough memory configuration, you'd better train your end
user more carefully or tune the sql statement to run more efficient with