In job log maybe found also these kind of messages:
======================================================================================================== | 2014-12-24 00:14:20 |INFO |X|SAP|pid=28584.140060886296320| uxsap_sync_wait_for_job_c | Following job (CACRASH) (00075801) not child of father [CACRASH][00075804]. Skipping... | 2014-12-24 00:14:20 |INFO |X|SAP|pid=28584.140060406044416| uxsap_sync_wait_for_job_c | Following job (CACRASH) (00082401) not child of father [CACRASH][00082400]. Skipping... ========================================================================================================
gdb core analysis indicates a segmentation fault error and should be similar to this (here on Linux SAP)
======================================================================================================== Program terminated with signal 11, Segmentation fault. #0 0x0000000000438ceb in uxsap_synchro_sys (p_conteneur_sys=0x744f30) at /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c:255 255 /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c: No such file or directory. in /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c (gdb) where #0 0x0000000000438ceb in uxsap_synchro_sys (p_conteneur_sys=0x744f30) at /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c:255 #1 0x00000000004389d6 in uxsap_synchro () at /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c:159 #2 0x000000000043887d in uxsap_synchro_start () at /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c:104 #3 0x00000000004387c8 in uxsap_sync_thread_trt (arg=0x0) at /etud_objp/indus/du_as/6.2.41/Linux_26_64/src/k_sap_mgr/src/server//uxsap_thread_sync.c:69 #4 0x00007f9eb41707b6 in start_thread () from /lib64/libpthread.so.0 #5 0x00007f9eb3ecbc5d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () (gdb) quit =======================================================================================================
Description :The SAP manager processe crashes when activity is high and SAP Child Jobs is activated. A core is generated. Possibly the journal file has to be deleted to allow the restart.
Conditions necessary to encounter the problem -- high activity -- SAP job with Child jobs
Environment
OS: All OS Version: But other OS maybe impacted : like AIX of HP Unix
Cause
Cause type: Defect Root Cause: N/A
Resolution
Update to the fix version listed below or a newer version if available.