Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
forcing a log switch in db2/udb
- Thread starter g046678
- Start date
Guest_imported
New member
- Jan 1, 1970
- 0
- 0
- 0
I don't believe this functionality is available until V7 fixpack 3
From the fixpack
7.6.6 On Demand Log Archive
DB2 now supports the closing (and, if the user exit option is enabled, the archiving) of the active log for a recoverable database at any time. This llows you to collect a complete set of log files up to a known point, and
then to use these log files to update a standby database.
Note:
On demand log archiving does not guarantee the log files will be archived immediately; it truncates the log file and issues an archive request, but it is still subject to delays associated with the user exit program
You can initiate on demand log archiving by invoking the new DB2 ARCHIVE LOG command, or by calling the new db2ArchiveLog API.
From the fixpack
7.6.6 On Demand Log Archive
DB2 now supports the closing (and, if the user exit option is enabled, the archiving) of the active log for a recoverable database at any time. This llows you to collect a complete set of log files up to a known point, and
then to use these log files to update a standby database.
Note:
On demand log archiving does not guarantee the log files will be archived immediately; it truncates the log file and issues an archive request, but it is still subject to delays associated with the user exit program
You can initiate on demand log archiving by invoking the new DB2 ARCHIVE LOG command, or by calling the new db2ArchiveLog API.
- Status
Similar threads
- Locked
- Question