on 12-09-2007 1:56 AM
Hi
This is an issue I ran into installing Netweaver 2004s on AIX and Oracle.
sapinst crashed during the installation before the database installation step. Already, tried using the latest verison of "sapinst" utility (ver 701) but ran into the same issue. Any suggestions pls ?
Error message from sapinst.log
" iauxsysex.c:317:
child /tmp/sapinst_exe.565346.1196967301/sapinst (pid
81974) has crashed. Executable directory
is /tmp/sapinst_exe.565346.1196967301. Contact Support.
iaextract.c:814: child has signaled an exec error. Keeping
directory /tmp/sapinst_exe.565346.1196967301"
Thanks
Vic
Hi Vic,
Typically this sapinst issue is due to AIX resources at OS level
I believe that it is problem of limits of stacksize, datasize and memory
Often a core occurs if the resource limits are to low, especially on
AIX. Depending on the shell you are using you can view and change the
limits using the limit or the ulimit command. If you change a limit the
new value holds only for the shell and processes started in this shell.
Hence if you change limits you have to do it in identically the same
shell process from which you start sapinst.
If you are using csh or tcsh run limit to view all limits. The limits
stacksize, datasize and memory are especially important. If they are
not yet unlimited you should set them to unlimited using the commands
limit stacksize unlimited
limit datasize unlimited
limit memory unlimited
Please verify the result using
limit
If you are using ksh or bash run
ulimit -a
to view the limits and
ulimit -d unlimited
ulimit -s unlimited
ulimit -m unlimited
to set the limits.
Please set also the coredumpsize to unlimited. It is even better if
you can also set all the other limits to unlimited.
By setting above, it should help to resolve the issue.
Also other typically recommendation for installation:
-- perform the installation locally by copying
the DVD files to local drive and run from there.
- usethe latest sapinst version
- there should be no space/permission issue in /tmp directory. If possible, set
777 chmod to /tmp directory.
Hope this helps.
Cheers,
Vincent
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.