Escolar Documentos
Profissional Documentos
Cultura Documentos
Versio
n
1.0
1.1
Author
Change Description
Page 1 of 63
1. PRE-DATABASE/SAP REFRESH....................................................................................7
1.1Post a System Message about Scheduled Downtime....................................................................................................7
1.2Saplicense..........................................................................................................................................................................7
1.3 Confirm Passwords for Source/Target system with Security team.........................................................................7
1.4 Stage Instance Specific Information before Volume Group is recreated................................................................8
1.5 Export User Master data.............................................................................................................................................8
1.6Transport Printer Definitions.........................................................................................................................................9
1.7Transport RFC Definitions.............................................................................................................................................9
1.8Logical System Definitions..............................................................................................................................................9
1.9Partner Profile.................................................................................................................................................................9
1.10 IDOC Port Definitions..................................................................................................................................................9
1.11 Client Definitions..........................................................................................................................................................9
1.12 Trusted Systems .........................................................................................................................................................10
1.13 Trust Manager Portals Certificates.......................................................................................................................10
1.14 Integration Engine Configuration.............................................................................................................................10
1.15 Maintain SLD Access data ........................................................................................................................................10
Page 2 of 63
2 DATABASE BACKUP.......................................................................................................19
2.1Oracle Database Backup Source System..................................................................................................................19
2.2SCM maxDB liveCache Backup - Source System......................................................................................................19
3.
Page 3 of 63
Page 4 of 63
Page 5 of 63
APPENDIX.............................................................................................................................62
Steps to reset the SDM password......................................................................................................................................62
Steps to synchronize SDM Server ....................................................................................................................................63
To recreate PSAPTEMP table space................................................................................................................................63
Starting Java SDM server..................................................................................................................................................63
Stopping Java SDM server:...............................................................................................................................................63
Page 6 of 63
1. Pre-Database/SAP Refresh
Most of the steps under this section will be performed at least One week prior to
Refresh .
1.2 Saplicense
Logon to as <sid>adm on Source System
Check your sap license
saplicense show
Export the saplicense information to a file under <sid>adm home directory.
cd /home/<sidadm>
saplicense show > saplicense.SID
Page 7 of 63
cd /usr/sap/put_refrersh
mkdir -p oracle/T_SID
mkdir -p usr/sap/T_SID/DVEBMSxx
mkdir -p sapmnt/T_SID
cd /oracle/<T_SID>
tar -cvf /usr/sap/put_refresh/oracle/U11/102_64.tar 102_64
{Note: To check the tar file structure tar -tvf <filename>.tar}
cd /oracle/<T_SID>
tar cvf /usr/sap/put_refresh/oracle/U11/dotastrik.tar .[a-z]*
cd /sapmnt/<T_SID>
tar -cvf /usr/sap/put_refresh/sapmnt/U11/profile.tar profile
cd /usr/sap/<T_SID>/DVEBMGSxx
tar -cvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar igs
cd /oracle
tar cvf /usr/sap/put_refresh/oracle/client.tar client
tar -cvf /usr/sap/put_refresh/oracle/oraInventory.tar oraInventory
Team - Please add any other directories or files that you want to save off before
the Volume Group is recopied with Target Volume Group.
1.5
Page 8 of 63
Page 9 of 63
1.16
1.16.1 ABAP
Run Transaction RZ70
Take screenshot or note the SLD Bridge Host and Service Info.
1.16.2 Java
Logon to Visual Admin
Go to services Select SLD Data Supplier Note SLD Data Collection Settings
Note CIM Client Generation Settings
Page 10 of 63
1.22
1.23
Page 11 of 63
1.26
XI Specific Steps
Page 12 of 63
Page 13 of 63
Page 14 of 63
1.27
BI Specific Steps
cdD
cd j2ee
cd admin
./go (make sure an x-client is used with DISPLAY variable set up)
select the Central Instance Server in the left pane and open it up
select Services -> JDBC Connector
Now select Connector Container in the left pane
Select the jdbc connector container, e.g.,
SDK_JDBC_TD
SDK_JDBC_TD_ISCP
Go to tab Managed Connection Factory and then Properties for all the
specified connector containers,
Note down the following for each of the Connectors
Document the FixedSchema
Find the password for Password field (Obtain Password Prior to refresh) and
document it for each landscap in this document for future refreshes.
Document for URL
Document for UserName
Page 15 of 63
1.28
cdD
cd j2ee
cd admin
./go (make sure an x-client is used with DISPLAY variable set up)
select the Central Instance Server in the left pane and open it up
select Services -> JDBC Connector
Now select Connector Container in the left pane
Select the jdbc connector container, e.g.,
SDK_JDBC_TD
SDK_JDBC_TD_ISCP
Go to tab Managed Connection Factory and then Properties for all the
specified connector containers,
Note down the following for each of the Connectors
Document the FixedSchema
Find the password for Password field (Obtain Password Prior to refresh) and
document it for each landscap in this document for future refreshes.
Document for URL
Document for UserName
Page 16 of 63
Page 17 of 63
Page 18 of 63
Database Backup
Page 19 of 63
3.
3.1
ln s /oracle/<T-SID> /oracle/<S-SID>
Validate user exists on the target system.
Change the ownership of all /oracle/<T-SID> files to source system ora<ssid>.
To change the ownership we need to be the root.
Now login as root
sudo su
Change the ownership
Page 20 of 63
3.2
3.3
su ora<s-sid>
sqlplus / as sysdba
startup;
exit
3.4
Page 21 of 63
RESETLOGS ARCHIVELOG
$
Move your cursor upto word ARCHIVELOG by using key h on your keyboard
dw
and move your cursor upto word REUSE and by using h on your keyboard
dw
now switch to insert mode i
Now write SET
Now your modified command looks like
CREATE CONTROLFILE SET DATABASE "<Target_System_SID>"
RESETLOGS
Now search the string RECOVER in the file and replace the following line:
/RECOVER
RECOVER DATABASE USING BACKUP CONTROLFILE
With
RECOVER DATABASE USING BACKUP CONTROLFILE until cancel
For editing the line do the following
Go to end of the line and append as follows
$
a
until cancel
Now your modified command looks like
RECOVER DATABASE USING BACKUP CONTROLFILE until cancel
Now save the file as /tmp/rename.sql using the following command:
:w /oracle/<Source_SID>/rename.sql
3.6
Copy back the pre-staged files from the staging Directory /usr/sap/put_refresh
sudo su
cd /oracle/<T_SID>
rm fr 102_64
cd /oracle/<T_SID{Note: To check the tar file structure tar- tvf
<filename>.tar}
tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/102_64.tar
cd /oracle/<T_SID>
tar -xvf /usr/sap/put_refresh/oracle/<T_SID>/dotastrik.tar
cd /sapmnt/<T_SID>
tar -xvf /usr/sap/put_refresh/sapmnt/<T_SID>/profile.tar
cd /usr/sap/<T_SID>/DVEBMGSxx
tar -xvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar
cd /oracle
tar -xvf /usr/sap/put_refresh/oracle/client.tar
tar -xvf /usr/sap/put_refresh/oracle/oraInventory.tar
Page 22 of 63
3.7
sudo su
Remove exe Directory from the Instance Directories. This will be recreated with
the J2EE
Install.
cd /usr/sap/<SID>/SCSxx
rm fr exe
cd /usr/sap/<SID>/DVEBMGSxx
rm fr exe
cd /usr/sap/<SID>/SYS/exe/
rm fr run
mkdir run
Page 23 of 63
3.8
Page 24 of 63
3.9
sqlplus / as sysdba
create pfile from spfile;
shutdown immediate;
Using vi add the following entry
"remote_login_passwordfile = exclusive"
Create the Oracle password file:
$ORACLE_HOME/bin/orapwd file=$ORACLE_HOME/dbs/orapw<SID>
password=<system password> entries=100
(Use password for system)
Logon to UNIX level as ora<sid>
sqlplus / as sysdba
create spfile from pfile;
startup
4
4.1
Page 25 of 63
sqlplus /nolog
connect / as sysdba
startup
Note:- when sqlplus /nolog is executed we get the error connected to an idle
instance. This means the database is not connected. So at that time we need to
start the database using startup command. Enter the following command to
delete the database objects of the database schema:
4.6
4.7
Page 26 of 63
Page 27 of 63
su <sid>adm
more <SID>.saplicense
saplicense install
su <sid>adm
cdpro
vi <sid>_DVEBMGS<no>_<host>
find parameter rdisp/wp_no_btc
comment out # rdisp/wp_no_btc
append
rdisp/wp_no_btc = 0
To make background process = 0
cd /sapmnt/<Target_SID>/global
rm fr *JOBLG*
rm fr *SLOGJ*
rm -fr WF_LOG*
5.4 STARTSAP
startsap
Logon to your sap
We see the default client of <Target System> which is configured in instance
profile
Remove the <target system> default client number and type <source system >
default client number.
Provide the logon information of <Source System>
5.5
Page 28 of 63
5.6
Delete Jobs
** WARNING: MAKE SURE YOU ARE IN TARGET SYSTEM/CLIENT **
Execute transaction SM37
Delete all released jobs from the system
5.7
su <sid>adm
cdpro
5.8
Re-initialize Jobs
After the database restore has successfully completed, the import jobs used by
the tp command may not work properly. Proceed as follows:
Logon to SAP in client 000 as DDIC and run transaction SE38
Execute program RDDNEWPP
Select Normal
A message will show up in the status bar which indicates the job has been
scheduled.
5.10
Page 29 of 63
5.12
Check the system logs to see if there were any unusual error messages
generated while the SAP system was started back up. Proceed as follows:
Execute transaction SM21
Select menu items System logs -> Choose -> All remote system logs.
Set the from date/time fields to the date and time just prior to starting the
SAP system.
Select the All messages radio button.
Click the Reread system log button.
Review the system messages. Take action on any messages that may look
suspicious.
5.13
Page 30 of 63
Re-execute transaction SMLG once again and validate the logon group
configuration.
5.14
5.15
5.16
5.17
Page 31 of 63
5.18
5.19
5.20
5.22
Page 32 of 63
components in the respective clients. Example, if the logical system client says
110, BDLS should be executed in client 110 for each logical system connected to
the system. This rule applies currently to ECC and SRM where there are multiple
clients.
Note: Check the logs in SLG1 for possible errors.
BW Systems:
Execute RSBKDTP_BDLS via SE38 for each source system in RSA1.
Old Logical System Name: (ex. P11CLNT500, P31CLNT500, etc)
New Logical System Name (ex. Q11CLNT500, Q31CLNT500, etc)
Verify and Redefine the logical systems as per the screenshot during pre-refresh.
5.24
5.26
5.27
Republish Services
Run Transaction SE38
Enter Program name W3_PUBLISH_SERVICES.
Execute and follow the screens to republish the services.
Run transaction SICF
Select the necessary services one at a time
Deactivate the Services
Activate the Services.
Page 33 of 63
Make sure that the SAP GUI service was enabled and working.
5.28
5.29
5.30
5.31
5.32
5.33
Page 34 of 63
5.34
5.35
Client Definition
Run Transaction SCC4
Change the client description to reflect as per pre-refresh description.
5.36
5.37
qRFC Monitor
Run transaction SMQR & SMQS
Delete old monitor and setup new monitor with correct system name. .
(Registration Table-> Reorganise)
SMQ1, SMQ2 deleted the old queues and any old error entries .
SLD Specific
5.38 Maintain SLD connection parameters
Run transaction SLDAPICUST
Change the connection parameters pointing to correct SLD source.
To change switch to editing mode and choose Insert Row. Specify the connection
parameters (host name, port, user, and password) and set this SLD server as
Primary. Only the entry marked as Primary is active.
Save your entries.
Configure the SLD Data Supplier Service in the Visual Administrator
Logon as j2ee_admin/administrator in Visual Admin.
Change and verify the connection parameters for SLD connection and CIM client
generation settings in SLD Data supplier service.
Verify by triggering the SLD data load.
Maintain the SLD connection in ABAP systems
Run transaction RZ70
Maintain SLD bridge host and gateway.
Validate SLD Connection/configuration
Run transaction SLDCHECK
Validate the all the checks are successful.
Page 35 of 63
5.40
Page 36 of 63
follow-up screen
Check the log file to validate that this command is completed successfully.
Logon to Satellite Client
Run T-Code: WE20
Validate that under LS, a Partner Profile for SA2CLNT100 is now defined and also
SU01 has lesser number of available options.
Important:
6.1
Page 37 of 63
Software Units
None
None
CRM-APP
JCRM
PI
6.2
Page 38 of 63
SCM
SAPCD Selection
DVD/CD Name Package Selection
/sapcd/sap/install/unicode/nw04sr1/hpux
/ia64/java_osind/DVD_NW_04_SR1_ SAP_Web_AS_JAVA/J2EE_OSINDEP
JAVA DVD
Export
/sapcd/sap/install/unicode/nw04sr1/hpux/ia64/export
6.3
Java Patches on CI
Before applying JAVA Patches we need to Update SDM (Software Deployment Manager) and
JSPM (JAVA Support Patch Manager) to the Patch level we going to apply.
E.g.: Applying JAVA SP11 on Q12 system.
Page 39 of 63
While updating it asks for SDM installation directory. Give the installation directory as
/usr/sap/<SID>/DVEBMGS<xx>/SDM/program
After the SDM update is successful again go to
cd ../program
./sdm.sh jstartup mode=integrated
./StartServer.sh
./RemoteGui.sh
No NWDI control
Click Next
Click Next
Check Queue and Deploy Queue to apply
If there is error while applying support package using JSPM, we need to identify the package
which got error.
Page 40 of 63
6.3.5 For Target systems (Eg: SRM, SCM) which have J2EE 640
(Oracle 9i) install on Oracle 10.2 Database
Review the Oracle Upgrade document and update the location of classes12.jar file under J2EE
Specific entries from Post Steps.
Page 41 of 63
7.
7.1
XI Specific Steps
7.1.2
7.1.3
7.1.5
Refresh XI Cache
Run transaction SXI_CACHE.
Select Goto
Select Adapter Engine Cache
Select line item under Adapter Engine Connection Data Cache section
Delete
7.1.6
Page 42 of 63
systems with the same syntax for file names and paths from pre-refresh
screenshot.
Check assignment of syntax group to operating system as per the
screenshot.
Go to SXMB_ADM Schedule Archiving Job Archive Administration
Make sure the object is BC_XMB Click on Customizing. Go to CrossArchiving Object Customizing Technical Settings Configure as per
pre-refresh screenshot
Go to Archiving Object Specific Customizing Technical settings.
Configure as per pre-refresh screenshot. Make sure the Delete Jobs is set
to Start Automatically and a logical File Name.
/* Go to SXMB_ADM Define Interfaces for Archiving and Retention
Periods Select the interfaces for Archiving using the Multiple selection
button and click on Flag interface for Archiving. */
Note: The following database tables are key tables in archiving and
Deletion process:
SXMSPMAST & SXMSPHIST
Go to SXMB_ADM as DDIC Schedule Archiving Job assign the Start
Date, Period & Spool Parameter data as per the pre-refresh screenshot.
Activate Archive infostructure,
Go to SXMB_ADM Schedule archiving jobs Archive Management
Information System Customizing Choose Archive Infostructure for
object SAP_BC_XMB Activate.
Page 43 of 63
Page 44 of 63
Page 45 of 63
7.2.3
7.2.4
7.2.5
RSA1 Check
In RSA1 perform source system check by right click the source system
check
Recommended
Perform simple master data load from source to target to confirm the extraction
to be okay.
In RSA1 InfoSources select some Master data attribute. For example
(0VENDOR_ATTR or 0BUSSYS or 0COMPCODE etc) select the the infopackage
and trigger the load.
Verify the successful completion of the load in transaction RSMON.
This helps in rectifying any ALE specific issues if still existing.
7.2.6
Page 46 of 63
7.2.7
Configure UDC
Logon to available WTS
Run ProgramsReflection and open X-term to UNIX server where you are installing
J2EE.
Check X-Windows
xclock
This will display Clock Window; then you can proceed, otherwise you need to export
DISPLAY.
Telnet to BI Central instance as <sid>adm.
cdD
cd j2ee
cd admin
./go (make sure an x-client is used with DISPLAY variable set up)
select the central instance server in the left pane and open it up.
select services -> JDBC Connector
In the middle pane select Driver and click on Create New Driver or
DataSource
For Driver Name enter teradata
When asked to pick a Jar file for the driver go to
/home/<sid>adm/TeraJDBC_304 and select the following 3 files:
tdgssconfig.jar, tdgssjava.jar, terajdbc4.jar
Now select Connector Container in the left pane
Open the jdbc connector container
Select SDK_JDBC and hit the Clone button
Enter the name SDK_JDBC_TD
Hit Save
Select SDK_JDBC_TD and go to the Resource Adapter tab
Click the add button and enter: library:teradata
Save
Go to tab Managed Connection Factory and then Properties
Enter the following configuration properties:
com.ncr.teradata.TeraDriver for DriverName
QTG_S for FixedSchema
???? for Password (Obtain Password Prior to refresh)
jdbc:teradata://td4.corp.pep.pvt for URL
RQ2250TD4 for UserName
Hit Save
Select SDK_JDBC_TD and hit the Clone button
Enter the name SDK_JDBC_TD_ISCP
Hit Save
Select SDK_JDBC_TD_ISCP
Go to tab Managed Connection Factory and then Properties
Enter or verify the following configuration properties:
com.ncr.teradata.TeraDriver for DriverName
QTG_S_ISCP for FixedSchema
???? for Password (Obtain Password Prior to refresh)
jdbc:teradata://td4.corp.pep.pvt for URL
RQ2250TD4 for UserName
Hit Save
Exit Visual Administrator
Page 47 of 63
7.2.8
Page 48 of 63
7.3
7.3.1
7.3.2
7.3.4
qRFC Monitor
Run transaction SMQR
SMQ1 and SMQ2 and make sure there is no data.
7.3.5
Page 49 of 63
7.3.6
liveCache Restore
run dbmgui > connect target system > make complete backup to the file
system > validate the backup file from unix
ftp the file to the source system > rename the file to the source system backup
file
dbmgui > select recovery > recovery with initialization > check and make one
more backup as above
dbmgui > menu instance > configuration > database user > validate the sap
user name sapSID
from /nLC10 > button integratin > change the user name and password of
"standard liveCache user" as sapSID
/nWE02 > check the failed iDOC
7.3.7
liveCache consistency
/n/SAPAPO/OM13
7.4
Page 50 of 63
D:\Documents and
Settings\09031393\Desktop\PEP\P1UP - TIBCO IDOC and CDM Usage Tracker.xls
7.5
Page 51 of 63
/usr/sap/<SID>/D<##>/sec.
Step 2: Then login to STRUSTSSO2, right click on System PSE and select
distribute, and all lights should go to green. Step should not be performed until
step 1 has been completed.
7.5.4 IPC Settings
Change the correct settings for IPC
Logon <sid>adm
sudo su
su ipcadm
Edit the parameters file under /usr/sap/ipc/lib/properties
vi /usr/sap/ipc/lib/properties/parameters.xml
Now serch for 500
Old Values:
<Database Alias="P51" IsBasisSystem="true" IsR3System="false"
IsServerConnection="true" ApplicationServer="prdp51.corp.pep.pvt"
SystemNo="55" DatabaseActive="true">
<Client ClientNo="500" User="IPCUSER"
Password="BEkERBEdRVkFUFVVARATMQ==
" ClientActive="true"
ClientEnabled="true">
Change the values in RED to your settings.
Smoke Test
Page 52 of 63
Select customizing.
Continue w/out specifying Project
Under Incentive and Commission Management --> BW-ICM Transfer of BW Data to ICM
Execute the Set up RFC Destinations for ICM Engine and BW System
Page 53 of 63
The ECC and BW RFC destinations should reflect the ECC & BW systems in the refreshed environment.
Page 54 of 63
Page 55 of 63
D:\Documents and
Settings\09031393\Desktop\PEP\FireFighter Installation.doc
Page 56 of 63
8.1
8.1.1
8.1.2
8.1.3
8.1.4
8.1.5
8.1.6
OS07
8.1.7
8.1.8
8.1.9
8.1.25 Tcode SICF -> execute -> default host -> sap -> bc -> gui -> sap -> its
-> webgui -> Test Service -> WebGui Logon Page
8.2
ECC Specific
8.2.2 SM59
TCP/IP Connections ->
IGS_RFC_DEST
HPOM_RFC_DESTINATION
SLD_UC
TIBCO_P11
TIB_QTG1_P11
VERTEX
Page 57 of 63
8.2.3
KGS
OAAD -> Technical Search ->
Business Object:
BUS0815
Client:
500
Archive:
-> Press Enter for the next pop-up window -> Select any of the two documents
-> Display PDF file
8.2.4
FAX
SBWP -> New Message ->
Title:
Test
Recipient:
US3128217756
Recip. Type: FAX
-> Send
SCOT -> At least 1 entry should be there under Waiting for FAXP11 queue
-> Start Send Process(CNTRL + F7)
-> The count for (In transit) followed by (Completed) should inccrease by 1.
8.2.5
ITS Check
Tcode : SITSPMON
8.3
BW Specific
8.3.1 RSA1 -> Source System -> Right Click individual system and select Check
8.3.2 Check for BI UDC
http://<SID_hostname>.corp.pep.pvt:5<SID Instance#>00/BI_UDC/servlet/GrmgServlet
Page 58 of 63
8.4
SRM Specific
8.4.4
Check encryption
Page 59 of 63
Page 60 of 63
8.5
XI Specific
8.5.1
SXMB_IFR -> On the web page select all the components to ensure proper connectivity
8.5.2
8.5.3
TIBCO SXMB_IFR
-> On the web page select (Runtime Workbench) -> Login as XISUPER ->
-> Select (Component Monitoring) -> Click on Display -> Adapter Engine prdp41
-> Adapter Monitoring -> login as XISUPER ->
-> Select the arrow on http://sap.com/xi/XI/System -> Select JMS
-> Ensure the status is Green for all the four line items under JMS section.
8.6
Page 61 of 63
APPENDIX
Steps to reset the SDM password.
Logon to the system as <sid>adm.
cd /usr/sap/<SID>/DVEBMGSxx/SDM/program
./sdm.sh jstartup sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program
mode=standalone
./sdm.sh changepassword sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program
newpassword=xxxxx
SAP Refresh Master Document
Page 62 of 63
./StopServer.sh
./sdm.sh SystemComponentState mode=Sync
./StartServer.sh
Once Dev1 Instance is up and TMS is set in the Dev1 instance then run the
following:
Reset TMS
Logon to SAP in client 000 as DDIC on the DEV Instance (TMS Domain Controller
for system, i.e. D11 or D21, D41, D51).
Run transaction STMS
Overview -> systems
CTRL F10 Distribute and Activate TMS configuration
Select Distribute configuration to all systems.
You might be prompted to LOGON to Target system, just logon to client 000 with
DDIC user/password.
mkdir p /oracle/Q41/sapdata3/temp2
sqlplus / as sysdba
create temporary tablespace psaptemp2 tempfile '/oracle/Q41/sapdata3/temp2/temp.data1'
size 100m;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP2";
drop tablespace PSAPTEMP including contents;
create temporary tablespace psaptemp tempfile '/oracle/Q41/sapdata3/temp_1/temp.data1'
size 1048584192 reuse autoextend off;
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP";
drop tablespace PSAPTEMP2 including contents;
exit;
Starting Java SDM server
Login <SID>adm
/usr/sap/<SID>/DVEBMGS<xx>/SDM/program
./StartServer.sh
Stopping Java SDM server:
Login <SID>adm
/usr/sap/<SID>/DVEBMGS<xx>/SDM/program
./StopServer.sh
Page 63 of 63