This page was exported from - SAP ADMINExport date: Thu Feb 23 6:06:21 2012 / +0000 GMT Database Refresh Procedure 1 Introduction A Database refresh/copy consists of three sections or units of work: - Pre Copy steps - Restoring/Copying 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 5.3 platform. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.com | Page 1/65 | This page was exported from - SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 2 Pre Copy steps 2.1 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) 2.2 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 www.ProfProjects.com | Page 2/65 | This page was exported from - SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT df -k | grep sapdata | sort Also make sure that the space in origlogA & B and mirrlogA & 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 system v The size of /sapdb/<TARGET SID> should be greater than or equal to /sapdb/<SOURCE SID> in the live cache host Additional Checks for storage inAPO? LCA system v The size of /sapdb/<TARGET SID> should be greater than or equal to /sapdb/<SOURCE SID> in the live cache host Example: If source is SSID and target system is TSID (df ?gt) /dev/lvusp_ssid_002 /dev/lvusp_tsid_002 58.88 70.00 0.97 0.91 57.90 69.09 2% /sapdb/SSID 2% /sapdb/TSID v In both systems go to T-code LC10 -> Live cache Monitoring -> Administration -> Configuration -> 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 www.ProfProjects.com | Page 3/65 | This page was exported from .SAP ADMIN Export date: Thu Feb 23 6:06:21 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 2. Below is an example of what the key would look like) <trusted server>. using Shift-G in vi.com | Page 4/65 | .<domain name> ssh-dss AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmu/eVE9+4t6Wd5sGRwWNAdyDtFF9ux/CKcgeK8o2OPFSeCcuNi w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6W/EXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRsp/Mw0 jsbBAAAAFQD4kBx7i/53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.pub (Example shown below) ssh-dss AAAAB3NzaC1kc3MAAACBAPyNO8hfzk9+WBS5nOSAhmu/eVE9+4t6Wd5sGRwWNAdyDtFF9ux/CKcgeK8o2OPFSeCcuNi w8d3NOHLCLHNjB6lH8V3L9R8+7b8hDpfpZ4fxcYKlP6W/EXHyWuv8DrEyCdyaFbYNzul7JaJx1j5lOEUa6TFJDbouqRsp/Mw0 jsbBAAAAFQD4kBx7i/53NeFZ7C2GXIEDL+mAuwAAAIBzbYbmh8xDG0DQzMt6Ury0aqyDoawbnEq9uAlulvcheivO2VnZfqO 9HEFd18JPIXTLWTCjtriE/6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrg/P0v WumYtGEw/n16tUr9LxRwAAAIEAjf+4Eis9/ippFAeNIVfKL28KlYrqlcdBHIhE/wy6/HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1/F7zwxQ5QLyB5puKNs05qofObC4vpfC3R/kOFMQ = (NOTE : The hostkey above is a single line?NOT 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 /etc/ssh # vi ssh_known_hosts (go to the last line of the file.3 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. along with the fully qualified DNS name. 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 /etc/ssh # cat ssh_host_dsa_key.<trusted server>.ProfProjects. enter the name of the trusted server. followed by the hostkey found in the previous step. and open a line at the bottom using the ?o? vi command) (using existing lines as a reference. /oracle/<SID>/sapdata1/cntrl and /oracle/<SID>/sapdata2/cntrl .shosts file to allow root access # vi /.ls ?l /oracle/<TSID>/sapdata1/cntrl . so the generic format is as follows : <trusted server>. 2.4 Verify Oracle control file directories on target server Logon to the target system .ls ?l /oracle/<TSID>/cntrl .instead of 9 lines. it should be a single long line On the trusting server.cd dbs The following command will display three directories where the controlfiles will be written grep dbf init<TSID>.<domain name> root By doing so now your Source server has become the Trusting server and Target system has become the trusted server.shosts (include a line of the format : <trusted server>.ls ?l /oracle/<TSID>/sapdata2/cntrl If not ensure that these directories are created and a copy of Control file is moved to them. YOU MUST FILL THIS VALUE IN OR IT WILL NOT WORK Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. update the /.<trusted server>.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 9HEFd18JPIXTLWTCjtriE/6zpsgUR9oR2PCMbNW9S+PtIZ5HZ4NbTlCvF7gNxlibZ4sAB5e6zbb3Xso59K9H6m0lFNZFKrg/P0v WumYtGEw/n16tUr9LxRwAAAIEAjf+4Eis9/ippFAeNIVfKL28KlYrqlcdBHIhE/wy6/HEvAoNZ3fdxMjzvgn8gtEpzsy1+gql3o00u SJiNJKcMDzREfPqqxtu7lttOT9VYFM9mGFaLW+eBWh+6I+9HHdewS4A1/F7zwxQ5QLyB5puKNs05qofObC4vpfC3R/kOFMQ = NOTE : The hostkey above is a single line?NOT multiple lines.<domain name> ssh-dss <hostkey from trusted server> Concatenate all the lines in the file . Execute transaction SCC8 Select profile: SAP_USER Target system: use ? DUM?. Log on to the SAP target system clients that need to have users preserved.This page was exported from .ora According to the standards they should be in /oracle/<SID>/cntrl.5 Export Target SID/Client Users & retain user master records This step only applies to those projects where the user master records are to be retained in the target system. 2.com | Page 5/65 | .ProfProjects.as ora<target_sid> . On the Info Client Export screen.This page was exported from .old: . . 2) Sometimes user master export shows COMPLETED status at SAP level but runs for a few minutes in the operating system.<SID>? ?exec ls ?lastr {} . select any SID except the SID name you are exporting from. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www./cofiles .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Click execute button. If any files are found. Always look to the date/time field to verify the correct logfile./data .ProfProjects.You must delete all cofiles./cofiles -name ?*00017. At first the log may indicate an error in the processing. and log files with the same number before starting the new export./data . MAKE SURE IT COMPLETES WITH RETURN CODE < 8./cofiles ?name ?*00017. Just wait about 3-5 minutes and check again. Also. return to SAP screen and click the green check mark to start the export. click continue button and STOP AT INFO CLIENT EXPORT SCREEN! Perform the following before proceeding with SAP screen. Therefore always check the file size until it reaches the saturation at operating system level. data files.cd /usr/sap/trans ./log ?name ?*00017. then remove them (consult if you aren?t sure) else rename them with extension .Now. Verify that the files were successfully removed: . after SCC3 indicates it?s successful you must check that the transport is completely exported using SE03.find ./data . YOU MUST FILL A SID IN OR IT WILL NOT WORK.find ./cofiles . verify they are the correct files and can be removed. STOP! and document the transport number displayed with the format: <sid>KTnnnnnnn This step will fail if files exist in the transport directories with the same number.com | Page 6/65 | . Remarks: . Here?s an example taken to find everything related to transport su ? <sid>adm ./data . the file size should become constant if you again trigger the command. Note: 1) Monitor the job using SCC3 logs.find . Login as sidadm user at os level cd /usr/sap/trans/ find ./log ?name ?*00017.If DUMMY system is not there.<SID>? ?exec rm {} .SID? ?exec ls ?lastr {} .<SID>? -exec ls -lastr {} . This page was exported from . SAPconnect. ITS. The contents of the Secure store can be viewed by using tx SECSTORE or SE38 RSECADMIN.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 2. For Eg Secure store tables are also exported. HTTP(S). Create a transport with the following object list: Program ID Object Object Name Table Key Description/Purpose 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 www.6 Save data for RFC.com | Page 7/65 | . SSO. SCOT and Logical Printers. SCOT and Logical Printer Server tables Here we Export the tables relevant to RFC. ITS. HTTP(S). These tables contain the RFC passwords. In earlier versions this was included in table RFCDES. SSO.ProfProjects. SAPconnect. com | Page 8/65 | .This page was exported from .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT R3TR TABU RFCDESSECU * SNC extensions for RFC destinations R3TR TABU RFCDOC * Description of Possible RFC Connections (->RFCDES) 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 www.ProfProjects. SAP ADMIN Export date: Thu Feb 23 6:06:21 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 www.ProfProjects.com | Page 9/65 | .This page was exported from . com | Page 10/65 | .ProfProjects.SAP ADMIN Export date: Thu Feb 23 6:06:21 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 www.This page was exported from . This page was exported from .SAP ADMIN Export date: Thu Feb 23 6:06:21 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 www.com | Page 11/65 | .ProfProjects. com | Page 12/65 | .ProfProjects.SAP ADMIN Export date: Thu Feb 23 6:06:21 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 www.This page was exported from . This page was exported from .SAP ADMIN Export date: Thu Feb 23 6:06:21 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 www.ProfProjects.com | Page 13/65 | . ProfProjects.Press ?Display ß> Change? do be in change mode .Click on New entries. one per line Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.SAP ADMIN Export date: Thu Feb 23 6:06:21 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 .Write down the transport number Click on transport request .com | Page 14/65 | . . where you have enough authorizations .Uncheck any other request type Enter Short description .Enter entries as listed in above table.Save .For Target system logon in SAP client.This page was exported from .Enter target (DUM) or enter a SID other than the target SID .Press ?Display object list? button .Check Request type: Transport of copies .Goto SE01 Create button . dmp tables=<tablename>. ?Entry is made in transport request? means successful creation.Log on to one of the SAP target system client 002 (or proper one for BW) with personal id. Save and go back 15. then click on <Insert Line>? 12. .A prompt for a transport number create a new one and press enter. 14.su ? ora<sid> {sapsid = SCHEMA (table owner) of sap tables} exp <sapsid>/<password> FILE=/oracle/<SID>/sapreorg/expdat. double click on each object to drill down to the key 11. select workbench request.Transport .Enter a short description. Check the transport log. go to Edit Transport > Transport All . . .7 Preserve printers There are two options to preserve the printers : . Click on ?Release directly?.Click on Change Icon . Select Request ? Request header. After you have entered all objects.Click Output Devices . 11. 12.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 10.SPAD . <tablename> buffer=1024000 grants=N indexes=N consistent=Y compress=N 2.This page was exported from .In menu. Repeat step 9-12 for all the objects. Enter '*' in each of the key field lines and save. When ?application? or ?temporary tables? which you want to export giving errors then you have to export them via Oracle : . Select the transport request and 16.ProfProjects. Correction : Click on <Edit>.Press enter 10.Local file Transport : . Execute transaction SE01. and click on display. enter a valid target = DUM Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. In the message window.Press enter at screen prompt . 13.com | Page 15/65 | . Click on the transport number. 17. 18. Click on execute Please check in your txt file : c:/apps/reserveprintersSID. followed by the back button.com | Page 16/65 | .ProfProjects. Press Release. 19.In menu.Export/Import file name : Fillin the destination of your C -drive where you can store the file for the printers.Export all data info from BugsEye instance Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. go to Edit --> Transfer --> Export .Click on the line of one of the printers . Press the save button in the popup menu. Click SAVE and ignore any errors. Press the save button in the popup menu. The task should now be displayed in a darker color. Local file : . 17. 14. followed by the back button.Click on Change Icon . Click on the Development/correction task number. 15. Example : c:/apps/reserveprintersSID.Log on to one of the SAP target system client 002 (or proper one for BW) with personal id.This page was exported from . Press Release. Select Execute export and Generate log 11. Click on the transport number. .Select Frontend computer .txt if the printers are there. Now the transport has been released.SPAD . 16.Click Output Devices . 2.txt .8 Backup BugsEye & eMerge data (Please don't forget this otherwise it will only export 1 printer) if the BugsEye data & eMerge data needs to be saved.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 13.Select Export 10. If the customer agrees to save the data do the following: For BugsEye: . For Output device : Fillin * 12. Export all data info from eMerge instance su ? ora<sid> exp emereq/<See WARP> file=/oracle/<SID>/sapreorg/exporteme.ora<sid> cd /oracle/<SID>/sapreorg (need at least 2GB free for SAPMIWDB) exp sap<sid>db/<Password> file=/oracle/<SID>/sapreorg/exportj2ee.9 Export J2EE Database Schema The schema of the J2EE 6.dmp full=y indexes=y grants=y log=/tmp/exportbug.This page was exported from . mode (2) U(sers) .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT su ? ora<sid> exp bugreq/<Password for bugreq user> file=/oracle/<SID>/sapreorg/exportbug. Export the SAP<SID>DB or SAPMIWDB schema using schema password su . export table data yes . compress extents yes For eMerge (for GSAP) . export grants yes .dmp full=y indexes=y grants=y log=/tmp/exportj2ee. mode (2) U(sers) .dmp full=y indexes=y grants=y log=/tmp/exporteme.log Note: wait for the prompt and enter the below values. compress extents yes 2.log Note: wait for the prompt and enter the below values. .log Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. export table data yes .00 must be saved to restart the engine after the system has been refreshed.40/7.com | Page 17/65 | . export grants yes .ProfProjects. . Select the Display All BIA Indexes button or select (F6) Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.11 Check & Preserve details of PSAPTEMP datafiles Execute the following command at Oracle level for details of tempfiles. export grants yes . Start transaction /nRSDDV in the BI instance.This page was exported from .(bytes/1024/1024/1024) from dba_temp_files where tablespace_name ='PSAPTEMP'.ProfProjects.com | Page 18/65 | .ora<SID> sqlpls ?/ as sysdba ? file_name.10 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. export table data yes .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Note: wait for the prompt and enter the below values. 2. compress extents yes In case none of the passwords work change the schema password as follows: sqlplus ?/ as sysdba? alter user sapmiwdb identified by <Password>. path & size of the temp files for the existing system and preserve the details for comparison after refresh: su . 2. .12 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. 2. we shall be Scheduling it later. mode (2) U(sers) . Therefore. where you have enough authorizations Execute transaction SMLG . RFC server group names are also case-sensitive.For Target system logon in SAP client.For Target system logon in SAP client.ProfProjects.13 Logon Group Names (SMLG and RZ12) Logon group names are used in projects to accomplish logon load balancing. 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. Screenshot: 2. used for parallel client copies. where you have enough authorizations Execute transaction RZ04 . These RFC server groups must be restored to their current configuration after the refresh. it is important to note the SAP logon group names in the target system prior to performing the database copy.Execute menu items System => List => Save => Local file => unconverted. .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Take a screen shot of these indexes and copy into a word document and save the document. Save a copy of the screen or write down the logon groups. where you have enough authorizations . .This page was exported from . amongst other things. Save a copy of the screen or write down the logon groups.14 Op-mode Snapshot Again depending on the requestor: normally the same op-mode would be maintained.This will ask for a directory/filename on the local PC to store the information. the logon group definitions will reflect those of the source system. Make note of the directory/filename for use in the post-processing steps Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. Therefore. The Source <SID> and Target <SID> may have different definitions of Op-modes.The logon group name(s) will be displayed on the screen. because after the copy. Proceed as follows: . Logon group names are also case-sensitive. 2. These logon groups are used in the SAP logon pad to automatically assign users to application servers based on currently application server usage.The RFC server group name(s) will be displayed on the screen. To retrieve the logon group name(s): .For Target system logon in SAP client. where you have enough authorizations Execute transaction RZ12 .com | Page 19/65 | .Double-click on one of the Op-modes or click instance/op-mode in menu bar . it is important to take a snapshot of the Op-modes in the Target <SID>. RFC server groups are. After a successful database copy the Op-modes in the Target <SID> will be replaced with the Op-modes in the Source <SID>.For Target system logon in SAP client. Make note of the absolute_path/filename (saplicense. If the field Logical System is not blank.15 Check and Save Logical System Definition Execute SCC4.Log on to the target system at UNIX as <sid>adm . Proceed as follows: . . After a successful database copy the SAP Licenses in the Target <SID> will be replaced with those in the Source <SID>.x Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.com | Page 20/65 | . .18 Determine SAP version This step is important in order to follow these instructions as they are version dependent.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 2.This page was exported from .17 SAP License Snapshot The Source <SID> and Target <SID> may have different list of SAP Licenses loaded in the system. and double click on all clients. document the name with each client. the entries of the DBA Planning Calendar must be saved.Click red X to exit pop-up. . 2.Log on to SAP with your personal id . . Proceed as follows: .16 Preserve DB13 entries As the DB13 tables will be cleared due to the refresh. the version of SAP is listed in the field named SAP Release (or BasisRelease).Make a hardcopy of the screen and/or save it in notepad.A pop-up screen appears.ProfProjects.saplicense ?show > saplicense_<Target_SID>.Goto DB13 on the target system.Enter ?STAT in the transaction field at the top left corner of the screen and press enter.save) for use in the Post Copy Steps. should be in /local/users/<sid>adm 2.save . 2. Therefore. it is important to take a snapshot of the SAP Licenses in the Target <SID>. Double click on the entry .com | Page 21/65 | .SAP RELEASE: ____________________ 2. 3 3.`date +?YYYYMMMDD?`(like root.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT .19 Preserve TXCOM table entries .SM54 .Log on to SAP with your personal id in client 002 .Take a screen shot of the entry and copy into a word document and save the document.2005JAN01) Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. 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 .crontab. addons and other applications we might have to upgrade the target system accordingly after refresh if required.ProfProjects. And also note that if source system is at lower level in terms support packages.1 Restoring/Copying the database Procedure to Refresh Database from the online/offline Backup Disable crontab for root on target system Disable root?s cron to make sure that nothing runs that might have an impact on the refresh <upgrade_server> # crontab -l > /local/etc/sapadm/root.This page was exported from .crontab. lsnrctl stop .This page was exported from .rm * Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.su ? ora<sid> .cd /oracle/<SID>/saparch .<sid>adm .cd /oracle/<SID> .stopsap . CCMSR etc) Bring down the J2ee Engine Access transaction SMICM Perform the following path: Administration > J2EE Server > Send Hard Shutdown > Without Restart Bring down SAP and clean up the system .rm ?r sapdata* .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT <upgrade_server> # crontab ?r Actions on Target System Bring down all the applications of SAP( for ex:: Patrol.ProfProjects.su . ControlM agent.saposcol ?k .com | Page 22/65 | . ProfProjects.anf <target system>:/oracle/<target SID>/sapbackup/ for standby (if applicable) 2.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT If this isn?t working then use : Check : find /oracle/SID/saparch -name "*" -exec ls {} .cd /oracle/<SID>/cntrl .anf> or more <*.This page was exported from .dbf Copy needed files from source system to target system On Source/Standby systemroot>cd /oracle/<SID>/sapbackup root>more <*.anf (or . 1.rm *.anf <target system>:/oracle/<target SID>/sapbackup/ or scp xxx.aff> for standby (if applicable) To make sure that the backup by which you need to restore is successful. On Target system : root> chmod g+r *. On Source/Standby system : root> cd /oracle/<SID>/sapbackup root> scp xxx. .aff file for standby (if applicable)) Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.com | Page 23/65 | . If it can find the files then use this : find /oracle/SID/saparch -name "*" -exec rm {} . This is needed to start the restore. 2.SCP the backup file needed from source system to target System.com | Page 24/65 | .utl root> chown ora<target sid>:dba init<source sid>. Change the permissions and ownership of Backup file. We need to change Config_file parameter.utl . root> cd /oracle/<sid>/dbs Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. 1.anf (or . root > vi init<source sid>.utl 3. 1.Change the permissions and ownership of init<source sid>.aff file for standby (if applicable)) .SCP init<sid>.utl Change CONFIG_FILE parameter as :CONFIG_FILE /oracle/<target sid>/dbs/init<source sid>.bki .utl <target system>:/oracle/<sid>/dbs/ 2.This page was exported from . On Source system .utl . On Target system root> chmod g+r init<source sid>.utl file from source to target.Edit init<source sid>. .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT root> chown ora<target sid>:dba *. On Source system: root> scp init<sid>.ProfProjects. bki <target system>:/oracle/<target sid>/ dbs/ 2.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT root> scp init<source sid>.ProfProjects.Change permissions & ownership of init<source sid>.Change the permission/ownership of trace file. sqlplus > exit .bki On source system 1.Scp the trace file to the target system.sql . .com | Page 25/65 | .To create the trace file.sql .bki from source to target .This page was exported from . Editing the tracefile on target system . ora<sid> sqlplus ?/ as sysdba? sqlplus > alter database backup controlfile to trace.bki root> chown ora<target sid>:dba init<source sid>. On Target system : root> cd /oracle/<sid>/dbs root> chmod g+r init<source sid>.SCP init<source sid>.sql root> chown ora<target sid>:dba createcontrol.On Target system root>cd /oracle /<SID> root> chmod g+r createcontrol.scp <trace file> target system: /oracle /<SID>/createcontrol.root> vi <trace file> Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.scp this file created in /oracle/<SID>/saptrace/usertrace to the target system /oracle /<SID> . .bki . This page was exported from .com | Page 26/65 | .data3' Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.Comment the 3 lines. This can be done by using vi command ? :1. because later you will need them again.Change all source sid to target sid.To remove all the unwanted lines.Remove all the starting lines of tracefile until STARTUP NOMOUNT 3. All the lines are to be removed until STARTUP NOMOUNT.data4' SIZE 1999M REUSE AUTOEXTEND OFF. . Check by table V$datafile.ProfProjects. If yes. at the bottom of the tracefile ? #RECOVER DATABASE #ALTER DATABASE OPEN RESETLOGS. Note :Make sure no new datafile has being added after the backup that is being used.Remove also all the 2 lines. Example: ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/PC6/sapdata6/temp_4/temp. which is present at the bottom of the tracefile. Edit the 2nd line as said. beginning from first line. .The file has been created double. We do this manually later. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/PC6/sapdata6/temp_3/temp. .This is an easy command to change all the sid of source system to the sid of target system. remove the first file . 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.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT . Edit the 2nd line ? CREATE CONTROLFILE REUSE DATABASE "SOURCE SID" NORESETLOGS ARCHIVELOG to CREATE CONTROLFILE SET DATABASE ?TARGET SID? RESETLOGS NOARCHIVELOG .To go into vi mode .$s/<source sid>/<target sid>/g . utl -b <backupfile>-m full ?c force? D for standby: su ? ora<sid> -c ?brrestore -r init<source sid>.for standby restore: brrestore -r init<source sid>.at now su ? ora<sid> -c ?brrestore -r init<source sid>.This page was exported from .as root .ProfProjects.chown ?R ora<sid>:dba sapdata* Rename the database Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.data1' SIZE 1999M REUSE AUTOEXTEND OFF.cd /oracle/<SID> .com | Page 27/65 | .for normal restore: brrestore -r init<source sid>.data2' SIZE 1999M REUSE AUTOEXTEND OFF. Restore database from Storage Start restore on targetsystem in the foreground with: .utl -b <backupfile>-m all ?c force? D After the restore is finished (on target system): . ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/PC6/sapdata6/temp_1/temp.as root .utl -b <backupfile> -m all ?c or Start restore in the background with: .su ? ora<sid> . ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/PC6/sapdata6/temp_2/temp.utl -b <backupfile> -m full ?c .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT SIZE 1999M REUSE AUTOEXTEND OFF. offline redologs files needs to be restored from Storage.com | Page 28/65 | . To know what files you will need you can look in the sourcesystem?s saparch directory. or a point-in-time recovery is needed).log chmod 660 arch<targetSID>.scp /oracle/<sourceSID>/saparch/arch<sourceSID>. You can also look in SAP (source system) with transaction DB12. To restore redologs you will need to copy the arch<sourcesid>.dba arch<targetSID>. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.chown ora<sid>. after the restore of an online backup.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT On Target System: . to apply all required redologs automatically type AUTO after completion we can now open the database by: sqlplus> alter database open resetlogs.g.sql Check in the /oracle/<SID>/saptrace/background/alert_<SID>.log .log to the targetsystems saparch directory .mv arch<sourceSID>.log arch<targetSID>. or sqlplus> recover database until time '2004-05-21:10:00:00' using backup controlfile.This page was exported from .su ? ora<sid> . Look for the file arch<SID>. Restoring offline redologs In case a recovery of the database is needed (e.log for any errors.log Recovering the database There are two ways of recovering the database by CANCEL (you decide how many logfiles you want to apply) or by TIMESTAMP.log <targetsystem>: /oracle /<targetSID>/saparch On target system: .log and decide which files you will need by timestamp.ProfProjects.sqlplus ?/ as sysdba? . sqlplus> recover database using backup controlfile until cancel.@createcontrol. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/SSID/sapdata6/temp_1/temp. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/SSID/sapdata6/temp_3/temp.com | Page 29/65 | .data4' SIZE 1999M REUSE AUTOEXTEND OFF.Change sourceSID to targetSID .data1' SIZE 1999M REUSE AUTOEXTEND OFF.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Checking the database First check if we can stop and start the system without problems. Example for 4 data files in sapdata6: ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/SSID/sapdata6/temp_4/temp. .This page was exported from . Recreation of the tempfiles which you saved at step Error! Reference source not found. Sqlplus> shutdown immediate Sqlplus> startup Also check the alert_SID.data3' SIZE 1999M REUSE AUTOEXTEND OFF.Create the needed subdorectories in the sapdata filesystem(s) cd /oracle/<targetSID>/sapdata6 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 www.data2' SIZE 1999M REUSE AUTOEXTEND OFF. Recreation of the tempfiles We need some additional action for BW.log for any errors. ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/SSID/sapdata6/temp_2/temp.ProfProjects. . Therefore.Sqlplus> ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/TSID/sapdata6/temp_3/temp. .data1 /oracle/SID/sapdata5/temp2. Making locally managed temporary datafiles non-sparse The added datafiles in the previous step are locally managed temporary datafiles.data2' SIZE 1999M REUSE AUTOEXTEND OFF.sqlplus ?/ as sysdba? . when the reserved space is claimed by newly added ?normal? datafiles.) This can lead to issues.ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/TSID/sapdata6/temp_1/temp. These kinds of datafiles are created as sparse files (they can grow to the configured size.shutdown immediate. but initially this amount of space is not yet claimed on the OS level. Find enough space (usually 2 Gb is enough) in another filesystem than where the datafile is currently located.Sqlplus> ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/TSID/sapdata6/temp_4/temp.This page was exported from .data1' SIZE 1999M REUSE AUTOEXTEND OFF.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Create the tempfiles: . .ProfProjects.data1 temp2_1/temp2. This will make the datafile non-sparse. cd /oracle/SID/sapdata3 ora<sid> 40> mv temp2_1/temp2.com | Page 30/65 | .su ? ora<sid> .sqlplus ?/ as sysdba? .data1 ora<sid> 41> mv /oracle/SID/sapdata5/temp2.data4' SIZE 1999M REUSE AUTOEXTEND OFF.exit.data3' SIZE 1999M REUSE AUTOEXTEND OFF. .su ? ora<sid> . these files need to be change to non-sparse files.Sqlplus> ALTER TABLESPACE PSAPTEMP ADD TEMPFILE '/oracle/TSID/sapdata6/temp_2/temp. Here is an exampleto move the files. The datafile needs to be moved to this other filesystem and back again. .data1 Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. /CHDBPASS. Change SAPR3 into SAPMIW .data2 /oracle/SID/sapdata5/temp2.102 .select option a./CHDBPASS. Set Password as relevant .817 . su ? ora<sid> . Change tablespace PSAPUSER1D into PSAPMIWUSR . Create new OPS$ user & drop old OPS$ user We need to generate a new OPS$ user. For c d use system password Later in the post step you can proceed to grant permissions to the user created Check Archive Log Mode Check if the database log mode is set on archive mode with sapdba.cd /sapmnt/<SID>/exe vi CHDBPASS..This page was exported from .com | Page 31/65 | .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT ora<sid> 40> mv temp2_2/temp2. Restart the database.ProfProjects. toggle database log mode.c and d . Start Oracle Listener The Oracle Listener should also be started Orasid> lsnrctl start Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. option a c d. .data2 temp2_2/temp2. If not.data2 You can now see that the files are non-sparse and use the entire space in the filesystem. for a use schema password.data2 ora<sid> 41> mv /oracle/SID/sapdata5/temp2.102 . If the above condition persist you can proceed with steps specified below Backup Source controlfile to trace .2 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).ProfProjects. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.This page was exported from .com | Page 32/65 | .alter database backup controlfile to trace.quit.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 3.sqlplus ?/ as sysdba? . .Log on to the source (or standby database) system?s as ora<sid> . dbf . they must be stopped first: Log on to the application servers of the target instance as <sid>adm.sqlplus ?/ as sysdba? .Write down the name of the trace file created (we will refer to it as <tracefile>) Stop Target SAP and Oracle Note: Downtime starts here If the target SAP Instance has any application severs.dbf Stop the hotstandby database .rhosts file in the target system contains a row like: <hotstandby system> root Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects.rm *.rm *.rm ?r sapdata*/* .shutdown immediate.cd /oracle/<sourceSID>/saptrace/usertrace .com | Page 33/65 | .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT .ls ?altr . You don?t want to remove datafiles belonging to another SID (like the standby database?) . Copy the database from hotstandby Note: If the target system is not on the same server as the hotstandby.cd /oracle/<targetSID> . make sure that /.This page was exported from .cd /oracle/<targetSID>/cntrl .Logon to the hotstandby system as ora<hotstandbysid> .Logon to the target system as root . Stopsap Logon to the target database server as <sid>adm Stopsap Remove the database existing on the Target System Caution: Be careful with following commands! Look twice before pressing enter.cd /oracle/<targetSID>/saparch . *sapdata([0-9]*)$/1/' ` do echo $(date): ?Copying /oracle/<hotstandbySID>/sapdata${i} filesystem?? scp ?p ?r /oracle/<hotstandbySID>/sapdata${i}/* <target_server>:/oracle/<targetSID>/sapdata${i} & done | tee -a /tmp/hotstandby_copy. please add this line and don?t forget to remove it when the procedure is completed. lsfs | grep sapdata | while read lv a fs rest do chfs -a options=rw.nodev.log D Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. the cio option needs to be switched off because otherwise the "cp" command will be extremely slow. if the hotstandby system is on MC-II platform.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT If not. it may be wise to copy and paste. please skip this step and proceed with the next step.This page was exported from . from the document into the UNIX terminal window because it may be difficult to identify whether you are using the proper character . As such. number.$(date +%Y%m%d%H%M%S). line for line. When performing the steps below. Therefore.nosuid $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 <hotstandbySID> | sed 's/. or letter in some cases.com | Page 34/65 | . 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. to prevent a very slow refresh from the hot-standby system. On MC-II systems. Please ensure that the number of sapdata* filesystems for the target SID matches the number of sapdata filesystems for the hotstandby SID?both in number and in size to ensure there is sufficient capacity for the copy process. the conccurent io (cio) option is turned on on the sapdata and origlog/mirrlog filessytems.ProfProjects. Now.SAP ADMIN Export date: Thu Feb 23 6:06:21 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 <hotstandbySID> | sed 's/.*sapdata([0-9]*)$/1/' ` do echo $(date): ?Copying /oracle/<hotstandbySID>/sapdata${i} filesystem?? cp -p -r /oracle/<hotstandbySID>/sapdata${i}/* /oracle/<targetSID>/sapdata${i} & done | tee -a /tmp/hotstandby_copy.nosuid.ProfProjects. if the cio option is switched off in one of the above steps.cd /oracle/<targetSID> .chown ?R ora<targetsid>:dba sapdata* Edit the trace file on target system Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. it must be turned on again. run the following commands on both the hotstandby and target systems:lsfs | grep sapdata | while read lv a fs rest do chfs -a options=rw.$(date +%Y%m%d%H%M%S).nodev. It makes sense to check for file sizes and compare with the source files. To do that.This page was exported from .cio $fs umount $fs mount $fs done Change ownership on restored files Logon to the target system as root .com | Page 35/65 | .log D Check if all files are copied successfully (this should be the case if there is enough space in sapdata filesystems). ProfProjects.tail ?f /oracle/<targetSID>/saptrace/background/alert_<targetSID>. Create controlfile and open the database Open another session and tail the alert log: . You want the last one. at the bottom of the tracefile.@/tmp/<tracefile> Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.In your initial session: . You will need to manually execute these statements later. #RECOVER DATABASE #ALTER SYSTEM ARCHIVE LOG ALL.data1' SIZE 52420608 REUSE AUTOEXTEND OFF.Logon to the target system as ora<sid> . #ALTER DATABASE OPEN. Perform the following changes: Remove all the starting lines of tracefile until the STARTUP NOMOUNT that precedes the command: CREATE CONTROLFILE REUSE DATABASE <SID> RESETLOGS.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Use an editor (like vi) to change /tmp/<tracefile>.$s/<sourse sid>/<target sid>/g Change the 2nd line from CREATE CONTROLFILE REUSE DATABASE <SID> RESETLOGS NOARCHIVELOG to CREATE CONTROLFILE SET DATABASE <SID> RESETLOGS NOARCHIVELOG Comment all lines below and including the following 3 lines. one with NORESETLOGS and one with RESETLOGS.Logon to the target system as ora<sid> .sqlplus ?/ as sysdba? . This can be done by using vi command :1.This page was exported from . Make sure to comment and make note of any statements at the bottom that have the key word TEMPFILE like the following. Change all source sid to target sid. Save the file and exit vi. Note: With ORACLE 9 the trace file will appear to have duplicate data.com | Page 36/65 | . #ALTER TABLESPACE PSAPPAT1I ADD TEMPFILE '/oracle/SID/sapdata4/pat1i_1/pat1i. The only difference is that it has two stanzas.log . .startup mount . You can open another window and cut-paste the statements into the sqlplus program. The following step ?Start Oracle listener? is only needed if the database is restored from standby.. Caution: Keep an eye on the alert log. the required redo logs must be applied to the database).shutdown immediate . .sqlplus ?/ as sysdba? . You don?t really have to apply logs. (NOTE: If an on-line backup was used. .Logon to the target system as ora<sid> . Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.alter database archivelog.sqlplus ?/ as sysdba? .recover database using backup controlfile until cancel.lsnrctl start Note: DO NOT START SAP HERE YET.com | Page 37/65 | . Start Oracle Listener Start the listener if it?s not already running: .Logon to the target system as ora<sid> .exit - Restart the database If the target database is supposed to run in ARCHIVELOG MODE.ProfProjects. Execute all the ? ALTER Tablespace <xxxx> ADD TEMPFILE ?. you have to activate it. .Following line ALWAYS: .Following line ONLY if you have to run in ARCHIVELOG MODE: .alter database mount standby database exclusive.startup nomount.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT . as eventual errors can end up in a RUNNING but inconsistent database! Restart the Standby database .Logon to the hotstandby system as ora<sid> .This page was exported from .alter database open resetlogs. Make sure they execute successfully.alter database open. Cancel this immediately. .? statements from step 0. c and d) Note: if The CHDBPASS.102 (Select option a. Perform the following steps: Logon to the target system as ora<sid> sqlplus ?/ as sysdba? drop user ops$ora<SID> cascade.com | Page 38/65 | .ProfProjects.This page was exported from . the commands to create the OPS$<SID>ADM account must be run manually. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. Therefore.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Create OPS$<SID>ADM user and grant sapdba role to First start Oracle (if not already started): Logon to the target system as ora<sid> lsnrctl start sqlplus internal startup exit Go to /sapmnt/<SID>/exe and run CHDBPASS. create user ops$ora<SID> identified externally default tablespace psapuser1d temporary tablespace psaptemp.817 or CHDBPASS.817 file is not available. ProfProjects. create table ops$<SSID>adm. drop user ops$<SID>adm cascade.resource to ops$<SID>adm. grant dba. exit Also the passwords for sapr3.com | Page 39/65 | . and system must be set.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT grant dba. sys. create user ops$<SID>adm identified externally default tablespace psapuser1d temporary tablespace psaptemp.resource to ops$ora<SID>.sapuser.connect.sapuser as select * from ops$<TSID>adm.This page was exported from . Run the following commands: Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.connect. exit Check for connectivity to the database with the following command as <sid>adm: R3trans -d 4 Post-Copy Steps 4. commit. DON?T JUST COMMENT the line. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. Logon to the target system as ora<sid> connect / as sysdba.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Find current passwords from warp . completely remove it. alter user sys identified by passwd. update ops$sidadm.This page was exported from .ProfProjects. alter user system identified by passwd.1 Removing hostname entries Remove the entries added during presteps .com | Page 40/65 | .sapuser set passwd = 'passwd'. alter user sapr3 identified by passwd. (this will show an entry for the old DB name) alter database rename global_name to <NEWSID>. This is recommended via notes about the homogeneous system copies (for example see note 201149 for 4.This page was exported from .com | Page 41/65 | .ProfProjects.shosts remove entry: <targetservername> root 4. for example) GLOBAL_NAME -------------------------------------------------------------------------------SID. (this will now show the right SID.WORLD 4. Change the global name via: su ? ora<sid> sqlplus ?/ as sysdba? select * from global_name.world.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Log on to the target system as root vi /.shosts remove entry: <sourceservername> root remove entry: <targetservername> root Log on to the source system as root (Noted : Not applicable for hot-standby machine) vi /.3 Reset Oracle SYS and SYSTEM password After database copy. which could cause Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.6C and 407123 for 6.2 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). the SYS and SYTEM passwords can become inconsistent with the encrypted password in . select * from global_name.x). ProfProjects.Delete the license from the source system .cat saplicense.Install the license for the target system. 4. .saplicense ?install Answer all questions with values provided by saplicense. 4. the SAP license key database will reflect only the key(s) that were in the source system.g. proceed as follows: Logon to the target system as <sid>adm .This page was exported from . the appropriate license key has to be installed.Click New Licenses . this will not work.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT database backup to fail.com | Page 42/65 | . If the license key is not installed. In order for users to be able to log into the target system.save Note: For NW07 systems with digitally-signed licenses e. Some projects install all of their project license keys in all systems so that this step can be eliminated. Since the files in the /sapmnt/SID/global directory are related to the Oracle database on the system. (find the current SYS/SYSTEM password from warp) su ? orasid sqlplus ?/ as sysdba? SQL> alter user sys identified by password. SQL> alter user system identified by password.5 Cleanup /sapmnt/SID/global Before starting SAP we have to remove the WF_LOG files and other directories in the /sapmnt/SID/global/ directory on the target system. Gchem CRM. all these files can be Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. In the SAP menu choose Administration ® Administration ® SAP Licenses or call transaction SLICENSE.4 Fix SAP License Key After a successful database copy.save . Use this command to remove the files and directories : rm -r /sapmnt/SID/global/* 4.ProfProjects. Stopsap Revert the btc processes to earlier value from 0 and Startsap 4. As this can cause serious issues. . This is done by setting the number of batchjobs to 0.7 Manual run of backup log Before you Proceed please check the saparch directory to see how much free space is available. After starting SAP there is now time to delete all released jobs in SM37.This page was exported from . Su ? sidadm Cdpro We can edit the number of background workprocesses to 0 in instance profile (eg:: rdisp/wp_no_btc=0 can be set in instance profile using vi editor) Startsap Then login to SAP and go to transaction SM37. all batchjobs that were not able to run during the time of the refresh will be released immediately when SAP is started. several customers want these jobs to be prevented from running. wihtout the danger of them being kicked off at the startsap command. These batchjobs can send out purchase-orders etc to actual suppliers.6 Start SAP for the first time When SAP is started after the refresh. Run the backup of logs in order to clean up the SAP directory.8 Re-enable crontab for root on target server Re-enable root?s 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 /local/etc/sapadm 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 www. Cancel all the released jobs to schedule.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT removed when the DB is replaced during a refresh. 4.com | Page 43/65 | . before starting SAP for the first time. .Press ?Post-installation processing? .Run transaction SE06 .This page was exported from . . .Select menu item Program => Execute in background . .com | Page 44/65 | .Confirm ?Do you want to reinstall the CTS?? .Enter Source System SID .ProfProjects.Confirm the next popup box that says ?Adjust with controller?? .Run transaction SE38.Enter RSPO1041(RSPO0041 for 3.1I) in the program field. Domain name(default is DOMAIN_<SID>) and domain description.Click green check. Check if the system is MC II then you have to fillin functional name instead of hostname. the spool requests listed in the Target <SID> will reflect those of the Source <SID>. the transport system needs to be reconfigured. .Select OK or YES to all remaining prompts. . Proceed as follows: Logon to the target SAP .Go to ?Overview?à?Transport routes? .Choose ?Database copy or migration? .`date +?%d%m%Y?` 4. and uncheck Print immediately. Proceed as follows: Logon to the target SAP in client 000 as DDIC .A printer destination screen appears.Validate the value is set to « objects cannot be changed> 4.10 Delete all spool request After a successful database copy.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT # crontab /local/etc/sapadm/root.Go to ?Configuration?à?Adjust with Controller? . and click execute.crontab.Go back to main screen.9 Transport System Configuration After a successful database copy. Therefore. .Click System Change Option button. run immediately. . and the job will begin in a batch process.Press Save . Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. enter LP01 as printer name.Enter the values like the following screen .Run transaction SE06. all spool requests need to be deleted from the Target <SID>.Run transaction STMS Enter Description. except for the DEFAULT.Click No to delete the files from the Op.12 Delete Lock Entries At the time that the backup of the Source <SID> was taken. These Op Modes need to be deleted and the correct Op Modes need to be imported. .Select Instance/Opmodes .This page was exported from . Proceed as follows: Logon to the target SAP . .Click Yes to first prompt to update the database . Proceed as follows: .Run transaction RZ04 . These will have been copied to the Target <SID> after the successful database copy and will need to be deleted. the active profiles listed in the SAP system will be from the source system.Run transaction SM12 .13 Delete Source SID Profile Parameter Files After the database refresh.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 4.Do this for each source system op mode listed. Sys. 4. .Import all profiles from Unix by selecting menu items: Utilities -> Import Profiles -> of active servers. Proceed as follows: Logon to the target SAP .11 Delete Update Entries Logon to the target SAP . .Repeat steps 1-3 for all source system profiles listed in the Profile drop-down list. These profiles need to be deleted and the profiles from the OS need to be re-imported.Select menu items: Profile -> Delete -> All versions of a profile. the target system will contain Operation Modes from the source system.Click the Profile drop-down box and choose a profile (this process must be done for each profile.Erase all entry fields displayed Select Menu Items Lock entry => Delete all 4. there may have been lock entries listed.Erase all entry fields and press enter/execute Delete all entries.PFL).Run transaction SM13 . .com | Page 45/65 | . 4.14 Delete Source SID Op Modes After a successful database copy.Click green check on all versions deleted screen . .Logon to the target SAP .Select a server name and press SHIFT F2.Create the target system op mode configuration(s) by selecting the menu items Settings -> Based on Current Status -> New Instances -> Generate Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects. . Level .Run transaction RZ10.Green back arrow.Delete source system profiles: . Verify the Op-modes with this hardcopy listing.Highlight the Source Logon Group.17 Fix Logon Group Names (SMLG and RZ12) Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.Review the system messages. Select Menu Items Workload => Reorg => Delete Stats file. . (case-sensitive) Run transaction RZ12 . the performance database will reflect that of the Source <SID> and. Proceed as follows: Logon to the target SAP Execute transaction SM21. Click the Delete Group button.Delete Source Logon Groups: .Set the From date/time fields to the date and time just prior to starting the SAP system. exactly as it looked in the snapshot taken in the Pre-Copy steps.Recall the target system?s Logon Group names which were captured in the Pre-Copy steps.Click the SAVE button. should be deleted from the Target <SID>.Check each of the new op modes for correctness. Select the All messages radio button. therefore. a snapshot of the Target <SID> Op-modes was taken and downloaded to a directory/filename on the local PC. Select menu items System logs -> Choose -> All remote system logs.Enter the source server db server name and click Continue . Click the Reread system log button. . 4.Recall the target system?s Logon Group names which were captured in the Pre-Copy steps. Select Menu Items Goto => Performance database => Contents of database Select Delete Data 1 Server button . .Delete RFC Server Groups: Highlight the Logon Group.This page was exported from . In the Pre Copy Steps. . Select NO to update the database Select YES to delete the statistics file 4. Proceed as follows: Logon to the target SAP Execute transaction ST03. Click the Add assignment button In the Logon group field type in the target logon group name. Click the Delete Group button. (case-sensitive) 4.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT .15 Delete Server Specific Performance Data After a successful database copy.16 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. exactly as it looked in the snapshot taken in the Pre-Copy steps. Take action on any messages that may look suspicious. .ProfProjects. Click the Add assignment button In the Logon group field type in the target logon group name.Repeat this for each source app server name. Logon to the target SAP Run transaction SMLG .com | Page 46/65 | . Execute the transaction.In menu.13.Click on the line of one of the printers .This page was exported from .Erase both date fields.18 Re-initialize Import Jobs After the database copy has successfully completed. and ?Ready? radio buttons. This will schedule the needed jobs in each client where transports will be migrated. .Log onto the target system in each of the other clients and repeat previous 2 steps. .SPAD . Run transaction SM37.tp addtobuffer <Transport Number> <SID> .?.15. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. .SPAD . .Login to SAP client 002 . Proceed as follows: Logon to the target system in client 000 as DDIC. go to Edit --> Transfer --> import . Delete All . <client_number> is the default system client or using the Local file.Ignore any errors/warnings Logon to the target system as <sid>adm . .Click on Change Icon . the import jobs used by the tp command may not work properly. ?Released?. Type RDDIMPDP* in the ?Job name? field. Specify job class A or highest priority.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 4. Execute program RDDNEWPP.Select all jobs and click the delete button.Log on to one of the SAP target system client 002 (or proper one for BW) with personal id. Run transaction SE38.cd /usr/sap/trans/bin .ProfProjects.Select Utilities. A message will show up in the status bar indicating the job has been scheduled. It is best to delete these jobs and reschedule them new.19 Restore printers Using the <Transport number> created in step 2. 4.tp import <Transport Number> <SID> client<client_number> U128 Local file : . .Click Output Devices .Type * in the ?User name? field.Only select the ?Sched.Export/Import file name : Fillin the destination of your C -drive where you saved the file of the printers in step 2. For Output Devices. Transport : .com | Page 47/65 | .Click the Change button . Select Import 11. Select Execute import and Generate log 12.Change the category to ?Test? for the client that you just imported the user masters into .20 Import User Master Records After a database copy. For Output device : Fillin * 13.Repeat this step for each client that the user import was performed 4.22 Perform client import post processing (All R3 systems) Steps Prior to Execution of SCC7 In all R3 systems. 4.Execute transaction SCC4 . The transport number was generated in one of the Pre-Copy steps .Logon to the target SAP in client 002 . For example if target system is AB3 the domain controller is DB3.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT . it is desirable to export the UMR?s prior to the database copy step and then re-import them after the copy completes.com | Page 48/65 | .Hit Save button .PFL ] U128 Note: The Part in the [ ] maybe required. we should re-build the index. cd /usr/sap/trans/bin tp addtobuffer <SID>KTxxxxx [pf=TP_DOMAIN_<Sid of domain controller>.txt .21 Change Client Settings . If the storage quality is less than 70%. The domain controller is usually the development server for this landscape. This process may have to be completed for multiple clients depending on customer requirements for the target system. the User Master Records (UMR) in the target system will be the same as was in the source system. Normally.Select Frontend computer 10. before executing scc7. This will speedup the scc7 run considerably.PFL> ] <SID> tp import <SID>KTxxxxx <SID> client<client_number> [pf=TP_DOMAIN_<Sid of domain controller>. Click on execute 4.ProfProjects. For determining the storage quality of the imported user master: v Logon to Production client v Go to ->tcode db02 Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. determine the storage quality of the table.This page was exported from .example : c:/apps/reserveprintersSID.Change the Client Protection to Level 0 . and Export System fields. at least.Click the ?Schedule in background? button.This page was exported from . Export time. .?No changes allowed? . Logon to the target SAP in each of the imported clients .Std Currency . 4. NOT production settings.Category (Note: only one client can be marked as ?Production? for the SID). go to Alter index->rebuild v After rebuild is completed.23 Change Client Settings Logon to the target SAP Execute transaction SCC4 . select Analyis Index->Storage quality from the menu v If Storage quality is less than 70%.Change the Client Protection to Level 1 . . Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.com | Page 49/65 | .ProfProjects. Change the main client back to ?Production? .Login to SAP again to verify your id profiles are now set to the target settings. . Part 2 ? Reset User buffers For systems at lower versions - Logon to the target system in the productive client Enter the transaction SU01 Go to Menu. this is the table for User buffer content for fast RFC logon v Click Table ->Indexes .Select each client and verify that entries are appropriate for the following fields: .Run transaction se38 .In the subsequent sections.Run transaction SCC7 . 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. . proceed to execute Scc7 Part 1 ? Run SCC7 Please note: in large systems.Logon to the target system in the productive client as firebasis . verify that these values are set: . Utilities -> mass changes -> reset all user buffers.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.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT v Click on Detailed Analysis v Type USRBF2 as object name. we have to rebuild index v For rebuilding indexes. this step may take an hour to complete.Enter program RSUSR405 and click execute.For productive clients. This page was exported from - SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT ?No changes to Repository and cross-client customizing objects? are selected. 4.24 Restore data for RFC, ITS, SAPconnect, SSO, HTTP(S), SCOT and Logical Printer 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 and/or the exported dump file for the ?application? and/or ?temporary? tables. Transport : Logon to the target SAP - Run STMS - Overview -> Imports - Double click the Target system SID name - Use menu option Extra -> Other Requests -> 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? and/or ?temporary? tables : <tablename> <tablename> To save copy of the refreshed tables: - su ? ora<sid> - sqlplus /nolog - connect <SAP tables schema>/password> {e.g. connect sappe8/m0tor} 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 www.ProfProjects.com | Page 50/65 | This page was exported from - SAP ADMIN Export date: Thu Feb 23 6:06:21 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 ? ora<sid> - sqlplus /nolog - connect <SAP tables schema>/<password> {e.g. connect sappe8/m0tor} 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 www.ProfProjects.com | Page 51/65 | This page was exported from - SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT - Import the original tables su ? ora<sid> {sapsid = SCHEMA (table owner) of sap tables} imp <sapsid>/<password> FILE=/oracle/<SID>/sapreorg/expdat.dmp tables= <tablename>, <tablename> 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. 4.25 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. 4.26 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: <a date a month ahead> - 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 SM37 Select Job name: DBA*, User name: *, Job status: Released, Job start condition to: <a date a month ahead> 4.27 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 www.ProfProjects.com | Page 52/65 | . Execute the Unix command stopsap to stop the SAP instance. Logon to the target SAP in default client using your own id .Change the server field to the Target Server name.Start transaction SM61 .Run transaction SCOM . Click on a message.Select the Object type Table. Logon to UNIX on the application server as < sid>adm account.This page was exported from . Click the Execute button.Run transaction SM54 .Review the report for errors. Logon to UNIX on the target database server as < sid>adm account. This will generate a listing of all SAP processes. Execute the Unix command ps -ef | grep sap. .Press Change push button. .29 Restore TXCOM table entries 4. Process type should be Direct.com | Page 53/65 | . .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT . .Press the Edit button. Execute the Unix command startsap to start the SAP application instance. select the Delete button. Proceed as follows: Logon to the target SAP Execute transaction SM02. Select the radio button ? All background servers?. . Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. Logon to the target SAP Run transaction SM65.Check the boxes for ?Profile parameter? and ?Execute external programs?. if there is no entry. 4. This will generate a listing of all Oracle processes. Enter the message and click Save button.Select radio-button delete data. click ?EXIT?. Execute the Unix command ps -ef | grep ora.ProfProjects. If a message existed prior to the refresh.Repeat this until all messages have been removed. . . Repeat steps 2-6 for each of the tables listed above.NOTE!!! DO NOT PRESS THE DELETE DB TABLE HERE!!! .28 Changing The Source Server To Target Server Name For SAPCOMM 4.Goto Object à Modify Object.In Destination block choose ?Server Assignment? .Click the Create button and enter the field info from the copy of the screen taken in the pre-Refresh steps.30 Remove System Messages (or adjust) Check the system to see if there were any system messages and remove/update them.Press activate and adjust database. There should be several of these Oracle processes listed. There should be several of these SAP processes listed. Execute the Unix command startsap to restart the SAP instance on the database server. Click the Create button. Logon to the target SAP in client 000 (as ddic) . Select Instance/Opmodes Create the target system op mode configuration(s) by selecting the menu items Settings -> Current Status -> New Instances -> Generate .34 Clear Background Objects 4. .Check each of the new op modes for correctness. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.Select menu option Workload -> Reorganize-> Parameters -> Performance Database.Run transaction RZ10.31 Re-cycle SAP 4.36 Add required application servers to the Op Modes 4.Run ST03 . Logon to the target SAP .Schedule the Standard Jobs which were running earlier 4. In the Pre Copy Steps.37 Reschedule Standard SAP Jobs 4. Click the SAVEbutton.This page was exported from .33 Check background processing 4.Import all profiles from Unix by selecting menu items: Utilities -> Import Profiles -> of active servers.Hit save Button. weeks=5 and months =12. Logon to the target SAP in client 002 Run transaction RZ04 . .35 Import application server Profile Parameter Files 4.Select modify parameters button . a snapshot of the Target <SID> Op-modes was taken and downloaded to a directory/filename on the local PC. .38 Fix workload storage parameters During a refresh the parameters that define how long to keep the workload storage statistics are reset to the default. Verify the Op-modes with this hardcopy listing.ProfProjects. .In the target system .32 Start SAP on all application servers (if applicable) 4. .com | Page 54/65 | .Change the Days= 31.Logon to the target system . To fix: .SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Click on Cleanup list button.Green back arrow. 00 After the refresh and before starting the SAP system for the first time.<ora>sid sqlplus ?/ as sysdba? drop user SAP<SSID>DB cascade. Create the J2EE Schema User (SAP<SID>DB or SAPMIWDB or SAPCRMDB ) As ora<sid> perform the following steps to create the J2EE user. Continue with create the J2EE schema user.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT 4. Perform the following: su . Type of path of the filesystem that contain more than 1GB of space. Select c ? New Size Type 1024M to create a 1GB tablespace.40/7. 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. the J2EE engine must be ?reconfigured? in order for the engine to start properly.ProfProjects. a new tablespace is created in the ABAP stack called PSAP<SID>DB. /oracle/SID/sapdata8 was used. By default the tablespace is created in sapdata1.Create/drop tablespace Select b ? New Path. This tablespace must be recreated after the system has been restored. Select s ? Start to Create the tablespace. Create the J2EE tablespace using sapdba During the installation of the J2EE engine.com | Page 55/65 | .This page was exported from . su ? ora<sid> Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.39 Configuring J2EE 6. drop tablespace PSAP<SSID>DB including contents and datafiles. Perform the following to create the tablespace: su ? ora<sid> sapdba (See the warp file for the system password) Select c ? Tablespace administration -> a ? Tablespace-> g . Press q to return. In this example. Click the Roles tab: Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT sqlplus ?/ as sysdba? create user SAP<SID>DB identified externally default tablespace PSAP<SID>DB temporary tablespace PSAPTEMP.This page was exported from . This prevent the password of the user from expiring.J2EE_GUEST . alter user sap<sid>db identified by <password>.J2EE_ADMIN .connect.e. Enter an initial password for the user Enter Group name in the User Group for Authorization Check field. exit Re-create the J2EE Users in the ABAP Stack The J2EE ABAP users are removed from the ABAP stack.ProfProjects. Click the button. set the User Type as Communications. In the Last Name and First Name field. resource to SAP<SID>DB. After creating the user. J2EE_ADMIN).com | Page 56/65 | . Perform the following: Access transaction SU01 Enter J2EE_ADMIN in the user field. Click the Logon data tab. grant select_catalog_role. the User type should be set as a Dialog user. During creation. enter the user name (i. The following users must be re-created in the ABAP stack The following users must be created on the main client: .SAPJSF All three users should be created with the Communication user type to prevent the passwords from expiring. Enter a valid email address in the E-Mail field. This page was exported from . SAP_NEW Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ProfProjects. User Roles Profile J2EE_ADMIN SAP_J2EE_ADMIN None J2EE_GUEST SAP_J2EE_GUEST None SAPJSF SAP_BC_JSF_COMMUNICATION SAP_ALL. For the J2EE_ADMIN user. add the SAP_ALL and SAP_NEW in the Profiles tab. 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.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Note: When creating the SAPJSF user.com | Page 57/65 | . enter SAP_J2EE_ADMIN in the role field. You should see the following processes (different on J2EE 7. Import the J2EE schema (SAP<SID>DB) Perform the following the import the J2EE schema: su .ProfProjects. tail /usr/sap/<SID>/DVEBMGSXX/work/dev_server0 [Thr 16708] Thu Sep 6 09:44:55 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.00 check if the state is Running.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Perform the steps above to re-create the remaining users.Logon with J2EE_ADMIN user to the Portal (HTTPS/<Port number>) . .This page was exported from .log RZ11 -> param-name: rdisp/j2ee_start -> display -> Change value -> New value: 1 -> save Start the J2EE engine using SMICM: Administration > J2EE Server > Restart > Yes At the OS level. .Expand Systemlandscape Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.Navigate to "System Administration" -> "System Configuration" .dmp full=y indexes=y grants=y log=/tmp/importj2ee.com | Page 58/65 | .Expand Portal Content.00): ps ?ef | grep jlaunch /usr/sap/SID/DVEBMGSXX/j2ee/os_libs/jlaunch pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSXX_<Host> -DSAPINFO=SID_<Sys no>_server /usr/sap/SID/DVEBMGSXX/j2ee/os_libs/jlaunch pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSXX_<Host> -DSAPINFO=SID_<Sys no>_sdm /usr/sap/SID/DVEBMGSXX/j2ee/os_libs/jlaunch pf=/usr/sap/SID/SYS/profile/SID_DVEBMGSXX_<Host> -DSAPINFO=SID_<Sys no>_dispatcher For J2EE 7. verify the J2EE is running.ora<sid> cd sapreorg imp sap<sid>db/<Password> file=/oracle/<SID>/sapreorg/exportj2ee. Drop user bugreq su ? ora<sid> sqlplus ?/as sysdba? drop user bugreq cascade. grant create table to BUGREQ.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT . Create user BUGREQ in SAP EBP system su .40 Re-import BugsEye & eMerge data (if applicable) Re-Import BugsEye data & eMerge data (if applicable) in the following way: Make sure the J2EE processes are stopped! (done for both BugsEye & eMerge) Stop the j2ee processes: Logon to SAP SMICM à Administration à J2EE Server à Send Hard shutdown à Without Restart Optional è Check processes: ps ?ef | grep jlaunch STEP.Right click on SAP_BW à Open à Connection Tests Select all tests and choose Test. The tests must complete successfully.ProfProjects.This page was exported from . 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. grant create session to BUGREQ. STEP. commit. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.ora<sid> sqlplus ?/as sysdba? create user BUGREQ identified by <See WARP> default tablespace PSAPBUGSEYE temporary tablespace PSAPTEMP.com | Page 59/65 | . 4. log STEP. grant create any context to BUGREQ.ora<sid> imp bugreq/<See WARP> file=/oracle/<SID>/sapreorg/exportbug. grant create any indextype to BUGREQ. grant create trigger to BUGREQ.htm For eMerge: Make sure the J2EE processes are stopped again. grant create view to BUGREQ. grant unlimited tablespace to BUGREQ. grant CTXAPP to BUGREQ. Import all bugseye data info into SAP EBP system su . grant create any index to BUGREQ. grant create synonym to BUGREQ.ProfProjects. Test connection Start the J2EE processes: Logon to SAP SMICM à Administration à J2EE Server à Send Hard shutdown à With Restart {it can take up to 5 minutes before the homepage is available} Test connection: http://<servername + dns>/requisite/login. grant create any procedure to BUGREQ.dmp full=y indexes=y grants=y commit=y log=/tmp/importbug.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT grant create sequence to BUGREQ. grant create any cluster to BUGREQ.com | Page 60/65 | . STEP.This page was exported from . Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. grant create any procedure to EMEREQ. grant create table to EMEREQ. grant create any indextype to EMEREQ. grant create view to EMEREQ. Create user EMEREQ in SAP EBP system su . grant create any context to EMEREQ. STEP.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT Logon to SAP SMICM à Administration à J2EE Server à Send Hard shutdown à Without Restart STEP.This page was exported from . Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. grant create trigger to EMEREQ. Drop user emereq su ? ora<sid> sqlplus ?/as sysdba? drop user emereq cascade. grant create session to EMEREQ.ProfProjects. grant create any cluster to EMEREQ. grant create any index to EMEREQ. commit.ora<sid> sqlplus ?/as sysdba? create user EMEREQ identified by <See WARP> default tablespace PSAPEMERGE temporary tablespace PSAPTEMP. grant unlimited tablespace to EMEREQ. grant create synonym to EMEREQ. grant create sequence to EMEREQ.com | Page 61/65 | . sql 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.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT grant CTXAPP to EMEREQ. Test connection Start the J2EE processes: Logon to SAP SMICM à Administration à J2EE Server à Send Hard shutdown à With Restart {it can take up to 5 minutes before the homepage is available} Test connection: http://<servername + dns>/emerge/login.ora<sid> imp emereq/<See WARP> file=/oracle/<SID>/sapreorg/exporteme. STEP. Import all emerge data info into SAP EBP system su .sql. You must run the sapdba_role. On the target server su ? ora<sid> cd /local/bin/sap/dbcopy grep OPS sapdba_role.41 Run sapdba_role.com | Page 62/65 | .ProfProjects. The results should look like the above Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.sql V_User := 'OPS$' || '&&1' || 'ADM'.dmp full=y indexes=y grants=y commit=y log=/tmp/importbug. V_User := 'OPS$SAPSERVICE' || '&&1'.log STEP. First you must make sure you have the proper script.This page was exported from .htm 4. com | Page 63/65 | . You can however safely continue with the next steps.42 SAP INFOCUBE INDEXES REPAIR Run report SAP_INFOCUBE_INDEXES_REPAIR (Applicable for BW systems on version 3.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT sqlplus system/<password> @sapdba_role. The output should look like the following : GRANTEE GRANTED_ROLE ADM DEF -----------------------------. 4. The solution is to drop/recreate these indexes in the refreshed system (switching on LOGGING in the production system is not feasible as performance would go down.This page was exported from .-----------------------------.43 Convert logical system names(BDLS RUN)] Old logical system name = <SSID>CLNT<Client number> Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. these indexes will get corrupted blocks.sql <SID> UNIX sqlplus ?/ as sysdba? select * from dba_role_privs where grantee like ?OPS%?. NOLOGGING is also the SAP recommendation for BW systems). While BW drop/recreates indexes quite frequently as part of dataloading.ProfProjects. In BW system client: SE38 à SAP_INFOCUBE_INDEXES_REPAIR à Program à Execute in background This can and probably will run for hours.--.5 and below) Some background: BW systems are running with NOLOGGING configured on Oracle level.--OPS$D04ADM OPS$D04ADM OPS$D04ADM SAPDBA CONNECT RESOURCE NO YES YES YES YES YES 4. There is no need to wait for this program to finish. lots of index creations are not in the redologs. When rolling forward a database during a refresh. This means that the creation of indexes are not captured in redologs. In this way the BDLS runs can still hit the same table simultaneously (and therefore slow down). Output as PDF file has been powered by [ Universal Post Manager ] plugin from www. it won?t work). and proceed to schedule all LSN conversions from Source to target(There might be more than one BDLS runs depending on LSN?s 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 à Execute in background.ProfProjects. You will get a warning LSN already exists: press ?enter? to ignore (don?t click on the warning. The output of the SM37 job does not give all the information.SAP ADMIN Export date: Thu Feb 23 6:06:21 2012 / +0000 GMT New logical system name = <TSID>CLNT<Client number> Login to the Production client and navigate to transaction BDLS. However. Go to the application log via transaction SLG1 à enter appopriate dates à Execute.com | Page 64/65 | .This page was exported from . It is not feasible to wait on the outcome of the first run before starting the second run. the application log of SAP catches the actual output of BDLS. as too much time would be wasted. Expand the row as below and doubleclick on the line Problem Class. Therefore scheduled the BDLS?s one hour behind eachother. but overall it will be quicker than running sequentially. This will run for quite a while. ProfProjects. Output as PDF file has been powered by [ Universal Post Manager ] plugin from www.SAP ADMIN Export date: Thu Feb 23 6:06:21 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.This page was exported from .com | Page 65/65 | .