The DLO upgrade fails in case the database files are present in a customized path.

book

Article ID: 100034249

calendar_today

Updated On:

Description

Error Message

DLO Database Version:
     DLO Database Version  8.0
     Dedupe Database Version - 9.0.1

Cause

1. In case of Remote Database upgrades, when the “Remotemdfpath” key in Registry on DLO Administration Server machine is not updated with the root directory of Database folders after the Database files are moved to a different location.

2. In case of Standalone upgrades, when there are insufficient privileges on the Database files in the old Database files path.
This happens when the databases are detached from osql using inline queries or Microsoft SQL Server Management Studio, the permissions on the database files are automatically removed and only the user who detached the database would have permissions on the database files. This is the behavior of osql and management studio DB detach process.

Resolution

Workaround:
To resolve this issue:

1. Detach the DLO and Dedupe database files
Following are the commands to be run
a. osql.exe –E –S .\DBInstanceName –Q “sp_detach_db ‘DLO’”
b. osql.exe –E –S .\DBInstanceName –Q “sp_detach_db ‘dedupedb’”
 
2. The Folder Structure seen below should be followed to place the Database files
When the Database files are moved to a different location, the below folder structure should be followed for the DB files:
a. The DLO.mdf and DLO_log.ldf files should be placed under a folder "\Data". (Fig 2)

Fig 2
User-added image
b. The dedupedb.mdf and dedupedb_log.ldf files should be placed under "\Dedupe\Database\". (Fig 3)

Fig 3
User-added image
c. Data and Dedupe folders should be located under same root folder.
For example: E:\DB_files\Data\ and E:\DB_files\Dedupe\Database\

Note: The Root folder containing the Data and Dedupe folders should not contain any other files. It is recommended to have a dedicated folder to place the Database files for DLO.

3. Below Permissions should be given on the Database files
In case the Database files are copied instead of moving, below permissions should be given on the detached database files in the previous path. (Fig 4)
• SYSTEM account
• The user who performs the installation.

Fig 4
User-added image


4. Attach both the DLO and Dedupe database files from the new MDF and LDF path.
 
Following are the commands to be run:

a. osql.exe -E -S \ -Q "sp_attach_db 'DLO','DLO MDF file path including MDF file name', 'DLO LDF file path including LDF file name'"

b. osql.exe -E -S \ -Q "sp_attach_db 'dedupedb', 'dedupe MDF file path including MDF file name', 'Dedupe LDF file path including LDF file name'"
 
5. Run the upgrade scripts as mentioned below
osql -E -S “\” -d -i \

Note: By default the upgrade scripts are present in the DLO installation folder i.e. C:\Program Files\Veritas \Veritas DLO
On the DLO database where the DBInstanceName is DLO, the following commands need to be run:

a. osql -E -S \DLO -d DLO -i \DLODBUpgrade20.sql

b. osql -E -S \DLO -d DLO -i \DLODBUpgrade30.sql

c. osql -E -S \DLO -d DLO -i \DLODBUpgrade.sql

d. osql -E -S \DLO -d DLO -i \DLODBInstallXSP.sql

6. Below Registry keys should be updated:
When the Database files are moved to ,
On the Server machine, update the keys,

a. [HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Veritas DLO\AdminService]
"Data Path"="\Data\" (Fig 5)

Fig 5
User-added image
 
b. [HKEY_LOCAL_MACHINE\SOFTWARE\Veritas\Veritas DLO\RemoteDB]
"Remotemdfpath"="\"
(Fig 6)

Fig 6
User-added image

NOTE 1: In case the upgrade is performed from versions prior to DLO 9.0, then the registry key path would be:
HKEY_LOCAL_MACHINE\SOFTWARE\veritas\veritas DLO\
NOTE 2: When the Database files are in the same machine, the “Remotemdfpath” key is not applicable.

Note: For future DLO upgrades, it is mandatory that the registry keys mentioned in Step 6 are updated with the appropriate path where the database files are present.

 

Issue/Introduction

The DLO upgrade fails in case the database files are present in a customized path.

The database version is not upgraded to 9.0.1 when the database files are manually moved to a different path prior to upgrade. (See Fig 1)

NOTE 1: Either or both of the DLO database version may not be updated to the latest version 9.0.1.
NOTE 2: The below screenshot reflects that the DLO Database version is not updated to 9.0.1 when upgraded from Veritas DLO 8.0.

Fig 1
User-added image