Cronjob is in need of a major overhaul,(for one thing it should understand the unix crontab format) at that time, maybe namespacing the proc will happen. I'm just wondering how to trace this type of problem, maybe it isn't in cronjob at all, but Oracle doesn't seem to find the query, the actual error was that the query length was zero, or too large. I assume zero was the actual problem.
