Archives of the TeradataForum

Message Posted: Tue, 28 Jan 2014 @ 20:46:44 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

Hi Sravan,

I don't have hands-on experience with online archive myself, but what you describe makes perfect sense to me.

The idea of online archive is that all changes done to a table during a backup are logged, so the table can be rolled back to a consistent state later, when you restore it. A table is not in a consistent state when it is in the middle of an update, so the online backup cannot start logging - it wouldn't be able to restore to a consistent state later. Therefore, the online archive and the logging can only take place when the table is not write-locked. From that point in time, any updates can be logged and eventually rolled back during the restore. FLOAD/MLOAD is another story, the table is skipped when being LOADED, just like during normal archive.

The tables are available 24/7 for reads and writes, you just cannot archive them at any point in time: you have to wait until they're in a consistent state. It's the backup user who's blocked, not the batch user, right?

Cheers,

Tomas Gorner

	<Prev	Next>		<<First	<Prev	Next>	Last>>