Homogeneous System Copy Steps Needed.

[Former Member]

Hi! Gurus,

Can you please help me by providing details (step by step)

procedure for Homogeneous System Copy for R/3 4.7 (Kernel 620 NU) on Windows /Oracle.

I have to migrate my system from existing Server to a new Server.

Thanks and regards,

Pratip

[Former Member · Accepted solution]

Here is an extensive document on System copy. You will find all the info you need.

Reasons for Copying a SAP System

SAP recommends that you make a system copy in order to build a test, demo, training or standby

system (Oracle and Informix: standby systems cannot be created with a system copy). You should

perform upgrades in a test system first. This way you can identify customer pecific problems which

might result from modifications. Thus, we can sort the general needs for a system copy as follow:

To create a new training system for end-user or project team education

To create a DEMO system

To create a Test system for upgrade or other purposes.

To recover a system on another machine with the same platform after a crash.

To copy large clients. If a client very large to export/import, it is better to do a system copy rather

than client transport.

If a system copy takes place between systems with same platform ( operating system and database

system ) , we call this HOMOGENEOUS SYSTEM COPY.

If The system copy takes place between systems with different platforms ( at least one of the

component must be different, OS or RDBMS ), we call this HETEROGENEOUS SYSTEM COPY.

There 3 ways of a Homogeneous System Copy in R/3 Systems.

1. Homogeneous System Copy using Online / Offline Database Backup.

2. Homogeneous System Copy using R3LOAD Procedure.

3. Homogeneous System Copy using R3COPY Procedure.

This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.

The procedure described tested on AIX 4.3.3/Oracle 8.1.7, AIX 5.1/Oracle 8.1.7, AIX 5.1/Oracle 9.2.0

and Win2K/Oracle 8.1.7 platforms.

The command reference given in this guide is taken from a homogeneous system copy done on AIX

4.3.3/Oracle 8.1.7 platform. Differences of other platforms such as Windows will be shown in the same

sections.

Homogeneous System Copy using Online/Offline Database

Backup

This guide is prepared for a Homogeneous System Copy using Online/Offline Database Backup.

Steps for a Homogeneous system copy are briefly as below:

Preparations on Target System.

Restore Online/Offline Backup of Source System onto Target System.

Create CONTROLFILE creation script on Source System.

Modification of CONTROLFILE script and creation of CONTROLFILEs of Target System.

Recovery of Oracle Database on Target System.

Completion of System Copy

Prerequisites

Following conditions must be provided to copy a system:

Both Source and Target Systems must have Same Operating System and Database System. Also

Patch levels must be same.

You have sufficient free space for sapdata directories on target system.

For Windows systems, you have to create all drives where datafiles resides on source system.

Use most current database backup in order to shorten database creation time.

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 3 of 9

Procedure

1. Data and Log directories on target system must be cleaned before restoring source database.

Here below are the commands to clean directories. Before this, you have to stop all SAP and

Oracle processes.

1. su - <targetsid>adm

2. stopsap all

3. exit

4. su – ora<targetsid>

5. lsnrctl stop

6. exit

7. cd /oracle/<SID>/

8. rm –rf sapdata?/*

9. rm –rf origlog?/*

10. rm –rf mirrlog?

11. rm –rf sapreorg/*

12. rm –rf saparch/*

13. rm –rf saptrace/usertrace/*

14. rm –rf saptrace/background/*

15. rm –rf sapbackup/*

16. rm –rf sapcheck/*

On Windows systems, SAP and Oracle services can be stopped via the following commandline

program after logging as <sid>adm:

ntscmgr stop SAP<SID>_<SYSNO>

ntscmgr stop SAPOSCOL

ntscmgr stop OracleService<SID>

2. You have to resize the following file systems before restore process. Take into account sizes of

source system.

/oracle/<SID>/sapdata1

/oracle/<SID>/sapdata2

/oracle/<SID>/sapdata3

/oracle/<SID>/sapdata4

/oracle/<SID>/sapdata5

/oracle/<SID>/sapdata6

/oracle/<SID>/saparch

3. After cleaning necessary file systems/directories, you have to restore most current database

backup to target system. For this, find the detail backup log (e.g. bdkxxsrh.anf) for that backup on

source system. You can determine this from back<SID>.log summary backup log file or using

DB12.

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 4 of 9

DB12 - Backup Logs

back<SID>.log File

Copy this detailed backup log file into /oracle/<TSID>/sapbackup directory on target system. Use

BRRESTORE command below to restore the source database on target system. You can also

restore datafiles and online redolog files (if you are using offline backup) using backup tools such

as BACKFM tool of IBM TSM.

On Windows systems, while restoring source database on target system, you have to keep

same mount points for Oracle Data Directories.

For example if all of your source data directories resides on "d:>" disk

(d:\oracle\<SSID>\sapdatax), then you have to create data dirs. at target system on "d:>" disk.

After restore process, you can change the directories. For example you can distribute sapdatax

directories on many disks. This will be mentioned in CONTROLFILE creation step later.

3.a. Mount the necessary backup volume on target system.

3.b. Use the following command to begin restore:

1. su - ora<tsid>

2. cd sapbackup

3. brrestore -m full -b <det_log_file> -c (det_log_file= for example bdkxxsrh.anf)

At the first step of restore, system will recognize that the Oracle SID is different on target

machine (where the restore command executed) and in backup. Also, Oracle_Home

parameters in backup and in current system will be different and recognized by brrestore. But

the restore command will restore the datafiles to match current systems file system. Here is a

sample log of a restore.

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 5 of 9

All the datafiles and online redolog files (only for Offline DB Backup) must be successfully

restored.

At this step, there are 3 probability that must be take into account for the following steps.

You are using an online database backup of source system to create target system.

You have to find and put all archive files created during online backup into target systems

archive directory to be able to recover database. You can also apply all the archives created

from the online backup start time to latest available.

You are using an offline database backup of source system which is running in

ARCHIVELOG mode to create target system.

You may find the archive files created after offline backup on source system to make database

current on target system via applying during recovery.

You are using an offline database backup of source system which is running in

NOARCHIVELOG mode to create target system.

You don't have any archive files created on source system so you don't need anything.

Those differences will be detailed in recovery step.

4. After restoring datafiles and redolog files, a scripts must be prepared on source system to create

CONTROLFILE of target system. For this you have 2 option.

4.a. You can use R3COPY program which is under "/kernel/UNIX/COMMON" directory of Kernel

CD. This program can be used only on UNIX systems. For Windows systems, "4.b" option

must be used.

Run this program by ora<sid> user on source system. After some confirmations, execute

step "(a) Source system: Generating the script CONTROL.SQL".

This will create a script named CONTROL.SQL under /oracle/<SSID>/sapreorg directory.

Copy this script into target system (any directory). This file is ready for execution and doesn't

require any modification.

4.b. SVRMGRL or SQLPLUS can create a scrpit to create controlfile using current

CONTROLFILE content. Login to source system as ora<sid> user and execute the following

SVRMGRL/SQLPLUS commands. To be able to execute following commands, database

must be at least in MOUNT mode..

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 6 of 9

1. svrmgrl

SVRMGR> connect internal

SVRMGR> alter database backup controlfile to trace;

SVRMGR> exit

As a result of this command, a trace file (e.g. ora_54764_hvd.trc ) will be created under

/oracle/<SSID>/saptace/usertrace directory. File can be determined by sorting according to

modification/creation dates (UNIX: # ls –ltr). Most current file must be cheched.

You have to edit this file to be able to use for CONTROLFILE creation on target system.

Rename file name as CONTROL.SQL

Open file to edit using VI (UNIX) or NOTEPAD (WIN).

Remove all lines before "STARTUP MOUNT" line. Delete all commented "#" lines. Also

remove all lines after CHARACTER SET WE8DEC;" line.

Change all Source SID's to Target SID via following commands.

UNIX (VI): :%s/<SSID>/<TSID>/g

WIN (NOTEPAD): CTRL+H

Change the line

CREATE CONTROLFILE REUSE DATABASE ‘SSID’ NORESETLOGS ARCHIVELOG;

as follow

CREATE CONTROLFILE REUSE SET DATABASE ‘TSID’ RESETLOGS ARCHIVELOG;

If you want to change datafile or redolog file destinations, first move the files on target

destination at OS level, then edit CONTROL.SQL file for new destinations.

If structural changes made in database on source system just after the backup restored on

target machine, differences will exists between datafiles in sapdata directories and datafiles

referenced in CONTROL.SQL file. Because CONTROL.SQL file is created for the current

status of source system, but later added files doen't exists in backup so in target system. To

overcome this problem, just delete the datafiles from CONTROL.SQL file.

If you don't know which files are created after the backup, let the problems arise during

CONTROLFILE creation command, and delete the files mentioned as error from

CONTROL.SQL and re-run creation command.

After deletion and successful creation of CONTROLFILE's on target system, you have to take

into account the following subjects:

If you are not going to recover database to the most current status using archive files, then

there is no problem.

But if you are planning to recover database to the most current status using archive files,

then deleted datafiles will be problem later while application of archive files. At this

moment, we offer you to keep datafile names you deleted during CONTROLFILE creation

and add those datafiles with the same sizes on source system after CONTROLFILE

creation.

5. After CONTROL.SQL script preparation, following commands must be run to create

CONTROLFILE of target system:

1. su – ora<targetsid>

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 7 of 9

1. svrmgrl

SVRMGR> connect internal

SVRMGR> @/<path_to_file>/control.sql

You have to guarantee the successful completion of this command as follow:

SVRMGR> @control.sql

Statement processed.

SVRMGR>

6. Database will be in inconsistent status after creation of CONTROLFILE. This can be viewed by

trying to open the database.

SVRMGR> alter database open;

alter database open

*

ORA-01589: must use RESETLOGS or NORESETLOGS option for database open

SVRMGR> alter database open resetlogs;

alter database open resetlogs

*

ORA-01195: online backup of file 1 needs more recovery to be consistent

ORA-01110: data file 1: '/oracle/<hedefSID>/sapdata1/system_1/system.data1'

At this step, a recovery must be made in order to be able to use the database.

7. 3 type of recovery can be made, according to your status mentioned at the end of STEP-3. all the

recovery types must be used by "USING BACKUP CONTROLFILE" as CONTROLFILE is created

manually.

7.a. If your source system is runnig in NOARCHIVELOG mode, then you have to use the

following command to recover database.

SVRMGR> recover database using backup controlfile until cancel;

7.b. If you restored an online backup on target system and put all the archive files created since

online backup start time, use the following commands.

SVRMGR> recover database using backup controlfile;

After execution of this command, Oracle will ask for archive files to be consistent. As archive

files contains only database changes commands, you will use source system archive file on

new systems database recovery. Copy all archive files created since online backup on source

system to archive directory of target system. Archive file names are different from asked

during recovery session. You can change archive file names for target system via the

following script.

cd /oracle/<TSID>/saparch

for i in `ls|grep <SSID>`;

do

file_name=`echo $i |cut -dD -f2`;

mv $i <TSID>$;

done

Alternatively you can enter file names manually as required by recovery session as follow:

SVRMGR> recover database using backup controlfile;

ORA-00279: change 44138924 generated at 03/26/2003 00:00:24 needed for thread 1

ORA-00289: suggestion : /oracle/HVS/saparch/HVSarch1_22746.dbf

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 8 of 9

ORA-00280: change 44138924 for thread 1 is in sequence #22746

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

/oracle/HVS/saparch/HVDarch1_22746.dbf

Log applied.

After application of all necessary archives (at least all the archives created during online

backup must be applied. Archives from this point can be applied to make database current),

next request for archive is cancelled via CANCEL command.

ORA-00279: change 44164157 generated at 03/26/2003 01:58:29 needed for thread 1

ORA-00289: suggestion : /oracle/HVS/saparch/HVSarch1_22754.dbf

ORA-00280: change 44164157 for thread 1 is in sequence #22754

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

CANCEL

Media recovery cancelled.

SVRMGR>

But recovery session must be started with the following command and cancelled again to ba

able to start database.

SVRMGR> recover database using backup controlfile until cancel;

ORA-00279: change 44164157 generated at 03/26/2003 01:58:29 needed for thread 1

ORA-00289: suggestion : /oracle/HVS/saparch/HVSarch1_22754.dbf

ORA-00280: change 44164157 for thread 1 is in sequence #22754

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}

CANCEL

Media recovery cancelled.

SVRMGR>

Otherwise following error will arise during database opening.

SVRMGR> alter database open resetlogs;

alter database open resetlogs

*

ORA-01113: file 1 needs media recovery

ORA-01110: data file 1: '/oracle/HVS/sapdata1/system_1/system.data1'

To open database, use the following command:

SVRMGR> alter database open resetlogs;

Statement processed.

SVRMGR>

7.c. If you restored an offline backup on target system, you can recover database to the time of

backup completed or you can recover database to the most current status using archive files.

The archive application and statup of database is same as an online backed up database

copy in "7.b".

8. after opening database, LISTENER process must be started.

1. su – ora<targetsid>

2. lsnrctl start

On Windows systems, Oracle Listener is started as below:

ntscmgr start OracleOraHome817TNSListener

9. To open SAP system, use the following commands.

Type Handbook Document

Area SAP Basis

Topic Homogeneous System Copy using Online/Offline Database Backup

Author Huseyin Bilgen

All Rights Reserved.

Copyright 2001-2003.basisconsultant.com Page 9 of 9

1. su - <targetsid>adm

2. startsap

On Windows systems, Oracle Listener is started as below:

ntscmgr start SAP<SID>_<SYSNO>

ntscmgr start SAPOSCOL

ntscmgr start OracleService<SID>

startsap name=<TSID> nr=<SYSNO> SAPDIAHOST=<target systems hostname>

10. As your Hardware Key is not changed, you don't have to get additional License Key from

SAPNET. You can use previous systems (on target system, if SID is not changed) License in new

system created on target system.

11. Logon to the SAP R/3 System and goto TCODE SE06. Select "Database Copy or Migration" and

execute "Post Installation Processing".

SE06

Change all of the Source System Objects to Target System Objects as asked.

12. Delete old TMS configuration and make new configuration for TMS via STMS TCODE.

13. After all of above steps, you have completed a System Copy using Online/Offline Database

Backup.

[Former Member]

Can someone send the same steps to me as well ?

My id is <email address removed by moderator>

Thank!

[Former Member]

Here is a good method I use, depending on your landscape, you may have a few more steps with setting permissions for the DB users. There may also be some steps you will not have to perform. READ THE WHOLE DOCUMENT VERY CAREFULLY and make the necessary adjustments to it prior to attempting to use.

PART 1

System Refresh

Preparing the Target System

Save DB13 configuration

1. Log on to the existing target SAP system

2. Run transaction DB13

3. From the Calendar menu, select print

4. Select a printer and press <Shift>+<F1>

Exporting the current users

SCC8

1. In the Selected Profile field, press <F4> and select SAP_USERS.

2. Press the Choose button

3. In the Target System, enter the <SID> of the existing target system.

4. Press the Start Immediately button.

5. Press the Continue button

6. Make note of the transport number for the client-specific data

7. Press <Enter> to continue.

SE01

1. Enter the transport number noted in step 6 above and enter it in the Request/Task box.

2. Press the Logs buttons.

3. If the export is still executing, press <F5> to refresh.

4. Repeat press <F5> on occasion to refresh. DO NOT CONTINUE UNTIL THE EXPORT IS COMPLETE

Export the current printer definitions

SPAD

1. Press <SHIFT>+<F8> to go in to change mode

2. Create a transport of the printer definitions by clicking on the Output devices button

3. From the Edit menu, select Transport and then Transport all

4. Press <Enter> when warned about processing target system.

5. When prompted for a new transport, press <F8> to create a new transport.

6. Make note of the transport number.

7. Enter a appropriate description (i.e Printers for import after refresh) and press <Enter> to save.

8. Press <Enter> to accept the newly created transport

SE01

1. Enter the transport number noted in step 6 above and enter it in the Request/Task box.

2. Press the Display button

3. Click on the task underneath the transport and press <F9> to release the task

4. Click on transport press <F9> to release the transport.

Preparing the Source System

Gather Information

DB12

1. Press the Overview of database backups button.

2. Locate the backup that your are going to use for the restore, and note the log name in the last column (i.e bdqjnsfk.anf)

3. Double click on backup entry to view the details.

4. Press the Detail Log button

5. Scroll down to the very bottom and note the date and time that the BRARCHIVE command was started.

6. Press <F3> 3 time to go back to the main DB13 screen

7. Press the Overview of redo log backups button.

8. Locate the backup that was started around the time noted in step and note the name of the log file associated with that backup (i.e. adqjomaf.cds).

9. Double click on backup entry to view the details.

10. Scroll down to the bottom and make note of the first and last Redo Log number included in that backup.

Copy Files

1. Locate the following files and copy them from the appropriate directory on source system to the corresponding directory on the target system.

File Name Typical Location

CATALOG.<SID> C:\BACKINTLOG or H:\ORACLE\<SID>\SABACKUP

BACKUP<SID>.LOG H:\ORACLE\<SID>\SAPBACKUP

<BACKUP>.ANF (noted in step 2 above) H:\ORACLE\<SID>\SAPBACKUP

ARCH<SID>.LOG H:\ORACLE\<SID>\SAPARCH

2. Rename or delete the existing CATALOG.<SID>, BACKUP<SID>.LOG and ARCH<SID>LOG files on the target system

3. Rename the CATALOG.<SID>, BACKUP<SID>.LOG and ARCH<SID>LOG files that were copied from the source system to reflect the System ID of the target system (i.e CATALOG.PFC will become CATALOG.QFC etc.)

Export Oracle Control file information

1. Logon on to the source system as <sid>adm

2. Start a command prompt,

3. Enter the command: sqlplus /nolog

4. Enter the following commands

connect / as sysdba

show parameter user_dump_dest

alter database backup controlfile to trace;

quit

5. Open Windows Explorer and navigate to directory noted the in the results of the show parameter user_dump_dest above

6. Locate the most recently created file and copy it to a directory on the target system.

7. Rename the file on the target system to NEWCNTRL.SQL

8. Start Notepad

9. From the File menu, select Open.

10. Select All Files from the Files of Type box and navigate to the NEWCNTRL.SQL and press the Open button.

11. Remove the entire first section of the file up to, but NOT including the STARTUP NOMOUNT line in the second section entitled Set #2. RESETLOGS case.

12. Replace the word REUSE with SET in the CREATE CONTROLFILE line.

13. From the Edit menu, select Replace…

14. In the Find What: box enter the <SID> of the source system. In the Replace With box, enter the <SID> of the target system. Press the Replace All button.

15. Remove all the lines at the end of the file after the semi-colon, beginning with the

1. Recovery is… line.

16. If the file paths on the source system are the same as on the target system, then no further editing of the file is required. Otherwise you need to adapt the file paths to reflect the directory structure on the target system.

17. From the File menu, select Save.

18. From the File menu, select Exit

Restore and Recover the Oracle Database

Restore the Oracle Database

1. Logon on to the source system as <sid>adm

2. Using the SAP System Manager, stop SAP as normal

3. Run the command SQLPLUS /NOLOG

4. Enter the following command into SQLPLUS

connect / as sysdba

shutdown immediate

quit

5. To restore the database run the following command

brrestore -m full -b <backup>.anf -d util_file -p init<newSID>.sap

<backup>.anf in the ANF file noted above in the Copy Files section

6. From the Start button, select Search, the For Files or Folders.

7. In the Search for files or folders box, enter CNTRL<SID>.DBF. Make sure the the Look in box is set to Local Harddrives. Press the OK button.

8. Once the search is complete, rename all of the existing CNTRL<SID>.DBF files to back them up.

9. To restore the redo logs required to fully recover the database, enter the following command.

brrestore -p init<newSID>.sap -a <1st redo>-<last redo> -d util_file -r init<newSID>.utl -k no -l E

<1st redo> and <last redo> are the numbers of the first and last redo logs associated with the backup that was used to do the restore. This was noted in the Gather Information section above.

10. Enter the command: sqlplus /nolog

11. Enter the following commands

connect / as sysdba

@<drive letter>:\<directory path>\newcntrl.sql (This is file that was edited previously)

shutdown immediate

startup mount

recover database using backup controlfile until cancel;

AUTO

If prompted for a redo log that wasn’t included in the backup, enter the command CANCEL

Alter database open resetlogs;

Shutdown immediate

Startup

Quit

12. At this point the Oracle database should be started with out any errors. If problems do exist, you must resolve them before continuing.

Reset Oracle system users

1. The Oracle user OPS$<hostname or domain>\<SID>ADM and OPS$<hostname or domain>\SAPSERVICE<SID> must exist for every SAP database. These are the Oracle users that connect to Oracle from Windows to run SAP integrated backups, CBO stats, etc. without having to supply an Oracle password.

2. Run the command SQLPLUS /NOLOG

3. Enter the following command into SQLPLUS

Connect / as sysdba

4. Check the users with the following: select USERNAME from DBA_USERS;

5. Use the SQL script attached to note 50088 --- @<drive letter>:\<directory path>\oradbusr.sql

@oradbusr.sql <schemaowner> NT <hostname or domain> <SID> oradbusr.sql is a txt file attached to note 50088

schemaowner is sapr3 for 46d systems it is sap<sid> for 6.x systems

6. Run the command SQLPLUS /NOLOG

Post Restore Procedures

Re-Install SAP License

1. Get the current license information for this system from Service Market Place by going to http://service.sap.com/system-data

2. From a command prompt, run the command saplicense –install

3. Follow the prompts using the information available on the Service Market Place.

Delete Old Licenses

1. From a command prompt, run the command saplicense -show

2. If there are other licenses list other than the one that was just installed, then enter the command saplicense –delete

3. Enter the <SID> associated with the old license.

4. Enter the Hardware Key associated with the old license

5. Enter R3_ORA as the Product ID.

Configure SAP for Zero Batch Processes

1. Create a copy of the instance profile usr\sap\<SID>\sys\profile\<SID>_DVEBMGS<SYSNR>_<HOSTNAME>

2. Open the instance profile \usr\sap\<SID>\sys\profile\<SID>_DVEBMGS<SYSNR>_<HOSTNAME> using SAPPAD or other text editor.

3. Make note of the number of batches processes configured by looking at the value on the rdisp/wp_no_btc line

4. Change the line containing rdisp/wp_no_btc to read

rdisp/wp_no_btc = 0

5. Save the new version of the instance profile

Start SAP

1. Using the SAP System Manager, start SAP as normal

Stop Batch Jobs

1. Log on to the newly refreshed target system

SM37

1. Set the fields as follows

Job name: *

User name: *

Job Status: Released and Ready checked off, all others unchecked

Fr: 01/01/0001

To: 12/31/9999

Or after event: *

2. Press <F8> to execute the query

3. From the list of released jobs, place a checkmark beside any jobs that begin with DBA:

4. From the Job menu, select Delete

5. Press the Yes button to delete the jobs

6. Press <F5> to select all the jobs

7. Remove the check marks from beside the following jobs

Any jobs starting with RDDIMPDP

Any job starting with SAP

AUTO_SESSION_MANAGER

8. From the jobs menu, select Release -> Scheduled

9. Press <F3> to go back

10. Repeat step 1 through 9 until it is confirmed that all jobs except those listed in step 7 are not listed.

Stop SAP

1. Using the SAP System Manager, stop SAP as normal

Restore the Number of Batch Processes.

1. Open the instance profile \usr\sap\<SID>\sys\profile\<SID>_DVEBMGS<SYSNR>_<HOSTNAME> using SAPPAD or other text editor.

2. Change the line containing rdisp/wp_no_btc back to the value it was at before changing it to zero.

3. Save the new version of the instance profile

[Former Member]

PART 2 of 2 Good luck!

Import New Kernel
1.	Close the SAP System Manager (MMC) console
2.	Stop the services SAPOSCOL and SAP<SID>_<SYSNR>
3.	Rename the existing kernel from usrsap<SID>sysexerun to run.old
4.	Copy the kernel from the source system to the newly refreshed system
5.	Ensure to copy LIBRFC32.DLL, SAPCAR.EXE and SAPMMC.MSC to the Windows SYSTEM32 directory
6.	Restart the SAPOSCOL and SAP<SID>_<SYSNR> services
Start SAP
2.	Using the SAP System Manager, start SAP as normal
Initial Consistency Check
SM28
1.	Logon to the newly refreshed SAP system and run transaction SM28
2.	Ensure that no errors are reported.  Otherwise, take the necessary steps to correct the problems.
Edit Batch Jobs
1.	Set the fields as follows
Job name: RDDIMPDP*
User name: *
Job Status: Released and Ready checked off, all others unchecked
Fr:  01/01/0001
To:  12/31/9999
Or after event: *
2.	Press <F8> to execute the query
3.	Highlight the first job in the list and press the <CTRL>+<F11> to change the job.
4.	Examine the Exec Target field.
a.	If the box is empty, press <F3> to exit
b.	If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save
5.	Repeat Steps 3 and 4 for each additonal job listed.
 
Workbench Organizer Reconfiguration
1.	Logon on to client 000 of the newly refreshed system with DDIC.

SE06
1.	Select the Database Copy or migration option 
2.	Press the Post-installation Processing button.
3.	When prompted Do you want to re-install the CTS?, press the Yes button
4.	When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected.  Press the checkmark button to continue.
5.	When prompted Change originals from PRD to QUA?, press the Yes button
6.	When prompted Delete TMS Configuration?, press the Yes button
7.	When prompted Delete old TMS configuration?, press the Yes button
8.	When prompted Delete Old Versions of transport routes?, press the No button
TMS Configuration
1.	Logon on to client 000 of the newly refreshed system.
STMS
1.	Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
2.	The information on this screen is automatically filled out from information provided during the SAP installation and should be correct. 
If it correct, then enter a description for the system and press <CTRL>+S to save.
Otherwise, press the Other configuration button  and manually configure.
3.	From the Overview menu, select Transport Routes
4.	From the Configuration menu, select Adjust with Controller
5.	Press the Yes button when prompted if you want copy the transport routes from the controller.
 
Import Printers

1.	Logon on to the production client of the newly refreshed system.
STMS
2.	Press <F5> to go to the import Overview.
3.	Double click on the <SID> of the newly refresh system
4.	From the Extras menu select Other Requests, then Add.
5.	In the Transp. Request box, enter the transport number containing the printer definitions that was exported.  Press <Enter> to save.
6.	Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import.
7.	In the Target client box, enter the productive client of the newly created system.  Press <Enter> to save.
8.	Press the <Yes> button to start the transport.
Client Configuration
SCC4
1.	From the Table view menu, select Display -> Change
2.	When warned that the table is cross-client, press the checkmark button.
3.	Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4.	Define client as follows:
Client role:  Test
Changes and transports for client-specific object:  Changes without automatic recording
Client-independent object changes:  Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool:  Protection level 0
Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

5.	Press <CTRL>+S to save.
6.	Repeat steps 4 through 6 for any additional clients

Set System Change Option
SE06
1.	Press the System Change Option button.
2.	Set the global setting to Modifiable
3.	From the Edit menu, select Software Components Modifiable
4.	From the Edit menu, select Namespaces Modifiable
5.	Press <CTRL>+S to save.

 
Import Users
STMS
1.	Press <F5> to go to the Import overview
2.	Double click on the <SID> of the newly refreshed system.
3.	Press <F5> to refresh the list of transports
4.	Locate the transport in the list containing the user exports done before the start of the refresh.  
If the transport is NOT in the list, then from the Extras menu, select Other requests then Add.   Enter the transport number and press <Enter>.  Then press the Yes button to add the transport.
5.	Highlight the transport and press the Import request icon .
6.	At the client import screen, enter the target client and then press the Import button
7.	Press <Enter> to confirm that the import will proceed
SCC7
1.	Run the Post Client Import Processing
2.	The transport number should be the same as that of the transport started in STMS
3.	Schedule the job to run in the background.  Do NOT schedule it to run immediately.  We need to modify the job before it can be released.
4.	Press <CTRL>+S to save.
SM37
1.	Set the fields as follows
Job name: CLIENTIMPORT*
User name: *
Job Status: All options checked
Fr:  01/01/0001
To:  12/31/9999
Or after event: *
2.	Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.
3.	Press the Step button.
4.	Select the RSCLXCOP line and press <CTRL>+<SHIFT>+<F7> to modify that step.
5.	In the User box, enter the background user for that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6.	Press <CTRL>+S to save the changes
7.	Press <F3> to go back to the main job screen.
8.	Press the Start condition button.
9.	Press the Immediate button.
10.	Press <CTRL>+S to save the changes
11.	Press <CTRL>+S again to save all the changes to the job.
12.	Job will start immediately once saved.  Press <F8> to refresh the list of jobs
13.	Continue to press <F8> every once in a while to update the status of the job.  Do not continue until the job is completed sucessfully.
 
SCC4
1.	From the Table view menu, select Display -> Change
2.	When warned that the table is cross-client, press the checkmark button.
3.	Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4.	Set the Protection to Protection level 1
5.	Press <CTRL>+S to save.
6.	Repeat steps 3 through 5 for any additional clients
Deleting Source System Profiles
RZ10
1.	From the Utilities menu, select Import Profiles then Of Active Servers 
(Note:  All application servers of the target system must be started)
2.	If the Display Profile Check Log screen is displayed, press <F3> to leave this screen.
3.	Select the Profile field and press <F4> to bring up a list of profiles.
4.	From the list select one of the profiles associated with the source production system.
5.	From the Profile menu, select Delete, then All versions, then of a profile.
6.	When prompted, press the Yes button to delete all version of the profile
7.	When prompted to delete the file at the operating system level, press the No button.
8.	Repeat steps 3 through 7 for all additional profiles associated with the source system
 
Reconfigure Operation Modes
RZ04
1.	From the Operation Mode menu, select Timetable
2.	Select Normal Operation and press the Change button.
3.	Highlight 00:00 in the left hand column and press the Delete Assignment button
4.	If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
5.	Once all the assignments are deleted, press <CTRL>+S to save.
6.	If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
7.	Press <F3> to go back to the main RZ04 screen.
8.	Right click on one of the listed Operation modes and select Delete
9.	Press the Yes button to confirm the deletion.
10.	Repeat steps 8 through 9 for any additional operation modes
11.	Press <F5> to create a new operation mode.
12.	Enter a name and short description for the operation mode
13.	Press <CTRL>+S to save.
14.	Press <F6> to create a new Instance
15.	From the Settings menu, select Based on current settings, then New Instances, then Set
16.	Press <F3> to go back to the main RZ04 screen.
17.	Press the Yes button to save
18.	From the Operation Mode menu, select Timetable
19.	Select Normal Operation and press the Change button.
20.	Highlight the 00:00 at the top and press <F2>
21.	Highlight the 00:00 at the bottom and press <F2>
22.	Press the Assign button.
23.	Press <F4> to select the operation mode created above.
24.	Press <CTRL>+S to save.
 
Delete Update Failures
SM13
1.	 Set the fields as follows
Client:  *
User: *
From data: 01/01/0001
From time: 00:00:00
2.	Press <Enter> to display the list of outstanding update requests
3.	If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.
4.	Press the Continue button to confirm the deletion.
Delete Batch Input Sessions
SM35
1.	From the Edit menu, select Select All
2.	Press <Shift>+<F2> to delete all the batch input sessions.
3.	Press the checkmark button to confirm
4.	Press the Yes button to start the delete.
Reorganize Spool
SPAD
1.	From the Administration menu select Clean-up Spool
2.	Check all check boxes and enter 0 for minimum age
3.	Press the Execute button
4.	Once complete, press <F3> twice to get back to the main SPAD screen
5.	From the Administration menu select Check Consistency
6.	Press the Delete All button.
SP12
1.	From the TemSe database menu, select Consistency check
2.	When the check is complete, press the Delete All button.
Delete Invalid Background Control Objects
SM61
1.	Press <F8> to switch in to change mode
2.	Press the Cleanup List button.
 
Restrict Outgoing Email and Faxes
SCOT
1.	Double click on the green Fax entry
2.	From the Supported Address Types area, press the Set button that is beside Fax
3.	In the Address area, ADJUST AS NECESSARY
4.	Double click on the green SMTP entry
5.	From the Supported Address Types area, press the Set button that is beside Internet
6.	In the Address area, ADJUST AS NECESSARY
Adjust RFC connections.
SM59
1.	Expand the TCP/IP connections section
2.	Double click on the first entry listed
3.	Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.  Make changes as necessary.
4.	Press the Test Connection button to test the connection
5.	Press Press <CTRL>+S and then <F3> to save and return to the list of RFCs.
6.	Repeat steps 1 through 5 for each additional RFC connection
 
Convert Logical Systems 
Under no circumstances perform this procedure on a Production system

BDLS
1.	When warned to read the documentation, press the checkmark button.
2.	In the Old logical system name box, press <F4>.
3.	Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
4.	In the New logical system name, enter what that logical system name should be called on this newly refreshed system (i.e. WIITRN400)   Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
5.	De-select the Test Run and Existence check on new names in tables options
6.	From the Program menu, select Execute in background
7.	Press the checkmark button when asked to select a spool device
8.	Press the Immediate button when asked for the schedule
9.	Press <Ctrl>+S to save
10.	Use SM37 to monitor the job
11.	When job is complete, repeat steps 2 through 10 for any additional logical system names that need to be changed.
Adjust Logical Systems names
SALE
1.	Expand Sending and Receiving Systems, then Logical Systems
2.	Click on the execute icon beside Define Logical System
3.	Press the checkmark button to confirm that the change is cross client
4.	…
 
Allow Certains Settings to be modifiable
(Refer to Note 356483 for more Details)
SM54
1.	Enter V_T001B in the Table/View box.
2.	Select the Generated Objects option.
3.	Press the Create/Change button.
4.	Enter any access keys if requested
5.	Change the Recording routine to no, or user, recording routine.
6.	Press <Ctrl>+S to save
7.	Press <Enter> if warned that you are changing a function group that doesn’t belong to you.
8.	You are prompted for transport.  Create a new local transport.  
9.	Repeat steps 1 through 8 for the following objects.  You can specify the same transport you created above.
V_T001B_GL
V_T093B_01
V_T093B_02
BSI Configuration (R3 HR Systems only)
SM59
1.	Expand TCP/IP Connections
2.	Highlight BSI70-US-TAX and press the Change button
3.	Change the program field to <hostname>sapmnt<SID>SYSEXERUNTF60SERVER.EXE
4.	Double check the target host and gateway point to the correct server
5.	Press <CTRL>+S to save
6.	Press the Test connection button to test.  If the connect is not successful, take the necessary steps to resolve the issue.
SE38
1.	In the Program field, enter RPUBTCU0
2.	Press <F8> to execute
3.	Select option BSI version 7.0
4.	Press <F8> to execute
5.	BSI should return tax calculations.  If there are errors, take the necessary steps to resolve.
Reconfigure DB13 schedule
DB13
1.	Using the print out created before the refresh, recreate the DB13 calendar.
 
Client Configuration
SCC4
1.	From the Table view menu, select Display -> Change
2.	When warned that the table is cross-client, press the checkmark button.
3.	Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4.	Define clients as follows depending on client role

Development
Client role:  Customizing
Changes and transports for client-specific object:  Automatic recording of changes
Client-independent object changes:  Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool:  Protection level 0
Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

Quality Assurance
Client role:  Test
Changes and transports for client-specific object:  No changes allowed
Client-independent object changes:  No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool:  Protection level 0
Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

Training
Client role:  Education
Changes and transports for client-specific object:  No changes allowed
Client-independent object changes:  No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool:  Protection level 0
Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

Sandbox
Client role:  Test
Changes and transports for client-specific object:  Changes without automatic recording
Client-independent object changes:  Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool:  Protection level 0
Restrictions when starting CATT and eCATT:  eCATT and CATT allowed

5.	Press <CTRL>+S to save.
6.	Repeat steps 4 through 6 for any additional clients
Set System Change Option
Skip this section of the system is a Development or Sandbox System.

SE06
1.	Press the System Change Option button.
2.	Set the global setting to Not Modifiable
3.	Press <CTRL>+S to save.
 
Release Background Jobs
Currently, all background jobs, except for system standard jobs have been placed on hold (status scheduled).  In coordination with Basis and functional support people, review the jobs and when considered to be safe, use transaction SM37 to reschedule the jobs.

[Former Member]

thx

[Former Member]

Hi!

As the Server hardware got problems and running out of disk space so I have to migrate the SAP system to a new Server H/W. This is a Dev. System.

Details :

Current : SAP R/3 4.7 (SR1) 1.10 IDES with Kernel 6.20 NU

OS : Windows 2000 AS

DB : Oracle 8.1.7.4.1

Proposed : SAP R/3 4.7 (SR1) 1.10 IDES with Kernel 6.20 NU

OS : Windows 2003 R/2

DB : Oracle 9.2 or 10.2g

I have the doc you provided but want exect step by step guide. Can U please provide me that (foe windows/oracle)?

Waiting for U R reply.

Thanks and regards,

Pratip

[Former Member]

There is a guide that describes the procedure available on the Service Marketplace (http://service.sap.com) at quicklink /instguides -> SAP NetWeaver -> <release> -> Installation -> SAP Web AS -> <documentation> -> Homogeneous and Heterogeneous System Copy.

Best Regards,

Matt

[Former Member]

Hi! Matt,

I have the pdf but I want exact step by step guide. Do U have that?

regards,

Pratip

[Former Member]

Hi Patrip,

Have you read the guide? In the sections called "Process Flow" there are steps that tell you exactly what to do.

Regards,

Matt