SM49 error in R3 4.7, Oracle 9i, solaris 10 - Process died due to signal 11

[Former Member]

Hi,

while executing the command in SM49 I am getting the error "Process died due to signal 11"

Any one faced this problem earlier. . . .

Advance thanks. . .

Regds

[Former Member]

please refer this note too

Note 350167 - Process killed by Signal 11 or Signal 10

1.Please check the shared memory parameters pool 10 and 40

2.Check the ulimits of sidadm

check oss note132853

Hope it help you.

Amit

[Former Member]

Hi jalli,

Please find the some of the solutions to resove the issue.

1. Please upgrade brtools to latest one (DBATL<--->.SAR): Note 12741

2. Pleae check the permissions of /usr/sap/ is 775 - as per oss note 109118.

3. Basically for SIGNAL 11, Suggested note: 350167 (Memory error).

4. We have faced same signal 11 error, for that we have applied latest oracle(9i) client, then issue resolved.

Please check with changing oracle client to latest one.

Hope this will definetely resolves the issue.

Thanks

Kishore

[markus_doehr2]

Signal 11 is a "Segfault" - a program tried to access and address it shouldn´t and the OS is killing that process.

Check if you have dumps in ST22 corresponding to that. Also see the syslog (SM21) and the corresponding workprocess trace.

Markus

[Former Member]

Hi,

This looks like a permission issue at OS level.

Check the permissions of the used sid<adm> (using command 'ls -l /home/<sid>adm').

It should have permission like 'drwxr-xr-x <sid>adm sapsys'

If you don't have the permission as above execute 'chmod 755 /home/<sid>adm' as 'root' user.

Vinayak