I did exactly what you outlined here. Things seem to be going ok.
-----Original Message----- From: Betsy Strebe [mailto:bstrebeZs...] Sent: Tuesday, January 30, 2001 1:13 PM To: aacsuggZn... Cc: sap400Zm... Subject: Re: Fwd: RE: Post Homogeneous System Copy Steps
Looks like PRD and TST are pointing to and starting with DEV's startup profiles in /usr/sap/DEV/SYS/profile/. What you need to do is get profiles activated for TST and PRD in /usr/sap/TST/SYS/profile/ and /usr/sap/PRD/SYS/profile/ respectivley. Since TST and PRD are new systems, there may not be a version of the profiles for TST and PRD at the OS level. First, look in the directory /usr/sap/TST/SYS/profile for the existence of DEFAULT.PFL, START_DVEBMGS02_ac4sap02 and TST_DVEBMGS02_ac4sap02.
If the bove profiles exist, then you can import them into TST with transaction RZ10 path profiles -> import. Point to the correct directories and files for the import. Review each one (Administrative data, Basic maintenance, and Extended mainternace) for correctness. If you see DEV listed anywhere, then the profiles have wrong information -- proceed below as if the profiles do not exist. If the profiles look okay, save and activate each one.
If the profiles do not exist in /usr/sap/TST/SYS/profile, you need to copy and edit each existing DEV profile to get the naming conventions and values correct for TST instead of DEV. Then save, and activate each one. For each profile there are three types of data (Administrative data, Basic maintenance, and Extended mainternace) which need to be changed. Change all occurences of DEV to TST, DEV's instance number to TST's instance number (02), and DEV's server name to TST's server name (ac4sap02). Then save and activate each profile to write the correct version back to the OS where they are actually used for startup.
If this all works out okay in TST, then follow the same procedure for PRD keeping in mind the naming conventions for the three profiles.
Default profile: DEFAULT (DEFAULT.PFL at OS level) Instance profile: <sid>_DVEBMGS<instance#>_<servername> Start profile: START_DVEBMGS<instance#>_<servername>
Hope this helps, is a lot to swallow. I've had to do this a few times and if I can help at all, let me know.
Subject: Fwd: RE: Post Homogeneous System Copy Steps
--- In SAP on System iZy..., aacsuggZn... wrote: I have just finished creating our TST and PRD systems from a system copy per note:36862. I have a *few* questions:
1. All 3 systems will start without a problem but if I look at my joblog from the OS, it says for each instance that I start "Unable to open file /usr/sap/trans/config/TST/ac4sap02_02.CFG". Parameter DIR_EXECUTABLE does not exist in exist /usr/sap/TST/SYS/profile/START_DVEBMGS02_ac4sap02." It seems to do this for all 3 systems. Can I create these directories? How?
2. Some objects in the directories are owned by TST02 or TSTOWNER not QSECOFR like the others. Will this cause a problem?
3. When I work with Profiles from R/3 (RZ10), the profiles for TST and PRD now have the DEV START profiles. How can I get the profiles back for the TST and PRD systems?
I'm sure thar there are more things that I need to check for that I am unaware of and that I can not find in OSS. I have ran the SBD4GEN and RSDB4GEN pgms. and configured TMS also. Can anyone offer some guidance?