Hi,
One of the tasks of production DBA is to guide developers with read-only access during the incident period to view some application data.
This requires DBA to share readonly user password with application team and then resetting it after few hours (generally automated) based on your organization policies.
As we all know changing the Oracle schema password does not terminate existing connections. This process is always followed by executing the procedure to kill all session for the user.
Ofcourse there are situations where we may not want sessions to be killed as they may from from application layer. So this is very much an optional step.
Can we not have a command which provides a feature to terminate existing sessions? It can easily be done by DBA’s but will be great if we have some command like:
ALTER USER USERNAME IDENTIFIED BY STRONGPASSWORD TERMINATE SESSION;
Oracle can consider this option as added security feature!
Regards!