You can roll back a deployment and purge the deployed versions from the target repository or folder. When you roll back a deployment, you roll back all the objects in a deployment group that you deployed at a specific date and time. You cannot roll back part of a deployment or roll back from a non-versioned repository.
To initiate a rollback, you must roll back the latest version of each object. The Repository Service ensures that the check-in time for the repository objects is the same as the deploy time. If the check-in time is different, then the repository object is not the same as the object in the deployment, and the rollback fails. The rollback also fails if the rollback process causes you to create duplicate object names. This might occur if you rename a deployed object, create a new object with the same name, and attempt to roll back the original deployment.
To roll back a deployment:
The Repository Service checks the object versions in the deployment against the objects in the target repository or folder, and the rollback either succeeds or fails. The rollback results appear at the end of processing. If the rollback fails, the Repository Service notifies you of the object that caused the failure.
What if the above steps fail?
Use the labels to identify the objects and purge them.
What is a label?
A label is a global object that you can associate with any version-ed object or group of version-ed objects in a repository. You may want to apply labels to version-ed objects to achieve the following results:
For example, you might apply a label to sources, targets, mappings, and sessions associated with a workflow so that you can deploy the workflow to another repository without breaking any dependency.
Use the labels to identify the version-ed objects and purge them. You can get the list of all the objects to be purged using queries in the Repository Manager. (Tools Menu –> Queries)