Solution : https://service.sap.com/sap/support/notes/1354197 (SAP Service marketplace login required)
Summary :
After a temporary offline state of the database in an SAP system, most workprocesses resumed normal function, but some faced difficulties reconnecting. The syslog reported an "F29" error linked to semaphore operation with Syslog-F29 code suggesting semaphore release issue. Tracing in ST11 revealed an "Invalid Operation" at Semaphore release, marked by key=12. Analysis indicated issues related with semaphore cleanup during workprocess restarts when the database was unavailable. A kernel patch was developed to provide enhanced diagnostic capabilities, including detailed message logging to facilitate further troubleshooting. It doesn't resolve the underlying semaphore issue but improves error reporting for better diagnosis in future incidents.
Key words :
640 kernel 309 700 kernel 233 701 kernel 69 710 kernel 177 711 kernel 64, '0000022112'operating system handle, os semaphore set, 2750sap semaphore key, operating system key, reconnect-status reason, kernel patch, sap system, key=12 [semux, semaphore cleanup
Related Notes :
| 864267 | Code page conversion error after WP has left reconnect state |
| 447519 | Kernel patches for code pages, languages and locales |