Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with DEV Refresh

Former Member
0 Kudos

Hi,

We are doing a system upgrade from SAP R/3 4.7 to ECC 6.0 and we are starting it by upgrading our DEV & then analyzing the impact on it, so we want to refresh DEV with the latest PRD data. My question is that since the DBSID of our DEV and PRD will be different, how will it be possible to refresh it? Will we need to change some thing in the control file after the restore? If so, how do we do it?

Thanks,

Manjula.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

Hi,

You can refresh DEV from PRD by way of a homogeneous (or heterogeneous) system copy, but you might not want to. There are several very good threads on this topic, since the question comes up every few months. The major pitfalls surround development or customizing in progress that has never made it to PRD, and the fact that you will lose your DEV version management history. The "minor" pitfalls involve the fact that DEV system are typically not sized for PRD data volume, and you may end up with sensitive data on your DEV system - where authorizations are necessarily more relaxed than PRD. If you have HR data in PRD, consider it a no-no without using a data refresh tool that scrambles sensitive data in the process.

I don't keep track of all of the niceties of the subject, since I personally would never want to refresh DEV; if you search the forum archives, you should find quite a lot of good information. All of the technical details you need are Monitoring Users Zin there, somewhere.

Reward points if found helpfull..

Cheers,

Chandra Sekhar.

2 REPLIES 2

Former Member
0 Kudos

If you do that, you will lose all your change history for your programs.

Rob

Former Member
0 Kudos

Hi,

You can refresh DEV from PRD by way of a homogeneous (or heterogeneous) system copy, but you might not want to. There are several very good threads on this topic, since the question comes up every few months. The major pitfalls surround development or customizing in progress that has never made it to PRD, and the fact that you will lose your DEV version management history. The "minor" pitfalls involve the fact that DEV system are typically not sized for PRD data volume, and you may end up with sensitive data on your DEV system - where authorizations are necessarily more relaxed than PRD. If you have HR data in PRD, consider it a no-no without using a data refresh tool that scrambles sensitive data in the process.

I don't keep track of all of the niceties of the subject, since I personally would never want to refresh DEV; if you search the forum archives, you should find quite a lot of good information. All of the technical details you need are Monitoring Users Zin there, somewhere.

Reward points if found helpfull..

Cheers,

Chandra Sekhar.