on 07-31-2014 1:06 PM
Hi,
On Monday, we have started implementing one OSS note in our dev system, which resulted in more than a hundred notes with manual correction steps. We are on ECC6 EHP5. Since Monday we have tried to revert the note back unsuccessfully and we have implemented about 30 notes so far.
Since Monday, about a dozen notes were moved from dev to prod.
Our basis team proposed to restore from online backup from Sunday but we are afraid of possible inconsistencies since some transports already made it to PRD system.
Please help with suggestions,
thanks,
Hi Maxence,
You have to be aware that if you restore from Sunday backup, you will loose the changes mades in DEV system since Sunday.
After the restore, you must apply to DEV the OSS notes transported to production system in order to have the same OSS notes applied to all of the systems.
Hope this helps.
Best regards,
Martina
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Martina,
Yes we are aware we will loose our changes. We are thinking to use the option overwrite originals when we transport notes to PROD again. We are also thinking about modifying the number ranges for the transport number to avoid conflicts.
We are afraid to create inconsistencies if we loose the trail of some transports that are in PROD but without any reference in the DEV system.
I would like to read more about potential inconsistencies issues if any,
You should be able to reimport the transports with those dozen notes that you already released into DEV after you do the restore. The transports exist as files in your \usr\sap\trans directory, and there are entries for them in your tp buffer. After the restore, go into STMS in DEV and use Extras... Other Requests... Add to add them back into the queue for DEV, with the Import Again option checked (and on the import itself, with Import again and overwrite originals, etc, set as well). That should at least allow you to get DEV back into sync, note-wise, with your QAS and PRD systems without having to completely reimplement the notes.
I'm not sure if that would update the number range for your transports, however, so you still might need to do that to ensure you don't reuse an existing transport number.
The next time you do a support pack import will probably overwrite all those notes and hopefully "clean up" the situation, as well.
Thanks all for the input, we will proceed with the system restore over the weekend
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Martina has already made you aware what needs to be done in your case.
If all the notes are implemented on the D system and added into a single transport request then importing the same transport request will cause you the same problem but if they are not then Matt's solutions is the one to be taken into consideration.
Regards
RB
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.