Veritas Storage Foundation for Oracle 5.0 Release Notes, First Edition

• Problem
Removing the SFO respository database using the sfua_db_config -o dropdb command
does not remove the /etc/vx/vxdbed/.odbc.ini file.
Workaround
After running sfua_db_config -o dropdb, manually remove .odbc.ini using the
rm command:
rm /etc/vx/vxdbed/.odbc.ini
• Problem
Creating Oracle 10gR1 database through ODM on a raw device, displays error message
similar to the following:
ORA-00200: controlfile could not be created
Workaround
After disabling ODM on the raw device, the database can be successfully created.
• Problem
If an instant checkpoint is created for a database that use Oracle Managed Files (OMF) control
files, creating a clone with the dbed_clonedb command will fail with following message:
SFORA dbed_clonedb ERROR V-81-7052 OMF data or redo files are not
supported for Instant Checkpoint clones.
Workaround
Either use offline or online checkpoints, or convert OMF control files to non-OMF.
• Problem
Clicking the Help button on the Oracle GUI wizard displays the following error message:
Error V-39-53246-8 Get EntryPoint failed.
Please check the manifest related information
Workaround
Press OK and ignore the error.
• Problem
The sfua_db_config command does not check if the disk being used for the repository
is a local disk or a shared disk in the case of an HA configuration.
Workaround
No workaround is available for this problem. The user must rely on the disk information
on which the repository is being created.
• Problem
Creating an online checkpoint for a database that has only DB_RECOVERY_FILE_DEST set
as an archive log destination causes a warning message to be printed from the checkpoint
creation command. The message states that a clone cannot be created from this checkpoint.
If the dbed_clonedb command is subsequently run using this checkpoint, database recovery
will fail with an Oracle error.
Workaround
To successfully create a clone of a database from an online checkpoint, define a mandatory
archive log destination that is not DB_RECOVERY_FILE_DEST.
• Problem
The dbdst_admin -o rmclass command fails when attempting to remove a class name
of 30 characters or more.
Workaround
Known Problems And Workarounds 15