Table class to container mapping-Solution Manager Upgrade 7.0 to 7.1

[Former Member]

Hi All,

I am in the process of upgrading the solution Manager from 7.0 EHP1 to 7.1.

Following is the error i am getting

****************************

NFO: An inconsistency has been detected in your system:

Container pair 'PSAPSR3BMCD'/'PSAPSR3BMCI' for tabart 'YBMC' not identical.

The inconsistency could cause problems when new tables are created. It may additionally lead to incorrect free space requirements.

You are urged to fix the entries listed on the previous page now and repeat the check. Check SAP note 541542 for more information.

************************

These are the entries in Table TAORA

TABART TABSPACE

APPL0 PSAPSR3

APPL1 PSAPSR3

APPL2 PSAPSR3

CLUST PSAPSR3

DDIM PSAPSR3

DFACT PSAPSR3

DODS PSAPSR3

POOL PSAPSR3

SDIC PSAPSR3

SDOCU PSAPSR3

SLDEF PSAPSR3700

SLEXC PSAPSR3700

SLOAD PSAPSR3

SPROT PSAPSR3

SSDEF PSAPSR3700

SSEXC PSAPSR3700

SSRC PSAPSR3

TEMP PSAPSR3

USER PSAPSR3USR

USER1 PSAPSR3USR

USER2 PSAPSR3BMCD

YBMC PSAPSR3BMCD

IAORA

Data class TablespaceName/index

APPL0 PSAPSR3

APPL1 PSAPSR3

APPL2 PSAPSR3

CLUST PSAPSR3

DDIM PSAPSR3

DFACT PSAPSR3

DODS PSAPSR3

POOL PSAPSR3

SDIC PSAPSR3

SDOCU PSAPSR3

SLDEF PSAPSR3700

SLEXC PSAPSR3700

SLOAD PSAPSR3

SPROT PSAPSR3

SSDEF PSAPSR3700

SSEXC PSAPSR3700

SSRC PSAPSR3

TEMP PSAPSR3

USER PSAPSR3USR

USER1 PSAPSR3USR

USER2 PSAPSR3BMCI

YBMC PSAPSR3BMCI

I have gone with the SAP note 541542 and 778784. But could not undesrstand the inconsistency.

The table space PSAPSR3BMCD and PSAPSR3BMCI are used for BMC patrol .

Br

Anthony

[former_member263703]

Hi

I recently performed BW upgrade Source NW 7.3 to NW 731 SP8 and run into similar issue  in preprocessing phase using SUM 1.0.8 version .I checked  below  OSS notes and however it did not help even updatedTAORA IAORA tables and retried but still run into same error message

Note 541542 - Upgrade phase INIT_CNTRANS: Container inconsistency

Note 777615 - Incorrect data class/database container assignment

Note 46272 - Implement new data class in technical settings

          In order to overcome the issue I restored back system (since my system was non prod) to old version of DB and created table space PSAPSR3731 in advance with default options using brtools  and then restarted SUM from beginning and did NOT  run in to issue and pass pre-processing stage  and execution stage .

What i notice some how shadow instance did not create proper table structure and it fail to sync up with main db in order to start execution phase .

Thanks

Siraj

[Former Member]

Hello,

The entries in TAORA and IAORA should always be identical.

What are the tablespace names you have in the system? Do you have any of them as PSAPSR3BMCI

This tablespace seems to get created during incremental conv.

I would go to SE16 -> Table IAORA and check the tables (Ctrl F7) one by one. Also I would change the name

PSAPSR3BMCI to PSAPSR3BMCD and rerun the upgrade depending on PSAPSR3BMCI

exists or PSAPSR3BMCD tablespace exists.

Regards,

Sai

[former_member189725]

Please check if there are tablespaces with the names PSAPSR3BMCD and PSAPSR3BMCI using DBACOCKPIT.

Probably there will be tablespaces with the name PSAPSR3BMC.

If so , edit the entries in TAORA and IAORA

TAORA

USER2 PSAPSR3BMC

YBMC PSAPSR3BMC

IAORA

USER2 PSAPSR3BMC

YBMC PSAPSR3BMC

[Former Member]

Hi Ratnajit,

No the tablespace in the DBACOCKPIT are the same as TAORA and IAORA.

PSAPSR3BMCD

PSAPSR3BMCI

Br

Anthony

[former_member189725]

Please check if the tablespace PSAPSR3BMCI has objects in it .

select count(*) from dba_indexes where TABLESPACE_NAME='PSAPSR3BMCI';