Problem solve Get help with specific problems with your technologies, process and projects.

Correct an installation error for R/3 Enterprise on Oracle

Discover possible solutions for an error message encountered while installing R/3 Enterprise to Sunos 5.10 with Oracle

Hello! I'm installing R/3 Enterprise on Sunos 5.10 with Oracle

SAP is stopping the process with an error in the "Database Load (post processing); R3load jobs: finished SAPSDIC"...

phase. The child process 5160 became a "defunct" process. What do you think? The message is below.

***** Transaction begin


TRACE      [iaxxbdbld.cpp:937]
CR3ldStep::startR3ldProcesses lib=iamodload module=CR3ldStep trying to start /
sapmnt/NAS/exe/R3load -dbcodepage 4102 -
i "/oracle/install/SAPinst_INSTDIR/SAPSSEXC.cmd" -
l "/oracle/install/SAPinst_INSTDIR/SAPSSEXC.log" -stop_on_error

TRACE [iaxxbdbld.cpp:937]
CR3ldStep::startR3ldProcesses lib=iamodload module=CR3ldStep trying to start
/sapmnt/NAS/exe/R3load -dbcodepage 4102 -i
"/oracle/install/SAPinst_INSTDIR/SAPDOKCL.cmd" -l
"/oracle/install/SAPinst_INSTDIR/SAPDOKCL.log" -stop_on_error

ERROR 2005-12-20 13:45:13 [iaxxbdbld.cpp:1037]
CR3ldStep::startR3ldProcesses lib=iamodload module=CR3ldStep
MSC-01017 ESyException: Not enough space ***** Transaction end ********************************************************** TRACE [iaxxejsbas.hpp:156]
EJS_Base::dispatchFunctionCall() JS Callback has thrown exception

ERROR 2005-12-20 13:45:13 [iaxxejsctl.cpp:241]
FJS-00012 Error when executing script.

TRACE [syuxctask.cpp:1107]
CSyTaskImpl::start(bool) A child process has been started. Pid = 5157

TRACE [syuxctask.cpp:1107] CSyTaskImpl::start(bool) A child process has been started. Pid = 5160

ERROR 2005-12-20 13:45:13 [syuxctask.cpp:1095] CSyTaskImpl::start(bool) FSL-04001 Unable to fork process. Not enough space sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline

Good question. It looks like SAPinst is unable to fork another process (see output above). This is probably caused by an error on the operating system level -- such as too many processes or no more shared memory. I doubt, however, that this is the first error SAPinst encounters. Have look at the individual R3load log files (such as SAPSDIC.log). One of them probably failed.
This was last published in January 2006

Dig Deeper on SAP Basis administration and NetWeaver administration

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.