SRM 4.0 upgrade to SRM 7.0 - Error in Phase PARDIST_SHD

[gautam_poddar2]

Hello,

I am upgrading the SAP SRM 4.0 / MSSQL 2005 / Windows 2003 (64 bit) to SRM 7.0 but I am getting this error in the phase PARDIST_SHD

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

DISTRIBUTION ERRORS and RETURN CODE in DS100310.SD1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

2EEDA300 No active nametab exists for "CDBC_LANG_TABLES"

Long text:

Cause

Thee is no active nametab in the system, although an

active ABAP/4 Dictionary object was expected.

System Response

None

What to do

Reactivate the ABAP/4 Dictionary object.

2EEDA432 Termination due to inconsistencies

2EEDA471 Result "CDBC_LANG_TABLES": Action: "DNA" Mode flag: "R" Return code: "9"

2EEDA300 No active nametab exists for "CRMC_ADJCONT"

Long text: see above

2EEDA432 Termination due to inconsistencies

2EEDA471 Result "CRMC_ADJCONT": Action: "DNA" Mode flag: "R" Return code: "9"

2EEDA300 No active nametab exists for "CRMC_HH_SRV_SYNC"

Long text: see above

2EEDA432 Termination due to inconsistencies

2EEDA471 Result "CRMC_HH_SRV_SYNC": Action: "DNA" Mode flag: "R" Return code: "9"

2EEDA300 No active nametab exists for "CRMC_PROCESSFLTT"

Long text: see above

2EEDA432 Termination due to inconsistencies

2EEDA471 Result "CRMC_PROCESSFLTT": Action: "DNA" Mode flag: "R" Return code: "9"

2EEDA300 No active nametab exists for "CRMC_PROCESS_FLT"

Long text: see above

2EEDA432 Termination due to inconsistencies

2EEDA471 Result "CRMC_PROCESS_FLT": Action: "DNA" Mode flag: "R" Return code: "9"

2EEDA300 No active nametab exists for "IPCE_MON_NODES"

Long text: see above

2EEDA432 Termination due to inconsistencies

2EEDA471 Result "IPCE_MON_NODES": Action: "DNA" Mode flag: "R" Return code: "9"

What will I do now? How will resolve this issue? Please help me ASAP

Thanks

Gautam

[Former Member]

Go to SE11, Menu->Utilities->Database Object->Check

Menu->Utilities->Runtime Object->Check

If there are inconsistency, please follow note 211492 to adjust the inc

onsistency in original instance . But if these tables are obsolete,

for example doesn't exist in the system any more, you could also choose the option to 'Ignore' the error and

continue with the upgrade. But this is a BC-UPG issue.

Regards

Lauren

[Former Member]

Hi,

what happend to this issue.

We will doing an upgrade like you next week and have seen the tables as inconsistency in DB02 too.

Kind regards

Sven