Table KMC_URIMAPPER - Conversion currently not possible

[Former Member]

Applies to:

SAP NetWeaver 7.0 EhP1 SP06 on Database DB2 UDB.

Summary

While we were upgrading our Enterprise Portal system to SAP NetWeaver 7.0 EhP1 SP06 stack from SP03 via JSPM, it was keep failing at deployment of component KMC-BC. I had to spend lots of hours to resolve this issue.

The problem occurs due to a change in width of field EXTERNAL_KEY in table KMC_URIMAPPER. Changing field width is not possible with DB2 V8 (and lower), and decreasing field widths is still not possible with DB2 V9 (and higher).

Author(s):    Siva Kumar Arivinti

Company:   Deloitte Consulting India Pvt Ltd.

Created on:  14 April 2012

Author Bio

Siva Kumar Arivinti is currently working with Deloitte Consulting India Pvt Ltd. as Consultant in AMS service line.

SAP NetWeaver Consultant with around 5 years of experience in SAP Basis and DB2 DBA Administration.
Expertise in Production support, Installations and Software Life Cycle Management including EHP/Release Upgrades.

Symptom:

Deployment fails with the following error message.

db6-Info:  Table KMC_WF_SUBSTITUTE contains  data. Table KMC_URIMAPPER: Conversion currently not possible

You can apply any one of the following solutions to resolve this issue.

Solution #1:

1. Locate the KMC SCA that is to be deployed and causes the error.
2. Open the SCA using WinRAR. (It is mandatory to use WinRAR as it allows for the reliable in-place modification of the archive that is necessary.) Inside the SCA, locate and open the SDA 'com.sap.netweaver.bc.db.sda'.
3. Open the file 'KMC_URIMAPPER.gdbtable'. Change the number '2048' inside to '2047' (it's is easily locatable, there is only one such number in the file).
4. Close WinRAR and copy the modified KMC SCA into …/EPS/in.
5. Resume upgrade from the point of failure.

Solution #2:

As explained in the note 1442501, perform the following steps at DB level.

1. Export and backup the content of table KMC_WF_SUBSTITUTE.
2. Delete the content of table KMC_WF_SUBSTITUTE.
3. Resume upgrade from the point of failure.
4. Import the content that was exported on step 1 into table KMC_WF_SUBSTITUTE