I tried to kill a oozie coordinator job like this:
$ oozie job -oozie http://10.0.3.2:11000/oozie -kill 0003288-130913181709024-oozie-oozi-C
There is no any error appears.
But after I check the oozie UI, the job still exists.
I encounter this error sometimes on my testing environment, where Oozie uses Derby as database. The solution is to clean Oozie state by removing the database:
sudo /etc/init.d/oozie stop
sudo rm -rf /var/lib/oozie/oozie-db/
sudo /etc/init.d/oozie start
Of course, this solution may not be appropriate for production system (althrough I've never seen this error in production).