Veritas Storage Foundation and High Availability Solutions Release Notes
Veritas Storage Foundation⢠and High ... - SORT - Symantec
Veritas Storage Foundation⢠and High ... - SORT - Symantec
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
About <strong>Veritas</strong> <strong>Storage</strong> <strong>Foundation</strong> <strong>and</strong> <strong>High</strong> <strong>Availability</strong> <strong>Solutions</strong>Known issues55DB2 databases are not visible from the VOM Web console (1850100)If you upgraded to SF 5.1, DB2 databases will be not visible from the VOM webconsole.This will be fixed in the SF 5.1 Patch 1 release.Workaround: Reinstall is required for VOM DB2-Hotfix (HF020008500-06.sfa),if the host is upgraded to SF 5.1. Use the deployment framework <strong>and</strong> reinstall thehotfix for DB2 (HF020008500-06.sfa) on the managed host.To resolve this issue1 In the Web GUI, go to Settings > Deployment.2 Select HF020008500-06 hotfix.3 Click Install.4 Check the force option while reinstalling the hotfix.A volume's placement class tags are not visible in the <strong>Veritas</strong> EnterpriseAdministrator GUI when creating a dynamic storage tiering placementpolicy (1880081)A volume's placement class tags are not visible in the <strong>Veritas</strong> EnterpriseAdministrator (VEA) GUI when you are creating a SmartTier placement policy ifyou do not tag the volume with the placement classes prior to constructing avolume set for the volume.Workaround:To see the placement class tags in the VEA GUI, you must tag the volumes priorto constructing the volume set. If you already constructed the volume set beforetagging the volumes, restart vxsvc to make the tags visible in the GUI.NULL pointer dereference panic with Solaris 10 Update 10 on x86 <strong>and</strong>Hitachi Data Systems storage (2616044)Due to a limitation with Solaris 10 Update 10 on x86, when the server is connectedto Hitachi Data storage, the system panics due to a NULL pointer deference duringthe boot cycle with the following stack trace:fffffe8000988570 unix:die+da ()fffffe8000988650 unix:trap+5e6 ()fffffe8000988660 unix:cmntrap+140 ()fffffe8000988870 scsi_vhci:hds_sym_path_get_opinfo+62 ()fffffe8000988920 scsi_vhci:vhci_update_pathinfo+5b ()fffffe80009889a0 scsi_vhci:vhci_pathinfo_online+2df ()fffffe8000988a10 scsi_vhci:vhci_pathinfo_state_change+202 ()fffffe8000988a70 genunix:i_mdi_pi_state_change+148 ()
Change language