Actual Process : The coretool runs on the uploaded file and identifies whether i t is a core file or data file.

Depending on the output further processing takes place.The process is different for a c ore file and data file What happened here : The coretool ran on the file "2004677788_secd.12380.2014176 064.2013-12-09.19_47_05.ucore.bz2" and identified it as a data file. But ideally it should be a core file here. What to do in future : Check in logs what is the file type that is being returne d by coretool ( core file or data file ?? ) means We have to confirm from logs that coretool output is "Fil etype=Data file" ( which is wrng, it should be "Filetype = core file" ) If it is returning data file ( which actually should be a core file) then we cannot process the file further means this file cannot be tr eated as core file by Application since coretool output returned as data file an d hence we follow remaining steps to process the file smoothly irrespective of c oretool output Note : We cannot process the file further = Application cannot process the file further. Step 1 Magma Team : Check in logs if the coretool is returning the file type as data fi le or core file If it is returning data file ( which actually should be a core file ) then we cannot process the file further Step 2 Magma Team : Gather all below information of file Case id : Priority : same as case priority Status : Crash Message : Core file path : Core Case Owner : System Id : Os Version : Step 3 SAP Team : Magma team provides all the information gather in step 2 and provides it to SAP team for creation of subcore case Step 4 Magma Team : Place the file in correct location, that means in the subcase folder created by SAP team. Below example has subcase 50059243 created by SAP team. Hence the file was place d in this location. (for ex: /x/eng/cs-cores1/2004677788/50059243) Update the path details and other required fields in file tracker and provide su bcore case to requester