|
|
|
Automatic recovery failed with error 413 if it tried to redo the create of a superfile member and the host did not exist, even if SKIP_MISSING_FILES YES was used. CTSTATUS.FCS showed messages with error 413 and indicated that recovery terminated due to that error.
When using SKIP_MISSING_FILES YES a missing superfile host is not expected to cause automatic recovery to fail.
The logic has been modified so that (when using SKIP_MISSING_FILES YES), recovery continues if opening a superfile member fails because the superfile host can't be opened. Now when this situation occurs, if DIAGNOSTICS TRAN_RECOVERY is in effect, we log the following message to RECOVERY.FCS:
<skip redo create of superfile member due to missing superfile host: SUPERFILE_MEMBER_NAME>
where SUPERFILE_MEMBER_NAME is the name of the superfile member whose create was being redone.
