SAP passport is lost for RFC connections
[access connections] [connections] [connections tray] [sap rfc]
- DB6: Timeout for secondary database connectionsSymptom Opening a database connection in an SAP work process takes a very long time. The SAP work process is blocked during this time. Other terms SQL_ATTR_LOGIN_TIMEOUT, DB6, UDB, LUW, logical unit...
Symptom
The SAP passport transfers information from the client to the server for RFC connections and HTTP connections so that trace information and statistical information from both sides can be assigned to each other. Under certain circumstances, the SAP passport is lost. When RFC communication takes place once or several times, the SAP passport data is transferred and saved correctly on the server. However, after several transfers, the SAP passport information on the server is lost.
Reason and Prerequisites
Due to an error in the kernel, some parts of SAP passport were discarded on the server if the RFC server was reset using the module SYSTEM_RESET_RFC_SERVER or if the client became active again after a rollout in another work process.
Solution
The attached kernel patch corrects the error. There is no workaround for the problem.
![[del.icio.us]](http://images.del.icio.us/static/img/delicious.small.gif){kind=small}