Dump - call_function_syscall_only
Can any one help me in understanding when will call_function_syscall_only dump will occur(we are gettign this dump in the production system).
How can we trace it.
pointers are apreciated .
dakshu kanojia replied
this type of dump occurs in following cases
1.The RFC destination uses the wrong logon data (in other words, the values entered for client, user, and password do not constitute a valid logon).
2.Not all servers within a system have the same kernel release and patch level.
3.The server does not have enough shared memory (PXA memory). For further details, refer to transaction ST22 (ABAP dump analysis and the ABAP runtime errors PXA_NO_SHARD_MEMORY or PXA_NO_FREE_SPACE.
The database key is different on the different servers within the system. This can be the case, for example, if more than one network card is installed on the database server, so that some servers identify the database server under a different host name and IP address. You may be able to see this data in the database data section of the system status display for the relevant server. The RFC logon screen only appears in dialog mode. In the background, the RFC communication terminates with a message that the logon data was incorrect (CALL_FUNCTION_SIGNON_REJECTED or CALL_FUNCTION_SYSCALL_ONLY in the developer trace file or the system log).
1.Check the logon data against the destination used. Ensure that the user has not been locked.
2.Ensure that all of the servers have the same kernel release and patch level.
3.Fix the shared memory (PXA) problem.
4.Ensure that all servers access the database server using the same host name and IP address.
hope this will help u..