Some files from the Veritas licensing package (VRTSvlic
) may not be removed from a non-global zone that was created after VRTSvlic
was originally installed. An error message is displayed if all files are not removed. If the error was encountered, after the package removal process ends, run the following command from the global zone to remove any remaining VRTSvlic
files:
#
rm -rf
zonepath
/root/var/sadm/pkg/VRTSvlic
If you are upgrading a product, and non-global zones are configured, instead of selecting the installer upgrade procedure (or running the script from the command line), perform the upgrade in steps: Uninstall the product, uninstall the infrastructure packages (uninstallinfr
script), then reinstall the product.
Because of a Solaris bug in the pkgadd
command, the permissions on the /etc
directory may change during the installation of Symantec product packages. Check after an installation procedure to see if this occurred. Use the chmod
command to reset the permissions.
The Symantec Shared DBMS feature creates the following configuration files:
/etc/vxdbms/VERITAS_DBMS3_hostname/conf/databases.conf
/etc/vxdbms/VERITAS_DBMS3_hostname/conf/databases1.conf
/etc/vxdbms/VERITAS_DBMS3_hostname/conf/registration.dat
These configuration files are created or modified by vxdbms_start_db.pl
, vxdbms_start-server.pl
, and vxdbms_register.pl
respectively.
The files are writable by everyone if the file mode creation mask is insufficiently restrictive. Symantec strongly recommends that you restrict the default file mode creation permissions (using the umask
command) for root and administrator accounts to avoid a potential security issue. Specifically, change the group|world write and execute permissions in the default umask. At its least restrictive, the default umask for root should be 022. Symantec recommends setting to 077.