How should I back-up an application database during a release? During an application release it is common that changes are made to the associated database schema and potentially the data it contains.  Should something go wrong with the application release, the changes made to the schema (and data) will need to be rolled back.

To throw a spanner in the works, there are multiple applications with their own schemas running on the same database instance.

What is the best way to create a back-up that would allow the application schema to be rolled back leaving all other schemas unaffected?
Use the expdp to dump the schema. When needed you can later import the schema back with impdp.