Im concearned that killing the o/s session may not clear up what is causing the issue.

The only thing that I can think of that might have effected this was that I made a precision change on a table that was used by the stored procedure, after I killed the session. I would have thought oracle would have obtained an exclusive lock on the table if it was rolling back transactions from that table.