cancel
Showing results for 
Search instead for 
Did you mean: 

error during installation of SAPNETWEAVR 7.02 system

Former Member
0 Kudos

Hello,

during installation of a system SAP NETWEAVER 7.02 (with EHP2) on SOLARIS MAXDB the following error occurs:

System call failed. Error 12 (Not enough space) in execution of system call 'fork()' with parameter (), line (631) in file (syuxctask.cpp), stack trace: syuxcsyinf.cpp: 165: CSySystemInfoImpl::getOSUname()

syuxctask.cpp: 1117: CSyTaskImpl::start(bool)

syuxctask.cpp: 623: CUnixProcessManager::fork(CTaskImpl & task)

.

ERROR 2012-02-24 16:15:22.851 [syuxctask.cpp:1221]

CSyTaskImpl::start(bool) lib=syslib module=syslib

FSL-04001 Unable to fork process. Not enough space

Can anyone help please ?

Kind Regards

Hartwig Latz

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Perhaps you could check the disk space via command df and also the RAM/swap usage via command top and free.

Regards,

Srikishan

Answers (8)

Answers (8)

Former Member
0 Kudos

Hello Venky,

the database was not started correctly, in this situation I don't know if I can start the database manually. We have started an OSS-Message.

Regrads

Hartwig

Former Member
0 Kudos

Hello,

DpAppcBlksLow: max appc blocks in queue is 500 (50 %)

      • ERROR => DpHdlDeadWp: W0 (pid 16183) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16183) exited with exit code 255

      • ERROR => DpHdlDeadWp: W1 (pid 16184) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16184) exited with exit code 255

      • ERROR => DpHdlDeadWp: W2 (pid 16185) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16185) exited with exit code 255

      • ERROR => DpHdlDeadWp: W4 (pid 16187) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16187) exited with exit code 255

      • ERROR => DpHdlDeadWp: W8 (pid 16193) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16193) exited with exit code 255

      • ERROR => DpHdlDeadWp: W9 (pid 16194) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16194) exited with exit code 255

      • ERROR => DpHdlDeadWp: W10 (pid 16195) died (severity=0, status=0) [dpxxwp.c 1507]

      • ERROR => DpHdlDeadWp: W11 (pid 16196) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16196) exited with exit code 255

      • ERROR => DpHdlDeadWp: W12 (pid 16197) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16197) exited with exit code 255

      • ERROR => DpHdlDeadWp: W14 (pid 16199) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16199) exited with exit code 255

      • ERROR => DpHdlDeadWp: W6 (pid 16189) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16189) exited with exit code 255

      • ERROR => DpHdlDeadWp: W13 (pid 16198) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16198) exited with exit code 255

      • ERROR => DpHdlDeadWp: W3 (pid 16186) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16186) exited with exit code 255

      • ERROR => DpHdlDeadWp: W5 (pid 16188) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16188) exited with exit code 255

      • ERROR => DpHdlDeadWp: W7 (pid 16192) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16192) exited with exit code 255

Thu Mar 1 11:09:34 2012

      • ERROR => DpHdlDeadWp: W15 (pid 16200) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16200) exited with exit code 255

      • ERROR => DpHdlDeadWp: W16 (pid 16201) died (severity=0, status=65280) [dpxxwp.c 1507]

DpTraceWpStatus: child (pid=16201) exited with exit code 255

      • DP_FATAL_ERROR => DpWPCheck: no more work processes

      • DISPATCHER EMERGENCY SHUTDOWN ***

The database was not started correctly.

dev_disp

Kind Regards

Hartwig

Former Member
0 Kudos

Hi Hartwig,

Are there any errors starting the database?

Post the contents of knldiag.err.

Br,

Venky

Former Member
0 Kudos

Are you getting errors during startup.

start the database using dbmcli tool:

dbmcli u2013d <SID> u2013u control,control db_online

or

dbmcli u2013d <SID> u2013u control,control

dbmcli on SID>db_online

dbmcli on SRD>exit

Br,

Venky

Former Member
0 Kudos

Hello Venky,

dev_w0

-


trc file: "dev_w0", trc level: 1, release: "720"

-


*

  • ACTIVE TRACE LEVEL 1

  • ACTIVE TRACE COMPONENTS all, MJ

*

M sysno 00

M sid TDS

M systemid 370 (Solaris on SPARCV9 CPU)

M relno 7200

M patchlevel 0

M patchno 46

M intno 20020600

M make single threaded, Unicode, 64 bit, optimized

M profile /usr/sap/TDS/SYS/profile/TDS_DVEBMGS00_tds

M pid 16183

M

M

M Thu Mar 1 11:09:13 2012

M kernel runs with dp version 125000(ext=118000) (@(#) DPLIB-INT-VERSION-125000-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 16183) [thxxhead.c 1292]

M

M Thu Mar 1 11:09:14 2012

M ThInit: running on host tds

M calling db_connect ...

B create_con (con_name=R/3)

B Loading DB library '/usr/sap/TDS/DVEBMGS00/exe/dbsdbslib.so' ...

B Library '/usr/sap/TDS/DVEBMGS00/exe/dbsdbslib.so' loaded

B Version of '/usr/sap/TDS/DVEBMGS00/exe/dbsdbslib.so' is "720.00", patchlevel (0.45)

B New connection 0 created

C

C DBSDBSLIB : version 720.00, patch 0.045 (Make PL 0.46)

C MAXDB shared library (dbsdbslib) patchlevels (last 10)

C (0.045) Unknown primary key (note 1459400)

C (0.039) Define your own command buffersize (note 1340617)

C (0.031) Dbm commands support added (note 1420733)

C (0.027) Count of records for bulk insert optimized (note 1340617)

C (0.021) Connect with special xuser key (note 1390464)

C (0.018) Error handling for external update statistics changed (note 1340617)

C (0.018) Dbsl procedure to update datasource information (note 1340617)

C (0.015) Special describe handling on MaxDB systemtables (note 1382175)

C (0.013) Possibility to disable UPSERT statements (note 1340617)

C (0.013) Check for external update statistics changed (note 1340617)

C

C

C Loading SQLDBC client runtime ...

C SQLDBC Module : /sapdb/clients/TDS/lib/lib64/libSQLDBC77.so

C SQLDBC SDK : SQLDBC.H 7.7.4 BUILD 009-123-173-450

C SQLDBC Runtime : libSQLDBC 7.8.1 BUILD 014-121-233-288

C SQLDBC client runtime is MaxDB 7.8.1.014 CL 233288

C SQLDBC supports new DECIMAL interface : 1

C SQLDBC supports VARIABLE INPUT data : 1

C SQLDBC supports VARIABLE OUTPUT data : 1

C SQLDBC supports Multiple Streams : 1

C SQLDBC supports LOB LOCATOR KEEPALIVE : 1

C SQLDBC supports LOB LOCATOR COPY : 1

C SQLDBC supports BULK SELECT with LOBS : 1

C INFO : SQLOPT= -I 0 -t 0 -S SAPR3

C Try to connect (DEFAULT) on connection 0 ...

C *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] database not accesssible: pipe open (6:N))

[dbsdbsql.cpp 139]

B ***LOG BV3=> severe db error -10709 ; work process is stopped [dbsh 1241]

B ***LOG BY2=> sql error -10709 performing CON [dblink 540]

B ***LOG BY0=> Connection failed (RTE:[1] database not accesssible: pipe open (6:N) [dblink 540]

M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1461]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 11087]

M

M Info for wp 0

M

M pid = 16183

M severity = 0

M status = 0

M stat = WP_NEW

M waiting_for = NO_WAITING

M reqtype = DP_RQ_DIAWP

M act_reqtype = NO_REQTYPE

M req.req_info =

M req.tid = -1

M req.uid = 4294967295

M req.mode = 255

M req.len = -1

M req.rq_id = 65535

M req.rq_source =

M req.vm = no VM

M last_tid = 0

M last_uid = 0

M last_mode = 0

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M mode_cleaned_counter = 0

M control_flag = 0

M int_checked_resource(RFC) = 0

M ext_checked_resource(RFC) = 0

M int_checked_resource(HTTP) = 0

M ext_checked_resource(HTTP) = 0

M report = > <

M action = 0

M tab_name = > <

M attachedVm = no VM

M

M ThIErrHandle: current request:

M

M -IN-- sender_id ? tid -1 wp_ca_blk -1 wp_id -1

M -IN-- action - uid -1 appc_ca_blk -1 type -

M -IN-- new_stat NO_CHANGE mode 255 len -1 rq_id -1

M PfStatDisconnect: disconnect statistics

M Entering TH_CALLHOOKS

M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP

M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 779]

M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 303]

M ThCallHooks: hook >ThrSaveSPAFields< o.k.

M ThCallHooks: call hook >ThrBtcCallLgCl< for event BEFORE_DUMP

M ThCallHooks: hook >ThrBtcCallLgCl< o.k.

M ThIErrHandle: entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M Entering ThReadDetachMode

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workp. 0 16183) [dpuxtool.c 327]

Regards

Hartwig

Former Member
0 Kudos

Hi Hartwig,

Clearly SAP can't connect to the database. Was the database started and working properly?

C  *** ERROR => Connect to database failed, rc = -10709 (Connection failed (RTE:[1] database not accesssible: pipe open (6:N))
 [dbsdbsql.cpp 139]
B  ***LOG BV3=> severe db error -10709    ; work process is stopped [dbsh         1241]
B  ***LOG BY2=> sql error -10709 performing CON [dblink       540]
B  ***LOG BY0=> Connection failed (RTE:[1] database not accesssible: pipe open (6:N) [dblink       540]
M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1461]
M  in_ThErrHandle: 1
M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   11087]

Br,

Venky

Former Member
0 Kudos

Hello Kishore,

we enlarged swap space to 300 GB. One Error is solved. At the moment the installation stops in phase

start Instance with the following error mesage:

Central System( Last error reported by the step :Instance TDS/DVEBMGS00 reached state SHUTDOWN after having state STARTING. Giving up.)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>Log Files</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to <code>/SAPCD/TMP/TDS/sapinst_instdir/NW702/AS-ABAP/ADA/CENTRAL/</code>. </p> </body></html>

System does not start.

Regards

Hartwig

Former Member
0 Kudos

Hi,

Could you please post dev_disp and dev_w0 logs.

Br,

Venky

Former Member
0 Kudos

Hello Venkatesh,

we set the parameters according to the notes but

process.max-file-descriptor=(basic,65536,deny),(priv,65536,deny) according to note 724713

was to high for our Zone (we install in Oracle Solaris Zones). The insgui did not start, after reducing this parameter to the value 8192 we were able to start SAPINSTGUI again.

Kind Regards

Hartwig Latz

Former Member
0 Kudos

Hi

Try to put some swap space in Local zone.. i had same issue with PI 710 but after assigning local swap space my installation completed sucessfully.

Regards

Kishore

Former Member
0 Kudos

Hi Hartwig,

Perhaps you should check soft and hard limits.

Also, increase the value for the kernel parameter maxuprc in /etc/system

Read the notes:

Note 724713 - parameter settings for Solaris 10

Note 870652 - Installation of SAP in an Oracle Solaris Zone

Note 628131 - SAP DB/MaxDB operating system parameters on Unix

Br,

Venky

Former Member
0 Kudos

Hello Srikishan,

df -k is sufficient too, there is enough space on the device.

Kind regards

Hartwig Latz

Former Member
0 Kudos

Hello,

thank you very much for your answer. We have 8 GB RAM (shoul be sufficient), I performed swap -s

total: 30084400k bytes allocated + 0k reserved = 30084400k used, 3470032k available

Should be sufficient too.

Kind Reagrds

Hartwig Latz