What are the differences between dump transaction and dump transaction with no_truncate?
When a dump transaction command is issued, the server makes a copy of all the inactive transactions that occurred on a particular database up to the point of the actual time of dump, and those transactions are removed from the log. When thedump transaction with no_truncate command is issued, the server makes a copy of the inactive transactions but does not remove those transactions from the log. Therefore, if successive transaction log dumps are performed using dump transaction with no_truncate, the log will grow in size and will eventually have to be purged either via dump transaction or dump transaction with truncate_only.
Related Questions
- What are the differences between calling a program, transaction ‘with return’ and ‘without return’ and how can each be accomplished?
- Explain the similarities and differences between EJB CMT and the Spring Frameworks declarative transaction management ?
- What are the differences between dump transaction with truncate_only and dump transaction with no_log?
