Dealing with Cursor Name Conflicts in SQL

Hey folks, I've been running into this annoying error about a cursor with the same name already existing. Anyone know the best way to handle this without messin…