How can I safely roll back a database schema change made through Eclipse DTP after a failed deployment?

When using Eclipse Data Tools Platform (DTP) to apply a schema change such as adding a column or modifying a table definition, the operation is typically executed as a plain SQL script. Because many relational databases do not support transactional DDL, a failure part‑way through the script can leave the database in a partially altered state, making a simple re‑run of the original script unsafe.

To achieve a reliable rollback, teams often need to keep a copy of the pre‑change schema, generate inverse DDL statements, and verify that applying those inverses restores the original objects without side effects. The challenge is to automate this workflow inside Eclipse while ensuring that the rollback can be tested repeatedly without affecting production data.

What is the recommended way to generate and store reversible DDL scripts within Eclipse DTP? How can I validate that a rollback script will return the database to a consistent, pre‑change state without manual inspection? Is there a method to integrate rollback verification into an Eclipse‑based build or continuous integration pipeline?