All depends on what version of NetBackup you are running - you signature says 7.1 and earlier so assuming that is the case this is what to do:
First off these are usually caused by a process crash some where - always worth investigating what errors on your system you had at around that time - it may also have been a server reboot just as a job was kicking in - plenty of possible reasons...
To get rid of it make a note of the job id (227858)
Make sure nothing is running, incomplete or suspended - so this rogue job is the onlything active.
On the Master Server shutdown NetBackup and make sure all processes have ended (not while any jobs are running or you may get more of these errors!)
Next, on the Master go to <install path>\netbackup\db\jobs\ and delete the bpjobd.act.db (do not delete the bpjobd.db!!!)
Then look under the ffilelogs folder for the file with that job id and delete it
Then look under the trylogs folder and do the same
Then start up NetBackup again
That should have got rid of your orphaned job
Now do some digging to see if you can identify what you had a crash / reboot/ restart at that time ( as no time is shown use the jobs either side to get an estimate)
Hope this helps