The following fixes have been made to Dynamic Dump:
Unhandled exception could be seen after a Dynamic Dump failed. This issue has been resolved.
An unexpected debug error message could be seen in selected cases when the dump script used wildcards and some wildcard specifications had no matching files. This problem has been fixed.
When the options PREIMAGE_DUMP YES and PERMIT_NONTRAN_DUMP NO are specified in ctsrvr.cfg, ctPREIMG files are expected to be switched to ctTRNLOG files for the duration of the Dynamic Dump and non-transaction files are not included in the Dynamic Dump. However, a bug caused some PREIMG files to be mistakenly excluded from the dump and some non-transaction files to be included. This error has been corrected.
In situations when a file could not be read due to a system error, the ctdump utility with !BLOCK_RETURN in the backup script reported a successful backup. CTSTATUS.FCS had a log entry indicating non-zero sysiocod: - User# 00019 getfile:ictio81: retsiz=0 recbyt=0000-004b0000x lstbyt=0000-013998fcx CHUNK=65536 sysiocod=23 :: 0xff fill: 443 The logic has been modified so that, when reading a file for dynamic dump and a system error occurs, it now reports this as a READ_ERR (36) and terminates the dynamic dump.
Dynamic Dump Restore failed with error 934 if Immediate Independent Commit Transaction (IICT) activity occurred during a dynamic dump backup. The logic has been modified to correct this.
