cancel
Showing results for 
Search instead for 
Did you mean: 

Database inconsistence in SE14

Former Member
0 Kudos

Hi

I hope one of you i5 exports can provide some advise.

We changed a table in development where we changed the length of a field. On development it went fine.

On the QA system the transport as such did not produce any errors but after the import the table was inconsistent (both the database object and the runtime object).

From se14 we tried to to a "activate and adjust database" but just got an error at the end saying it was not possible du to "a pending operation". After a while we tried at again and it finished without any errors but we still have a inconsistent database object (the field is not extended in the db).

What do you recommend to do in this case? Is a "force conversion" what has to be done?

Best regards

Flemming Grand

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Volker and thank you for you reply.

Yes I didn't write that but I'm 99% sure that you are right. There was a lot of activity at the system at the time and I guess that made it impossible to lock the table when doing the ALTER TABLE.

Regards

Flemming

Former Member
0 Kudos

Hi Flemming,

to me it sounds, that the needed ALTER TABLE crashed - most likely because of locks on the table and the nametab is updated now.

For that, SAP created something special called "Recreate Nametab" in SE14 for DDIC only. But, I do not know, if unexperienced people should use this tool ? At least you need to activate in SE11 after that - and you should get rid of the lock on the table first in order to not run into the same issue ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de