Operating system call connect failed (error no. 239 ) in SM21

[Former Member]

Hi all, I keep getting the above error in the SM21 of my SAP 4.6c system. It happens every 5 mins consistently. The type is MS and the MNo is Q0I.

I have checked SM37 but cannot find a single consistent job that causes this. I cannot find anything in SM35 to relate to this error too. There is also no userid attached to this error message

Can anyone shed some light on this? Thank you!

[markus_doehr2 · Accepted solution]

Check your dev_* traces also for this error message.

Markus

[Former Member · Accepted solution]

Hi,

Goto SM21 and check what is the Work process(WP) used ?, then goto dev_wXX file and check exactly what happend during that specific time. You may find some Note if U search with exact error, other wise pase that log here.

Regards,

Hari.

[Former Member · Accepted solution]

Hi sorry for the late reply. My other technical guys managed to resolve this issue using the following:

Operating system call connect failed (error no. 239 )

adm> cd /tmp

Syntax: ln u2013s .sapstream32<instance-nr> .sapstream3200

Syntax: ln u2013s .sapstream36<instance-nr> .sapstream3600

Example:

adm> ln -s .sapstream3232 .sapstream3200

adm> ln -s .sapstream3632 .sapstream3600

Thanks for those who have helped! Points awarded

[markus_doehr2 · Accepted solution]

> adm> ln -s .sapstream3232 .sapstream3200

> adm> ln -s .sapstream3632 .sapstream3600

This is really strange.

Those dot-files are sockets which are created on system start by the work processes.

Did you try to rename the instance or copy it on the same system?

Markus

[Former Member · Accepted solution]

Hi Markus, real sorry but I cannot answer your questions about this as this was done by another group of people who have access to the OS level and I do not know if they actually used this command or modified it somewhat.