Object Versions invalid after DB actions (table copy)

[waelkensd]

Hi all,

recently I have encountered some weird issues during a little archiving run I'm doing on MM_MATBEL.

Tables involved:

IMEXT

MKPF

MSEG

MSEGO1

MSEGO2

NAST

OIAQB

After the archiving was done I logically went for an online reorg of these tables. This worked for all tables, except for MSEG. The reason was the following:

BR1962W Table SAPSR3.MSEG has more than 255 columns

BR1967W Table SAPSR3.MSEG would be implicitly decompressed during reorganization

BR1111I Reorganization of table SAPSR3.MSEG will be skipped

So apparently the table had been compressed in the past (when it had less than 255 columns) and now cannot be rebuilt anymore with compression.

In the following note they mention a workaround/solution:

http://service.sap.com/sap/support/notes/1872983

The solution consists of copying the compressed table into a newly created table. After some problems with the script (which will be fixed) and consulting SAP Support I finally succeeded in rebuilding the tables.

After this rebuild there are numerous dumps (LOAD_FORMAT_ERROR,  DDIC_TYPE_INCONSISTENCY, LOAD_TYPE_VERSION_MISMATCH, etc...) in SAP itself, rendering the system practically unusable.

One workaround is to manually re-activate the object generating the shortdump, this does solve the issue on that object, but that's it.

I can hear you think: "Run SGEN, you stupid". Well, I did, and it did not help, or at least not much. It did regenerate some objects, but apparently it's not sufficient.

To me it seems like some inconsistency in the Dictionary, caused by the tables that were rebuilt. Is there a way that we can regenerate the Data Dictionary of SAP? Or at least fix the DDL inconsistencies?

The tables that I have recreated using note 1872983 are:

LIPS

MSEG

VBAP

VBRP

ZEKPO

N2CA02

N2CA03

N2CA04

N2CA05

N2CA09

PA0008

PA0146

PA0701

PA0706

PA0764

PA0897

PB0008

T5ITT7

RSEUMOD

COMPMOVE

WDFR_POS

N3BGF1008

OIUH_RV_JE

OIUH_RV_RJE

TTONFTVZZBEPP

TLVC_DFT_ASSGN

If you have any suggestions, I'd love to hear them.

Thanks in advance

Dieter Waelkens

Ps:

I've found notes

http://service.sap.com/sap/support/notes/1567187

http://service.sap.com/sap/support/notes/162991

I'll analyze them and come back with an update

Message was edited by: Dieter Waelkens (added notes in the end)

[ACE-SAP · Accepted solution]

Hello Dieter,

Looks like your errors are more related to DDIC problems than program problems, this might be why SGEN could not help.

Report RUTMSJOB could help, at least to identify if there are inconsistencies, that could be fixed by re-activating the tables.

Check note  1538932 - RUTMSJOB error with check DDTYPES

You could also use report RSNTABCONSISTENCY  from note 1167784 - Runtime error DDIC_TYPE_INCONSISTENCY

Regards

Options for RUTMSJOB in expert mode.

[waelkensd · Accepted solution]

Hi Yves,

that's exactly what I was looking for. I'll check

Thanks

D.

[waelkensd · Accepted solution]

Yves,

it seems like this is the path I need to follow. I'll see if it'll guide me towards enlightenment 😉

I'll let you know when there are any results

Regards,

Dieter

[Reagan]

Hello Dieter

Could you provide the ABAP dumps please ?

Are the dumps mentioning any of the above mentioned tables by you?

Regards

RB

[waelkensd]

Hi Benjamin,

I uploaded them:

http://we.tl/JFxGcCXQdL

http://we.tl/DEmrUs5HVp

http://we.tl/TiM1hAYhyl

I don't see any of those tables mentioned in the notes.

Regards,

Dieter

[Reagan]

Hello Dieter

I would try a restart of the SAP system to see if that helps.

Regards

RB

[waelkensd]

It didn't help.

thanks anyway.

Regards,

Dieter

[former_member188883]

Hi Dieter,

Workaround solution:

Stop sap application

Perform DB statistics update.

Start sap application

Check the results.

Regards,

Deepak Kori

[waelkensd]

Little update.

Restart didn't help.

Regards,

Dieter