cancel
Showing results for 
Search instead for 
Did you mean: 

REMOTE_OS_AUTHENT

0 Kudos

Hi ,

I have set REMOTE_OS_AUTHENT parameter value to false in my UAT server. Post that I am not able to start the SAP. I got error that "*ORA-01017: invalid username/password; logon denied". But I have set the same value in another UAT server and it got started.

Is there any dependencies for the parameter?  Please suggest me on this.

Accepted Solutions (1)

Accepted Solutions (1)

ACE-SAP
Active Contributor
0 Kudos

Hi

REMOTE_OS_AUTHENT parameter should be set to FALSE (or reset as it is the default value, I think as of 11g) if you are using SSF.

You need to set it to TRUE if you are connecting to Oracle in the 'legacy mode' using OPS$ (externally identified user).

Regards

1622837 - Secure connection of AS ABAP to Oracle via SSFS

400241 - Problems with ops$ or sapr3 connect to Oracle

1860519 - SAP fails to connect to the database

1576837 - ORA-01017: invalid username/password

sumit_goel553
Explorer
0 Kudos

in oracle 11g REMOTE_OS_AUTHENT PARAMETER is deprecated

For remote connections to work, remote_os_authent must be= TRUE

a database restart is required

alter system set remote_os_authent=true scope=spfile;

Answers (2)

Answers (2)

Former Member
0 Kudos

Agree with RB's comment.

Check from which  connectivity mechanism your database is using?

Check SM50(Trace) to get the details of connectivity.

If it is using OPS$ mechanism, you need to have the value TRUE, It is not required for SSFS authentication.

Regards,

Nick Loy

0 Kudos

Hi,

Thanx for your valuable reply. I have checked the trace file from WP and i got the below log. can you please suggest me on this.

Sat Mar 15 18:49:10 2014

M  kernel runs with dp version 138000(ext=119000) (@(#) DPLIB-INT-VERSION-138000-UC)

M  length of sys_adm_ext is 588 bytes

M  ThStart: taskhandler started

M  ThInit: initializing DIA work process W0

M  ***LOG Q01=> ThInit, WPStart (Workp. 0 1 16836) [thxxhead.c   1315]

M

M Sat Mar 15 18:49:11 2014

M  ThInit: running on host erpdev

M  calling db_connect ...

B  Loading DB library '/usr/sap/RD1/SYS/exe/run/dboraslib.so' ...

B  Library '/usr/sap/RD1/SYS/exe/run/dboraslib.so' loaded

B  Version of '/usr/sap/RD1/SYS/exe/run/dboraslib.so' is "720.00", patchlevel (0.327)

C  Register application info.

C  Oracle client version: 11.2.0.2.0, V1, default build, (dbsl 720 291112, UNICODE[2])

C  Installed Oracle client patches:

C  # Patch  9930315      : Created on  3 Nov 2010, 01:32:38 hrs PST8PDT

C  # Patch  10302309     : Created on 23 Nov 2010, 12:10:03 hrs CET

C  Client NLS setting (by OCINlsGetInfo(con=0)): 'AMERICAN_AMERICA.UTF16'

C  Logon as OPS$-user to get SAPSR3's password

C  Connecting as /@RD1 on connection 0 (nls 0) ... (dbsl 720 291112, UNICODE[2])

C  Attaching to database server RD1 (con=0, svchp=60000000042decd8, srvhp=60000000043047d0)

C

C Sat Mar 15 18:49:12 2014

C  Starting user session: OCISessionBegin(con=0, usr='/', svc=60000000042decd8, srv=60000000043047d0, usr=60000000043760f0)

C     OCISessionBegin(OCI_DEFAULT) failed with SQL error 1017:

C     ORA-01017: invalid username/password; logon denied

C  *** ERROR => CONNECT failed with sql error '1017'

[dbsloci.c    15284]

C  Info: 99=DBSL_ERR_DB, oerr=1017, try to connect with default password.

C  Connecting as SAPSR3/<pwd>@RD1 on connection 0 (nls 0) ... (dbsl 720 291112, UNICODE[2])

C  Starting user session: OCISessionBegin(con=0, usr='SAPSR3', svc=60000000042decd8, srv=60000000043047d0, usr=60000000043760f0)

C  Now 'SAPSR3/<pwd>@RD1' is connected: con=0, nls=0, session=8, time='2014-03-15 18:49:12'

C  DB instance RD1 is running on erpdev with ORACLE version 11.2.0.2.0 since MAR 15, 2014, 18:48:43.

C  con=0, V$NLS_PARAMETERS: NLS_LANG=AMERICAN_AMERICA.UTF8, NLS_NCHAR=UTF8

C  Nls CharacterSet                      NationalCharSet                   EnvHp            ErrHp            ErrBt

C    0 UTF16                             AL16UTF16                         60000000042d3920 60000000042dedb8 60000000043038d8

B  Connection 0 opened (DBSL handle 0)

C     DbSlControl(DBSL_CMD_SAPRELEASE_SET,abap='701')

M  ThInit: db_connect o.k.

M  ICT: exclude compression: *.zip,*.rar,*.arj,*.z,*.gz,*.tar,*.lzh,*.cab,*.hqx,*.ace,*.jar,*.ear,*.war,*.css,*.pdf,*.gzip,*.uue,*.b

Former Member
0 Kudos

Logon as OPS$-user to get SAPSR3's password

So it is using OPS$ mechanism and not SSFS.

Change the parameter value to TRUE and start your application.

Paste ERROR lines from dev_w0 log, if you still face same issue.

Regards,

Nick Loy

0 Kudos

Dear Nick,

I have set the parameter value to true and started the application. But in another server I have set the parameter remote_os_authent to false and still I am able to start the SAP. How it is possible? Is there any other mechanism to connect?

FYI the logs which I have pasted is belongs to the server in which I have set the parameter(remote_os_authent) value to false. please clarify me on this.

Regards,

Zahir

Former Member
0 Kudos

Hi,

Then the other system must be using SSFS mechanism.

Go through the below link and Google/Search SDN with a key word "SSFS mechanism SAP" for more details.

http://scn.sap.com/community/oracle/blog/2013/07/23/ssfs-secure-storage-in-file-system-configuration...

Regards,

Nick Loy

Reagan
Advisor
Advisor
0 Kudos

Maybe you have one system configured with SSFS and the other still with the old OPS$ mechanism.

Read this SAP note as it clearly states what should be set for REMOTE_OS_AUTHENT and when

1622837 - Secure connection of AS ABAP to Oracle via SSFS

Regards

RB