Job operations are validated by Oracle VM Manager as they are added to the Jobs tab. The failure of any job operation causes the following to happen:
The failed job is canceled.
Remaining jobs are attempted.
In previous Oracle VM releases (before Release 3.3.x), multiple operations could be combined into a single job. If the job failed, operations belonging to the job that had not yet been executed could be canceled and changes to the database could be rolled back to a consistent state prior to when the job was triggered. Sometimes rollback was ineffective and some manual cleanup may have been required. Unfortunately, since the operations were bundled into a single job, the actual status of each operation in the job was not transparent. This made it difficult to determine what actions needed to be performed to remedy the situation.
From Release 3.3.x onwards, this does not occur. The current architecture treats each operation as a single API call so that each job performs a single action. This makes each action more transparent so that when a job fails, the state of the environment is much clearer and it is easier to determine what caused the job to fail. It is true that a job can spawn child jobs, but each job is a discrete operation. This means that if an operation fails you must look through the job list to see which jobs failed, and which succeeded. When you find a failed job, attempt to remedy the error or fault, then retry the job. If the Oracle VM environment is left in an inconsistent state due to a failed job, then you must clean it up using the Oracle VM Manager Web Interface, or, if this cannot be done, using the Oracle VM Manager Command Line Interface.