We have DS 7.5.1 and BW Pack 4.1 and are having problems with the RFC server manager functionality. If the connection between a BW instance and the DS server is lost (e.g. the BW server is re-booted), the RFC server manager should react to the situation by stopping the associated rfc servers. However, this version of the PACK does not seem to function properly. The rfc servers continue to run, but they do not work correctly; they no longer are recognized as a valid connection by BW when it completes the re-boot. When I run a manually "stop" for the rfc servers and manager, the manager is stopped, but the rfc servers continue to run with a parent process of "1"; these need to be removed with a UNIX "kill" command before re-starting the RFC server manager.
The result is any lost BW connection like a re-boot or crash of the BW server, or a network issue requires me to run a custom script to "repair" the rfc servers.
Has anyone else seen similar behavior ?
This topic has been locked.
3 replies Latest Post - 2005-08-04T09:45:03Z by SystemAdmin
Pinned topic BW Pack 4.1
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2005-08-04T09:45:03Z at 2005-08-04T09:45:03Z by SystemAdmin
Re: BW Pack 4.12005-08-04T09:45:03Z in response to SystemAdminThis issue has not been resolved in BW4.1, depends on what state your job is in, RFC server may restablish the connection or may not. If the server reboots before loading started, rfc server will restablish the connection, however, if the reboot happens during the loading, the existing rfc connection is lost, you need manually kill the rfc process, and clean your data directory, especially your dsrfcsvr file, then you can try to go to the sap administrator, stop and restart the rfc service there.
However, in BW4.2, this should no longer be an issue.