The user_data tablespace is in backup. Some users are going to insert a few lakhs of records. What happens in between that? Is the data inserted and if it is inserted, then how?
If the tablespace is in BACKUP mode, users are still able to write changes to the tablespace's datafiles. This normally causes a problem because you could be backing up a datafile that is undergoing change. This makes the backup of that datafile "inconsistent." The backup of the file is not consistent with any point in time. Some parts of the backup may be older than other parts (which have changed more recently). This is not an issue since you put the tablespace in BACKUP mode. When in BACKUP mode, the database writes extra information to the online redo logs. When you restore from this inconsistent backup, Oracle uses this extra information to make the datafile consistent with the point in time right after the tablespace was taken out of BACKUP mode. So when you perfrom these hot backups, just anticipate a higher redo generation rate in your online redo logs.
Dig Deeper on Oracle database backup and recovery
Oracle expert Brian Peasland answers one reader's question about common pitfalls when connecting Oracle to outside programs.
One reader asks expert Brian Peasland a question about datafile sizes with the Oracle RMAN duplicate 10g command.
Managing parent table-child table relations in Oracle SQL environments is key to efficient programming.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.