Veritas Storage Foundation for Oracle 5.0 Release Notes, First Edition

The maximum class name length is 29 characters.
• Problem
The tablespace folder is empty when the Oracle database is started from the Oracle GUI,
without running the dbed_update command from the command line. Re-scanning from
the Oracle GUI does not solve the problem.
Workaround
Run the dbed_update command from the command line before starting an Oracle database
from the GUI.
• Problem
Repository changes resulting from executing SFDB Storage Checkpoint CLIs do not get
reflected immediately in the SFO GUI. The affected commands are dbed_update,
vxckpt_create, vxckpt_mount, vxckpt_umount, and vxckpt_remove.
Workaround
Manually refresh from the SFO GUI or wait for 30 minutes because the SFO provider will
automatically rescan after every 30 minutes.
• Problem
The Web GUI statistic scheduler uses the client timestamp instead of the server timestamp.
This causes the first statistic collection to be skipped. For example, suppose the machine
time is 14:00 and the client time is 13:45. If the user wants to have three samples taken starting
at 13:45, with 30 minutes interval between each sample, only two samples will be shown:
one at 14:15 and another at 14:45.
Workaround
Ensure that the system time of the web server is the same as the system time of the backend
server on which the vxdbd daemon is running.
• Problem
When using the Web GUI with the Mozilla Firefox browser, the Refresh command in the
View Statistics wizard does not work.
Workaround
No workaround is available. You must use Internet Explorer instead.
• Problem
If you specify with the dbed_vmsnap command a snapplan that does not exist, the following
error is displayed:
SFORA dbed_vmsnap ERROR V-81-6518
Could not find snapplan'snap_plan' in repository.
/opt/VRTSdbed/bin/dbed_vmsnap[21]: test: argument expected.
Workaround
Correct the name of the snapplan to be one that exists and re-run the dbed_vmsnap
command.
• Problem
Changing the communication port number in the /etc/vx/vxdbed/admin.properties
requires resetting the file permission.
Workaround
If you change the communication port number in /etc/vx/vxdbed/admin.properties,
you must change the permission of this file to 444 by using the following command:
chmod 444 /etc/vx/vxdbed/admin.properties
16 Veritas Storage Foundation for Oracle (SFO) 5.0 Release Notes