Veritas Storage Foundation 5.1 SP1 Cluster File System Release Notes (5900-1509, April 2011)

Veritas Storage Foundation for Databases (SFDB) tools known issues
The following are known issues in this release of Veritas Storage Foundation
products.
Upgrading Veritas Storage Foundation for Databases (SFDB)
tools from 5.0MP2 to 5.1SP1 (2003131)
While upgrading from 50mp2 to 51SP1 the following error message could be seen
when running sfua_rept_migrate:
# /opt/VRTSdbed/migrate/sfua_rept_migrate
Mounting SFUA Sybase ASA repository.
SFORA sfua_rept_migrate ERROR V-81-8903 Could not start repository database.
/usr/lib/dld.sl: Can't find path for shared library: libcur_colr.1
/usr/lib/dld.sl: No such file or directory
sh: 3845 Abort(coredump)
Symantec DBMS 3.0.85.0 vxdbms_start_db utility
ASA failed. Sybase ASA error code: [134].
Sybase ASA Error text: {{{}}}
SFORA sfua_rept_migrate ERROR V-81-9160 Failed to mount repository.
Using SFDB tools after upgrading Oracle to 11.2.0.2 (2203228)
The procedure which Oracle recommends for upgrading to Oracle 11.2.0.2 results
in the database home changing. After you upgrade to Oracle 11.2.0.2, you must
run the dbed_updatecommand with the new Oracle home provided as an argument
to the -H option before using any SFDB tools. After this step, the SFDB tools can
be used normally.
Database fails over during Flashsnap operations (1469310)
In an SFCFS environment, if the database fails over during Flashsnap operations
such as the dbed_vmsnap -o resync command and various error messages appear.
This issue occurs because Flashsnap commands do not create a VCS resource for
the SNAP disk group. As such, when the database fails over, only the primary disk
group is moved to another node.
Workaround
There is no workaround for this issue.
The error messages depend on the timing of the database failover. To fix the
problem, you need to bring the FlashSnap state to SNAP_READY. Depending on
45Storage Foundation Cluster File System Release Notes
Known issues