Hi Ahmad, problem (-> incident 323636 2017) has been solved. status "NEW" was shown incorrectly (due to the log_dir full condition), because the conversion was already started. when deleting such an enty, DB6CONV first checks not only the JOB_STATU...

Hi Ahmad, please check SM37 for Job(s) DB6CONV_FAGLFLEXA and check the Job Status - if the Job Status changed, please refresh DB6CONV to see if the Status in DB6CONV changed as well. if not, please open an incident (already open the System Connec...

Hi, I just saw your 20 day old question. Is it still relevant? Has the problem been solved (and if yes, how)? If not, please sum up the current status.Best regards, Frank

Hi Andreas,DB6CONV 6.31 has been released just 2 hours ago. please check note 1513862 for the related SAR attachment. also read the version history section about V6.31 as well as section 3.11 . hopefully this new version corrects the errors/problems ...