Error during upgrading repo from 3.2 to 4.2

[Former Member]

Hello All,

While performing the repository upgrade from 3.2 to 4.2 I faced below error.

Please, suggest me on this.

Regards,

Srinivas Bandi

[DayaJha · Accepted solution]

Hi Srinivas,

Issue is related to rights on database level.

Please ask your database administrator to assign full rights on metadata (local repository".

Please refer the below KBA for more details.

1969188 - The local repository upgrade was cancelled. (BODI-300056) - Data Services

https://service.sap.com/sap/support/notes/1371070

Thanks,

Daya

[Former Member · Accepted solution]

Thanks Daya for immediate reply.

As per your suggestion I have tried but the problem stays as is.

If you have any other solution, please suggest.

Thanks

Srinivas Bandi

[DayaJha · Accepted solution]

Hi Srini,

Please check the BODS version for more details please refer the below KBA

Coments in KBA:

Product updates and issues addressed in SAP Data Services 4.2 Support Pack 1

Patch 2 (DS 4.2 Patch 1.2)

ADAPT01715814
Upgrading Data Services repository to
version 14.2.1.0 on Microsoft SQL server database fails with an error message
“(BODI-20002) Error or warning in executing the SQL statement <alter table
AL_LANG alter column NAME nvarchar(128) not null >.  The message from the
underlying database is: <SQL submitted to ODBC data source <DB_NAME>
resulted in error <[Microsoft][ODBC SQL Server Driver][SQL Server]The index
'AL_LANG_INDX1' is dependent on column 'NAME'. [Microsoft][ODBC SQL Server
Driver][SQL Server]ALTER TABLE ALTER COLUMN NAME failed because one or more
objects access this column.>. The SQL submitted is <alter table AL_LANG
alter column NAME nvarchar(128) not null >.>. (BODI-20004) The local
repository upgrade was cancelled. (BODI-300056).” This issue has been fixed in
this release.

1985648 - Release Notes for SAP Data Services 4.2 Support Pack 1 Patch 3 (Version 14.2.1.622)

https://service.sap.com/sap/support/notes/1985648

Thanks,

Daya

[Former Member · Accepted solution]

Thanks Daya,

Instead of upgrading the repository we went through creation of  new repository approach and it worked fine .

While we had the backup of the jobs from the repository which were already upgraded on the different server.

Thanks,

Srinivas

[santossh]

Hi Srini,

Check out this SAP Note : 1972337

Regards,

Santosh