VERITAS Storage Foundation 4.1 Release Notes

VERITAS Storage Foundation Release Notes

Software Limitations

Storage Checkpoint Limitations

◆ You cannot create a clone database using a mounted Storage Checkpoint. [32726]

◆ You must r un t he dbed_update command after upgrading to VERITAS Storage Foundation

4.1 for Oracle from a previous release. This will allow you to roll back to a Storage

Checkpoint that was created prior to this release. [86431]

◆ If you create an Oracle instance using the spfile option, you must run the dbed_update

command before you can successfully perform any Storage Checkpoint or Database FlashSnap

functions.

VEA and VxDBA Menu Utility Limitations

◆ VERITAS Enterprise Administrator (VEA) and the VxDBA menu utility do not display

tablespace information when the v$table column names are changed using the SQL*Plus

profile facility. Normally this happens when SQL*Plus settings are used in login.sql to

change column names in reports. [34446]

◆ VEA may display system fonts incorrectly. On a Japanese desktop, VEA may incorrectly

display system fonts.

Japanese characters may not be properly displayed when you select the

non-default font for the VEA GUI.

Database FlashSnap Limitations

◆ The Database FlashSnap feature does not support RAID-5 volumes. [34570]

◆ When cloning a database using Database FlashSnap, the Oracle database must have at least

one mandatory archive destination, otherwise dbed_vmchecksnap results in this error

message:

SFORA dbed_vmchecksnap ERROR V-81-5677 Could not find a

mandatory, primary and valid archive destination for database

PROD.

Please review the LOG_ARCHIVE_DEST_n parameters and check

v$archive_dest.

This example shows how to establish a mandatory archive destination using SQL*Plus:

alter system set log_archive_dest_1 =

'LOCATION=/ora_mnt/oracle/oradata/PROD/archivelogs MANDATORY

[REOPEN]' [scope=both];

For more information about Oracle parameters for archiving redo logs, see your Oracle

documentation. [

270905]

◆ Existing snapshot plexes created by the vxassist command are not supported. A

combination of snapshot plexes created by vxassist and vxsnap is also not supported.