07-21-2015 1:05 PM
Hi,
I work on a 4.7 System. A Type group was created few months ago. I add a constant in this type group this week, and I transport order in production today.
In the workbench order there is only this object:
Type Group | R3TR | TYPE | ZBC01 |
After the transport in production system, 8 DUMP appears: LOAD_PROGRAM_LOST:
Program "SAPLV61A" was modified during the run, etc ...
I understand the DUMP but I want to know if there is a solution to avoid DUMP after transport of type group ? Is it better to avoid use them ?
Thanks a lot for your answers,
Best regards,
Nicolas
07-21-2015 1:46 PM
Nicolas,
I guess anything being changed at the global level, you need to exercise a bit of caution. In this case you need to make there are no programs that are currently executing the object you are transporting and this is a normal procedure.
For example you are transporting some changes to an interface you need to make sure that the interface is not running until the transport is moved completely.
Also it is always a better practice not to declare/work with global data unless absolutely required.
V.
07-21-2015 1:46 PM
Nicolas,
I guess anything being changed at the global level, you need to exercise a bit of caution. In this case you need to make there are no programs that are currently executing the object you are transporting and this is a normal procedure.
For example you are transporting some changes to an interface you need to make sure that the interface is not running until the transport is moved completely.
Also it is always a better practice not to declare/work with global data unless absolutely required.
V.
07-21-2015 1:48 PM
Nicolas,
Before making a change golden rule is you need to check :-
If the Dev version is in synch with Prod version or not.
Then you have to check the where used list of this type group.
Only then you have to proceed with the changes.Now check on those lines and if possible attach the screenshot of the dump.
K.Kiran.
07-21-2015 2:14 PM
Hi Kiran,
The Type-group is included in more than 300 programs. I think we have to stop to update this type-group ...
What did you mean by: check dev version is in synch with prod version ?
ST22:
Best regards,
Nicolas
07-21-2015 2:03 PM
Hi,
Please search at least OSS and SCN before posting - there is plenty of information about this out there... The easiest way to avoid LOAD_PROGRAM_LOST is to deliver to production only when the system is out of productive use (when users are logged off). The dump is not related to type groups in particular but rather the fact that program was changed during runtime. Note 5451 - LOAD_PROGRAM_LOST has quite good summary.
cheers
Jānis
07-21-2015 2:21 PM
Hi Jānis,
Unfortunately users are not on the same timezone, so there is no time were all users are logged off. And the production is very rarely stopped.
I have already read notes on that subject. I just try to find a solution to avoid these dump.
I think we must not used global includes for constants ...
Thank you for your answer.
Nicolas
07-21-2015 2:29 PM
Ok, thanks, that explains and that's a tough one. If the deliveries can not planned for "maintenance windows", then one can only give the poor users system message: "save your work and take a XX min break, guys"
Maybe it's feasible to split up the type group if it changes often...?
cheers
Jānis
07-21-2015 2:38 PM
07-21-2015 2:28 PM
Hello Nicolas,
Jānis Bis correct, I have come across this error many times "Program "XYZ" was modified during the run error " when I try to change any program and that program was already there in debugging mode.
Are you still getting the errors in production system?
Regards,
TP