first, if this is third party application then grant the sysdba role to application user and once the installation is over, revoke the privilege.
second is if you can create the required users first and then installation of the application can continue, then create the users in advance and initiate the installation.
Off-course, granting SYSDBA role to application user is bad and so you MUST not.
if you have server oracle user access then you can do the same using
sqlplus / as sysdba
recommended that not to do until and unless your dba team allow so contact your DBA.
Thanks for your reply.
This is not third party application, these all are oracle applications.
Actually Granting sysdba requirement is given in oracle document and and since it requires at installation time so even if it require to change the password of sysdba then we must notify to application team to change the same in their application configuration file.
There are many oracle applications which requires sysdba privilege while installing & integrating with Oracle database, some of them I have mentioned in my first post.
i think you can use proxy user that has sysdba privilege, in case you want to protect the password of sysdba account.