Answer
Check for a comment line like -- [END IFS COMPLETE BLOCK] in the .cdb file — removing that specific comment has resolved this exact parse error for at least one case, even though the reason a plain comment would affect the delivery pipeline's PL/SQL block parsing (as opposed to Developer Studio's own deployment path, which tolerated it) isn't fully understood. If you hit this specific symbol-'/' parse error only through the delivery/Build Place path and not through Developer Studio, checking for and removing IFS-internal marker comments like this is worth trying before assuming the SQL itself is malformed.