You are not seeing quite what you think. You asked 'Is SysDBA Oracle User?', and the answer to that is 'No'. SYSDBA
is a system privilege, not a predefined user account provided by Oracle. Users granted that privilege can connect with administrative privileges, like:
connect / as sysdba
That is a very different thing to how your SysDBA
user can connect:
connect "SysDBA"/sysdba
The user has been created within your database by someone in your organisation; it is not a default Oracle account, they are completely unrelated, although I suppose it's conceivable it could also have been granted SYSDBA
privileges just to really mess with you. (And yes, that really is the password I'm afraid).
Also note that it has been created with mixed case, which means it needs to be quoted when used outside a query. You can do:
select * from dba_users where username = 'SysDBA';
... but if you aren't referring to a table column value it has to be quoted, as shown in the connect
above and in things like alter user
:
alter user "SysDBA" account lock;
It looks like it's probably an internal account for an application, and one that isn't setting the module (v$session.program
?) via an dbms_application_info
call - so perhaps an in-house application. If so you might be able find out why it's there and what it's doing, and why it's been given a confusing name, but locking it might cause problems for whoever is running that application.