Scribd
Upload
9 views4 pages

DBAM Lec6

Uploaded by

sufyanriazahmad912
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
9 views4 pages

DBAM Lec6

Uploaded by

sufyanriazahmad912
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Slide 1: Title Slide

Title: Managing Undo Data and Undo Data Statistics


Subtitle: Database Administration and Management

Slide 2: Agenda
1. What is Undo Data?
2. Why Do We Need Undo Data?
3. How is Undo Data Managed?
4. Undo Data Statistics
5. Best Practices for Managing Undo Data

Slide 3: What is Undo Data?


 Definition: Undo data is information stored in the database to reverse
changes made during a transaction.
 Purpose:
o Helps with rolling back transactions if needed (e.g., user cancels an
action).
o Supports read consistency, allowing users to see data as it was at a
specific point in time.

Slide 4: Why Do We Need Undo Data?


 Rollback Transactions: Undo data allows you to cancel or undo changes if a
transaction fails or if a user cancels an operation.
 Read Consistency: Ensures that users see a consistent view of the data
even while other transactions are being executed.
 Recovery: During system recovery, undo data helps revert incomplete
transactions.

Slide 5: How is Undo Data Managed?


1. Automatic Undo Management:
o Most modern databases manage undo data automatically.

o The system creates Undo Tablespaces to store undo information.


o Automatic Tuning adjusts how much undo data is stored based on
usage patterns.
2. Manual Undo Management:
o In some cases, administrators manually manage undo by specifying
the size of undo segments.
o Undo Retention Period: The time for which undo data is kept before
it is overwritten.

Slide 6: Undo Data Process Flow


1. Transaction Starts: Undo data is generated when a user performs an action
(e.g., update, delete).
2. Undo Tablespace: The undo information is stored in the undo tablespace.
3. Commit or Rollback:
o If the transaction is committed, the changes are saved, and the undo
data can be reused.
o If the transaction is rolled back, the undo data is used to restore the
previous state.

Slide 7: Undo Data Statistics


 What are Undo Data Statistics?
o These are metrics collected by the database to track how undo data is
being used.
 Key Statistics:
o Used Undo Space: How much space is used for storing undo data.

o Expired Undo Space: Undo data that is no longer needed and can be
overwritten.
o Active Undo Space: Undo data currently in use by active
transactions.
o Undo Retention: How long undo data is kept before it is overwritten.

Slide 8: Monitoring Undo Data Statistics


1. Database Views:
o In Oracle, use the V$UNDOSTAT view to see undo data usage and
statistics.
o Common metrics include:

 UNDO_BLOCKS: Number of blocks used for undo data.


 TXNCOUNT: Number of active transactions.
2. Tools:
o Database Management Tools: Some database systems have built-in
tools for monitoring undo data (e.g., Oracle Enterprise Manager).
o Alerts: Set up alerts to notify administrators if undo data is running
low.

Slide 9: Best Practices for Managing Undo Data


1. Set the Right Undo Retention Period:
o Choose a retention period that balances between keeping enough undo
data and not wasting storage space.
o Monitor your workload and adjust based on usage.

2. Monitor Undo Tablespace:


o Regularly check the space in your undo tablespace to avoid running
out of room for undo data.
o Use database tools or queries to track space usage.

3. Optimize Transaction Size:


o Keep transactions short and efficient to reduce undo data generation.

o Avoid large transactions that generate a lot of undo data in one go.

4. Handle Long-Running Queries:


o Ensure that the undo retention period is long enough for long-running
queries.
o Otherwise, you may lose undo data before the query completes.

Slide 10: Common Issues with Undo Data


1. Undo Tablespace Full: If the undo tablespace runs out of space, it can lead
to transaction failures.
2. Snapshot Too Old Error: Occurs when undo data needed for a long-running
query has been overwritten.
3. Poor Performance: Insufficient undo space can slow down database
performance.

Slide 11: Conclusion


 Undo Data: Essential for maintaining data integrity and ensuring read
consistency.
 Undo Management: Can be automatic or manual, depending on the
database system.
 Statistics: Monitoring undo data usage is important to avoid errors and
ensure efficient performance.
 Best Practices: Proper undo retention and monitoring prevent issues like full
tablespaces or transaction errors.

You might also like