System Refresh Precautions?

Former Member — Tue, 22 May 2007 09:52:29 GMT

Hi,

During system refresh, are all types of data - master data, transaction data as well as <b>customising data</b> get refreshed from prouduction environment?

Could you please suggest what is best way to get back project specific new customising data on a refreshed environment? Is there some sap recommended best practice on this.

regards,

Karthik

Re: System Refresh Precautions?

Former Member — Tue, 22 May 2007 10:09:47 GMT

Hi Please go through. This will give you exhaustive information. After refresh we used this to get back the required system specific customizations.

Refresh from PR1 to QA1

1. Before the copy

 Note down customer key, Installation number and license key - Done

• LICENSE system: QA1

• Customer key: L1985917776

• Expiration_date: 99991231

• Installation no: 0020065063

• Key: GKRZ25H353129JYX8HCJRS13

• Productid: R3_ORA

license useable ***

(directory: \usr\sap\QA1\SYS\exe\run)

(run command: saplicense – show)

Team Involved: SAPDBA

 Download RFC tables - To be done

Tables rfcattrib, rfcdes and rfcdoc have been exported using sapdba on QA1 and the corresponding files are kept in a new temporary directory: /oracle/QA1/rfc_dest. After the system copy, these files have to be moved from /oracle/QA1/rfc_dest to /oracle/QA1/sapreorg and then the tables can be imported into QA1, to revert back to the RFC destination information as it is now.

Steps : 1)login with oraqa1

2) type sapdba

3) select e - Export/import

Perform this step two days before the scheduled refresh.

Team Involved: SAPDBA

 Backup user master records in QA1 - To be done

Procedure : login to QA1 400.

Execute Transaction code: SCC8 (CLIENT EXPORT)

Selected profile: SAP_USER

Target system: QA1/DV1(safety backup)

Perform this step two days before the scheduled refresh.

Team Involved: SAPDBA

 Compare filesystem spaces - Done

Team Involved: SAPDBA

 Compare transports To be done

Team Involved: SAPDBA

 OPERATION MODES(RZ04) Done

Existing QA1 operation modes.

Team Involved: SAPDBA

 Successful backup of PR1 To be done

A successful offline backup has been scheduled on *** and that backup will be restored on to QA1 by the Unix team.

Team Involved: USTO

 System messages/E-mails To be done

SM02- CREATE A TEST MESSAGE IN PR1

Two days before the scheduled refresh perform this step.

Team Involved: SAPDBA

 Delete the existing datafiles on QA1 To be done

lsnrctl stop

rm –rf sapdata?/*

Team Involved: SAPDBA

2. The copy To be done

Copy all the datafiles from /oracle/PR1/sapdata? To /oracle/QA1/sapdata?

Owner, group and permissions of the new files/directories to be maintained as before

Copy Command: rcp –p /oracle/PR1/sapdata* Sierra: /oracle/QA1/sapdata*

(NOTE: If errors occur when restoring/copying the sapdata on the target system, the complete restore/copying has to be repeated.)

Team Involved: UNIX FOF/USTO

3. After the copy To be done

 Creating the control file on PR1 – To be Done

connect internal

alter database backup controlfile to trace;

exit

FILE created under the following Location: \ORACLE\PR1\saptrace\usertrace\ <pr1_ora_xxxx>.trc chose the latest run

ftp the file onto desktop

Team Involved: SAPDBA

 Edit the control file – To be done

Here is the edited control file:

Team Involved: SAPDBA

 Creating the control file on QA1 - To be done

connect internal

@control.sql

alter database open resetlogs;

lsnrctl start

exit

Team Involved: SAPDBA

 Post system copy activities

• License installation - to be done

Goto /usr/sap/QA1/SYS/exe/run

command: saplicense –install

• Installation check (Transaction SICK)

• SE06 > Database Copy or Migration > Post Installation Processing

• Delete entries from tables: DBSTATHORA, DBSTAIHORA, DBSTATIORA, DBSTATTORA, MONI, PAHI, OSMON, DBSNP, SDBAH, SDBAD, SDBAP, SDBAR, DDLOG, TPFET, TLOCK and TPFHT

• Initial SAP consistency check (Transaction SM28)

• Database consistency check (Transaction DB02)

• Server check (Transaction SM51)

• TMS configuration

Logon to the SAP R/3 System and goto TCODE SE06. Select "Database Copy or Migration" and execute "Post Installation Processing".

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

• Logical system set-up and BDLS

Delete logical system for client 400 after system refresh and create new logicalsystem and assigned to client 400.

After refresh: LOGSYS400(logical system for client 400)

Delete this logical system and create new logical system

New logical system: QA1CLNT400 (logical system same before refresh in QA1)

• ITS and Bugseye settings

• RFC destinations as per Appendix (import the exported tables and then delete the temporary directory /oracle/QA1/rfc_dest)

• Logon load balancing(Transaction SMLG)

• Instance profiles

Import profiles from active servers using RZ10

Save and Activate instance profile. And restart the sap services.

• CCMS configuration

• Housekeeping jobs

Background jobs(daily jobs)

• Application jobs

• Printer/spool/TemSe set-up

• User administration

The transports are imported implicitly in post processing with transaction

SCC7.

• Transport sequence number set-up

• Mass transport and Support package/patch application.

Re-import transports to QA1 from DV1 which are not available in PR1.

• Manual configuration

• Create the rest of the clients:

o 400 UAT/OAT Live Copy

New client 340 to be created with the following settings.

Source client: 400

Target client :340

Profile: SAP_UCSV

COPY MODE: local copy

Team Involved: SAPDBA

Re: System Refresh Precautions?

Former Member — Tue, 22 May 2007 12:37:17 GMT

Make sure you export 2 items from Quality before you refresh it from PROD.

1. User -Master

2. Import tables - all those specific to the Quality System like Logical Systems,etc

Question Re: System Refresh Precautions? in Technology Q&A

System Refresh Precautions?

Re: System Refresh Precautions?

Re: System Refresh Precautions?