sys / as sysdba should require a password

-


sys / as sysdba should require a password

Applies to:
            Enterprise Linux – Version: 5

Description:
            Sqlplus / as sysdba connections go through OS authentication rather than database authentication. Any user with OS access can log into database irrespective of valid account available in database. Sys / as sysdba could not login without a password.
How can we control OS authentication to stop any OS user to login as SYSDBA?

Solution:
Set the following parameter in init.ora file:
REMOTE_OS_AUTHENT = FALSE

open sqlnet.ora file and set the following parameter:
SQLNET.AUTHENTICATION_SERVICES=(NONE)

save and exit file.

now you cannot login "sys / as sysdba" without password.


Your comments, especially which will help us improve the functionality, will be greatly appreciated :)

Comments

Post a Comment

Popular posts from this blog

FRM-92101: Forms Server Not Starting Up

-
Forms Server Not Starting Up / Forms Server Start Up Issue Applies to:             Oracle Enterprise Linux – Version: 5             Oracle EBS R12 Description:             After cloning EBS R12 successfully on a new server machine, when I am going to access any form on EBS clone it did not open the page and show the following error: FRM-92101: Forms Server Java Exception: oracle.forms.net.ConnectionException: Forms session <1> failed during startup: no response from runtime process at oracle.forms.net.ConnectionException.createConnectionException(Unknown Source) at oracle.forms.net.HTTPNStream.getResponse(Unknown Source) I have restarted all the services of application and database but the problem is same. I have also restarted the whole machine/server but still the same issue. Cause and Solution: I found the following error: In $LOG_HOME/ora/10.1.3/j2ee/<oacore>/<oacore>_<default_group_1>/application.log $LOG_HOME/ora/1
Read more

How to Rebuild/Recreate Concurrent Manager

-
How to Rebuild/Recreate Concurrent Manager Applies to:             Oracle Applications – Version: 11.5.10.2 and above Description:             After cloning, concurrent manager unable to start successfully at 0 status. Solution:             Check the following solution on test environment before implement on production environment, rebuild concurrent manager using following steps: ·          Stop concurrent manager and wait to clear all processes of FNDLIBR or kill the processes ·          select * from fnd_concurrent_processes where process_status_code='A'; ·          update fnd_concurrent_processes set process_status_code='K' where process_status_code='A'; ·          select * from fnd_concurrent_queues where control_code='N'; ·          update fnd_concurrent_queues set control_code=null where control_code='N'; ·          update fnd_concurrent_queues set node_name=null,node_name2=null where concur
Read more

ORA-10564 Tablespace UNDOTBS1 ORA-01110 ORA-10560

-
ORA-10564 Tablespace UNDOTBS1 ORA-01110 ORA-10560 Applies to:             Oracle Enterprise Linux – Version: 7             Oracle EBS R12 Description:             After abnormal shutdown of server we face the problem “ORA-10564 Tablespace UNDOTBS1 ORA-01110 data file 7 UNDOTBS01.DBF ORA-10560 block type KTU UNDO BLOCK”. I have restarted all the services of database but the problem is same. I have also restarted the whole machine/server but still the same issue. Solution:             After some research I found that recreate the undo tablespace to resolve the issue. Following the steps to resolve the above issue: 1-       Connect / as sysdba 2-       Create undo tablespace UNDOTBS2 datafile ‘/u01/oracle/oradata/undotbs02.dbf’ size=1G; 3-       Alter system set undo_tablespace = UNDOTBS2; 4-       Shutdown immediate 5-       startup 6-       Drop tablespace UNDOTBS1 including contents and datafiles; Database is working fine now.
Read more