Database Management

DPA - Version 2024.2 Upgrade Issue with Oracle Repo

The purpose of this article is to cover resolution steps in resolving a known issue when upgrading DPA 4024.2 on an Oracle Database.

First published date

5/16/2024 7:13 PM

Last published date

2/19/2025 5:17 AM

Overview

While upgrading DPA to 2024.2 , the repository upgrade is failing at customer’s environment with below error. This issue is seen for ORACLE repository when DOUBLE_BYTE_SYSTEM value is set to TRUE in CONPRM table. This issue is not seen with SQL server, Azure SQL and MySQL repositories. The issue is also not seen when the value of DOUBLE_BYTE_SYSTEM is FALSE (Default).

image.png

Product section

Database Performance Analyzer

Cause

As per analysis Identified that in CONPRM table ,property DOUBLE_BYTE_SYSTEM was TRUE.

image.png

If this property is true , DPA’s DDLTranslator let the NVARCHAR datatype used as is during script execution.

As NVARCHAR(4000) is not be a suitable length in the standard Oracle server setups, therefore script error out : “specified length too long for its datatype”

Whereas,if the property is false translator will process NVARCHAR to VARCHAR and executes the script.

VARCHAR(4000) is under valid range and therefore DPA installer runs smoothly.

Resolution

Steps for 2024.2 upgrade:

  1. Check DOUBLE_BYTE_SYSTEM in Advance options → System Options → Support Options

Default value of this property is FALSE.

image.png

OR

run query on DPA repo : select V from CONPRM where P='DOUBLE_BYTE_SYSTEM'

  1. If it is set to true , update it to false from back-end (this Advance option is read only from UI) by running query on DPA repository schema as :

update CONPRM set V = 'false' where P = 'DOUBLE_BYTE_SYSTEM'

  1. Run the DPA upgrade.

  2. Once the upgrade is successfully done

  3. Reset the property to true from back-end

update CONPRM set V = 'true' where P = 'DOUBLE_BYTE_SYSTEM'