Anyone out there experience hung jobs which state "Started" in OEM?
I created a backup job which runs just fine in OEM 2.2. Then I added a "Run OS Command" before the backup to delete the previous night's backup set.
When I run the job it shows that it started but it just sits there. If there is an error I would like it to fail so I can see the log but its just sits in a hung state which is useless.
thx in advance,
-Eddie Hernandez