0% found this document useful (0 votes)
20 views51 pages

Sybase Refresh_08-07-2020

The document outlines the pre-steps and procedures for refreshing a Sybase system from a production (PRD) server to a quality assurance (QA) server. Key tasks include transferring backups, configuring SAP licenses, checking disk space, and exporting logical systems and RFC destinations. It also emphasizes the importance of performing a QA backup before proceeding with the refresh process.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
20 views51 pages

Sybase Refresh_08-07-2020

The document outlines the pre-steps and procedures for refreshing a Sybase system from a production (PRD) server to a quality assurance (QA) server. Key tasks include transferring backups, configuring SAP licenses, checking disk space, and exporting logical systems and RFC destinations. It also emphasizes the importance of performing a QA backup before proceeding with the refresh process.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 51

Sybase Refresh KCT

Pre-Steps

 Transfer backup from PRD server to QA server

 SAP License (SLICENSE)


Hardware Key: M0633535226
Installation Number: 0020879747
System Number: 000000000850011164

 Target System: Table V_TBDLS


 BD54

 Check Disk Space

Prod Server

QA Server

 WE20
Client- 100


 WE21
Client 100
 Print Transport history and Transport Routes
TMS Configuration
 SCC4
 RZ04
 SMLG and RZ12

 DB13
No jobs scheduled
 SPAD
Screenshot and eport
 Assignment of Logical systems to RFC
Call table RSLOGSYSDEST with transaction se16 in client 000.
Note table entries.

EDPP1
 SMT1
 SCOT
 SMQR

 SMQS

 SLDAPICUST
 RZ70
 RZ21

 SM59
 STRUSTSSO2
 Export User from target System
SCC8  SAP_USER
KQEKO00008
KQEKT00008
KQEKX00008

 Export Logical system table from target system

# begin of script
# execute script with
# R3trans -w export_ls.log export_ls.sql
# as <sid>adm in /home/<SID>adm/
# this creates a file export_ls.dat for import of Logical system names
# logfile export_ls.log
export
client=all
file='export_ls.dat'
delete from PATH
select * from PATH
# end of script

Execute:
R3trans -w Export_logical_system.log Export_logical_system.sql

 Export RFC destination in Target system:

Log on to the host on which the system is running as user <KQE>adm.

In addition to the rfc tables, we include securestore tables in the export from the target system. If these tables are
imported after the valid license is installed, passwords in RFC’s need not be reentered. No RFC’s should exist to
productive system (except CUA and Solman).

Log on to the target system host on which the system is running as user <SID>adm. Use a text editor to create the
export controlfile “export_sm59.sql” in /home/<SID>adm as shown below:

# start of script
# execute script with
# R3trans -w export_sm59.log export_sm59.sql
# as <sid>adm in /home/<SID>adm/SM59
# this creates a file export_sm59.dat for import of RFC data and a
# logfile export_sm59.log
export
client=all
file='export_sm59.dat'
delete from RFCDES
select * from RFCDES
delete from RFCDOC
select * from RFCDOC
delete from RFCATTRIB
select * from RFCATTRIB
delete from RFCCHECK
select * from RFCCHECK
delete from RFCDESSECU
select * from RFCDESSECU
delete from RFCSYSACL
select * from RFCSYSACL
delete from RFCTRUST
select * from RFCTRUST
delete from RFCCMC
select * from RFCCMC
delete from RFCGO
select * from RFCGO
delete from SXRFC
select * from SXRFC
delete from IBSSI_RFCDEST
select * from IBSSI_RFCDEST
delete from PARAMVALUE
select * from PARAMVALUE
delete from TXCOM
select * from TXCOM
delete from RSECTAB
select * from RSECTAB
delete from RSECACTB
select * from RSECACTB
delete from RZLLITAB
select * from RZLLITAB
# end of script

Perform the export as user <SID>adm

R3trans -w export_sm59.log export_sm59.sql


 QA backup before proceeding for refresh

Backup transfer
Start SAP and suspend all jobs

SE38  BTCTRNS1

Apply license
BDLS

STMS configuration

SE06 
YES
Yes
YES
YES

You might also like