Dynamic Root Disk A.3.10.* Release Notes (January 2012)

fails with the return code 1. The error message from
the command is "diskinfo: can't open /dev/rdisk/disk12_p1:
No such device or address
Issue Resolution
In order to clear out the outdated information on your new system, simply remove the registry file, which is used
by DRD to hold pertinent clone and disk information. Once a system is rehosted, this information no longer
applies. To remove the registry file:
# rm /var/opt/drd/registry/registry.xml
Status – plan to fix this in a future release.
4.3 Limitations due to OS interactions
Issue Description – LVM 2.x awareness not available on 11i v3 releases prior to September 2008
Prior to release B.11.31.A.3.4 of DRD, a disk specified in a DRD command as a target or mirror was not
checked for LVM 2.x usage or formatting. Release B.11.31.A.3.4 of DRD recognizes LVM 2.x disk formatting
on all releases of LVM 2.x. However, it only determines disk usage of LVM 2.x for the September 2008 release
and later.
If DRD is given the disk as a target or mirror with the
–x overwrite=true option, there is a possibility that
DRD will overwrite the LVM 2.x data disk when it is in use.
Issue Resolution
If the version of LVM 2.x on the system is from September 2008 or newer, and DRD B.11.31.A.3.4 is also
installed, DRD recognizes usage and formatting by an LVM 2.x volume group on the system. In this case,
DRD will not overwrite a disk in use by LVM 1.0, or LVM 2.x.
If you have DRD B.11.31.A.3.4 installed and a version of LVM 2.x released prior to September 2008, DRD
recognizes when a disk is formatted, but will overwrite it if the user specifies
overwrite=true on the
command line—even if the disk is in use. DRD cannot determine usage in this case.
If the versions of DRD and LVM are not updated on the system—as is the case for other usages (swap, dump,
database, etc.)—it is the system administrator’s responsibility in these cases to identify a disk that can be
overwritten by DRD.
Status – More of a limitation than a problem.
Issue Description – limitation on nsswitch.conf entries during drd runcmd
The
drd runcmd command does not support the following nsswitch.conf file entries on the clone while
managing software through
drd runcmd. If the file contains them, the drd runcmd command will fail.
passwd: compat
group: compat
hosts: nis [NOTFOUND=return] files
You might see the following error message during the execution of drd runcmd if your nsswitch.conf file
contains the "
hosts: nis" entry: