Which has the higher priority in your organization: Deploying a new database or securing the ones you already have?
Looking for a website, and resources, dedicated solely to securing Oracle databases? Check out DBSecWorx.
Part of this package was developed before the 10g release of command-line Flashback capabilities ... and is now obsolete. TRANSACTION_BACKOUT is a new capability added in 11g and is priceless.
Constants for Transaction Backout
Default: Backs out specified transactions, expected to have no dependent transactions. If dependents an exception is raised and the error can be found in DBA_FLASHBACK_TXN_REPORT.
Backs out specified transactions, ignoring dependent transactions. Backout happens in reverse order of commit times.
Backs out changes to nonconflicting rows. The database remains consistent but atomicity is lost.
Backs out specified transactions and all dependent transactions in a post-order fashion (children first: parents second).
Data Types Used
CREATE OR REPLACE TYPE "SYS"."TXNAME_ARRAY" AS VARRAY(100) OF VARCHAR2(256);
Time specified is too old
Invalid system change number specified
User cannot begin read-only or serializable transactions in Flashback mode
User cannot enable Flashback within an uncommitted transaction
User cannot enable Flashback within another Flashback session
SYS cannot enable Flashback mode
Related Sysem Privileges
FLASHBACK ANY TABLE
Owned by SYS with EXECUTE granted to MDSYS and the DBA role