Before you begin a batch-update transaction in your programs, you
    should create a backup copy of the database.

    You can reduce overhead in large, initial load operations by
    using the BATCH_UPDATE option. To speed update operations,
    Oracle Rdb does not write to the process' recovery-unit journal
    (RUJ) file in the batch-update transaction. Therefore, you
    cannot explicitly roll back a batch-update transaction with a
    ROLLBACK statement. If Oracle Rdb attempts to perform an automatic
    rollback due to any error (for example, a constraint condition is
    violated) that you do not trap in your program, the transaction
    fails and your database is permanently corrupted (because no
    RUJ file exists). You must then re-create the database from
    the backup copy you created prior to starting the batch-update
    transaction. After you have corrected the error condition, you
    can restart the program from the beginning.

    For critical information on the hazards of batch-update
    transactions, read the START TRANSACTION statement's section
    on batch-update transactions in the RDO reference manual.