Veritas Storage Foundation and High Availability Solutions Release Notes

80About Veritas Storage Foundation and High Availability SolutionsKnown issuesSFDB vxsfadm ERROR V-81-0564 Oracle returned error.Reason: ORA-02236: invalid file name (DBD ERROR: error possibly near indicator at char 172 in 'CREATE CONTROLFILE REUSE SET DATABASE'TClone03' RESETLOGS NOARCHIVELOGWorkaround:For the 6.0.3 release, create distinct archive and datafile mounts for the checkpointservice.FileSnap detail listing does not display the details of a particular snap(2846382)FileSnap does not support displaying a detailed listing of a snapshot or clone.FileSnap only supports displaying a summary of all the snapshots or clones. Forexample, for the CLI vxsfadm -s filesnap -a oracle --name=snap1 -o list,a summary listing all the snapshots is displayed, instead of a detailed listing of aparticular snapshot.Workaround:There is no workaround for this issue.'vxdbd' process is online after Flash archive installation (2869269)After a Flash archive installation of the SF stack, the vxdbd process is up, even ifthe stack is not configured.Workaround: You can ignore, or stop the vxdbd process using the/opt/VRTSdbed/common/bin/vxdbdctrl stopcommand.Checkpoint clone fails in CFS environment if cloned using same checkpointand same clone name on both nodes (2869268)The Checkpoint clone of an oracle database fails in a CFS environment, if youcreate a clone with a clone name and checkpoint name same as another clone upon a different CFS node.Workaround:There is no workaround. Create a clone with a different clone name.Very long off-host cloning times for large number of datafiles (2849540)When cloning off-host in certain Oracle database configurations, particularlywith several hundred datafiles, the cloning can take a very long time, upto anhour or more. This problem does not cause the cloning to fail. The problem applies