Thank You.

I’ll use glogin.sql/login.sql, that is easy to check user.
I have to aware privileges + “drop user” as well.

Thank You Your Sharing/Comment

Thanks for the comment. I use the following in my glogin.sql so that the user I am connected as is always displayed in the prompt:

set sqlprompt “_user’@'_Connect_identifier> ”

I guess the key point with SYSDBA connections is that you connect as SYS, but may have authenticated as someone else, who has the SYSDBA privilege via OS group or database grant.

SQL> connect dba_user/basic_pass@orcl
Connected.
SQL> show user;
USER is “DBA_USER”
SQL> select user from dual;

USER
——————————
DBA_USER

>>>

SQL> connect sysdba_user/basic_pass@orcl as sysdba
Connected.
SQL> show user;
USER is “SYS”
SQL> select user from dual;

USER
——————————
SYS

your method is much better because there is no risk to upset users which is my major concern during hijacking user’s password.

My solution is not very practical but it worked for me several times so I stopped searching for another solution mostly because I don’t create db links in another user’s schema very often.

But anyway, thanks for sharing this useful information.

Regards,
Marko