Installing EHP4 in Suse SLES 11 SP2 fails in Phase 24 of 29 (Start central services instance)

[Former Member]

Hi,

I am installing “SAP ERP 6.0 EHP4 Ready – Support Release 1” -> “SAP Application Server ABAP” -> “Oracle” -> “Central System”, the installation stops in phase 24 of 29 (Start central services instance).

Does anyone have an idea of what may be the problem, the warnings and errors I have in sapinst_xxx.log are:

WARNING[E] 2012-04-12 18:13:19.270

           CJSlibModule::writeError_impl()

FSL-02015  Node /usr/sap/DEV/SYS/exe/run/rfcexec.sec does not exist.

ERROR      2012-04-12 18:13:19.737 [sixxcstepexecute.cpp:950]

FCO-00011  The step copyRFCExecSec with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|copyRFCExecSec was executed with status ERROR .

Kind regards

[former_member189546 · Accepted solution]

Hello,

From error the installation is failing due to RFC issues.  Can you

logon to the sapsystem using DDIC with the default password? If so

run the reports RSWBOINS and RADDBDIF from SE38. Do you get errors?

regards,

John Feely

[Former Member · Accepted solution]

Hi John,

I could logon, started the RSWBOINS and RADDBDIF from SE38, the first report returned a pop-up message "Change and Transport System not configured", the second returned no message.

I executed the first report a second time and it returned no message.

I re-checked the sapinst log and found more errors:

WARNING[E] 2012-02-03 13:49:27.921 [syxxcfstrm.cpp:406]

           CSyFileStreamImpl::open()

FSL-02015  Node /proc/sys/vm/compact_memory does not exist.

WARNING[E] 2012-02-03 13:49:27.936 [syxxcfstrm.cpp:406]

           CSyFileStreamImpl::open()

FSL-02015  Node /proc/sys/net/ipv4/route/flush does not exist.

WARNING[E] 2012-02-03 13:49:27.989 [syxxcfstrm.cpp:406]

           CSyFileStreamImpl::open()

FSL-02015  Node /proc/sys/net/ipv6/route/flush does not exist.

*** ERROR => CTrcOpen: fopen dev_sapinst

---------------------------------------------------

trc file: "dev_sapinst", trc level: 1, release: "701"

---------------------------------------------------

=>sapparam(1c): No Profile used.

=>sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

WARNING[E] 2012-02-03 13:49:32.790

           CJSlibModule::writeError_impl()

FSL-02015  Node /usr/sap/DEV/SYS/exe/run/rfcexec.sec does not exist.

ERROR      2012-02-03 13:49:32.805 [sixxcstepexecute.cpp:950]

FCO-00011  The step copyRFCExecSec with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind|ind|ind|ind|11|0|copyRFCExecSec was executed with status ERROR .

Help would be appreciated

[Former Member · Accepted solution]

Hi,

Found the cause of the problem.

The errror was due to missing kernel file /usr/sap/DEV/SYS/exe/run/rfcexec.sec

During installation, I replaced the original file

"NW_7.01_SR1_Kernel_Linux__OS_400/DATA_UNITS/K_701_U_LINUX_X86_64/DBINDEP/SAPEXE.SAR"

from the kernel installation media "UC-Kernel 7.01 Linux on x86_64 64bit" (original file 51036769_2.ZIP) 

with the kernel 7.20 file SAPEXE_120-10007264.SAR.

The new SAP file doesn't have file rfcexec.sec.

The solution was to get the missing file from original SAR file "NW_7.01_SR1_Kernel_Linux__OS_400/DATA_UNITS/K_701_U_LINUX_X86_64/DBINDEP/SAPEXE.SAR".

I used the commands:

> SAPCAR -xvf SAPEXE.SAR.old

> cp rfcexec.sec /usr/sap/DEV/SYS/exe/run/

The reason that I made this replacement was due to the documented issue "Support of Linux kernel 3.x (SLES 11 SP2)", SAP Notes: 1310037, 1629558.

Thank your for your support

[Former Member · Accepted solution]

we are downloads New kernel release patch to service marketplace we can resolve the issues.

[Former Member]

Basically it's a text file you can create manually to your likings.

It should contain access priviliges as follows:

Information for the access control is maintained in the 'rfcexec.sec' operating system file and the RFCEXEC program reads the information from this file. You can select the storage location as you wish. If the 'rfcexec.sec' file is not contained in the work directory of RFCEXEC, you must find the storage location of the file using the 'RFCEXEC_SEC_FILE_PATH' environment variable on RFCEXEC.
The system administrator is responsible for protecting the 'rfcexec.sec' file against unauthorized access.


Structure of 'rfcexec.sec' file
The format of the file is similar to the format of Saprouter strings and has the following syntax:
           /U/<user name>/C/<client>/T/< list of allowed connection types>/F/<list of allowed functions>/O/<list of not allowed operating system commands>/S/<allowed partner snc name>/




Optional specifications and an alternative syntax are not permitted. If an entry is to be treated as irrelevant, an asterix #*# is used as a value for positive lists and a blank ' ' is used for negative lists.
A comma ',' is used as a list separator.


Examples for the 'rfcexec.sec' file
Contents of the file if no particular restriction has been made (delivery status of the file):
           /U/*/C/*/T/*/F/*/O/ /S/*/


Contents of the file if calls are only allowed from an ABAP system:
           /U/*/C/*/T/3/F/*/O/ /S/*/


Contents of the file if calls are only allowed from an ABAP system by user "SMITH". The user is allowed to call all functions.
           /U/SMITH/C/*/T/3/F/*/O/ /S/*/


Contents of the file if access to the RFC_REMOTE_EXEC and RFCPING functions is restricted. In this case, the "rm" statement must not be executed by the functions.
           /U/*/C/*/T/*/F/RFC_REMOTE_EXEC,RFCPING/O/rm/S/*/