R3trans -d gives 0012 (SAP) in RAC env
Issue:
Some times You might find the issue (Especially in SAP env) that, your application is showing connection good with your Database (RAC) and all of sudden not, and then again shows connection then again not...
When you run R3trans -d from Application ( SAP) many times output comes as 0000 and many times 0012.
And in this if you find:
[oracle@eul2504 ~]$ sqlplus /@SID001
SQL*Plus: Release 11.2.0.2.0 Production on Fri Jun 16 01:03:28 2017
Copyright (c) 1982, 2010, Oracle. All rights reserved
ERROR:ORA-01017: invalid username/password; logon denied
Then There is a chance that one of the node in RAC might have remote parameter set wrong.
Solution:
Check for the remote authentication parameter:
"primary:sys@SID001> show parameter AUTHENT
NAME TYPE VALUE
------------------------------------ ----------- -------------------
os_authent_prefix string ops$
remote_os_authent boolean FALSE
primary:sys@SID001>alter system set remote_os_authent= TRUE;
Check for the remote authentication parameter:
"primary:sys@SID001> show parameter AUTHENT
NAME TYPE VALUE
------------------------------------ ----------- -------------------
os_authent_prefix string ops$
remote_os_authent boolean TRUE
Now you might need to take a restart of that node and, Get rid out of this issue.
Best Wishes,
Nikhil Kumar.
Some times You might find the issue (Especially in SAP env) that, your application is showing connection good with your Database (RAC) and all of sudden not, and then again shows connection then again not...
When you run R3trans -d from Application ( SAP) many times output comes as 0000 and many times 0012.
And in this if you find:
[oracle@eul2504 ~]$ sqlplus /@SID001
SQL*Plus: Release 11.2.0.2.0 Production on Fri Jun 16 01:03:28 2017
Copyright (c) 1982, 2010, Oracle. All rights reserved
ERROR:ORA-01017: invalid username/password; logon denied
Then There is a chance that one of the node in RAC might have remote parameter set wrong.
Solution:
Check for the remote authentication parameter:
"primary:sys@SID001> show parameter AUTHENT
NAME TYPE VALUE
------------------------------------ ----------- -------------------
os_authent_prefix string ops$
remote_os_authent boolean FALSE
primary:sys@SID001>alter system set remote_os_authent= TRUE;
Check for the remote authentication parameter:
"primary:sys@SID001> show parameter AUTHENT
NAME TYPE VALUE
------------------------------------ ----------- -------------------
os_authent_prefix string ops$
remote_os_authent boolean TRUE
Now you might need to take a restart of that node and, Get rid out of this issue.
Best Wishes,
Nikhil Kumar.
Comments
Post a Comment