Veritas Storage Foundation for Oracle 5.0 Release Notes, First Edition

Problem
The sfua_db_config -o startdb command does not print a message to indicate whether
the SFO repository database was successfully started or not.
Workaround
Check for the success or failure by subsequently running the following command:
sfua_db_config -o dbstatus
Problem
If a database contains a symbolic link to Quick I/O files, Oracle 10g displays the following
error:
ORA-27094: raw volume can not be used
Workaround
To avoid this error, do not use symbolic links to Quick I/O files. This issue applies to Oracle
version 10.1.0.2.
Problem
Running statistic tasks from the Web GUI is not supported when connecting to a 4.1 host.
If you try to run Create Statistic Task, the following error message will be displayed:
Error V-40-49408-42 - An interface with the unique identifier
specified does not exist for this object.
Workaround
No workaround is available for this problem.
Problem
The Oracle GUI does not support Oracle users having a different locale from the super user
locale. The GUI will display unintelligible characters if the SFO repository server starts with
a locale that is different from the Oracle user locale (client).
Workaround
The locale for Oracle GUI should be the same as the super user locale.
Problem
Problems with display of deep mapping topology in PC-based UNIX emulators like Exceed.
Workaround
Use the Windows VEA client instead of running the UNIX VEA client using the emulators.
Problem
You can click the Quota tab for the Storage Checkpoint available from the GUI. If the file
system and the Storage Checkpoint are on a version prior to Disk Layout Version 6, you
will see the unknown error code 4646.
Workaround
For Disk Layout Version 5 and older, to display Storage Checkpoints Quotas from the GUI,
complete the following steps:
1. Using Veritas File System 3.5, create a file system.
2. Upgrade to Veritas File System 5.0, but do not upgrade the file system disk layout
version.
3. Create a checkpoint and then click the Quota tab accessible from the GUI.
Problem
Renaming columns in login.sql can sometimes cause scripts to fail or produce incorrect
results.
Workaround
Known Problems And Workarounds 17