SAP System Refresh

-

SAP System Refresh Procedure





REFRESH PROCEDURE
FOR  R/3 + Win2K



Prerequisites


Source SAP system (usually production)

Destination SAP system (to be refreshed, usually test or development)

Source system outage start (for database copy)

Source system outage duration

Refreshed system role (test/dev)

BDLS processing required
NO
Refresh project leader



Skills required

SAP BASIS
Win2k operating system
Oracle database concepts



Useful OSS notes

147243
R3 system copy
50088
Creating OPS$ users under  WindowsNT/Oracle








Preparation stage (by refresh project leader)

Refresh project leader should perform the following.

1) Order outage and get approval from system owner
2) Ensure that both source and destination systems are successfully backuped


Pre-refresh tasks

Step
Description
Task
10
Export variants, ALE, authorizations, RFCs, etc from DESTINATION SYSTEM

1) Choose your Windows menu “Start -> Run” and execute:

         \\source_system_server\d$

(for example if it is NC3, then execute \\vegnt2.veg.eu.mars\d$)

You will be asked for user and password, use sidadm. Then destination system drive D: will appear.

Please note that:
a) Remote disk opening may take a long time, up to 1 minute!
b) In opened Explorer window you can copy/rename/delete any files
without any restrictions, so be attentive!

2) Create folder REFRESH on drive D:


3) Unpack these files and copy them into folder REFRESH on destination system using Windows clipboard:


4) Logon DESTINATION SYSTEM  using “Terminal services client” as sidadm

5) Run  command prompt in terminal window and run the following:

d:
cd REFRESH


(Users and Authorisations export)

R3trans -w EXPUSR.log EXPUSR.R3trans
Check for a file called USEREXP.dat
Check the EXPUSR.log for errors.

(RFC destinations export)

R3trans -w EXPRFC.log EXPRFC.R3trans
Check for a file called EXPRFC.dat
Check the EXPRFC.log file for errors.

(IACOR Sites export)

R3trans -w EXPIACOR.log EXPIACOR.R3trans
Check for a file called EXPIACOR.dat
Check EXPIACOR.log for errors.

(ALE model export)

R3trans -w EXPALE.log  EXPALE.R3trans
Check for a file called EXPALE.dat
Check EXPALE.log for errors.

(TQRFC export)

R3trans -w EXPTQRFC.log EXPTQRFC.R3trans
Check for a file called EXPTQRFC.dat
Check EXPTQRFC.log for errors.

(Variants export)

R3trans -w EXPVARI.log EXPVARI.R3trans
Check for a file called EXPVARI.dat
Check EXPVARI.log for errors.
20
Stop destination system
DESTINATION SYSTEM:
Stop SAP and Oracle according to Start/stop instructions
30
Delete destination database
DESTINATION SYSTEM:

1) Delete the next directories on destination system:

D:\oracle\sid
E:\oracle\sid
F:\oracle\sid  (if exists)

2) Empty the Recycle Bin.
40
Backup profile files
DESTINATION SYSTEM:

1) Copy the following files  from c:\oracle\SID\920\database  to d:\REFRESH directory:

InitSID.ora
InitSID.dba
InitSID.sap

2) Copy  SAP profiles from d:\usr\sap\SID\sys\profile  to d:\REFRESH directory.
50
Copy profiles from source to destination system
1) Copy files:

InitSID.ora
InitSID.dba
InitSID.sap

from source to destination server, directory c:\oracle\SID\920\database

2) Rename copied files according to destination SID on destination server


To access source host  from destination server  you   can use 
 \\<remote_host>\<disk>$  command via Windows "Start > Run" menu.

For example to access disk C: on server VEGNT2 do the follow:

A.       Choose Windows menu “Start -> Run”
B.       In “Run” window issue:

\\vegnt2.veg.eu.mars\c$

C.       Press OK
D.         Wait until Explorer window with remote disk opens
60
Correct copied profiles
DESTINATION SYSTEM:

Edit files on destination server, check parameters and replace source  SID with destination SID :

InitSID.ora
InitSID.dba
InitSID.sap



Database copy

        This stage may take up to 5 hours !
Step
Description
Task
70
Stop source system, start in mount mode  and generate “control.sql”
SOURCE SYSTEM:

1) Stop SAP and Oracle on source system according to Start/stop instructions

2) Run SQLPLUS and issue:

startup mount

alter database backup controlfile to trace resetlogs;

shutdown;

3) Find *.trc file in  %SAPTRACE%\usertrace\  directory and rename it  to control.sql
80
Prepare “control.sql”

1)       Copy the generetaed in previous step file control.sql  to destination server into  d:\oracle  directory and open it using the Editor.
2)       Delete the introductory text  so that the file starts directly with the following line:
             "CREATE CONTROLFILE..."


3)  Delete all lines after “CREATE CONTROLFILE…” statement (this statement ends with semi colon ; )

4) Change datafiles paths  in "CREATE CONTROLFILE..." statement from source SID to destination SID.

5) Replace

"CREATE CONTROLFILE REUSE DATABASE <SOURCE SID> NORESETLOGS ARCHIVELOG"

by

"CREATE CONTROLFILE SET DATABASE <DESTINATION SID> RESETLOGS ARCHIVELOG"
90
Database copy
1)       Make sure that SAP and Oracle are stopped on the source system

You should not, under any circumstances, start the database during the copy procedure!


2)       Copy from source to destination system directories:

D:\oracle\SID
E:\oracle\SID
F:\oracle\SID  (if exists)

3)       Change all occurrences of the source SID in the directories  names to destination SID
100
If outage time is over – start source system

(See pre-requisites for outage start time and duration)

If you have enough time – do not start the source system until you have  successfully started the destination database (until you reach step 130). In this case  parts that  have possibly been forgotten can be recopied.

If you decide to start source system at this step - use start/stop instructions from "Common SAP R/3 Technical Docs"
110
Rename old controlfiles
DESTINATION SYSTEM:

Find all control files and rename them to *.OLD

You can find list of controlfiles in  initSID.ora file on destination server, parameter name: CONTROL_FILES
120
Restart service
DESTINATION SYSTEM:

Stop and start the service "OracleService<SID>" in the control panel
130
Start destination database
DESTINATION SYSTEM:

Run SQLPLUS, logon as “/ as sysdba”  and enter the following:
  
   startup nomount
   @d:\oracle\control.sql
   alter database open resetlogs;

 
140
Start source system
IMPORTANT !

If you haven’t started the source system before – start it now according to start/stop instructions from "Common SAP R/3 Technical Docs"
150
Restart destination database
DESTINATION SYSTEM:

Ensure that database is able to start/shutdown. Run SQL plus and execute:

shutdown;

startup;

exit;




Post-copy steps: Database        ONLY DESTINATION SYSTEM !

Step
Description
Task

160

Create OPS$ users

 1) Run SQLPLUS


2) Find all OPS$ users and drop them using these clauses:

select username from dba_users where username like 'OPS%';

For every OPS$ user found execute this:

drop user "<OPS$ user>" cascade;

3) Create new OPS$ users:

"OPS$<DOMAIN>\<SID>ADM"
"OPS$<DOMAIN>\SAPSERVICE<SID>"

Domain is database server name, this is example of OPS$ user for PM2, database server VEGNTB:
"OPS$VEGNTB\PM2ADM"

Execute these statements in SQLPLUS:

connect / as sysdba

create user "OPS$<DOMAIN>\<SID>ADM" default tablespace psapuser1d temporary tablespace psaptemp identified externally;

create user "OPS$<DOMAIN>\SAPSERVICE<SID>" default tablespace psapuser1d temporary tablespace psaptemp identified externally;

grant connect, resource, sapdba to "OPS$<DOMAIN>\<SID>ADM";

grant connect, resource, sapdba to "OPS$<DOMAIN>\SAPSERVICE<SID>";

drop public synonym sapuser;
(it may be an error on this step, you can continue with the other steps)

create table SYS.SAPUSER (USERID VARCHAR(256), PASSWD VARCHAR(256));

insert into SYS.SAPUSER values ('SAPR3', '<password>');
(See password for SAPR3 user in “Common R/3 technical docs” Lotus database, for source system.

commit;

create public synonym sapuser for SYS.SAPUSER;

grant select, insert, update on SAPUSER  to "OPS$<DOMAIN>\<SID>ADM";

grant select, insert, update on SAPUSER  to "OPS$<DOMAIN>\SAPSERVICE<SID>";

grant select, insert, update on SAPUSER  to SAPR3;

4) Check that OPS$ users can logon database. Execute:


connect /

select * from sapuser;

connect /@<SID>

select * from sapuser;

In both cases you should get at least 1 record.


5) Check if parameter remote_os_authent is set to true in initSID.ora . If not – set it.

170

Clean up some SAP tables

Run SQLPLUS and delete entries from some tables:

connect sapr3
delete sapr3.dbstathora;
delete sapr3.dbstaihora;
delete sapr3.dbstatiora;
delete sapr3.dbstattora;
delete sapr3.moni;
delete sapr3.pahi;
commit;

delete sapr3.osmon;
delete sapr3.dbsnp;
delete sapr3.sdbah;
delete sapr3.sdbad;
delete sapr3.sdbap;
delete sapr3.sdbar;
delete sapr3.tpfet;
delete sapr3.tpfht;
delete sapr3.ddlog;
delete sapr3.tlock;
commit;
  175
 Truncate RFC destinations
Truncate some tables using SQLPLUS:

TRUNCATE TABLE RFCDES;
TRUNCATE TABLE RFCDOC;
TRUNCATE TABLE RFCATTRIB;
TRUNCATE TABLE RFCDESSECU;
TRUNCATE TABLE RFCSYSACL;
TRUNCATE TABLE RFCTRUST;
COMMIT;
180
Re-install SAP license on destination system
1)       Delete  old SAP licenses from destination system

2)       Install SAP license.
PLEASE, DO NOT ORDER A  NEW LICENSE !
You can find license details for destination system on SAP OSS site (http://service.sap.com) or in  “Common SAP R/3 technical docs” Lotus database, part
SAP TCC Configuration Management -> Access -> SAP systems

To show installed licenses use:
saplicense -show

To know the hardware key of the destination server use:
saplicense -get

To delete a license use:
saplicense -delete

To install a license use:
saplicense -install




--------------- Example of deletion old licenses after NC2 -> NC3 refresh --------------




--------------- Example of installation of saplicense after NC2 -> NC3 refresh ---------------

If any problems with license installation - you can install a temporary license and continue.

190

Block all background jobs

IMPORTANT ! Block execution of SAP background jobs to prevent interfaces working on test/development system:

Edit SAP instance profile in directory D:\usr\sap\SID\sys\profile
set parameter   rdisp/wp_no_btc  to 0

(remember old value or comment the old value and add new one!)




Post-copy steps: SAP        ONLY DESTINATION SYSTEM !

Step
Description
Task
200
Run destination SAP system
Run SAP management console and run SAP:

In tree right-click on target SID and in context menu
select “Start"
210
First logon into refreshed SAP system
Logon into destination SAP system.

Take into account that the source system logins should be used!
220
Update logins in “Common R/3 technical docs”
Check SAP and Oracle logins, correct them in “Common R/3 technical docs” as they have changed in destination system after database copy.

230

Delete ALL background jobs to prevent production interfaces running

1) Run SM37
2) Select jobs with all statuses, leave “From”, “To” fields empty.
3) List of jobs appears. Select all jobs and delete.
If problems with deletion – check status of problem jobs using SM37 menu.
240
Configure Workbench Organizer
1)       Run SE06, option “Database copy or migration”
2)       Click “Post-installation processing” button

Proceed according to this:




Answer: YES


Enter source system

Then:

Answer: YES

If window is opened with unreadable text - just close it.

Other screens appears about TMS not configured:

Answer: YES

Answer: YES

Answer: YES

Press the button with green check.



--------------  SE06 Screens -----------------------------------------

250

Maintain SAP profiles

1)       On operating system level make copies of default, start and instance SAP profiles.

Directory:
D:\usr\sap\SID\sys\profile

Then:
2)       Run RZ10
3)       Menu option "Utilities --> Import Profiles of Active servers"
4)         Save and activate every imported profile
260
Convert printers to new spool server
The following procedure is used to convert the printers taken over from the source system to the target spool server. Typically this procedure will be used during the post system copy activities.


1)      Delete ALL spool requests. Run SPAD
Administration -> Delete old spool requests

2) Run transaction se38 and run report RSTS0022
Select 'All Objects older than' and enter 0 for the number of days
Select Delete

3)      Delete TemSe objects : SP12
TemseDtabaseStorage > Consistency Check > Delete All

4)      Maintain  spool servers : SPAD

Select "Output Devices", switch to EDIT mode

Menu "Utilities" -->"for output devices"  -->
"Assign Server" --> "Display list" --> "Convert & Unlock"
270
Change number of background processes

1) Edit SAP instance profile in directory D:\usr\sap\SID\sys\profile
set parameter   rdisp/wp_no_btc  to previous value, remembered in step 190.
280
Restart SAP

Restart SAP using “SAP system management console”
290
Create new instance definition and operation modes

1)       RZ04 -> button “Instances/Profiles”
2)       Menu “Profile -> Create new instance”
3)       Fill in fields
4)       Press “Maintain details” button, correct “Instance name” and “Home directory” fields
(replace DVEMS… by DVEBMGS… in “Instance name” and “Home firectory” fields)
5)       Save
6)       Deactivate and delete old instance
7)       Activate new instance
300
Define operation modes and timetable

1)       RZ03
2)       Menu “Edit -> Operation modes -> Configure”
3)       Create new operation mode “Day”
4)       Configure workprocess distribution for “Day”. You can use these values:

BGD: 3
SPO: 1
UPD: 2
UP2: 1
ENQ: 1
and other processes - DIA

5)       Menu “Edit -> Operation modes -> Timetable”, assign mode Day to all time intervals.

6)       Activate operation mode “Day”, if workprocess inconsistencies problems – fix them (If needed – correct SAP profiles and restart SAP)

7)       Delete old operation modes
310
Check workprocess distribution

SM50
320
Check SAP consistency

Run transaction SICK, fix errors
330

Check database connectivity

1)       Run sapdba
Menu “DB check/verification -> Database System check”
340
Create SAP standard housekeeping jobs
1)       Transaction SM36
2)       Press the button “Standard jobs”
3)       Menu “Reorg job -> Default scheduling”
350
Schedule job for TMS

Start report RDDNEWPP in 000 client
360
Create signon message
Signon message contains information  which source system was copied from and when:

1)       Logon to 000 client

2) Run transaction SCC4. 

Allow client-independent customising and repository changes in client 000.

3)       Run transaction SE06, press the button “System change option”

Set the global system change option to “modifiable” and set the following software components to modifiable:
a.       HOME
b.       LOCAL
and set the following namespaces to modifiable:
a.       Customer name range
Namespaces /BIC/* and /BI0/*)



4)          SE61
5)          Enter data element name “ZLOGIN_SCREEN_INFO”, choose document class: “General text”.

Choose the same language as used in logon screen !
(English or Dutch)

6)          Choose “Change”. If object doesn’t exist – “Create”.

  Once the Create( or the change)  is activated you can enter a free text!
Suggested format:
<Destination SID> : System refreshed from <Source SID> - date

The date should be the date of the database forward recovery (step 130)

Example for PM2:
PM2: System refreshed from PM1 – 13 December 2006

7) Save and activate . (save as “LOCAL OBJECT” if you create )

8) Only for test system: run transaction SE06, press the button “System change option”, choose global settings "Not modifiable".

9) Run SCC4, set "No changes allowed" and "No changes to Repository and cross-client objs" for client 000
370
Configure working client(s)

1)       Run SCC4
2)       Set Edit mode
3)       Double-click on every working client (for Veghel PM systems: 002, for Veghel HR systems: 002 and 003) and set:

For test system refresh:

-         Change client name from production to test
-         Change client role to “test”
-         “No changes allowed”
-         “No changes to Repository and cross-client Customizing jobs”
-         “No overwriting”
-         “eCATT and CATT” allowed

For development system refresh:

-         Change client name from production to development
-         Change client role to “Customizing”
-         “Automatic recording of changes”
-         “Сhanges to Repository and cross-client Customizing allowed”
-         “No overwriting”
-         “eCATT and CATT” allowed

4)       Save changes
380
Check status values

Menu “System -> Status…”. Check status values at status window (server name, database name, etc.)
390
Check SAP&Oracle start/stop instructions
Check that SAP and Oracle can be started/stoped according to
Sart/Stop instructions in “Common R/3 technical docs”.
If you get error messages – fix the problems.

Stop and then start  SAP&Oracle
400
Configure STMS

Skip this step (to be performed by refresh project manager later).

410
Create DB13 schedule

Skip this step (to be performed by refresh project manager later).
420
Import  variants, ALE, authorizations, RFCs, etc to  DESTINATION SYSTEM

Skip this step (to be performed by refresh project manager later).
430

Notification

Refresh is finished. Please notify refresh project manager about completion (see prerequisites).




Comments

Post a Comment

Popular posts from this blog

SAP NWA: Net Weaver Administration Tool

-
SAP ERP NWA Tool    SAP NetWeaver Administrator  Use SAP NetWeaver Administrator is a Web-based tool for administration and monitoring that offers a single entry point to configure, administer, and monitor your SAP NetWeaver system, its components, and the applications running on top of it. Prerequisites The Application Server Java (AS Java) is running. Features The SAP NetWeaver Administrator unifies the most important administration, monitoring, and troubleshooting tools. Some of the main SAP NetWeaver Administrator features are:  ●  A single, central tool for administration, troubleshooting, and problem analysis of your SAP NetWeaver system. You can perform administration tasks, such as starting and stopping instances, checking and modifying configuration settings, analyzing logs and traces, ensuring the error-free functioning of all system components by continuous system monitoring.  ●  An easy-to-use, task-oriented interface.  ...
Read more

SAP BASIS Spool Process

-
SAP BASIS SPOOL PROCESS : Spool Work process: This is used to print the documents, user cannot access this process directly, user uses dialog process or background process to print the documents. The data which to be printed will be stored in Temse (Temporary sequential objects) either OS level or DB level .Spool process look into Tempse and print the documents.   Which is determined by parameter rspo/store_location= db/g If it is G (Global ) it is tored in sys global directory Usr/sap/sid/sys/Global If it is database , it is stored in the table TST01 & TSTC Advantage of TEMSE at G file System : It is easily accessable. Disadvantages : when the spool size is increases , managing the spool will difficult ( no indexing at file system level ) File system will (may ) be corrupted file system is a not a part of regular backup in case of crashes entire spool data will be lost Advantages of Tempse store at D/B ...
Read more

SAP BASIS SPOOLING : Printing problems and general issues

-
Image
SAP BASIS Printing problems : General Issues How to Resolve SAP Printing Problems Print request from SAP R/3 is not printing. Try to print something else from a different application (for instance an email message or a page from Netscape) via the network. If you cannot print at all then the problem is not SAP printing, but the network. If you can print a file from a different application but not from SAP, then the problem is SAP printing and probably not the network. If you have a local IT support provider , report the problem to this person. Tell your IT support provider the four-character printer name, e.g. "wtpr". Remember to give the four-character name of the printer and its location. You can find this information in SAP by looking at your User Profile or opening the Print Screen List screen. the SAP system from which you sent the print request the spool request number displa...
Read more