Dynamic Root Disk A.3.13 * Release Notes (766141-001, March 2014)

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.
Workaround
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
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:
ERROR: Could not contact host "myserver". Make sure
the hostname is correct and an absolute pathname
is specified (beginning with "/").
You might see the following error message during the execution of drd runcmd if your
nsswitch.conf file contains the "passwd compat" or "group: compat" entries:
ERROR: Permission is denied for the current operation.
There is no entry for user id 0 in the user
database. Check /etc/passwd and/or the NIS
user database.
Workaround
Because DRD does not need NIS to be running during swinstall, swremove, or update you
can move the nsswitch.conf file on the clone to a temporary location. After you are done
modifying the clone, you can move it back.
# drd mount
# bdf
# mv /var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf \
/var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf.orig
# drd runcmd <command_to_run>
# mv /var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf.orig \
/var/opt/drd/mnts/sysimage_001/etc/nsswitch.conf
# drd umount
Limitations due to OS interactions 17