Upload
munnalal-nagariya
View
54
Download
1
Embed Size (px)
Citation preview
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Database Refresh Procedure
1 Introduction
A Database refreshcopy consists of three sections or units of work
- Pre Copy steps
- RestoringCopying the database files
- Post Copy Steps
Note The method of copying the database files depends on if the target system has the same number and size of file systems or
greater to accommodate the source system
Below are the steps to be followed during refresh Commands shown in this document are for AIX 53 platform
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
2 Pre Copy steps
21 Verify the passwords in the source and target systems
Before you Proceed with the refresh you should have the login credentials in both Source and Target system with Enough
Authorisations ( Super user with sap_all and sap_new profiles) (both OS and SAP level)
22 Check Space in Target System
Make sure that you have enough space in the Target System equal to or more than in the Source System Check via command (on
both Source and Target Systems)
As user root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
df -k | grep sapdata | sort
Also make sure that the space in origlogA amp B and mirrlogA amp B is the same or more in the Target system as compared to the
source system If they are not the same size they must be removed from the target and the file systems are enlarged to allow them to
be built to the Source sizes Check via
As user root
df -k | grep log| sort
Additional Checks for storage inAPO LCA systemv The size of sapdbltTARGET SIDgt should be greater than or equal to sapdbltSOURCE SIDgt in the live cache host
Additional Checks for storage inAPO LCA systemv The size of sapdbltTARGET SIDgt should be greater than or equal to sapdbltSOURCE SIDgt in the live cache host
Example If source is SSID and target system is TSID (df gt)
devlvusp_ssid_002 5888 097 5790 2 sapdbSSID
devlvusp_tsid_002 7000 091 6909 2 sapdbTSID
v In both systems go to T-code LC10 -gt Live cache Monitoring -gt Administration -gt Configuration -gt Volumes
v Select Data area tab size of the Data area in Target system should be greater than that of the Data area in Source system
irrespective of the number of data volumes present
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Source system(Source SID(SSID))
Target System(Target SID(TSID))
If the size of data area is less than the source system then add data volumes
23 OpenSSH to OpenSSH trust (host based trust)
Server which will be trusted for root login (referred to as trusted server)
Open the connection between Source system and Target system Just in case you want to transfer any file during refresh You can
do so by directly using Secure copy command
In Target System
cd etcssh
cat ssh_host_dsa_keypub
(Example shown below)
ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
(NOTE The hostkey above is a single lineNOT multiple lines and must be copied over as a single line)
On Server allowing the root trust (referred to as the trusting server)(Source system)
cd etcssh
vi ssh_known_hosts
(go to the last line of the file using Shift-G in vi and open a line at the bottom using the o vi command)
(using existing lines as a reference enter the name of the trusted server along with the fully qualified DNS name followed by the
hostkey found in the previous step Below is an example of what the key would look like)
lttrusted servergtlttrusted servergtltdomain namegt ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
NOTE The hostkey above is a single lineNOT multiple lines so the generic format is as follows lttrusted servergtlttrusted
servergtltdomain namegt ssh-dss lthostkey from trusted servergt
Concatenate all the lines in the file - instead of 9 lines it should be a single long line
On the trusting server update the shosts file to allow root access
vi shosts
(include a line of the format
lttrusted servergtltdomain namegt root
By doing so now your Source server has become the Trusting server and Target system has become the trusted server
24 Verify Oracle control file directories on target server
Logon to the target system
- as oralttarget_sidgt
- cd dbs
The following command will display three directories where the controlfiles will be written
grep dbf initltTSIDgtora
According to the standards they should be in oracleltSIDgtcntrl oracleltSIDgtsapdata1cntrl and oracleltSIDgtsapdata2cntrl
- ls l oracleltTSIDgtcntrl
- ls l oracleltTSIDgtsapdata1cntrl
- ls l oracleltTSIDgtsapdata2cntrl
If not ensure that these directories are created and a copy of Control file is moved to them
25 Export Target SIDClient Users amp retain user master records
This step only applies to those projects where the user master records are to be retained in the target system
Log on to the SAP target system clients that need to have users preserved
Execute transaction SCC8
Select profile SAP_USERTarget system use DUM YOU MUST FILL THIS VALUE IN OR IT WILL NOT WORK
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click execute button click continue button and STOP AT INFO CLIENT EXPORT SCREEN
Perform the following before proceeding with SAP screen
On the Info Client Export screen STOP and document the transport number displayed with the format ltsidgtKTnnnnnnn
This step will fail if files exist in the transport directories with the same numberYou must delete all cofiles data files and log files
with the same number before starting the new export Heres an example taken to find everything related to transport su
ltsidgtadm
- cd usrsaptrans
- find data cofiles name 00017SID exec ls lastr
If any files are found verify they are the correct files and can be removed then remove them (consult if you arent sure) else rename
them with extension old
- find data cofiles log name 00017ltSIDgt exec rm
Verify that the files were successfully removed
- find data cofiles log name 00017ltSIDgt exec ls lastr
- Now return to SAP screen and click the green check mark to start the export
Remarks
- If DUMMY system is not there select any SID except the SID name you are exporting from YOU MUST FILL A SID IN
OR IT WILL NOT WORK
Note
1) Monitor the job using SCC3 logs At first the log may indicate an error in the processing Just wait about 3-5 minutes and check
again Always look to the datetime field to verify the correct logfile Also after SCC3 indicates its successful you must check that
the transport is completely exported using SE03 MAKE SURE IT COMPLETES WITH RETURN CODE lt 8
2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system
Therefore always check the file size until it reaches the saturation at operating system level
Login as sidadm user at os level
cd usrsaptrans
find data cofiles -name 00017ltSIDgt -exec ls -lastr
the file size should become constant if you again trigger the command
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
2 Pre Copy steps
21 Verify the passwords in the source and target systems
Before you Proceed with the refresh you should have the login credentials in both Source and Target system with Enough
Authorisations ( Super user with sap_all and sap_new profiles) (both OS and SAP level)
22 Check Space in Target System
Make sure that you have enough space in the Target System equal to or more than in the Source System Check via command (on
both Source and Target Systems)
As user root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
df -k | grep sapdata | sort
Also make sure that the space in origlogA amp B and mirrlogA amp B is the same or more in the Target system as compared to the
source system If they are not the same size they must be removed from the target and the file systems are enlarged to allow them to
be built to the Source sizes Check via
As user root
df -k | grep log| sort
Additional Checks for storage inAPO LCA systemv The size of sapdbltTARGET SIDgt should be greater than or equal to sapdbltSOURCE SIDgt in the live cache host
Additional Checks for storage inAPO LCA systemv The size of sapdbltTARGET SIDgt should be greater than or equal to sapdbltSOURCE SIDgt in the live cache host
Example If source is SSID and target system is TSID (df gt)
devlvusp_ssid_002 5888 097 5790 2 sapdbSSID
devlvusp_tsid_002 7000 091 6909 2 sapdbTSID
v In both systems go to T-code LC10 -gt Live cache Monitoring -gt Administration -gt Configuration -gt Volumes
v Select Data area tab size of the Data area in Target system should be greater than that of the Data area in Source system
irrespective of the number of data volumes present
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Source system(Source SID(SSID))
Target System(Target SID(TSID))
If the size of data area is less than the source system then add data volumes
23 OpenSSH to OpenSSH trust (host based trust)
Server which will be trusted for root login (referred to as trusted server)
Open the connection between Source system and Target system Just in case you want to transfer any file during refresh You can
do so by directly using Secure copy command
In Target System
cd etcssh
cat ssh_host_dsa_keypub
(Example shown below)
ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
(NOTE The hostkey above is a single lineNOT multiple lines and must be copied over as a single line)
On Server allowing the root trust (referred to as the trusting server)(Source system)
cd etcssh
vi ssh_known_hosts
(go to the last line of the file using Shift-G in vi and open a line at the bottom using the o vi command)
(using existing lines as a reference enter the name of the trusted server along with the fully qualified DNS name followed by the
hostkey found in the previous step Below is an example of what the key would look like)
lttrusted servergtlttrusted servergtltdomain namegt ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
NOTE The hostkey above is a single lineNOT multiple lines so the generic format is as follows lttrusted servergtlttrusted
servergtltdomain namegt ssh-dss lthostkey from trusted servergt
Concatenate all the lines in the file - instead of 9 lines it should be a single long line
On the trusting server update the shosts file to allow root access
vi shosts
(include a line of the format
lttrusted servergtltdomain namegt root
By doing so now your Source server has become the Trusting server and Target system has become the trusted server
24 Verify Oracle control file directories on target server
Logon to the target system
- as oralttarget_sidgt
- cd dbs
The following command will display three directories where the controlfiles will be written
grep dbf initltTSIDgtora
According to the standards they should be in oracleltSIDgtcntrl oracleltSIDgtsapdata1cntrl and oracleltSIDgtsapdata2cntrl
- ls l oracleltTSIDgtcntrl
- ls l oracleltTSIDgtsapdata1cntrl
- ls l oracleltTSIDgtsapdata2cntrl
If not ensure that these directories are created and a copy of Control file is moved to them
25 Export Target SIDClient Users amp retain user master records
This step only applies to those projects where the user master records are to be retained in the target system
Log on to the SAP target system clients that need to have users preserved
Execute transaction SCC8
Select profile SAP_USERTarget system use DUM YOU MUST FILL THIS VALUE IN OR IT WILL NOT WORK
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click execute button click continue button and STOP AT INFO CLIENT EXPORT SCREEN
Perform the following before proceeding with SAP screen
On the Info Client Export screen STOP and document the transport number displayed with the format ltsidgtKTnnnnnnn
This step will fail if files exist in the transport directories with the same numberYou must delete all cofiles data files and log files
with the same number before starting the new export Heres an example taken to find everything related to transport su
ltsidgtadm
- cd usrsaptrans
- find data cofiles name 00017SID exec ls lastr
If any files are found verify they are the correct files and can be removed then remove them (consult if you arent sure) else rename
them with extension old
- find data cofiles log name 00017ltSIDgt exec rm
Verify that the files were successfully removed
- find data cofiles log name 00017ltSIDgt exec ls lastr
- Now return to SAP screen and click the green check mark to start the export
Remarks
- If DUMMY system is not there select any SID except the SID name you are exporting from YOU MUST FILL A SID IN
OR IT WILL NOT WORK
Note
1) Monitor the job using SCC3 logs At first the log may indicate an error in the processing Just wait about 3-5 minutes and check
again Always look to the datetime field to verify the correct logfile Also after SCC3 indicates its successful you must check that
the transport is completely exported using SE03 MAKE SURE IT COMPLETES WITH RETURN CODE lt 8
2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system
Therefore always check the file size until it reaches the saturation at operating system level
Login as sidadm user at os level
cd usrsaptrans
find data cofiles -name 00017ltSIDgt -exec ls -lastr
the file size should become constant if you again trigger the command
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
df -k | grep sapdata | sort
Also make sure that the space in origlogA amp B and mirrlogA amp B is the same or more in the Target system as compared to the
source system If they are not the same size they must be removed from the target and the file systems are enlarged to allow them to
be built to the Source sizes Check via
As user root
df -k | grep log| sort
Additional Checks for storage inAPO LCA systemv The size of sapdbltTARGET SIDgt should be greater than or equal to sapdbltSOURCE SIDgt in the live cache host
Additional Checks for storage inAPO LCA systemv The size of sapdbltTARGET SIDgt should be greater than or equal to sapdbltSOURCE SIDgt in the live cache host
Example If source is SSID and target system is TSID (df gt)
devlvusp_ssid_002 5888 097 5790 2 sapdbSSID
devlvusp_tsid_002 7000 091 6909 2 sapdbTSID
v In both systems go to T-code LC10 -gt Live cache Monitoring -gt Administration -gt Configuration -gt Volumes
v Select Data area tab size of the Data area in Target system should be greater than that of the Data area in Source system
irrespective of the number of data volumes present
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Source system(Source SID(SSID))
Target System(Target SID(TSID))
If the size of data area is less than the source system then add data volumes
23 OpenSSH to OpenSSH trust (host based trust)
Server which will be trusted for root login (referred to as trusted server)
Open the connection between Source system and Target system Just in case you want to transfer any file during refresh You can
do so by directly using Secure copy command
In Target System
cd etcssh
cat ssh_host_dsa_keypub
(Example shown below)
ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
(NOTE The hostkey above is a single lineNOT multiple lines and must be copied over as a single line)
On Server allowing the root trust (referred to as the trusting server)(Source system)
cd etcssh
vi ssh_known_hosts
(go to the last line of the file using Shift-G in vi and open a line at the bottom using the o vi command)
(using existing lines as a reference enter the name of the trusted server along with the fully qualified DNS name followed by the
hostkey found in the previous step Below is an example of what the key would look like)
lttrusted servergtlttrusted servergtltdomain namegt ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
NOTE The hostkey above is a single lineNOT multiple lines so the generic format is as follows lttrusted servergtlttrusted
servergtltdomain namegt ssh-dss lthostkey from trusted servergt
Concatenate all the lines in the file - instead of 9 lines it should be a single long line
On the trusting server update the shosts file to allow root access
vi shosts
(include a line of the format
lttrusted servergtltdomain namegt root
By doing so now your Source server has become the Trusting server and Target system has become the trusted server
24 Verify Oracle control file directories on target server
Logon to the target system
- as oralttarget_sidgt
- cd dbs
The following command will display three directories where the controlfiles will be written
grep dbf initltTSIDgtora
According to the standards they should be in oracleltSIDgtcntrl oracleltSIDgtsapdata1cntrl and oracleltSIDgtsapdata2cntrl
- ls l oracleltTSIDgtcntrl
- ls l oracleltTSIDgtsapdata1cntrl
- ls l oracleltTSIDgtsapdata2cntrl
If not ensure that these directories are created and a copy of Control file is moved to them
25 Export Target SIDClient Users amp retain user master records
This step only applies to those projects where the user master records are to be retained in the target system
Log on to the SAP target system clients that need to have users preserved
Execute transaction SCC8
Select profile SAP_USERTarget system use DUM YOU MUST FILL THIS VALUE IN OR IT WILL NOT WORK
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click execute button click continue button and STOP AT INFO CLIENT EXPORT SCREEN
Perform the following before proceeding with SAP screen
On the Info Client Export screen STOP and document the transport number displayed with the format ltsidgtKTnnnnnnn
This step will fail if files exist in the transport directories with the same numberYou must delete all cofiles data files and log files
with the same number before starting the new export Heres an example taken to find everything related to transport su
ltsidgtadm
- cd usrsaptrans
- find data cofiles name 00017SID exec ls lastr
If any files are found verify they are the correct files and can be removed then remove them (consult if you arent sure) else rename
them with extension old
- find data cofiles log name 00017ltSIDgt exec rm
Verify that the files were successfully removed
- find data cofiles log name 00017ltSIDgt exec ls lastr
- Now return to SAP screen and click the green check mark to start the export
Remarks
- If DUMMY system is not there select any SID except the SID name you are exporting from YOU MUST FILL A SID IN
OR IT WILL NOT WORK
Note
1) Monitor the job using SCC3 logs At first the log may indicate an error in the processing Just wait about 3-5 minutes and check
again Always look to the datetime field to verify the correct logfile Also after SCC3 indicates its successful you must check that
the transport is completely exported using SE03 MAKE SURE IT COMPLETES WITH RETURN CODE lt 8
2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system
Therefore always check the file size until it reaches the saturation at operating system level
Login as sidadm user at os level
cd usrsaptrans
find data cofiles -name 00017ltSIDgt -exec ls -lastr
the file size should become constant if you again trigger the command
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Source system(Source SID(SSID))
Target System(Target SID(TSID))
If the size of data area is less than the source system then add data volumes
23 OpenSSH to OpenSSH trust (host based trust)
Server which will be trusted for root login (referred to as trusted server)
Open the connection between Source system and Target system Just in case you want to transfer any file during refresh You can
do so by directly using Secure copy command
In Target System
cd etcssh
cat ssh_host_dsa_keypub
(Example shown below)
ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
(NOTE The hostkey above is a single lineNOT multiple lines and must be copied over as a single line)
On Server allowing the root trust (referred to as the trusting server)(Source system)
cd etcssh
vi ssh_known_hosts
(go to the last line of the file using Shift-G in vi and open a line at the bottom using the o vi command)
(using existing lines as a reference enter the name of the trusted server along with the fully qualified DNS name followed by the
hostkey found in the previous step Below is an example of what the key would look like)
lttrusted servergtlttrusted servergtltdomain namegt ssh-dss
AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmueVE9+4t6Wd5sGRwWNAdyDtFF9uxCKcgeK8o2OPFSeCcuNi
w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6WEXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRspMw0
jsbBAAAAFQD4kBx7i53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
NOTE The hostkey above is a single lineNOT multiple lines so the generic format is as follows lttrusted servergtlttrusted
servergtltdomain namegt ssh-dss lthostkey from trusted servergt
Concatenate all the lines in the file - instead of 9 lines it should be a single long line
On the trusting server update the shosts file to allow root access
vi shosts
(include a line of the format
lttrusted servergtltdomain namegt root
By doing so now your Source server has become the Trusting server and Target system has become the trusted server
24 Verify Oracle control file directories on target server
Logon to the target system
- as oralttarget_sidgt
- cd dbs
The following command will display three directories where the controlfiles will be written
grep dbf initltTSIDgtora
According to the standards they should be in oracleltSIDgtcntrl oracleltSIDgtsapdata1cntrl and oracleltSIDgtsapdata2cntrl
- ls l oracleltTSIDgtcntrl
- ls l oracleltTSIDgtsapdata1cntrl
- ls l oracleltTSIDgtsapdata2cntrl
If not ensure that these directories are created and a copy of Control file is moved to them
25 Export Target SIDClient Users amp retain user master records
This step only applies to those projects where the user master records are to be retained in the target system
Log on to the SAP target system clients that need to have users preserved
Execute transaction SCC8
Select profile SAP_USERTarget system use DUM YOU MUST FILL THIS VALUE IN OR IT WILL NOT WORK
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click execute button click continue button and STOP AT INFO CLIENT EXPORT SCREEN
Perform the following before proceeding with SAP screen
On the Info Client Export screen STOP and document the transport number displayed with the format ltsidgtKTnnnnnnn
This step will fail if files exist in the transport directories with the same numberYou must delete all cofiles data files and log files
with the same number before starting the new export Heres an example taken to find everything related to transport su
ltsidgtadm
- cd usrsaptrans
- find data cofiles name 00017SID exec ls lastr
If any files are found verify they are the correct files and can be removed then remove them (consult if you arent sure) else rename
them with extension old
- find data cofiles log name 00017ltSIDgt exec rm
Verify that the files were successfully removed
- find data cofiles log name 00017ltSIDgt exec ls lastr
- Now return to SAP screen and click the green check mark to start the export
Remarks
- If DUMMY system is not there select any SID except the SID name you are exporting from YOU MUST FILL A SID IN
OR IT WILL NOT WORK
Note
1) Monitor the job using SCC3 logs At first the log may indicate an error in the processing Just wait about 3-5 minutes and check
again Always look to the datetime field to verify the correct logfile Also after SCC3 indicates its successful you must check that
the transport is completely exported using SE03 MAKE SURE IT COMPLETES WITH RETURN CODE lt 8
2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system
Therefore always check the file size until it reaches the saturation at operating system level
Login as sidadm user at os level
cd usrsaptrans
find data cofiles -name 00017ltSIDgt -exec ls -lastr
the file size should become constant if you again trigger the command
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
9HEFd18JPIXTLWTCjtriE6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrgP0v
WumYtGEwn16tUr9LxRwAAAIEAjf+4Eis9ippFAeNIVfKL28KlYrqlcdBHIhEwy6HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u
SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1F7zwxQ5QLyB5puKNs05qofObC4vpfC3RkOFMQ
=
NOTE The hostkey above is a single lineNOT multiple lines so the generic format is as follows lttrusted servergtlttrusted
servergtltdomain namegt ssh-dss lthostkey from trusted servergt
Concatenate all the lines in the file - instead of 9 lines it should be a single long line
On the trusting server update the shosts file to allow root access
vi shosts
(include a line of the format
lttrusted servergtltdomain namegt root
By doing so now your Source server has become the Trusting server and Target system has become the trusted server
24 Verify Oracle control file directories on target server
Logon to the target system
- as oralttarget_sidgt
- cd dbs
The following command will display three directories where the controlfiles will be written
grep dbf initltTSIDgtora
According to the standards they should be in oracleltSIDgtcntrl oracleltSIDgtsapdata1cntrl and oracleltSIDgtsapdata2cntrl
- ls l oracleltTSIDgtcntrl
- ls l oracleltTSIDgtsapdata1cntrl
- ls l oracleltTSIDgtsapdata2cntrl
If not ensure that these directories are created and a copy of Control file is moved to them
25 Export Target SIDClient Users amp retain user master records
This step only applies to those projects where the user master records are to be retained in the target system
Log on to the SAP target system clients that need to have users preserved
Execute transaction SCC8
Select profile SAP_USERTarget system use DUM YOU MUST FILL THIS VALUE IN OR IT WILL NOT WORK
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click execute button click continue button and STOP AT INFO CLIENT EXPORT SCREEN
Perform the following before proceeding with SAP screen
On the Info Client Export screen STOP and document the transport number displayed with the format ltsidgtKTnnnnnnn
This step will fail if files exist in the transport directories with the same numberYou must delete all cofiles data files and log files
with the same number before starting the new export Heres an example taken to find everything related to transport su
ltsidgtadm
- cd usrsaptrans
- find data cofiles name 00017SID exec ls lastr
If any files are found verify they are the correct files and can be removed then remove them (consult if you arent sure) else rename
them with extension old
- find data cofiles log name 00017ltSIDgt exec rm
Verify that the files were successfully removed
- find data cofiles log name 00017ltSIDgt exec ls lastr
- Now return to SAP screen and click the green check mark to start the export
Remarks
- If DUMMY system is not there select any SID except the SID name you are exporting from YOU MUST FILL A SID IN
OR IT WILL NOT WORK
Note
1) Monitor the job using SCC3 logs At first the log may indicate an error in the processing Just wait about 3-5 minutes and check
again Always look to the datetime field to verify the correct logfile Also after SCC3 indicates its successful you must check that
the transport is completely exported using SE03 MAKE SURE IT COMPLETES WITH RETURN CODE lt 8
2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system
Therefore always check the file size until it reaches the saturation at operating system level
Login as sidadm user at os level
cd usrsaptrans
find data cofiles -name 00017ltSIDgt -exec ls -lastr
the file size should become constant if you again trigger the command
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click execute button click continue button and STOP AT INFO CLIENT EXPORT SCREEN
Perform the following before proceeding with SAP screen
On the Info Client Export screen STOP and document the transport number displayed with the format ltsidgtKTnnnnnnn
This step will fail if files exist in the transport directories with the same numberYou must delete all cofiles data files and log files
with the same number before starting the new export Heres an example taken to find everything related to transport su
ltsidgtadm
- cd usrsaptrans
- find data cofiles name 00017SID exec ls lastr
If any files are found verify they are the correct files and can be removed then remove them (consult if you arent sure) else rename
them with extension old
- find data cofiles log name 00017ltSIDgt exec rm
Verify that the files were successfully removed
- find data cofiles log name 00017ltSIDgt exec ls lastr
- Now return to SAP screen and click the green check mark to start the export
Remarks
- If DUMMY system is not there select any SID except the SID name you are exporting from YOU MUST FILL A SID IN
OR IT WILL NOT WORK
Note
1) Monitor the job using SCC3 logs At first the log may indicate an error in the processing Just wait about 3-5 minutes and check
again Always look to the datetime field to verify the correct logfile Also after SCC3 indicates its successful you must check that
the transport is completely exported using SE03 MAKE SURE IT COMPLETES WITH RETURN CODE lt 8
2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system
Therefore always check the file size until it reaches the saturation at operating system level
Login as sidadm user at os level
cd usrsaptrans
find data cofiles -name 00017ltSIDgt -exec ls -lastr
the file size should become constant if you again trigger the command
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
26 Save data for RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printer Server tables
Here we Export the tables relevant to RFC ITS SAPconnect SSO HTTP(S) SCOT and Logical Printers
For Eg
Secure store tables are also exported
These tables contain the RFC passwords In earlier versions this was included in table RFCDES
The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN
Create a transport with the following object list
Program ID
Object
Object Name
Table Key
DescriptionPurpose
R3TR
TABU
RSECTAB
Secure store table client-specific
R3TR
TABU
RSECACTB
Secure store table cross-client
R3TR
TABU
RFCATTRIB
Administration table for RFC destinations
R3TR
TABU
RFCDES
Destination table for Remote Function Call
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RFCDESSECU
SNC extensions for RFC destinations
R3TR
TABU
RFCDOC
Description of Possible RFC Connections (-gtRFCDES)
R3TR
TABU
RFCTRUST
List of existing trusting systems
R3TR
TABU
RFCSYSACL
List of permitted trusted systems for the current system
R3TR
TABU
IACORDES
RFC Destinations for IACOR ITS
R3TR
TABU
TSPSV
Spool Server table
R3TR
TABU
TSPSI
Spool Server Information (Updated by Spool Work Processes)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
TSP03
Spool Printer declaration
R3TR
TABU
TSP03A
Spool Device description (new format)
R3TR
TABU
TSP03C
Spool Device Description Extension
R3TR
TABU
TSP03D
Spool Device Description (New Format)
R3TR
TABU
TSP03L
Spool Long device names
R3TR
TABU
TSP03T
Paper format in the device paper tray
R3TR
TABU
TBD11
ZKOST
Transaction BD95 Configuration
R3TR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TABU
TWPURLSVR
Logical Web Servers for Logical Systems I
R3TR
TABU
ROIDOCPRMS
Control parameters for data transfer from the source system
R3TR
VDAT
V_TBDLS
Logical System Names IHUB
R3TR
TABU
SXNODES
SAPconnect Communication nodes
R3TR
TABU
SXROUTE
SAPconnect Routing table
R3TR
TABU
SXSERV
SAPconnect Node capabilities
R3TR
TABU
SXADMINTAB
SAPconnect and SAPphone Administration
R3TR
TABU
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SXDOMAINS
SAPconnect Management of Internet Mail Addresses Domains
R3TR
TABU
SOPR
SAPoffice System-wide profile (default domain)
R3TR
TABU
SXADDRTYPE
SAPconnect Address types
R3TR
TABU
SXCONVERT
SAPconnect Conversion functions
R3TR
TABU
SXCONVERT2
SAPconnect Conversion Functions for Forma
R3TR
TABU
SXCOS
SAPconnect Send attribute classes
R3TR
TABU
SXCOS_T
SAPconnect Text table for send classes
R3TR
TABU
SXDEVTYPE
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SAPconnect Device Types for Format Conver
R3TR
TABU
SXFORMATG
SAPconnect Format groups
R3TR
TABU
SXJOBS
SAPconnect Send Jobs
R3TR
TABU
SXRETRY
SAPconnect Disruptions in RFC connections
R3TR
TABU
SXRFC
SAPconnect Assignment of RFC address to n
R3TR
TABU
SXTELMOIN
SAPconnect Telephone number modification
R3TR
TABU
SXTELMOOUT
SAPconnect Telephone number modification
R3TR
TABU
T160PR
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Profile for External Purchasing System
R3TR
TABU
TWPSSO2ACL
Workplace Single Sign-On 2 Access Control List
R3TR
TABU
SSF_PSE_H
SSF Personel Security Environment
R3TR
TABU
SSF_PSE_D
SSF Storage for Personal Security Environment Data
R3TR
TABU
SSFARGS
Application-Dependent Parameters for SSF Functions (SSFG)
R3TR
TABU
SXMSCONFVL
XMS Integration Engine Configuration Parameters
R3TR
TABU
CREP_HTTP
KPRO CMS Content Repositories (HTTP)
R3TR
TABU
HTTPURLLOC
HTTP URL Location Exception Table
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
R3TR
TABU
RSADMINA
Control Parameters for BI (Accelerator)
R3TR
TABU
RSDDTREXADMIN
Additional Settings for Indexing of an HPA Index
R3TR
TABL
RSPOR_T_PORTAL
Maintaining Settings for Integration into SAP EnterprisePortal
- For Target system logon in SAP client where you have enough authorizations
- Goto SE01
Create button
- Check Request type Transport of copies
- Uncheck any other request type
Enter Short description
- Enter target (DUM) or enter a SID other than the target SID
- Save
- Write down the transport number
Click on transport request
- Press Display object list button
- Press Display szliggt Change do be in change mode
- Click on New entries
- Enter entries as listed in above table one per line
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
10 After you have entered all objects double click on each object to drill down to the key
11 Correction Click on ltEditgt then click on ltInsert Linegt
12 Enter in each of the key field lines and save
13 Repeat step 9-12 for all the objects
14 Save and go back
15 Select the transport request and
16 Click on Release directly
17 Check the transport log
When application or temporary tables which you want to export giving errors then you have to export them via Oracle
- su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
exp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables=lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N consistent=Y compress=N
27 Preserve printers
There are two options to preserve the printers
- Transport
- Local file
Transport
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- In menu go to Edit Transport gt Transport All
- Press enter at screen prompt
- A prompt for a transport number create a new one and press enter
- Enter a short description
- Press enter
10 In the message window Entry is made in transport request means successful creation
11 Execute transaction SE01 select workbench request and click on display
12 Click on the transport number Select Request Request header enter a valid target = DUM
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
13 Click SAVE and ignore any errors
14 Click on the Developmentcorrection task number Press Release
15 Press the save button in the popup menu followed by the back button
16 The task should now be displayed in a darker color
17 Click on the transport number Press Release
18 Press the save button in the popup menu followed by the back button
19 Now the transport has been released
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt Export
- ExportImport file name Fillin the destination of your C -drive where you can store the file for the printers
Example cappsreserveprintersSIDtxt
- Select Frontend computer
- Select Export
10 Select Execute export and Generate log
11 For Output device Fillin (Please dont forget this otherwise it will only export 1 printer)
12 Click on execute
Please check in your txt file cappsreserveprintersSIDtxt if the printers are there
28 Backup BugsEye amp eMerge data
if the BugsEye data amp eMerge data needs to be saved
If the customer agrees to save the data do the following
For BugsEye
- Export all data info from BugsEye instance
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
su oraltsidgt
exp bugreqltPassword for bugreq usergt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y
log=tmpexportbuglog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
For eMerge (for GSAP)
- Export all data info from eMerge instance
su oraltsidgt
exp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y log=tmpexportemelog
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
29 Export J2EE Database Schema
The schema of the J2EE 640700 must be saved to restart the engine after the system has been refreshed
Export the SAPltSIDgtDB or SAPMIWDB schema using schema password
su - oraltsidgt
cd oracleltSIDgtsapreorg (need at least 2GB free for SAPMIWDB)
exp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpexportj2eelog
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note wait for the prompt and enter the below values
mode (2) U(sers)
export grants yes
export table data yes
compress extents yes
In case none of the passwords work change the schema password as follows
sqlplus as sysdba
alter user sapmiwdb identified by ltPasswordgt
210 Capture the standard SAP jobs released in SAP
Login to Target system
Go to SM37
Query for all the released jobs in the system and take a screen shot we shall be Scheduling it later
211 Check amp Preserve details of PSAPTEMP datafiles
Execute the following command at Oracle level for details of tempfiles path amp size of the temp files for the existing system and
preserve the details for comparison after refresh
su - oraltSIDgt
sqlpls as sysdba
file_name(bytes102410241024) from dba_temp_files where tablespace_name =PSAPTEMP
212 Preserve BI Accelerator Indexes
If the BI system is connected to BIA the BIA indexes need to be saved so these indexes can be rebuild later
Start transaction nRSDDV in the BI instance
Select the Display All BIA Indexes button or select (F6)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Take a screen shot of these indexes and copy into a word document and save the document Screenshot
213 Logon Group Names (SMLG and RZ12)
Logon group names are used in projects to accomplish logon load balancing These logon groups are used in the SAP logon pad to
automatically assign users to application servers based on currently application server usage The spelling of the logon groups are
important because the names in the logon pad must match exactly with what is configured in the system Therefore it is important
to note the SAP logon group names in the target system prior to performing the database copy because after the copy the logon
group definitions will reflect those of the source system To retrieve the logon group name(s)
- For Target system logon in SAP client where you have enough authorizations
Execute transaction SMLG
- The logon group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups Logon
group names are also case-sensitive
RFC server groups are amongst other things used for parallel client copies These RFC server groups must be restored to their
current configuration after the refresh
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ12
- The RFC server group name(s) will be displayed on the screen Save a copy of the screen or write down the logon groups
RFC server group names are also case-sensitive
214 Op-mode Snapshot
Again depending on the requestor normally the same op-mode would be maintained
The Source ltSIDgt and Target ltSIDgt may have different definitions of Op-modes After a successful database copy the Op-modes
in the Target ltSIDgt will be replaced with the Op-modes in the Source ltSIDgt Therefore it is important to take a snapshot of the
Op-modes in the Target ltSIDgt Proceed as follows
- For Target system logon in SAP client where you have enough authorizations
- For Target system logon in SAP client where you have enough authorizations
Execute transaction RZ04 - Double-click on one of the Op-modes or click instanceop-mode in menu bar
- Execute menu items System =gt List =gt Save =gt Local file =gt unconverted
- This will ask for a directoryfilename on the local PC to store the information Make note of the directoryfilename for use
in the post-processing steps
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 1965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
215 Check and Save Logical System Definition
Execute SCC4 and double click on all clients
If the field Logical System is not blank document the name with each client
216 Preserve DB13 entries
As the DB13 tables will be cleared due to the refresh the entries of the DBA Planning Calendar must be saved
Proceed as follows
- Goto DB13 on the target system
- Make a hardcopy of the screen andor save it in notepad
217 SAP License Snapshot
The Source ltSIDgt and Target ltSIDgt may have different list of SAP Licenses loaded in the system After a successful database
copy the SAP Licenses in the Target ltSIDgt will be replaced with those in the Source ltSIDgt Therefore it is important to take a
snapshot of the SAP Licenses in the Target ltSIDgt Proceed as follows
- Log on to the target system at UNIX as ltsidgtadm
- saplicense show gt saplicense_ltTarget_SIDgtsave
- Make note of the absolute_pathfilename (saplicensesave) for use in the Post Copy Steps should be in
localusersltsidgtadm
218 Determine SAP version
This step is important in order to follow these instructions as they are version dependent
- Log on to SAP with your personal id
- Enter STAT in the transaction field at the top left corner of the screen and press enter
- A pop-up screen appears the version of SAP is listed in the field named SAP Release (or BasisRelease)
- Click red X to exit pop-upx
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- SAP RELEASE ____________________
219 Preserve TXCOM table entries
- Log on to SAP with your personal id in client 002
- SM54
- Double click on the entry
- Take a screen shot of the entry and copy into a word document and save the document
This is for saving CPIC destinations for SNC protection
Note Apart from the steps above we should take care to see that customer specific data is preserved as requested or applicable
And also note that if source system is at lower level in terms support packages addons and other applications we might have to
upgrade the target system accordingly after refresh if required
3 RestoringCopying the database
31 Procedure to Refresh Database from the onlineoffline Backup
Disable crontab for root on target systemDisable roots cron to make sure that nothing runs that might have an impact on the refresh
ltupgrade_servergt crontab -l gt localetcsapadmrootcrontab`date +YYYYMMMDD`(like rootcrontab2005JAN01)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
ltupgrade_servergt crontab r
Actions on Target SystemBring down all the applications of SAP( for ex Patrol ControlM agent CCMSR etc)
Bring down the J2ee Engine
Access transaction SMICM
Perform the following path
Administration gt J2EE Server gt Send Hard Shutdown gt Without Restart
Bring down SAP and clean up the system
- su - ltsidgtadm
- stopsap
- saposcol k
- su oraltsidgt
- lsnrctl stop
- cd oracleltSIDgt
- rm r sapdata
- cd oracleltSIDgtsaparch
- rm
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If this isnt working then use
Check
find oracleSIDsaparch -name -exec ls
If it can find the files then use this
find oracleSIDsaparch -name -exec rm
- cd oracleltSIDgtcntrl
- rm dbf
Copy needed files from source system to target system
On SourceStandby system-
rootgtcd oracleltSIDgtsapbackup
rootgtmore ltanfgt or more ltaffgt for standby (if applicable)
To make sure that the backup by which you need to restore is successful
1 On SourceStandby system
rootgt cd oracleltSIDgtsapbackup
rootgt scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup
or scp xxxanf lttarget systemgtoraclelttarget SIDgtsapbackup for standby (if applicable)
2 On Target system
rootgt chmod g+r anf (or aff file for standby (if applicable))
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt chown oralttarget sidgtdba anf (or aff file for standby (if applicable))
- SCP the backup file needed from source system to target System
2 Change the permissions and ownership of
Backup file
1 On Source system
rootgt scp initltsidgtutl lttarget systemgtoracleltsidgtdbs
2 On Target system
rootgt chmod g+r initltsource sidgtutl
rootgt chown oralttarget sidgtdba initltsource sidgtutl
3 root gt vi initltsource sidgtutl
Change CONFIG_FILE parameter as -
CONFIG_FILE oraclelttarget sidgtdbsinitltsource sidgtbki
- SCP initltsidgtutl file from source to target
- Change the permissions and ownership of initltsource sidgtutl
- Edit initltsource sidgtutl We need to
change Config_file parameter This is
needed to start the restore
1 On Source system
rootgt cd oracleltsidgtdbs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
rootgt scp initltsource sidgtbki lttarget systemgtoraclelttarget sidgt
dbs
2 On Target system
rootgt cd oracleltsidgtdbs
rootgt chmod g+r initltsource sidgtbki
rootgt chown oralttarget sidgtdba initltsource sidgtbki
- SCP initltsource sidgtbki from source to target
- Change permissions amp ownership of initltsource sidgtbki
On source system
1 oraltsidgt sqlplus as sysdba
sqlplus gt alter database backup controlfile to trace
sqlplus gt exit
- scp this file created in oracleltSIDgtsaptraceusertrace to the target system oracle ltSIDgt
- scp lttrace filegt target system oracle ltSIDgtcreatecontrolsql
- On Target system
rootgtcd oracle ltSIDgt
rootgt chmod g+r createcontrolsql
rootgt chown oralttarget sidgtdba createcontrolsql
- To create the trace file
- Scp the trace file to the target system
- Change the permissionownership of trace file
Editing the tracefile on target system
- rootgt vi lttrace filegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- The file has been created double remove the first file
- Remove all the starting lines of tracefile until STARTUP NOMOUNT
3 Edit the 2nd line
CREATE CONTROLFILE REUSE DATABASE SOURCE SID NORESETLOGS ARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE TARGET SID RESETLOGS NOARCHIVELOG
- Remove also all the 2 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER DATABASE OPEN RESETLOGS
- Change all source sid to target sid This can be done by using vi command
1$sltsource sidgtlttarget sidgtg
- To go into vi mode
- To remove all the unwanted lines All the lines are to be removed until STARTUP NOMOUNT beginning from first line
Edit the 2nd line as said
- Comment the 3 lines which is present at the bottom of the tracefile We do this manually later
- This is an easy command to change all the sid of source system to the sid of target system
Note -
Make sure no new datafile has being added after the backup that is being used Check by table V$datafile If yes edit the trace
file(remove the datafile entry that are entered after the backup that if used)
At the end of the tracefile on the BW system you will also find some comments about the TEMP files For now you need to delete
these entries but save them somewhere else because later you will need them again Example
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_3tempdata3
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oraclePC6sapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
Restore database from StorageStart restore on targetsystem in the foreground with
- su oraltsidgt
- for normal restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m full c
- for standby restore brrestore -r initltsource sidgtutl -b ltbackupfilegt -m all c
or Start restore in the background with
- as root
- at now
su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m full c force
D
for standby su oraltsidgt -c brrestore -r initltsource sidgtutl -b ltbackupfilegt-m all c force
D
After the restore is finished (on target system)
- as root
- cd oracleltSIDgt
- chown R oraltsidgtdba sapdata
Rename the database
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
On Target System
- su oraltsidgt
- sqlplus as sysdba
- createcontrolsql
Check in the oracleltSIDgtsaptracebackgroundalert_ltSIDgtlog for any errors
Restoring offline redologsIn case a recovery of the database is needed (eg after the restore of an online backup or a point-in-time recovery is needed) offline
redologs files needs to be restored from Storage
To know what files you will need you can look in the sourcesystems saparch directory Look for the file archltSIDgtlog and decide
which files you will need by timestamp You can also look in SAP (source system) with transaction DB12
To restore redologs you will need to copy the archltsourcesidgtlog to the targetsystems saparch directory
- scp oracleltsourceSIDgtsaparcharchltsourceSIDgtlog lttargetsystemgt oracle lttargetSIDgtsaparch
On target system
- mv archltsourceSIDgtlog archlttargetSIDgtlog
- chown oraltsidgtdba archlttargetSIDgtlog
chmod 660 archlttargetSIDgtlog
Recovering the databaseThere are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP
sqlplusgt recover database using backup controlfile until cancel
or
sqlplusgt recover database until time 2004-05-21100000 using backup controlfile
to apply all required redologs automatically type AUTO
after completion we can now open the database by
sqlplusgt alter database open resetlogs
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Checking the databaseFirst check if we can stop and start the system without problems
Sqlplusgt shutdown immediate
Sqlplusgt startup
Also check the alert_SIDlog for any errors
Recreation of the tempfilesWe need some additional action for BW Recreation of the tempfiles which you saved at step Error Reference source not found
Example for 4 data files in sapdata6
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleSSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Change sourceSID to targetSID
- Create the needed subdorectories in the sapdata filesystem(s)
cd oraclelttargetSIDgtsapdata6
mkdir temp_1
mkdir temp_2
mkdir temp_3
mkdir temp_4
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 2965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create the tempfiles
- su oraltsidgt
- sqlplus as sysdba
- ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_1tempdata1
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_2tempdata2
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_3tempdata3
SIZE 1999M REUSE AUTOEXTEND OFF
- Sqlplusgt ALTER TABLESPACE PSAPTEMP ADD TEMPFILE oracleTSIDsapdata6temp_4tempdata4
SIZE 1999M REUSE AUTOEXTEND OFF
Making locally managed temporary datafiles non-sparseThe added datafiles in the previous step are locally managed temporary datafiles These kinds of datafiles are created as sparse files
(they can grow to the configured size but initially this amount of space is not yet claimed on the OS level) This can lead to issues
when the reserved space is claimed by newly added normal datafiles Therefore these files need to be change to non-sparse files
- su oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- exit
Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located The datafile needs to
be moved to this other filesystem and back again This will make the datafile non-sparse
Here is an exampleto move the files
cd oracleSIDsapdata3
oraltsidgt 40gt mv temp2_1temp2data1 oracleSIDsapdata5temp2data1
oraltsidgt 41gt mv oracleSIDsapdata5temp2data1 temp2_1temp2data1
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
oraltsidgt 40gt mv temp2_2temp2data2 oracleSIDsapdata5temp2data2
oraltsidgt 41gt mv oracleSIDsapdata5temp2data2 temp2_2temp2data2
You can now see that the files are non-sparse and use the entire space in the filesystem
Restart the database
Create new OPS$ user amp drop old OPS$ userWe need to generate a new OPS$ user
su oraltsidgt
- CHDBPASS817
- select option ac and d
- cd sapmntltSIDgtexe
vi CHDBPASS102 Change tablespace PSAPUSER1D into PSAPMIWUSR
Change SAPR3 into SAPMIW
CHDBPASS102 option a c d Set Password as relevant
for a use schema password For c d use system password
Later in the post step you can proceed to grant permissions to the user created
Check Archive Log ModeCheck if the database log mode is set on archive mode with sapdba If not toggle database log mode
Start Oracle ListenerThe Oracle Listener should also be started
Orasidgt lsnrctl start
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
32 Procedure to Refresh Database from the database residing in the same server
(Relevant only if your standby server resides in the same system of the landscape)
For eg if standby Server of production resides in Acceptance system you can refresh the Acceptance system from the Hotstandy of
Production(this is common practice for major clients)
If the above condition persist you can proceed with steps specified below
Backup Source controlfile to trace
- Log on to the source (or standby database) systems as oraltsidgt
- sqlplus as sysdba
- alter database backup controlfile to trace
- quit
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- cd oracleltsourceSIDgtsaptraceusertrace
- ls altr
- Write down the name of the trace file created (we will refer to it as lttracefilegt)
Stop Target SAP and OracleNote Downtime starts here
If the target SAP Instance has any application severs they must be stopped first Log on to the application servers of the target
instance as ltsidgtadm
Stopsap
Logon to the target database server as ltsidgtadm
Stopsap
Remove the database existing on the Target SystemCaution Be careful with following commands Look twice before pressing enter You dont want to remove datafiles belonging to
another SID (like the standby database)
- Logon to the target system as root
- cd oraclelttargetSIDgt
- rm r sapdata
- cd oraclelttargetSIDgtcntrl
- rm dbf
- cd oraclelttargetSIDgtsaparch
- rm dbf
Stop the hotstandby database
- Logon to the hotstandby system as oralthotstandbysidgt
- sqlplus as sysdba
- shutdown immediate
Copy the database from hotstandbyNote If the target system is not on the same server as the hotstandby make sure that rhosts file in the target system contains a row
like
lthotstandby systemgt root
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If not please add this line and dont forget to remove it when the procedure is completed
Please ensure that the number of sapdata filesystems for the target SID matches the number of sapdata filesystems for the
hotstandby SIDboth in number and in size to ensure there is sufficient capacity for the copy process When performing the steps
below it may be wise to copy and paste line for line from the document into the UNIX terminal window because it may be difficult
to identify whether you are using the proper character number or letter in some cases
On MC-II systems the conccurent io (cio) option is turned on on the sapdata and origlogmirrlog filessytems As such to prevent a
very slow refresh from the hot-standby system the cio option needs to be switched off because otherwise the cp command will be
extremely slow
Therefore if the hotstandby system is on MC-II platform stop the SAP instances running on the hotstandby and target systems if
this is not done yet in the previous steps and run the following commands as root to disable the cio option Not that if both the
hotstandby and target systems are on MC-1 platforms please skip this step and proceed with the next step
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuid $fs
umount $fs
mount $fs
done
If the target system is not on the same server as the hotstandby
Logon to the hotstandby system as root and run the following command-
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
scp p r oraclelthotstandbySIDgtsapdata$i lttarget_servergtoraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
If the target system is on the same server as the hotstandby
Logon to the hotstandby system as root
at now
for i in `df -Ik |grep sapdata |grep lthotstandbySIDgt | sed ssapdata([0-9])$1 `
do
echo $(date) Copying oraclelthotstandbySIDgtsapdata$i filesystem
cp -p -r oraclelthotstandbySIDgtsapdata$i oraclelttargetSIDgtsapdata$i amp
done | tee -a tmphotstandby_copy$(date +YmdHMS)log
D
Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems) It makes sense to
check for file sizes and compare with the source files
Now if the cio option is switched off in one of the above steps it must be turned on again To do that run the following commands
on both the hotstandby and target systems-
lsfs | grep sapdata | while read lv a fs rest
do
chfs -a options=rwnodevnosuidcio $fs
umount $fs
mount $fs
done
Change ownership on restored files
Logon to the target system as root - cd oraclelttargetSIDgt
- chown R oralttargetsidgtdba sapdata
Edit the trace file on target system
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Use an editor (like vi) to change tmplttracefilegt
Perform the following changes
Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command CREATE CONTROLFILE
REUSE DATABASE ltSIDgt RESETLOGS
Note With ORACLE 9 the trace file will appear to have duplicate data The only difference is that it has two stanzas one with
NORESETLOGS and one with RESETLOGS You want the last one
Change all source sid to target sid This can be done by using vi command
1$sltsourse sidgtlttarget sidgtg
Change the 2nd line from
CREATE CONTROLFILE REUSE DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
to
CREATE CONTROLFILE SET DATABASE ltSIDgt RESETLOGS NOARCHIVELOG
Comment all lines below and including the following 3 lines at the bottom of the tracefile
RECOVER DATABASE
ALTER SYSTEM ARCHIVE LOG ALL
ALTER DATABASE OPEN
Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following You
will need to manually execute these statements later
ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE oracleSIDsapdata4pat1i_1pat1idata1 SIZE 52420608 REUSE
AUTOEXTEND OFF
Save the file and exit vi
Create controlfile and open the database
Open another session and tail the alert log
- Logon to the target system as oraltsidgt
- tail f oraclelttargetSIDgtsaptracebackgroundalert_lttargetSIDgtlog
- In your initial session
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- tmplttracefilegt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- recover database using backup controlfile until cancel
Cancel this immediately You dont really have to apply logs (NOTE If an on-line backup was used the required redo logsmust be applied to the database) - alter database open resetlogs
Execute all the ALTER Tablespace ltxxxxgt ADD TEMPFILE statements from step 0 You can open another window and
cut-paste the statements into the sqlplus program Make sure they execute successfully
Caution Keep an eye on the alert log as eventual errors can end up in a RUNNING but inconsistent database
Restart the Standby database
- Logon to the hotstandby system as oraltsidgt
- sqlplus as sysdba
- startup nomount
- alter database mount standby database exclusive
- exit
-
Restart the databaseIf the target database is supposed to run in ARCHIVELOG MODE you have to activate it
- Logon to the target system as oraltsidgt
- sqlplus as sysdba
- shutdown immediate
- startup mount
- Following line ONLY if you have to run in ARCHIVELOG MODE
- alter database archivelog
- Following line ALWAYS
- alter database open
The following step Start Oracle listener is only needed if the database is restored from standby
Start Oracle ListenerStart the listener if its not already running
- Logon to the target system as oraltsidgt
- lsnrctl start
Note DO NOT START SAP HERE YET
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Create OPS$ltSIDgtADM user and grant sapdba role toFirst start Oracle (if not already started)
Logon to the target system as oraltsidgt
lsnrctl start
sqlplus internal
startup
exit
Go to sapmntltSIDgtexe and run CHDBPASS817 or CHDBPASS102 (Select option ac and d)
Note if The CHDBPASS817 file is not available Therefore the commands to create the OPS$ltSIDgtADM account must be run
manually Perform the following steps
Logon to the target system as oraltsidgt
sqlplus as sysdba
drop user ops$oraltSIDgt cascade
create user ops$oraltSIDgt identified externally default tablespace psapuser1d
temporary tablespace psaptemp
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant dbaconnectresource to ops$oraltSIDgt
drop user ops$ltSIDgtadm cascade
create user ops$ltSIDgtadm identified externally
default tablespace psapuser1d
temporary tablespace psaptemp
grant dbaconnectresource to ops$ltSIDgtadm
create table ops$ltSSIDgtadmsapuser as select from ops$ltTSIDgtadmsapuser
exit
Also the passwords for sapr3 sys and system must be set Run the following commands
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 3965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Find current passwords from warp Logon to the target system as oraltsidgt
connect as sysdba
alter user system identified by passwd
alter user sapr3 identified by passwd
alter user sys identified by passwd
update ops$sidadmsapuser set passwd = passwd
commit
exit
Check for connectivity to the database with the following command as ltsidgtadm
R3trans -d
4 Post-Copy Steps
41 Removing hostname entries
Remove the entries added during presteps DONT JUST COMMENT the line completely remove it
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Log on to the target system as root
vi shosts
remove entry ltsourceservernamegt root
remove entry lttargetservernamegt root
Log on to the source system as root
(Noted Not applicable for hot-standby machine)
vi shosts
remove entry lttargetservernamegt root
42 Fix GLOBAL_NAME parameter in Oracle
SAP recommends to change the GLOBAL_NAME parameter after a change of the SID (which is of course done with a refresh)
This is recommended via notes about the homogeneous system copies (for example see note 201149 for 46C and 407123 for 6x)
Change the global name via
su oraltsidgt
sqlplus as sysdba
select from global_name (this will show an entry for the old DB name)
alter database rename global_name to ltNEWSIDgtworld
select from global_name (this will now show the right SID for example)
GLOBAL_NAME
--------------------------------------------------------------------------------
SIDWORLD
43 Reset Oracle SYS and SYSTEM password
After database copy the SYS and SYTEM passwords can become inconsistent with the encrypted password in which could cause
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
database backup to fail
(find the current SYSSYSTEM password from warp)
su orasid
sqlplus as sysdba
SQLgt alter user sys identified by password
SQLgt alter user system identified by password
44 Fix SAP License Key
After a successful database copy the SAP license key database will reflect only the key(s) that were in the source system In order
for users to be able to log into the target system the appropriate license key has to be installed Some projects install all of their
project license keys in all systems so that this step can be eliminated If the license key is not installed proceed as follows
Logon to the target system as ltsidgtadm
- cat saplicensesave
- saplicense install
Answer all questions with values provided by saplicensesave
Note For NW07 systems with digitally-signed licenses eg Gchem CRM this will not work
In the SAP menu choose Administration reg Administration reg SAP Licenses or call transaction SLICENSE
- Click New Licenses
- Delete the license from the source system
- Install the license for the target system
45 Cleanup sapmntSIDglobal
Before starting SAP we have to remove the WF_LOG files and other directories in the sapmntSIDglobal directory on the target
system Since the files in the sapmntSIDglobal directory are related to the Oracle database on the system all these files can be
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
removed when the DB is replaced during a refresh
- Use this command to remove the files and directories
rm -r sapmntSIDglobal
46 Start SAP for the first time
When SAP is started after the refresh all batchjobs that were not able to run during the time of the refresh will be released
immediately when SAP is started These batchjobs can send out purchase-orders etc to actual suppliers As this can cause serious
issues several customers want these jobs to be prevented from running This is done by setting the number of batchjobs to 0 before
starting SAP for the first time After starting SAP there is now time to delete all released jobs in SM37 wihtout the danger of them
being kicked off at the startsap command
Su sidadm
Cdpro
We can edit the number of background workprocesses to 0 in instance profile
(eg rdispwp_no_btc=0 can be set in instance profile using vi editor)
Startsap
Then login to SAP and go to transaction SM37 Cancel all the released jobs to schedule
Stopsap
Revert the btc processes to earlier value from 0 and
Startsap
47 Manual run of backup logBefore you Proceed please check the saparch directory to see how much free space is available Run the backup of logs in order to
clean up the SAP directory
48 Re-enable crontab for root on target server
Re-enable roots cron (make sure that the same file saved earlier during the step 0 pre-work is loaded it should have been saved
and restored to localetcsapadm as part of the procedures) May need to replace the date format with the actual date the backup was
made-)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
crontab localetcsapadmrootcrontab`date +dmY`
49 Transport System Configuration
After a successful database copy the transport system needs to be reconfigured
Proceed as follows
Logon to the target SAP in client 000 as DDIC - Run transaction SE06
- Choose Database copy or migration
- Press Post-installation processing
- Confirm Do you want to reinstall the CTS
- Enter Source System SID
- Select OK or YES to all remaining prompts
- Run transaction STMS
Enter Description Domain name(default is DOMAIN_ltSIDgt) and domain description Check if the system is MC II then you have
to fillin functional name instead of hostname
- Press Save
- Go to OverviewagraveTransport routes
- Go to ConfigurationagraveAdjust with Controller
- Confirm the next popup box that says Adjust with controller
- Go back to main screen
- Run transaction SE06
- Click System Change Option button
- Validate the value is set to laquo objects cannot be changedgt
410 Delete all spool request
After a successful database copy the spool requests listed in the Target ltSIDgt will reflect those of the Source ltSIDgt Therefore all
spool requests need to be deleted from the Target ltSIDgt Proceed as follows
Logon to the target SAP - Run transaction SE38
- Enter RSPO1041(RSPO0041 for 31I) in the program field and click execute
- Enter the values like the following screen
- Select menu item Program =gt Execute in background
- A printer destination screen appears enter LP01 as printer name and uncheck Print immediately
- Click green check and the job will begin in a batch process run immediately
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
411 Delete Update Entries
Logon to the target SAP - Run transaction SM13
- Erase all entry fields and press enterexecute
Delete all entries
412 Delete Lock Entries
At the time that the backup of the Source ltSIDgt was taken there may have been lock entries listed These will have been copied to
the Target ltSIDgt after the successful database copy and will need to be deleted Proceed as follows
Logon to the target SAP - Run transaction SM12
- Erase all entry fields displayed
Select Menu Items Lock entry =gt Delete all
413 Delete Source SID Profile Parameter Files
After the database refresh the active profiles listed in the SAP system will be from the source system These profiles need to be
deleted and the profiles from the OS need to be re-imported Proceed as follows
Logon to the target SAP - Run transaction RZ10
- Delete source system profiles
- Click the Profile drop-down box and choose a profile (this process must be done for each profile except for the
DEFAULTPFL)
- Select menu items Profile -gt Delete -gt All versions of a profile
- Click Yes to first prompt to update the database
- Click No to delete the files from the Op Sys Level
- Click green check on all versions deleted screen
- Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
414 Delete Source SID Op Modes
After a successful database copy the target system will contain Operation Modes from the source system These Op Modes need to
be deleted and the correct Op Modes need to be imported Proceed as follows
- Logon to the target SAP
- Run transaction RZ04
- Select InstanceOpmodes
- Select a server name and press SHIFT F2
- Do this for each source system op mode listed
- Create the target system op mode configuration(s) by selecting the menu items Settings -gt Based on Current Status -gt New
Instances -gt Generate
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
- Click the SAVE button
415 Delete Server Specific Performance Data
After a successful database copy the performance database will reflect that of the Source ltSIDgt and therefore should be deleted
from the Target ltSIDgt Proceed as follows
Logon to the target SAP Execute transaction ST03
Select Menu Items Goto =gt Performance database =gt Contents of database Select Delete Data 1 Server button
- Enter the source server db server name and click Continue
- Repeat this for each source app server name
Select Menu Items Workload =gt Reorg =gt Delete Stats fileSelect NO to update the database
Select YES to delete the statistics file
416 Check System Logs
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
Logon to the target SAP Execute transaction SM21
Select menu items System logs -gt Choose -gt All remote system logs
- Set the From datetime 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
Logon to the target SAP Run transaction SMLG - Delete Source Logon Groups
- Highlight the Source Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)Run transaction RZ12 - Delete RFC Server Groups
Highlight the Logon Group
Click the Delete Group button
- Recall the target systems Logon Group names which were captured in the Pre-Copy steps
Click the Add assignment button
In the Logon group field type in the target logon group name exactly as it looked in the snapshot taken in the Pre-Copy steps(case-sensitive)
417 Fix Logon Group Names (SMLG and RZ12)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
418 Re-initialize Import Jobs
After the database copy has successfully completed the import jobs used by the tp command may not work properly It is best to
delete these jobs and reschedule them new Proceed as follows
Logon to the target system in client 000 as DDIC
Run transaction SM37
Type RDDIMPDP in the Job name field
- Type in the User name field
- Only select the Sched Released and Ready radio buttons
- Erase both date fields
Execute the transaction
- Select all jobs and click the delete button
Run transaction SE38
Execute program RDDNEWPP Specify job class A or highest priority A message will show up in the status bar indicating the job
has been scheduled
- Log onto the target system in each of the other clients and repeat previous 2 steps This will schedule the needed jobs in
each client where transports will be migrated
419 Restore printers
Using the ltTransport numbergt created in step 213 ltclient_numbergt is the default system client or using the Local file
Transport
- Login to SAP client 002
- SPAD
- Click the Change button
- Select Utilities For Output Devices Delete All
- Ignore any errorswarnings
Logon to the target system as ltsidgtadm
- cd usrsaptransbin
- tp addtobuffer ltTransport Numbergt ltSIDgt
- tp import ltTransport Numbergt ltSIDgt clientltclient_numbergt U128
Local file
- Log on to one of the SAP target system client 002 (or proper one for BW) with personal id
- SPAD
- Click on Change Icon
- Click Output Devices
- Click on the line of one of the printers
- In menu go to Edit --gt Transfer --gt import
- ExportImport file name Fillin the destination of your C -drive where you saved the file of the printers in step 215
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- example cappsreserveprintersSIDtxt
- Select Frontend computer
10 Select Import
11 Select Execute import and Generate log
12 For Output device Fillin
13 Click on execute
420 Import User Master Records
After a database copy the User Master Records (UMR) in the target system will be the same as was in the source system Normally
it is desirable to export the UMRs prior to the database copy step and then re-import them after the copy completes
cd usrsaptransbin
tp addtobuffer ltSIDgtKTxxxxx [pf=TP_DOMAIN_ltSid of domain controllergtPFLgt ] ltSIDgt
tp import ltSIDgtKTxxxxx ltSIDgt clientltclient_numbergt [pf=TP_DOMAIN_ltSid of domain controllergtPFL ] U128
Note The Part in the [ ] maybe required The domain controller is usually the development server for this landscape For example
if target system is AB3 the domain controller is DB3
The transport number was generated in one of the Pre-Copy steps This process may have to be completed for multiple clients
depending on customer requirements for the target system
421 Change Client Settings
- Logon to the target SAP in client 002
- Execute transaction SCC4
- Change the category to Test for the client that you just imported the user masters into
- Change the Client Protection to Level 0
- Hit Save button
- Repeat this step for each client that the user import was performed
422 Perform client import post processing
(All R3 systems) Steps Prior to Execution of SCC7In all R3 systems before executing scc7 determine the storage quality of the table If the storage quality is less than 70 we should
re-build the index This will speedup the scc7 run considerably
For determining the storage quality of the imported user master
v Logon to Production client
v Go to -gttcode db02
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
v Click on Detailed Analysis
v Type USRBF2 as object name this is the table for User buffer content for fast RFC logon
v Click Table -gtIndexes the table name and the index are displayed
v Place the cursor on the index(USRBF2~0) and click on Detailed Analysis button
v Check the storage quality select Analyis Index-gtStorage quality from the menu
v If Storage quality is less than 70 we have to rebuild index
v For rebuilding indexes go to Alter index-gtrebuild
v After rebuild is completed proceed to execute Scc7
Part 1 Run SCC7Please note in large systems this step may take an hour to complete
Logon to the target SAP in each of the imported clients
- Run transaction SCC7
- Verify the transport request number matches the transport number that was created during the user master export in the
Request field
- Verify the profile name Export time and Export System fields
- Click the Schedule in background button
- Logon to the target system in the productive client as firebasis
- Run transaction se38
- Enter program RSUSR405 and click execute
- Login to SAP again to verify your id profiles are now set to the target settings NOT production settings
Part 2 Reset User buffersFor systems at lower versions
- Logon to the target system in the productive client
- Enter the transaction SU01
- Go to Menu Utilities -gt mass changes -gt reset all user buffers
423 Change Client Settings
Logon to the target SAP Execute transaction SCC4 - Select each client and verify that entries are appropriate for the following fields
- Std Currency
- Category (Note only one client can be marked as Production for the SID) Change the main client back to Production
- Change the Client Protection to Level 1
- In the subsequent sections verify that these values are set
- No changes allowed - For productive clients at least
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 4965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
No changes to Repository and cross-client customizing objects are selected
424 Restore data for RFC ITS SAPconnect SSO HTTP(S) SCOT and LogicalPrinter Server tables
After a successful database copy the RFC destinations in the target system will have values reflecting the source system This needs
to be changed to reflect the target system In this case you have already a transport available containing RFC tables andor the
exported dump file for the application andor temporary tables
Transport
Logon to the target SAP - Run STMS
- Overview -gt Imports
- Double click the Target system SID name
- Use menu option Extra -gt Other Requests -gt Add
- Enter the transport number from RFC Export done in Pre steps
- Highlight the transport from the list and hit the transport button
Exported dump file
Import the exported dump file of the application andor temporary tables
lttablenamegt
lttablenamegt
To save copy of the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtpasswordgt eg connect sappe8m0tor
Example tables
create table
ZTBD00
as select from
TBD00
create table
ZTBD05
as select from
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
TBD05
create table
ZEDIPOA
as select from
EDIPOA
create table
ZEDIPORT
as select from
EDIPORT
To confirm the tables have already being backup
Select table_name from dba_tables where table_name like Z
To drop the refreshed tables
- su oraltsidgt
- sqlplus nolog
- connect ltSAP tables schemagtltpasswordgt eg connect sappe8m0tor
Example tables
drop table
TBD00
drop table
TBD05
drop table
EDIPOA
drop table
EDIPORT
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Import the original tables
su oraltsidgt
sapsid = SCHEMA (table owner) of sap tables
imp ltsapsidgtltpasswordgt FILE=oracleltSIDgtsapreorgexpdatdmp tables= lttablenamegt lttablenamegt buffer=1024000 grants=N
indexes=N
For Gchem CRM it is not necessary to save a copy of the refreshed tables before doing the import
425 Run System Consistency Check
This will execute the system consistency check and will report any problems that were found There should be no errors however
if any do appear they need to be resolved before opening up the system to end-users
Logon to the target SAP - Run transaction SM28
426 Fix DB13 jobs
During the refresh the DB13 (DBA Planning Calendar) tables are reset To fix that proceed as follows
First delete the SM37 DBA Batch jobs
Logon to the Target server using your id
- Execute the transaction SM37
- Select Job name DBA User name Job status Released Job start condition to lta date a month aheadgt
- Select all the Jobs
- Goto Job and click on Delete
- Confirm message
- Then create the DB13 jobs preserved in Pre steps with transaction DB13
Confirm that jobs are released by executing the transaction SM37Select Job name DBA User name Job status Released
Job start condition to lta date a month aheadgt
427 Convert CCMS tables
The tables OSMON PAHI MONI DBSNP are to be converted in the database with transaction SE14 (delete with data) The old
monitor data is thus cleared from the CCMS monitors Proceed as follows
Logon to the target SAP in client 000 (as ddic user)
- Run transaction SE14
- Enter one of the table names (OSMON PAHI MONI AND DBSNP)
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Select the Object type Table
- Press the Edit button
- Select radio-button delete data Process type should be Direct
- NOTE DO NOT PRESS THE DELETE DB TABLE HERE
- Press activate and adjust database
Repeat steps 2-6 for each of the tables listed above
Logon to the target SAP in client 000 (as ddic)
- Run transaction SCOM
- In Destination block choose Server Assignment
- Press Change push button if there is no entry click EXIT
- Change the server field to the Target Server name
Logon to the target SAP in default client using your own id
- Run transaction SM54
- Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps
428 Changing The Source Server To Target Server Name For SAPCOMM
429 Restore TXCOM table entries
430 Remove System Messages (or adjust)
Check the system to see if there were any system messages and removeupdate them Proceed as follows
Logon to the target SAP Execute transaction SM02
Click on a message select the Delete button
- Repeat this until all messages have been removed
If a message existed prior to the refresh Click the Create button
Enter the message and click Save button
Logon to UNIX on the target database server as ltsidgtadm account
Execute the Unix command stopsap to stop the SAP instance
Execute the Unix command startsap to restart the SAP instance on the database server
Execute the Unix command ps -ef | grep ora This will generate a listing of all Oracle processes There should be several of these
Oracle processes listed
Execute the Unix command ps -ef | grep sap This will generate a listing of all SAP processes There should be several of these
SAP processes listed
Logon to UNIX on the application server as ltsidgtadm account
Execute the Unix command startsap to start the SAP application instance
Logon to the target SAP Run transaction SM65
- Check the boxes for Profile parameter and Execute external programs
Select the radio button All background servers
Click the Execute button
- Review the report for errors
- Start transaction SM61
- Goto Object agrave Modify Object
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on Cleanup list button
Logon to the target SAP - Run transaction RZ10
- Import all profiles from Unix by selecting menu items Utilities -gt Import Profiles -gt of active servers
- Green back arrow
Logon to the target SAP in client 002
Run transaction RZ04 - Select InstanceOpmodes
Create the target system op mode configuration(s) by selecting the menu items Settings -gt Current Status -gt New Instances -gtGenerate - Check each of the new op modes for correctness In the Pre Copy Steps a snapshot of the Target ltSIDgt Op-modes was
taken and downloaded to a directoryfilename on the local PC Verify the Op-modes with this hardcopy listing
Click the SAVEbutton
- Logon to the target system
- Schedule the Standard Jobs which were running earlier
431 Re-cycle SAP
432 Start SAP on all application servers (if applicable)
433 Check background processing
434 Clear Background Objects
435 Import application server Profile Parameter Files
436 Add required application servers to the Op Modes
437 Reschedule Standard SAP Jobs
438 Fix workload storage parameters
During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default To fix
- In the target system
- Run ST03
- Select menu option Workload -gt Reorganize-gt Parameters -gt Performance Database
- Select modify parameters button
- Change the Days= 31 weeks=5 and months =12
- Hit save Button
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
439 Configuring J2EE 640700
After the refresh and before starting the SAP system for the first time the J2EE engine must be reconfigured in order for the
engine to start properly
Drop the Source System J2EE Schema and Tablespace
The J2EE schema and tablespace for the source system must be removed before re-configuring the J2EE engine on the target
system Perform the following
su - ltoragtsid
sqlplus as sysdba
drop user SAPltSSIDgtDB cascade
Continue with create the J2EE schema user
drop tablespace PSAPltSSIDgtDB including contents and datafiles
Create the J2EE tablespace using sapdbaDuring the installation of the J2EE engine a new tablespace is created in the ABAP stack called PSAPltSIDgtDB This tablespace
must be recreated after the system has been restored Perform the following to create the tablespace
su oraltsidgt
sapdba (See the warp file for the system password)
Select c Tablespace administration -gt a Tablespace-gt g - Createdrop tablespace
Select b New Path
By default the tablespace is created in sapdata1 Type of path of the filesystem that contain more than 1GB of space In this
example oracleSIDsapdata8 was used
Select c New Size
Type 1024M to create a 1GB tablespace
Select s Start to Create the tablespace Press q to return
Create the J2EE Schema User (SAPltSIDgtDB or SAPMIWDB or SAPCRMDB )As oraltsidgt perform the following steps to create the J2EE user
su oraltsidgt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus as sysdba
create user SAPltSIDgtDB identified externally default tablespace PSAPltSIDgtDB temporary tablespace PSAPTEMP
alter user sapltsidgtdb identified by ltpasswordgt
grant select_catalog_roleconnect resource to SAPltSIDgtDB
exit
Re-create the J2EE Users in the ABAP StackThe J2EE ABAP users are removed from the ABAP stack The following users must be re-created in the ABAP stack The
following users must be created on the main client
- J2EE_GUEST
- J2EE_ADMIN
- SAPJSF
All three users should be created with the Communication user type to prevent the passwords from expiring
Perform the following
Access transaction SU01
Enter J2EE_ADMIN in the user field
Click the button
In the Last Name and First Name field enter the user name (ie J2EE_ADMIN)
Enter a valid email address in the E-Mail field
Click the Logon data tab
Enter an initial password for the user
Enter Group name in the User Group for Authorization Check field
During creation the User type should be set as a Dialog user After creating the user set the User Type as Communications This
prevent the password of the user from expiring
Click the Roles tab
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5665 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Note When creating the SAPJSF user add the SAP_ALL and SAP_NEW in the Profiles tab
For the J2EE_ADMIN user enter SAP_J2EE_ADMIN in the role field The J2EE_ADMIN and J2EE_GUEST users do not have
any profile assigned
The following chart contains the roles and profiles for the J2EE ABAP users
UserRolesProfile
J2EE_ADMIN
SAP_J2EE_ADMIN
None
J2EE_GUEST
SAP_J2EE_GUEST
None
SAPJSF
SAP_BC_JSF_COMMUNICATION
SAP_ALL SAP_NEW
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5765 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Perform the steps above to re-create the remaining users
Import the J2EE schema (SAPltSIDgtDB)Perform the following the import the J2EE schema
su - oraltsidgt
cd sapreorg
imp sapltsidgtdbltPasswordgt file=oracleltSIDgtsapreorgexportj2eedmp full=y indexes=y grants=y log=tmpimportj2eelog
RZ11 -gt param-name rdispj2ee_start -gt display -gt Change value -gt New value 1 -gt save
Start the J2EE engine using SMICM
Administration gt J2EE Server gt Restart gt Yes
At the OS level verify the J2EE is running You should see the following processes (different on J2EE 700)
ps ef | grep jlaunch
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_server
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_sdm
usrsapSIDDVEBMGSXXj2eeos_libsjlaunch pf=usrsapSIDSYSprofileSID_DVEBMGSXX_ltHostgt
-DSAPINFO=SID_ltSys nogt_dispatcher
For J2EE 700 check if the state is Running
tail usrsapltSIDgtDVEBMGSXXworkdev_server0
[Thr 16708] Thu Sep 6 094455 2007
[Thr 16708] JLaunchISetState change state from [Starting applications (10)] to [Running (3)]
Test the connection to the J2EE engine using the Appropriate URL and port number
The following is displayed
Verify the configuration Portal Connection for BW systems
- Logon with J2EE_ADMIN user to the Portal (HTTPSltPort numbergt)
- Navigate to System Administration -gt System Configuration
- Expand Portal Content
- Expand Systemlandscape
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5865 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
- Right click on SAP_BW agrave Open agrave Connection Tests
Select all tests and choose Test The tests must complete successfully
Note If there exist a problem in bringing up java after refresh check if user sapjsf in unlocked and correct password of it is
maintained in secure store
440 Re-import BugsEye amp eMerge data (if applicable)
Re-Import BugsEye data amp eMerge data (if applicable) in the following way
Make sure the J2EE processes are stopped (done for both BugsEye amp eMerge)
Stop the j2ee processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
Optional egrave Check processes ps ef | grep jlaunch
STEP Drop user bugreq
su oraltsidgt
sqlplus as sysdba
drop user bugreq cascade
commit
STEP Create user BUGREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user BUGREQ identified by ltSee WARPgt default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP
grant create session to BUGREQ
grant create table to BUGREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 5965 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant create sequence to BUGREQ
grant unlimited tablespace to BUGREQ
grant create view to BUGREQ
grant create any cluster to BUGREQ
grant create any context to BUGREQ
grant create any index to BUGREQ
grant create any indextype to BUGREQ
grant create any procedure to BUGREQ
grant create synonym to BUGREQ
grant create trigger to BUGREQ
grant CTXAPP to BUGREQ
STEP Import all bugseye data info into SAP EBP system
su - oraltsidgt
imp bugreqltSee WARPgt file=oracleltSIDgtsapreorgexportbugdmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtrequisiteloginhtm
For eMerge
Make sure the J2EE processes are stopped again
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6065 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave Without Restart
STEP Drop user emereq
su oraltsidgt
sqlplus as sysdba
drop user emereq cascade
commit
STEP Create user EMEREQ in SAP EBP system
su - oraltsidgt
sqlplus as sysdba
create user EMEREQ identified by ltSee WARPgt default tablespace PSAPEMERGE temporary tablespace PSAPTEMP
grant create session to EMEREQ
grant create table to EMEREQ
grant create sequence to EMEREQ
grant unlimited tablespace to EMEREQ
grant create view to EMEREQ
grant create any cluster to EMEREQ
grant create any context to EMEREQ
grant create any index to EMEREQ
grant create any indextype to EMEREQ
grant create any procedure to EMEREQ
grant create synonym to EMEREQ
grant create trigger to EMEREQ
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6165 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
grant CTXAPP to EMEREQ
STEP Import all emerge data info into SAP EBP system
su - oraltsidgt
imp emereqltSee WARPgt file=oracleltSIDgtsapreorgexportemedmp full=y indexes=y grants=y commit=y
log=tmpimportbuglog
STEP Test connection
Start the J2EE processes
Logon to SAP
SMICM agrave Administration agrave J2EE Server agrave Send Hard shutdown agrave With Restart
it can take up to 5 minutes before the homepage is available
Test connection httpltservername + dnsgtemergeloginhtm
441 Run sapdba_rolesql to fix Oracle privileges for OPS$SIDADM
The OPS$SIDADM Oracle account must have the privilege of SAPDBA to allow the DBA housekeeping jobs to work properly
You must run the sapdba_rolesql First you must make sure you have the proper script
On the target server
su oraltsidgt
cd localbinsapdbcopy
grep OPS sapdba_rolesql
V_User = OPS$ || ampamp1 || ADM
V_User = OPS$SAPSERVICE || ampamp1
The results should look like the above
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6265 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
sqlplus systemltpasswordgt
sapdba_rolesql ltSIDgt UNIX
sqlplus as sysdba
select from dba_role_privs where grantee like OPS
The output should look like the following
GRANTEE GRANTED_ROLE ADM DEF
------------------------------ ------------------------------ --- ---
OPS$D04ADM SAPDBA NO YES
OPS$D04ADM CONNECT YES YES
OPS$D04ADM RESOURCE YES YES
442 SAP INFOCUBE INDEXES REPAIR
Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 35 and below)
Some background BW systems are running with NOLOGGING configured on Oracle level This means that the creation of indexes
are not captured in redologs While BW droprecreates indexes quite frequently as part of dataloading lots of index creations are not
in the redologs When rolling forward a database during a refresh these indexes will get corrupted blocks The solution is to
droprecreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance
would go down NOLOGGING is also the SAP recommendation for BW systems)
In BW system client
SE38 agrave SAP_INFOCUBE_INDEXES_REPAIR agrave Program agrave Execute in background
This can and probably will run for hours You can however safely continue with the next steps There is no need to wait for this
program to finish
443 Convert logical system names(BDLS RUN)]Old logical system name = ltSSIDgtCLNTltClient numbergt
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6365 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
New logical system name = ltTSIDgtCLNTltClient numbergt
Login to the Production client and navigate to transaction BDLS and proceed to schedule all LSN conversions from Source to
target(There might be more than one BDLS runs depending on LSNs which exist in the system which indeed depends on clients
too)
Be sure to select radio button Conversion of client-dependant and client-independent tables
Deselect the check boxes Test Run and Existence check on new names in tables
Program agrave Execute in background
You will get a warning LSN already exists press enter to ignore (dont click on the warning it wont work)
This will run for quite a while
It is not feasible to wait on the outcome of the first run before starting the second run as too much time would be wasted Therefore
scheduled the BDLSs one hour behind eachother In this way the BDLS runs can still hit the same table simultaneously (and
therefore slow down) but overall it will be quicker than running sequentially
The output of the SM37 job does not give all the information However the application log of SAP catches the actual output of
BDLS
Go to the application log via transaction SLG1 agrave enter appopriate dates agrave Execute
Expand the row as below and doubleclick on the line Problem Class
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6465 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |
This page was exported from - SAP ADMIN Export date Thu Feb 23 60621 2012 +0000 GMT
Click on the Choose button to see the actual output of the BDLS run
If there persist a problem in BDLS Conversion we can proceed converting them from SQL prompt too
Output as PDF file has been powered by [ Universal Post Manager ] plugin from wwwProfProjectscom | Page 6565 |