During installation of 22.214.171.124, 126.96.36.199 or 188.8.131.52, if the <install_path>/openv/db/data directory is a link, the installation will fail on AIX, Linux and Solaris operating systems. HP Systems are not impacted by this problem.
This problem does not occur if the <install_path>/openv/db directory is a link.
On Linux and AIX platforms:
ERROR: Unable to create/upgrade the NB database. Refer to the log
pkgrm: ERROR: unable to remove existing directory at </opt/openv/db/data>
This issue is due to how the native package installers recognize symbolic links from <install_path>/openv/db/data to an alternate location.
There are two methods to work around this problem:
Move the database files back to the the <install_path>/openv/db/data directory before beginning the patch installation.
Move the entire <install_path>/openv/db directory to the alternate location and create a symlink of <install_path>/openv/db to the alternate location.
Using the following example configuration:
<install_path>/openv/db/data is a symlink to /space/data
ls -al <install_path>/openv/db
drwxr-xr-x 7 root bin 512 Jun 24 15:40 .
drwxr-xr-x 15 root bin 1024 Jun 24 15:40 ..
drwxr-xr-x 2 root bin 1024 Jun 24 15:40 bin
lrwxrwxrwx 1 root root 11 Jun 19 15:33 data -> /space/data
Contents of the /space/data directory are:
-rwxr-xr-x 1 root root 101 Jun 19 15:31 .odbc.ini.az
-rw------- 1 root root 26218496 Jun 19 15:31 DARS_DATA.db
-rw------- 1 root root 26218496 Jun 19 15:31 DARS_INDEX.db
-rw------- 1 root root 26218496 Jun 24 04:12 DBM_DATA.db
-rw------- 1 root root 26218496 Jun 24 04:12 DBM_INDEX.db
-rw------- 1 root root 26218496 Jun 19 15:31 EMM_DATA.db
-rw------- 1 root root 26218496 Jun 19 15:31 EMM_INDEX.db
-rw------- 1 root root 26218496 Jun 24 04:32 JOBD_DATA.db
-rw------- 1 root root 2441216 Jun 24 15:27 NBAZDB.db
-rw------- 1 root root 4096 Jun 24 15:27 NBAZDB.log
-rw------- 1 root root 2994176 Jun 24 15:33 NBDB.db
-rw------- 1 root root 4096 Jun 24 15:33 NBDB.log
-rw------- 1 root root 26218496 Jun 19 15:31 SEARCH_DATA.db
-rw------- 1 root root 26218496 Jun 19 15:31 SEARCH_INDEX.db
-rw------- 1 root root 399 Jun 19 15:39 vxdbms.conf
-rw------- 1 root root 0 Jun 19 15:31 vxdbms_conf.lock
Instructions for Method 1:
1. Shutdown the NetBackup processes
2. Remove the <install_path>/openv/db/data link.
3. Make an <install_path>/openv/db/data directory:
4. Copy the contents of the /space/data directory to <install_path>/openv/db/data:
cp /space/data/* <install_path>/openv/db/data/
5. Install the specified patch.
6. If needed, once the patching is finished, move the data back to /space/data and recreate the link:
cp <install_path>/openv/db/data/* /space/data
mv <install_path>/openv/db/data <install_path>/openv/db/data_MMDDYY
ln -s /space/data <install_path>/openv/db/data
7. Start the NetBackup processes.
8. If step 6 was completed, the <install_path>/openv/db/data_MMDDYY can be removed in a few days after verifying there are no problems with the link and database information.
Instructions for Method 2:
1. Shutdown the NetBackup processes
2. Remove the <install_path>/openv/db/data link:
3. Create a /space/db directory
4. Copy the contents of <install_path>/openv/db directory to /space/db
cp -r <install_path>/openv/db/* /space/db
5. Rename the <install_path>/openv/db directory to something different:
mv <install_path>/openv/db <install_path>/openv/db.MMDDYY
6. Move the /space/data directory into /space/db:
mv /space/data /space/db/
7. Link the /space/db path to the original location:
ln -s /space/db <install_path>/openv/db
8. Install the specified patch.
9. Start the NetBackup processes.
10. The <install_path>/openv/db.MMDDYY can be removed in a few days after verifying there are no problems with the link and database information.
ETA of Fix:
Symantec Corporation is committed to product quality and satisfied customers. This issue is currently being considered by Symantec Corporation to be addressed in a forthcoming Maintenance Pack, Release Update, or version of the product. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk. Please refer to the maintenance pack readme or contact NetBackup Enterprise Support to confirm this issue (Etrack 2783980) was included in the specified release.
Note the resolution of this issue depends on the patch installation after 184.108.40.206. This means that systems being patched to 220.127.116.11 or later will be susceptible to this problem if the version of NetBackup at the time of patch installation is 18.104.22.168 or earlier.
This issue is scheduled to be fixed after the following release.
- NetBackup 22.214.171.124
As future maintenance packs are released, please visit the following link for download and readme information: