Attempting to move the EMM database configuration files, data files and Transaction logs fails. This is required before an upgrade to move the files back to the original location prior to the upgrade.
The CLI reports the following when executing the command:
# /usr/openv/db/bin/nbdb_move -data /usr/openv/db/data -index /usr/openv/db/data -tlog /usr/openv/db/data
Move of database files failed.
There is an extra space in /usr/openv/netbackup/db/data/vxdbms.conf This can be demonstrated by running:
cat -evn /usr/openv/netbackup/db/data/vxdbms.conf
(this command will print a $ at the end of each line)
/usr/openv/netbackup/logs/nbdb/<date>.log reports the following:
13:30:12.583  <4> nbdb_move: Entering.
13:30:12.583  <4> nbdb_move: /usr/openv/db/bin//nbdb_move.bin -data /usr/openv/db/data -index /usr/openv/db/data -tlog /usr/openv/db/data
13:30:12.619  <2> vnet_pcache_init_table: ../../libvlibs/vnet_private.c.232: 0: starting cache size: 200 0x000000c8
13:30:12.620  <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1514: 0: found in file cache name: tinbubm2800p
13:30:12.620  <2> vnet_cached_getaddrinfo_and_update: ../../libvlibs/vnet_addrinfo.c.1515: 0: found in file cache service: NULL
13:30:12.628  <4> nbdb_move: SQLANY = /usr/openv/db
13:30:12.628  <4> nbdb_move: SQLANY11 = /usr/openv/db
13:30:12.628  <4> nbdb_move: LD_LIBRARY_PATH = /usr/openv/db/lib 13:30:12.628  <4> nbdb_move: SATMP = /usr/openv/tmp/sqlany
13:30:12.631  <16> dbspaces_exist: File does not exist: /usr/openv/netbackup/db/data /EMM_DATA.db
13:30:12.631  <16> nbdb_move: Error locating data dbspaces
13:30:12.631  <4> nbdb_move: Exiting with rc = 12
Note the space between /usr/openv/netbackup/db/data and /EMM_DATA.db
VXDBMS_NB_SERVER = NB_SERVER
VXDBMS_NB_PORT = 13785
VXDBMS_NB_DATABASE = NBDB
VXDBMS_AZ_DATABASE = NBADB
VXDBMS_NB_DATA = /usr/openv/netbackup/db/data (at the end of this line there was an extra space, which was causing the problem)
VXDBMS_NB_INDEX = /usr/openv/netbackup/db/data
VXDBMS_NB_TLOG = /usr/openv/netbackup/db/data
VXDBMS_NB_STAGING = /usr/openv/db/data/staging
VXDBMS_NB_PASSWORD = eff741a725e20860787bfc4b57a3b72b6bc64302c23a9c42
AZ_DB_PASSWORD = Jj8mkP3sKTo=
VXDBMS_NB_FULL_KEYWORD = NBDB:3460312:1398402001:F
VXDBMS_NB_INCREMENTAL = NBDB.log.1
VXDBMS_AZ_INCREMENTAL = NBAZDB.log.1
Remove any extra spaces from the end of the lines in the file vxdbms.conf, and the command will execute with no problem.
ETA of Fix:
Symantec has acknowledged that the above mentioned issue (Etrack 3512367) is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers. 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.
This issue is present on versions 7.0 (all versions), 7.1 (all versions) and 126.96.36.199 (all versions)