on 02-27-2008 10:18 AM
Hello group
We encountered a strange situation this morning.
At 07:00 in the morning we usually schedule our transport. This morning there was a transport of an ABAP query where a new SELECT statement to table MARA was added. (SELECT SINGLE).
Nothing out of the ordinary, but at 07:16 the first user running the changed query got the above problem.
After that, all processes accessing MARA were hanging with a LCKW on the SQL Package MARA in R3PESX0000.
We finally solved the problem by stopping the system and deleting the SQL Packages,.... but I hope we don't have to delete SQL packages every time we transport a change in a query on table MARA.
Any of you have experienced this before ?
Hi Jo,
My quick and dirty solution is to re-activate the table in question using SE14 or SE11.
This invalidates the corresponding SQL packages for only this affected table without having to restart the whole instance.
If this is not enough, then in se14
'Activate and adjust database' with 'save data' set.
if even this don't help you, make a copy of this table at OS level, delete this table from within SAP, recreate an empty one and refill it with the saved data.
But this last remedy needs strong nerves and a sound understanding of what you are doing.
Good luck,
Paul Hoogendoorn
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Did this problem recur? We have seen this twice now on MARC - but we are running ECC5 on V5R3.
We are raising with SAP now that it has occurred again.
Or did you find a solution?
Thanks, Andy.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Ernesto,
that the problem disappears is clear - similar to DLTR3PKG - that would have helped as well ...
The only question is: Is this a permanent solution ? Most likely not ....
Good luck,
Volker Gueldenpfennig, consolut international ag
http://www.consolut.net - http://www.4soi.de - http://www.easymarketplace.de
Hi Joe,
you should open an oss ticket on this with componente BC-DB-DB4. Then they should collect, what still can be collected. At least they can tell you, what collect the next time. This is definetely NOT the way it should work !
Regards
Volker Gueldenpfennig, consolut international ag
http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.