Documente Academic
Documente Profesional
Documente Cultură
Versio
n
1.0
1.1
Author
Change Description
Page 1 of 73
Page 2 of 73
XI..............................................................................................................................................2
SRM.........................................................................................................................................2
SCM.........................................................................................................................................2
1. PRE-DATABASE/SAP REFRESH...................................................................................18
1.1
Post a System Message about Scheduled Downtime..........................................................................................19
1.2
Saplicense...............................................................................................................................................................19
Logon to as <sid>adm on Source System........................................................................................................................19
Check your sap license.....................................................................................................................................................19
saplicense show..............................................................................................................................................................19
Export the saplicense information to a file under <sid>adm home directory..................................................................19
cd /home/<sidadm>..........................................................................................................................................................19
saplicense show > saplicense.SID.................................................................................................................................19
1.3 Confirm Passwords for Source/Target system with Security team........................................................................19
DDIC password in Client 000..........................................................................................................................................19
DDIC and BASIS-BATCH in default client....................................................................................................................19
1.4 Stage Instance Specific Information before Volume Group is recreated...............................................................19
Validate staging FS is available. This should return a valid FS entry..............................................................................19
bdf /usr/sap/put_refresh....................................................................................................................................................19
Copy the required directories to the staging Directory - /usr/sap/put_refresh.................................................................19
cd /usr/sap/put_refrersh...................................................................................................................................................19
mkdir -p oracle/T_SID....................................................................................................................................................19
mkdir -p usr/sap/T_SID/DVEBMSxx...............................................................................................................................19
mkdir -p sapmnt/T_SID..................................................................................................................................................19
cd /oracle/<T_SID>.......................................................................................................................................................19
tar -cvf /usr/sap/put_refresh/oracle/U11/102_64.tar 102_64....................................................................................19
{Note: To check the tar file structure tar -tvf <filename>.tar}......................................................................................19
cd /oracle/<T_SID>......................................................................................................................................................19
tar cvf /usr/sap/put_refresh/oracle/U11/dotastrik.tar .[a-z]*.................................................................................19
cd /sapmnt/<T_SID>......................................................................................................................................................19
tar -cvf /usr/sap/put_refresh/sapmnt/U11/profile.tar profile........................................................................................19
cd /usr/sap/<T_SID>/DVEBMGSxx.............................................................................................................................19
tar -cvf /usr/sap/put_refresh/usr/sap/DVEBMGSxx/igs.tar igs...................................................................................19
cd /oracle.........................................................................................................................................................................19
tar cvf /usr/sap/put_refresh/oracle/client.tar client.................................................................................................19
tar -cvf /usr/sap/put_refresh/oracle/oraInventory.tar oraInventory..........................................................................20
Team - Please add any other directories or files that you want to save off before the Volume Group is recopied with
Target Volume Group.......................................................................................................................................................20
1.5 Export User Master data...........................................................................................................................................20
Log on to source client with SAP.....................................................................................................................................20
Run Transaction SCC8...................................................................................................................................................20
start immediately.....................................................................................................................................................20
Make note of the SIDKTxxxxx transport number from the pop-up screen. The data and cofiles will be created with this
numbers............................................................................................................................................................................20
Check the appropriate export log to validate if the export was successful......................................................................20
SCC3 exports check for the current export logs..............................................................................................................20
Always, logon as <sid>adm at the OS level and validate the recent creation of cofiles & data files..............................20
cd /usr/sap/trans/cofiles..................................................................................................................................................20
ls ltr................................................................................................................................................................................20
The KTxxxxx.SID file should have been created with recent time stamp.......................................................................20
cd /usr/sap/trans/data......................................................................................................................................................20
ls ltr................................................................................................................................................................................20
The RTxxxxx.SID file should have been created with recent time stamp.......................................................................20
Page 3 of 73
1.6
Transport Printer Definitions...............................................................................................................................20
Run Transaction SPAD..................................................................................................................................................20
RFCATTRIB............................................................................................................................................................20
RFCDES..................................................................................................................................................................20
RFCDESSECU........................................................................................................................................................20
RFCDOC.................................................................................................................................................................20
Now double click on each of your RFC table entry and it will open another screen and click on Insert Row button.20
Give * as input (i.e. all the keys corresponding to that table are taken)..........................................................................20
Now save the transport request........................................................................................................................................20
Note down your request number......................................................................................................................................21
Release your request.........................................................................................................................................................21
1.8
Logical System Definitions....................................................................................................................................21
Run Transaction BD54..................................................................................................................................................21
Take a screenshot of Logical Systems Definition............................................................................................................21
1.9
Partner Profile.......................................................................................................................................................21
Run Transaction WE20..................................................................................................................................................21
Take a screenshot of Partner Profile, specifically all Partner Type Logical Systems...................................................21
1.10
IDOC Port Definitions..........................................................................................................................................21
Run Transaction WE21..................................................................................................................................................21
Drill Down on Transactional RFC, Take a screenshot of RFC Destination Port Assignment.......................................21
1.11
Client Definitions...................................................................................................................................................21
Run Transaction SCC4...................................................................................................................................................21
Take a screenshot of clients overview to note the Client Description and settings.....................................................21
1.12
Trusted Systems.....................................................................................................................................................21
Run Transaction SMT1..................................................................................................................................................21
Take a screenshot of trusted systems to note the Client Description............................................................................21
This needs to be reconfigured during post refresh activities............................................................................................21
1.13
Trust Manager Portals Certificates..................................................................................................................21
Run Transaction STRUSTSSO2.................................................................................................................................21
Check the existing public-key certificate of Portal Servers in component system's certificate list. This needs to be
reconfigured during post refresh activities.......................................................................................................................21
1.14
Integration Engine Configuration........................................................................................................................21
Run transaction SXMB_ADM......................................................................................................................................21
Double Click on Integration engine configuration...........................................................................................................21
Take screenshot of configuration data..............................................................................................................................21
1.15
Maintain SLD Access data....................................................................................................................................21
Run transaction SLDAPICUST...................................................................................................................................21
Take a snapshot or make note of the entries.....................................................................................................................21
1.16
SLD Bridge Info ABAP/JAVA...........................................................................................................................22
1.16.1 ABAP....................................................................................................................................................................22
Run Transaction RZ70...................................................................................................................................................22
Take screenshot or note the SLD Bridge Host and Service Info......................................................................................22
1.16.2 Java......................................................................................................................................................................22
Logon to Visual Admin....................................................................................................................................................22
Go to services Select SLD Data Supplier Note SLD Data Collection Settings.....................................................22
Note CIM Client Generation Settings..............................................................................................................................22
1.17
Port Maintenance IDOC Adapters......................................................................................................................22
Run transaction IDX1....................................................................................................................................................22
Note all the ports and corresponding RFC destinations or take a screenshot of the same...............................................22
This needs to be reconfigured during post refresh...........................................................................................................22
Page 4 of 73
1.18
IDOC Adapter Metadata Overview.....................................................................................................................22
Run transaction IDX2....................................................................................................................................................22
Note all the ports and corresponding RFC destinations or take a screenshot of the same...............................................22
This needs to be reconfigured during post refresh...........................................................................................................22
1.19
Distribution Model View.......................................................................................................................................22
Run transaction BD64....................................................................................................................................................22
Take a snapshot or make note of the entries.....................................................................................................................22
1.20
Maintain CRM RFC Parameter..........................................................................................................................22
This entry is maintained in table CRMRFCPAR in all sender/receiver systems (R3/BW etc)......................................22
Verify the entries take a screenshot..................................................................................................................................22
1.21
Validate HP OMS entry in SPAD.........................................................................................................................22
Use transaction SPAD....................................................................................................................................................22
Click on Display......................................................................................................................................................23
Page 5 of 73
DATABASE BACKUP....................................................................................................31
2.1
2.2
3.
Page 6 of 73
Page 7 of 73
rm fr /usr/sap/<SAPSID>/DVEBMGS<xx>/SDM.........................................................................................................38
rm fr /usr/sap/<SAPSID>/DVEBMGS<xx>/j2ee..........................................................................................................38
rm fr /usr/sap/<SAPSID>/SCS<xx>..............................................................................................................................38
rm fr /sapmnt/<SAPSID>/exeU (If it exists.).................................................................................................................38
Note: - The directory exeU is only present in versions below 640..................................................................................38
4.3 Delete the following directories on each of the application server......................................................................38
/usr/sap/<SAPSID>/D<xx>/j2ee.....................................................................................................................................38
4.4 Delete the JAVA profile...........................................................................................................................................38
cdpro.................................................................................................................................................................................38
rm -f /sapmnt/<SAPSID>/profile/<SID>_SCSxx_hostname..........................................................................................38
rm - f /sapmnt/<SAPSID>/profile/START_SCSxx_hostname..........................................................................................38
4.5 Drop your j2ee schema............................................................................................................................................38
Log on as user ora<Target_sid>......................................................................................................................................38
Start sqlplus and connect to the database.........................................................................................................................38
sqlplus /nolog...................................................................................................................................................................38
connect / as sysdba...........................................................................................................................................................38
startup...............................................................................................................................................................................38
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:........................................................................................................38
drop user SAP<Source_System_SID>DB cascade;........................................................................................................38
Enter the following command to get the name of schema of the associated data files in the system.........................38
select file_name from dba_data_files where tablespace_name = 'PSAP<Source_System_SID>DB';...........................38
4.6 Now drop the table spaces as they are empty....................................................................................................39
Enter the following command to delete the tablespace of the database schema:.............................................................39
drop tablespace PSAP<Source_System_SID>DB including contents;...........................................................................39
Exit sqlplus:......................................................................................................................................................................39
shutdown immediate.........................................................................................................................................................39
exit....................................................................................................................................................................................39
4.7 Delete the data files of tablespace PSAP<Source_SID>DB from the system...................................................39
rm rf /oracle/<Source_SID>/sapdata4/<Source_SID>db_1........................................................................................39
Now your java instance is completely deleted..............................................................................................................39
5.1 Install sap license........................................................................................................................................................40
Logon as <sid>adm..........................................................................................................................................................40
su <sid>adm..................................................................................................................................................................40
Browse to the directory where the license backup file is kept.........................................................................................40
more <SID>.saplicense...................................................................................................................................................40
saplicense install............................................................................................................................................................40
5.2 Set Background Process as Zero...............................................................................................................................40
Logon as <sid>adm..........................................................................................................................................................40
su <sid>adm..................................................................................................................................................................40
cdpro.................................................................................................................................................................................40
Edit SAP Instance Profile.................................................................................................................................................40
vi <sid>_DVEBMGS<no>_<host>..................................................................................................................................40
find parameter rdisp/wp_no_btc......................................................................................................................................40
comment out # rdisp/wp_no_btc.....................................................................................................................................40
append..............................................................................................................................................................................40
rdisp/wp_no_btc = 0........................................................................................................................................................40
To make background process = 0.....................................................................................................................................40
5.3 Cleanup /sapmnt/SID/global......................................................................................................................................40
Before starting SAP remove the JOBLOG & SLOG files in the /sapmnt/SID/global/ directory on the target system.. .40
cd /sapmnt/<Target_SID>/global...................................................................................................................................40
rm fr *JOBLG*...............................................................................................................................................................40
rm fr *SLOGJ*...............................................................................................................................................................40
rm -fr WF_LOG*..............................................................................................................................................................40
5.4 STARTSAP..................................................................................................................................................................40
startsap..............................................................................................................................................................................40
Logon to your sap.............................................................................................................................................................40
We see the default client of <Target System> which is configured in instance profile...................................................40
Remove the <target system> default client number and type <source system > default client number..........................40
Page 8 of 73
Page 9 of 73
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:...........................................................................................................................................42
Execute transaction SM21.............................................................................................................................................42
Select menu items System logs -> Choose -> All remote system logs............................................................................42
Set the from date/time fields to the date and time just prior to starting the SAP system.................................................42
Select the All messages radio button................................................................................................................................42
Click the Reread system log button..................................................................................................................................42
Review the system messages. Take action on any messages that may look suspicious..................................................42
5.13 Fix Logon Group Names.........................................................................................................................................43
Run transaction SMLG...................................................................................................................................................43
Add the newly added systems to existing LOGON groups.............................................................................................43
Highlight the New Hostname Entries...............................................................................................................................43
Click the Assign Group button and assign the Logon groups respectively......................................................................43
Highlight the Old Hostname Entries................................................................................................................................43
Click the Delete button.....................................................................................................................................................43
Save..................................................................................................................................................................................43
Note: Do not delete the groups instead of that delete only instances assigned. If you delete..........................................43
the groups both the groups and instances will be deleted................................................................................................43
Re-execute transaction SMLG once again and validate the logon group configuration................................................43
5.14 Fix Server Group Names.........................................................................................................................................43
Run transaction SM61...................................................................................................................................................43
Click pencil for change mode, click cleanup list.............................................................................................................43
Select Job-ServerGruppen................................................................................................................................................43
Click Create Group...........................................................................................................................................................43
Type GENERAL, click continue......................................................................................................................................43
Expand All Groups folder................................................................................................................................................43
Highlight GENERAL, click on + assignment..................................................................................................................43
Drop down instance name box, select only application servers.......................................................................................43
Do this for each application server available, but if no app servers are configured for the instance, use the CI............43
Once all the new entries are added. Delete the Source System Entries...........................................................................43
5.15 Import User Master Data........................................................................................................................................43
Importing the previously exported Users from the Pre-Client Copy Steps......................................................................43
Run T-Code: STMS........................................................................................................................................................43
Click on the transport button (Truck)...............................................................................................................................43
Double click on the System name....................................................................................................................................43
On the toolbar, goto ExtrasOtherAddAdd the transport request number.............................................................43
Click on the transport button (Half Truck) after selecting the added request..................................................................43
Provide target Client number and continue......................................................................................................................43
5.16 Post user master import..........................................................................................................................................43
Login into your target client.............................................................................................................................................43
Run Transaction SCC7...................................................................................................................................................43
From Menu options choose start immediately.................................................................................................................43
SCC3 check your logs......................................................................................................................................................43
5.17 Import Printer, RFC Definitions............................................................................................................................44
Run Transaction SPAD..................................................................................................................................................44
Select menu items utilities for output devices delete all........................................................................................44
Run Transaction STMS..................................................................................................................................................44
Select menu items overview imports double click on target system.................................................................44
Select your request. Import request give client no ok........................................................................................44
Click refresh until your truck symbol is lost and the transport is successful...................................................................44
Repeat this transaction for all the transports....................................................................................................................44
Run transaction SPAD...................................................................................................................................................44
Select menu items utilities for output devices assign server.............................................................................44
Run transaction SM59...................................................................................................................................................44
Validate RFC definitions..................................................................................................................................................44
5.18 Fix ITS Information................................................................................................................................................44
Run transaction SM30...................................................................................................................................................44
Edit the table TWPURLSVR by selecting the change option..........................................................................................44
Change the hostname reflecting the new hostname.........................................................................................................44
Page 10 of 73
Save..................................................................................................................................................................................44
5.19 Delete Local CUA/Detach a Satellite Client..........................................................................................................44
Delete the target hostname and system number under SM1 trusted connection entry.....................................................44
Run transaction SE38....................................................................................................................................................44
Execute the report RSDELCUA......................................................................................................................................44
Select Child System -> <SID>CLNT500 and unselect Test -> execute..........................................................................44
Use the Green back arrow to go to the previous screen...................................................................................................44
Re-execute the last step to invalidate the CUA contents..................................................................................................44
5.20 Update HP OMS entry in SPAD.............................................................................................................................44
Use transaction SPAD....................................................................................................................................................44
Select Full Administration button....................................................................................................................................44
Go to Output Management Systems tab...........................................................................................................................44
Check Real Output Management Systems by clicking on Display..................................................................................44
Select change and update HP-DAZEL with the new OMS Configuration info...............................................................44
For QA2, set it to: -N -DDAZELNS=DAZEL:hpomdev.d,qa1oms1[4008]................................................................44
For UA1, set it to: -N -DDAZELNS=DAZEL:hpompre.d,preoms1[4007]................................................................44
Save..................................................................................................................................................................................44
5.21 Disconnect from previously connected P21............................................................................................................44
(For all systems that are source systems of BW: ECC, SRM, CRM)..............................................................................44
Run Transaction SE37...................................................................................................................................................44
Enter RSAP_BIW_DISCONNECT.................................................................................................................................44
Hit Test/Execute (F8).......................................................................................................................................................44
Enter data into the following fields:.................................................................................................................................45
I_BIW_LOGSYS: P21CLNT500...................................................................................................................................45
I_OLTP_LOGSYS: <Logical system for your Production System>...............................................................................45
I_FORCE_DELETE: X....................................................................................................................................................45
Hit execute (F8)................................................................................................................................................................45
5.22 Converting Logical Systems....................................................................................................................................45
Run transaction BDLS....................................................................................................................................................45
Enter Old logical system name in the Old logical system name field..............................................................................45
Enter New logical system name in the new Logical system Name field.........................................................................45
Select Conversion of Client-Dependent and Client-Independent tables..........................................................................45
Uncheck Test Run............................................................................................................................................................45
Uncheck Existence of New Names in Tables...................................................................................................................45
Execute.............................................................................................................................................................................45
Press Return again, if any warnings are encountered.......................................................................................................45
Rerun this transaction for all the Target Logical System entries......................................................................................45
Note: BDLS should be executed for each existing connection to other 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..................................................45
Note: Check the logs in SLG1 for possible errors..........................................................................................................45
BW Systems:...................................................................................................................................................................45
5.23 Logical System Names..............................................................................................................................................45
Run Transaction BD54..................................................................................................................................................45
Verify and Redefine the logical systems as per the screenshot during pre-refresh..........................................................45
5.24 IDOC Port Definitions.............................................................................................................................................45
Run Transaction WE21..................................................................................................................................................45
Adjust the port assignment / RFC Destinations as per the pre-refresh screenshot..........................................................45
Note: During port creation, use the system provided port numbers.................................................................................45
Remove any ports that were pointing to production........................................................................................................45
5.25 Partner Profile...........................................................................................................................................................45
Create and adjust the Logical System/RFC Destinations as per the pre-refresh screenshot............................................45
Activate the partner profiles if set to I set it to A........................................................................................................45
If a particular message type is not associated with the IDOC type, maintain the association.........................................45
in WE82 transaction.........................................................................................................................................................45
5.26 Create Trusted System............................................................................................................................................46
Run Transaction SMT1..................................................................................................................................................46
Reconfigure the trusted systems as per the pre-refresh screenshot/description...............................................................46
Delete the entries reflecting Source System entries.........................................................................................................46
Page 11 of 73
To create the Trusted systems you need to have access to the remote systems with proper authorization in the case of
QA2 it was SA2 and SM1. SM1 system will be created by Kevin Flattery.....................................................................46
5.27 Republish Services...................................................................................................................................................46
Run Transaction SE38...................................................................................................................................................46
Enter Program name W3_PUBLISH_SERVICES...........................................................................................................46
Execute and follow the screens to republish the services................................................................................................46
Run transaction SICF.......................................................................................................................................................46
Select the necessary services one at a time......................................................................................................................46
Deactivate the Services....................................................................................................................................................46
Activate the Services........................................................................................................................................................46
Make sure that the SAP GUI service was enabled and working......................................................................................46
5.28 Trust Manager Portals Certificates.....................................................................................................................46
Delete existing certificates and import portal certificates corresponding to target system..............................................46
Run Transaction STRUSTSSO2.................................................................................................................................46
Check the existing public-key certificate of Portal Servers in component system's certificate list.................................46
Delete the Certificates......................................................................................................................................................46
Reconfigure/Import the appropriate certificates in component system as during pre-refresh.........................................46
Portals Certificates will be imported by Portal administrators........................................................................................46
5.29 Integration Engine Configuration..........................................................................................................................46
Run transaction SXMB_ADM......................................................................................................................................46
Double Click on Integration engine configuration...........................................................................................................46
Reconfigure integration engine data as per the pre-refresh screenshot............................................................................46
5.30 Port Maintenance IDOC Adapters.........................................................................................................................46
Run transaction IDX1....................................................................................................................................................46
Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot............................................46
5.31 IDOC Adapter Metadata Overview.......................................................................................................................47
Run transaction IDX2....................................................................................................................................................47
Configure all the ports and corresponding RFC destinations as per pre-refresh screenshot............................................47
5.32 Verify Distribution Model View..............................................................................................................................47
Run transaction BD64 and check pertinent model views..............................................................................................47
Verify the same pre-refresh distribution model views existing after request import.......................................................47
5.33 Delete Workload Analysis Logs for Old Server....................................................................................................47
Run Transaction ST03...................................................................................................................................................47
Change your user mode to Expert Mode..........................................................................................................................47
Collector and Performance DB Performance Database Monitoring Database contents...................................47
Double click on contents..................................................................................................................................................47
In the Host Column select the old host name Delete Server Confirm Delete........................................................47
To make the changes effective save it after deleting the server. To view the changes go to the first screen and come
back after saving the changes...........................................................................................................................................47
5.34 Reset the passwords for the following users..........................................................................................................47
Run transaction SU01....................................................................................................................................................47
Reset the password for the following users from the default client. These users will be recreated during the JAVA
Install................................................................................................................................................................................47
J2EE_ADMIN..................................................................................................................................................................47
J2EE_GUEST...................................................................................................................................................................47
SAPJSF.............................................................................................................................................................................47
XI* (Only on XI systems)................................................................................................................................................47
LD* ( Only on XI systems)..............................................................................................................................................47
5.35 Client Definition.......................................................................................................................................................47
Run Transaction SCC4...................................................................................................................................................47
Change the client description to reflect as per pre-refresh description............................................................................47
5.36 Maintain DBA Planning Calendar.........................................................................................................................47
Run transaction DB13 as BASIS-BATCH....................................................................................................................47
Setup DBA jobs as per the pre-refresh screenshot...........................................................................................................47
5.37 qRFC Monitor..........................................................................................................................................................47
Run transaction SMQR & SMQS..................................................................................................................................47
Delete old monitor and setup new monitor with correct system name. .(Registration Table-> Reorganise)...................47
SMQ1, SMQ2 deleted the old queues and any old error entries .....................................................................................47
SLD Specific........................................................................................................................................................................48
Page 12 of 73
5.38
Maintain SLD connection parameters............................................................................................................48
Run transaction SLDAPICUST...................................................................................................................................48
Change the connection parameters pointing to correct SLD source................................................................................48
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....................................48
Save your entries..............................................................................................................................................................48
Configure the SLD Data Supplier Service in the Visual Administrator.......................................................................48
Logon as j2ee_admin/administrator in Visual Admin......................................................................................................48
Change and verify the connection parameters for SLD connection and CIM client generation settings in SLD Data
supplier service.................................................................................................................................................................48
Verify by triggering the SLD data load............................................................................................................................48
Maintain the SLD connection in ABAP systems............................................................................................................48
Run transaction RZ70....................................................................................................................................................48
Maintain SLD bridge host and gateway...........................................................................................................................48
Validate SLD Connection/configuration..........................................................................................................................48
Run transaction SLDCHECK........................................................................................................................................48
Validate the all the checks are successful.........................................................................................................................48
5.39 Schedule XML Messages Delete Jobs......................................................................................................................48
Run Transaction SXMB_ADM as user DDIC............................................................................................................48
Go to SXMB_ADM Define Interfaces for Archiving and Retention Periods Retention periods.......................48
Retention Periods for Asynchronous messages in the Database:.....................................................................................48
XML Messages without Errors Awaiting Deletion:
30 Days.....................................................................................48
XML Messages without Errors Awaiting Archiving:
7 Days.....................................................................................48
Retention periods for Synchronous messages in the Database:.......................................................................................48
XML Messages with Errors Awaiting Deletion:
7 Days.............................................................................................48
XML Messages without Errors Awaiting Deletion:
0 Days.......................................................................................48
Retention periods for History entries in the Database:....................................................................................................48
History Entries for Deleted XML Messages:
35 Days...............................................................................................48
Run Transaction SXMB_ADM as user DDIC.................................................................................................................48
Schedule Delete Jobs........................................................................................................................................................48
Check the settings and reconfigure as per the screenshot taken......................................................................................48
Verify Parameters: Period of Days set to 1......................................................................................................................48
Click on Job Overview (SM37) and verify the below jobs scheduled as pre-refresh......................................................48
SAP_BC_XMB_DELETE_<client>................................................................................................................................48
SAP_BC_XMB_HIST_DELETE_<client>.....................................................................................................................48
5.40 Attach a Satellite Client to CUA.............................................................................................................................49
Logon to Satellite Client................................................................................................................................................49
Run T-Code: SM59........................................................................................................................................................49
Validate entry for an ABAP system - SA2_SYSTEM.....................................................................................................49
Validate entry for an ABAP system - SA2CLNT100.......................................................................................................49
Run T-Code: BD54........................................................................................................................................................49
Select New Entry..............................................................................................................................................................49
Define a new Logical System for CUA, e.g., SA2CLNT100..........................................................................................49
Provide a description under Name...................................................................................................................................49
Save..................................................................................................................................................................................49
Create a new transport or use an existing transport.........................................................................................................49
Run T-Code: SMT1........................................................................................................................................................49
Select Create Button.........................................................................................................................................................49
SA2CLNT100 in Destination field..................................................................................................................................49
Login to CUA System.....................................................................................................................................................49
Run T-Code: SM59........................................................................................................................................................49
Validate ebtry for the ABAP system Q42CLNT500.....................................................................................................49
Run T-Code: BD54........................................................................................................................................................49
Validate Logical System entry for Satellite System, e.g., Q42CLNT500........................................................................49
Create a new transport or use an existing transport.........................................................................................................49
Run T-Code: SCUA........................................................................................................................................................49
Enter the Satellite Instance Name, e.g., S11CLNT005 at the bottom of the list..............................................................49
Select SAVE.....................................................................................................................................................................49
You will have to enter DDIC user-id and password for the satellite system on the follow-up screen.............................49
Page 13 of 73
Check the log file to validate that this command is completed successfully...................................................................49
Logon to Satellite Client................................................................................................................................................49
Run T-Code: WE20..........................................................................................................................................................49
Validate that under LS, a Partner Profile for SA2CLNT100 is now defined and also SU01 has lesser number of
available options...............................................................................................................................................................49
7.
Page 14 of 73
8.
Page 15 of 73
8.6.3
8.6.4
8.6.5
8.6.6
APPENDIX............................................................................................................................75
Steps to reset the SDM password......................................................................................................................................75
Logon to the system as <sid>adm....................................................................................................................................75
cd /usr/sap/<SID>/DVEBMGSxx/SDM/program............................................................................................................75
./sdm.sh jstartup sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program mode=standalone.................................75
./sdm.sh changepassword sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program newpassword=xxxxx.................75
./sdm.sh jstartup sdmhome=/usr/sap/<SID>/DVEBMGSxx/SDM/program mode=integrated..................................75
Steps to synchronize SDM Server.....................................................................................................................................75
if required if your java patches doesnt reflect in the system info after applying them with JSPM................................75
Go to /usr/sap/DC2/DVEBMGS37/SDM/program..........................................................................................................75
./StopServer.sh..................................................................................................................................................................75
./sdm.sh SystemComponentState mode=Sync..............................................................................................................75
./StartServer.sh.................................................................................................................................................................75
Once Dev1 Instance is up and TMS is set in the Dev1 instance then run the following:................................................75
Reset TMS........................................................................................................................................................................75
Logon to SAP in client 000 as DDIC on the DEV Instance (TMS Domain Controller for system, i.e. D11 or D21, D41,
D51)..................................................................................................................................................................................75
Run transaction STMS.....................................................................................................................................................75
Overview -> systems........................................................................................................................................................75
CTRL F10 Distribute and Activate TMS configuration................................................................................................75
Select Distribute configuration to all systems..................................................................................................................75
You might be prompted to LOGON to Target system, just logon to client 000 with DDIC user/password....................75
To recreate PSAPTEMP table space.................................................................................................................................75
Logon to UNIX level as ora<sid>....................................................................................................................................75
mkdir p /oracle/Q41/sapdata3/temp2.............................................................................................................................75
sqlplus / as sysdba........................................................................................................................................................75
create temporary tablespace psaptemp2 tempfile '/oracle/Q41/sapdata3/temp2/temp.data1' size 100m;......................75
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP2";.............................................................75
drop tablespace PSAPTEMP including contents;............................................................................................................75
create temporary tablespace psaptemp tempfile '/oracle/Q41/sapdata3/temp_1/temp.data1' size 1048584192 reuse
autoextend off;..................................................................................................................................................................75
ALTER DATABASE DEFAULT TEMPORARY TABLESPACE "PSAPTEMP";...............................................................75
drop tablespace PSAPTEMP2 including contents;..........................................................................................................75
exit;...................................................................................................................................................................................75
Starting Java SDM server..................................................................................................................................................76
Stopping Java SDM server:...............................................................................................................................................76
Page 16 of 73
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 17 of 73
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 18 of 73
The RTxxxxx.SID file should have been created with recent time stamp.
1.10
1.11
Client Definitions
Run Transaction SCC4.
Take a screenshot of clients overview to note the Client Description and
settings.
Page 19 of 73
1.12
Trusted Systems
Run Transaction SMT1.
Take a screenshot of trusted systems to note the Client Description.
This needs to be reconfigured during post refresh activities.
1.13
1.14
1.15
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
1.17
1.18
Page 20 of 73
1.19
1.20
1.21
1.22
1.23
1.24
1.25
Page 21 of 73
XI Specific Steps
1.26
1.26.1
Page 22 of 73
Page 23 of 73
Page 24 of 73
BI Specific Steps
1.27
1.27.2
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 25 of 73
1.28
1.28.1
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 26 of 73
Page 27 of 73
Page 28 of 73
Database Backup
Page 29 of 73
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 30 of 73
3.3
su ora<s-sid>
sqlplus / as sysdba
startup;
exit
3.4
Page 31 of 73
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 32 of 73
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 33 of 73
3.8
Note:- here it will ask us for CANCEL option at the end of command execution.
Say CANCEL
Page 34 of 73
This should give the return code of (0000) for successful logon to database.
If it was not able to connect /logon to database it will throw a return code 0008.
3.9
sqlplus / as sysdba
create pfile from spfile;
shutdown immediate;
"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 35 of 73
rm - f /sapmnt/<SAPSID>/profile/START_SCSxx_hostname
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:
Enter the following command to get the name of schema of the associated data
files in the system
4.6
4.7
Page 36 of 73
Page 37 of 73
su <sid>adm
Browse to the directory where the license backup file is kept
more <SID>.saplicense
saplicense install
su <sid>adm
cdpro
Edit SAP Instance Profile
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 38 of 73
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.7.3
Start SAP
startsap
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 39 of 73
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 40 of 73
Re-execute transaction SMLG once again and validate the logon group
configuration.
5.14
5.15
5.16
5.17
Page 41 of 73
5.18
5.19
5.20
5.22
Page 42 of 73
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 43 of 73
Make sure that the SAP GUI service was enabled and working.
5.29
5.30
5.31
5.33
Page 44 of 73
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 45 of 73
Page 46 of 73
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 47 of 73
SAPCD
Software Units Selection (Central Instance Java Add In for ABAP)
Usage Type
ECC
BI
CRM
XI
Software Units
None
None
CRM-APP
JCRM
PI
6.2
JAVA DVD
/sapcd/sap/install/unicode/nw04sr1/hpux
/ia64/java_osind/DVD_NW_04_SR1_ SAP_Web_AS_JAVA/J2EE_OSINDEP
Page 48 of 73
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 49 of 73
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.
Login to SDM and go to Undeployment tab.
Select the error package and undeploy completely.
Now apply the Error package using SDM tool from Deployment tab.
Make sure all the packages are deployed completely from URL
http://qa2q12.corp.pep.pvt:51200
Select the system information and check for successfully applied Support packs.
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 50 of 73
Page 51 of 73
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 52 of 73
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 prerefresh 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 53 of 73
Page 54 of 73
Page 55 of 73
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 56 of 73
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 57 of 73
7.2.8
7.2.9
Page 58 of 73
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 59 of 73
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 60 of 73
D:\Documents and
Settings\09031393\Desktop\PEP\P1UP - TIBCO IDOC and CDM Usage Tracker.xls
7.5
Page 61 of 73
/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 62 of 73
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 63 of 73
The ECC and BW RFC destinations should reflect the ECC & BW systems in the refreshed environment.
Page 64 of 73
Page 65 of 73
D:\Documents and
Settings\09031393\Desktop\PEP\FireFighter Installation.doc
Page 66 of 73
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 67 of 73
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 68 of 73
8.4
SRM Specific
8.4.4
Check encryption
Page 69 of 73
Page 70 of 73
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 71 of 73
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 72 of 73
./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 73 of 73