RESB & T604 table data loss after upgrade to ECC 6.0

[Former Member]

Hi all,

We have performed an upgrade from our R/3 4.6C (MDMP) system to ECC 6.0 (unicode) using CUUC approach.

Now during our unit testing we found that the table RESB has only 4 million records, but it was around 19 million records earlier.

we have also lost data from the table T604.

Current no of entries in table T604 - 9019.

The value before the upgrade is approx - 279,326

we have lost around 270307 records.

We have stored all the upgrade and unicode conversion logs. We scanned thru the logs but could not find any errors.

Can anyone help on this regards

Database - 10.2.0.2

OS - HPUX 11.31

Upgrade - SR3 software

Thanks & Regards

Senthil

[Former Member]

Thank you the issue is due to the table activation by one of our ABAPers

[Former Member]

Senthil,

check your export log to see how many rows actually got exported. If the export logs is clear and shows up 4 million records then its a problem and some where in the pre-unicode conversion steps went wrong.

If you see 19 miillion records in export log check your import logs.Ideally this problem occurs if you do not do proper pre-unicode conversion steps.

regards,

Vamshi.

[Former Member]

Hi Vamshi,

Thank you for replying. Export logs doesn't show how many rows got exported. Only the import logs shows how many rows got import.

I strongly feel that it has got lost during the upgrade.

Can you help

Senthil

[Former Member]

Senthil,

If you have your source system Non-Unicode available you can bring up DB and check your records. Otherwise its not possible to verify where you lost these records.

If you are sure you lost recrods in UPG its impossible to get records back.

Have you adjusted this table structure during SPDD in upgrade.

regards,

Vamshi.

[Former Member]

ya! we are restoring the database just before the upgrade to a different server now.

In SPDD phase we had to adjust only the index part of this table (adopt the change of one field added to that table), not the table, also there was no errors during the upgrade for this table.

We have written to SAP also with the log files, awaiting for their reply

Thanks Vamshi

Senthil

[Former Member]

Senthil,

One more thing.I dont think indexes adjustment will impact table data.You dont have to adjust Indexes during SPDD if indexes are std. you will not loose any data.However It can be created after upgrade also.

regards,

Vamshi.

[Former Member]

ya! in our case, we had added an extra field to the index RESB~M, so in the SPDD we adopted the 4.6C version.

After adopting the older version in SPDD, we activated the index and it was active.

But when we tried to activate the table RESB, we could not activate, as we got some Runtime object inconsistency, But the table RESB was in active state, so we proceed with the upgrade and we never faced any problems in the upgrade.

Now we found that there are 75% of data is missing in the table RESB

Regards

Senthil

[Former Member]

Senthil,

Were you able to recover DB and check the records.

My experience says you dont have to activate tables or Indexes during SPDD. SAP upgrade process will takecare.once all SAP objects are copied like tables,indexes,structues,etc... to shadow database it will takecare of activation we dont have to adjust manually.When adjustements are done it takes the snap shot of the changes and activates later in the upgrade phases.

Regards,

Vamshi.

[Former Member]

ya! Vamshi, we restored the backup and found that T604 table entries was the same before and after upgrade, so that eliminates this table.

But RESB table has 22 million records before upgrade vs 4 million after upgrade, we are co-ordinating with SAP to find the issue

Regards

Senthil