system copy 1.docx

7/30/2019 system copy 1.docx

1/2

1. Stop SAP system, saposcol and listener.

2. Take a complete file system backup or you need to take a off-line backup.

3. Create a CONTROL FILE.

a) Logon as orap01.

b) Find the program R3COPY under CDs

Master/UNIX/COMMON/INSTALL

c) Copied R3COPY program under /sapmnt/P01/exe through ftp.d) Execute R3COPY. Respond to queries and execute the step (a) Source system: Generating the script CONTROL.SQL .

Give Target SID :

e) Find the script CONTROL.SQL in /oracle//sapreorg directory. Following files will be created by R3COPY :

CONTROL.SQL

DATAFILES.TMP

LOGFILES.TMP

R3COPY.log

R3COPY.tmp

initP01.ora

f) The CONTROL.SQL file has to be transferred to (target system) under /oracle/P01/sapreorg through ftp.

After the above mentioned steps you need to perform the undermentioned activites in the the TARGET SYSTEM:

1. Change group id of OS created Groups from 100 series to 200 series (i.e. smbnull to 201 etc). This is done to keep the GID of

100 series free for oper, dba and sapsys.

2. Change UID of users with 100 series to UIDs of 200 series. This is done to keep the 100 series UIDs free for adm and

ora.Ensure that all hardware requirements are met.

3. Create directory trans at /usr/sap/trans

4. Ensure that LANG-MIN is installed

5. Ensure that JDK is installed

6. Ensure that NFS is running

7. Check rpcbind:

8. Ensure that National Language support is installed.

9. Ensure that C++ runtime is installed

10. Check LDAP support

11. Check Fonts

12. Modified the following kernel parameters as per requirement

13. Check the SWAP Space14. Check memlimits

15. Login as root. Ensure that /etc/profile contains umask 022. If not enter the same in /etc/profile and log out and login again.

16. Run SAPinst in the target system

17. Install Database and the patches

18. Take a complete backup of the new target system

19. Restore the following file system from off-line or file system backup on a temporary space into the target system: (This step may

not be required if you can directly restore files from tape to the target directories)

/oracle/P01/origlogA

/oracle/P01/origlogB

/oracle/P01/mirrlogA

/oracle/P01/mirrlogB

/oracle/P01/sapdata1




/oracle/P01/sapreorg

20. Stop SAP System in the Target System

21. Data and Log directories of the Target system must be cleaned up before restoring source database.

7/30/2019 system copy 1.docx

2/2

/oracle/P01/sapdata1/




/oracle/P01/origlogA/

/oracle/P01/origlogB/

/oracle/P01/mirrlogA/

/oracle/P01/mirrlogB//oracle/P01/sapreorg/

/oracle/P01/saparch/

/oracle/P01/saptrace/usertrace/

/oracle/P01/saptrace/background/

/oracle/P01/sapbackup

/oracle/P01/sapcheck

Copy files from the backup of the source system into respective directories as above

22. Copy the script CONTROL.SQL (created in source system) in /oracle//sapreorg directory.

23. Edit the control file to give full path to log files. Also check whether all data files under all corresponding directories are included

under CONTROL.SQL file.

24. Create control file of the target system.

25. After the Control files are recreated in the target system, do the following:

SQL> shutdown

SQL> exit

Orat01> sqlplus / as sysdba

SQL> alter database open resetlogs;

If this command is not successful, you may have to recover the database using following commands:

SQL> recover database using backup controlfile until cancel;

26. Check the database by starting up.

The database is now in NOARCHIVELOG mode. Change the mode to ARCHIVELOG.

27. In some cases you may have to Change global name to new-db

28. Start up SAP

29. Apply atservice.sap.com/licensekeyspermanent license for

Steps :

tcode slicense and note down the active hardware key

login toservice.sap.com/licensekeys

my sap business suite

request license key

select an installation

select new system (or an old system to indicate a change to an existing system)

add the required information

click send request to submit the data to SAP.

You will get the license with in one hour to 3 hours.

Install the new license with tcode slicense.

30. Modify transport management system TMS (that came from Source System).

31. Test for OSS Connectivity and take complete file system backup.
http://service.sap.com/licensekeyshttp://service.sap.com/licensekeyshttp://service.sap.com/licensekeyshttp://service.sap.com/licensekeyshttp://service.sap.com/licensekeyshttp://service.sap.com/licensekeyshttp://service.sap.com/licensekeyshttp://service.sap.com/licensekeys

system copy 1.docx

Documents