User manipulated data in hot backup mode
My tablespace is in hot backup mode. At the same time another user manipulated some rows in that tablespace; where will the manipulated data be stored, and why are redo logs generated?

    Requires Free Membership to View

    Login

    By submitting your registration information to SearchOracle.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchOracle.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

The changes will be found in the redo logs (online or archived). You may even see the changes in the tablespace's datafiles if a checkpoint occurred in the middle of the tablespace's backup. Oracle's transaction control mechanisms keep everything in place.

During normal operating mode, only the specific changes are written to the online redo logs. However, when the tablespace is being backed up, it is possible for the database block to be modified while it is being backed up. This means that part of the block will be "new" and part of the block will be "old" in your backup copy. This is called a split block. To help with this split block issue, Oracle writes the entire block (not just the part that was changed) to the online redo logs when the tablespace is in BACKUP mode.

This was first published in February 2007

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top