Self-Solve Knowledge Search

Minimize Maximize
Upgrading from Asset Manager 9.32 to 9.50 using oracle causes error related to a...
Title :
Upgrading from Asset Manager 9.32 to 9.50 using oracle causes error related to a duplicate column name
Document ID :
KM01510335
Product - Version:
asset manager 9.50 ;
OS :
Windows
Updated :
Fri Apr 10 15:01:42 GMT 2015
Summary :
While running the update from Application Designer on Asset Manager 9.50, run into an issue with the following error message. 2015/03/31 15:16:20.524 4 1 (-2006) Oracle error: ORA-00957: duplicate column name 2015/03/31 15:16:20.524 4 1 (-2006) SQL statement 'CREATE TABLE amStatistic(lStatisticId NUMBER(10) Default 0 NOT NULL, dtLastModif DATE, AqlAgregExpr VARCHAR2(255 CHAR), b3D NUMBER(5) Default 0 NOT NULL, bLegend NUMBER(5) Default 0 NOT NULL, bMarble NUMBER(5) Default 0 NOT NULL, bScript NUMBER(5) Default 0 NOT NULL, bStacked NUMBER(5) Default 0 NOT NULL, bStored NUMBER(5) Default 0 NOT NULL, bUseAgregExpr NUMBER(5) Default 0 NOT NULL, Colors VARCHAR2(500 CHAR), GroupBy VARCHAR2(255 CHAR), Name VARCHAR2(128 CHAR), seType NUMBER(5) Default 0 NOT NULL, SQLName VARCHAR2(32 CHAR), SubGroupBy VARCHAR2(255 CHAR), TableName VARCHAR2(25 CHAR), Title VARCHAR2(128 CHAR), lCommentId NUMBER(10) Default 0 NOT NULL, lDataId NUMBER(10) Default 0 NOT NULL, lDomainId NUMBER(10) Default 0 NOT NULL, lFilterId NUMBER(10) Default 0 NOT NULL, lIconId NUMBER(10) Default 0 NOT NULL, lScriptId NUMBER(10) Default 0 NOT NULL, UPPERStatistique_SQLName VARCHAR2(33 CHAR), UPPERStatistique_SQLName VARCHAR2(32 CHAR) )' could not be executed
Problem

Problem description

While running the update from Application Designer on Asset Manager 9.50, run into an issue with the following error message.

 

2015/03/31 15:16:20.524    4    1    (-2006) Oracle error: ORA-00957: duplicate column name

2015/03/31 15:16:20.524    4    1    (-2006) SQL statement 'CREATE TABLE amStatistic(lStatisticId NUMBER(10) Default 0 NOT NULL, dtLastModif DATE, AqlAgregExpr VARCHAR2(255 CHAR), b3D NUMBER(5) Default 0 NOT NULL, bLegend NUMBER(5) Default 0 NOT NULL, bMarble NUMBER(5) Default 0 NOT NULL, bScript NUMBER(5) Default 0 NOT NULL, bStacked NUMBER(5) Default 0 NOT NULL, bStored NUMBER(5) Default 0 NOT NULL, bUseAgregExpr NUMBER(5) Default 0 NOT NULL, Colors VARCHAR2(500 CHAR), GroupBy VARCHAR2(255 CHAR), Name VARCHAR2(128 CHAR), seType NUMBER(5) Default 0 NOT NULL, SQLName VARCHAR2(32 CHAR), SubGroupBy VARCHAR2(255 CHAR), TableName VARCHAR2(25 CHAR), Title VARCHAR2(128 CHAR), lCommentId NUMBER(10) Default 0 NOT NULL, lDataId NUMBER(10) Default 0 NOT NULL, lDomainId NUMBER(10) Default 0 NOT NULL, lFilterId NUMBER(10) Default 0 NOT NULL, lIconId NUMBER(10) Default 0 NOT NULL, lScriptId NUMBER(10) Default 0 NOT NULL, UPPERStatistique_SQLName VARCHAR2(33 CHAR), UPPERStatistique_SQLName VARCHAR2(32 CHAR) )' could not be executed

Cause

The cause might be related to the internal process that the upgrade performs. It will be investigated deeper the root cause.

The error has been reported an a case with develop has been raise the solution will be delivered on QCCR1E122172

Affected database types
• Oracle
• DB2

Affected upgrading AM versions
• AM 5.2x
• AM 9.3x
• AM 9.4x

Fix

Workaround summary
The workaround is to use the Alter Table mode to migrate an Oracle/DB2 database of a previous Asset Manager version to Asset Manager 9.50.

Workaround prerequisites
• The upgrading Asset Manager database is Multi-Tenancy disabled
• The workaround applies to only Oracle database
• It supports the migration from Asset Manager 5.2x, 9.3x and 9.4x
• Reference to the Asset Manager 9.50 Migration guide for the detailed information of migration

Steps to apply the workaround
•             Open the Asset Manager 9.50 Application Designer
•             Hold the Ctrl key and click Edit > Options
•             Locate the Advance mode > UseAlterTable and set its value to 'Yes'
•             Close the Application Designer
•             Follow the steps described in the Asset Manager 9.50 Migration guide to perform the database migration

A database backup is required before the migration.

Please track via SSO: QCCR1E122172