new

5/27/2018 New

1/19

STEP BY STEP SYSTEM COPY

(Backup Restore)1. Pre - Requisites:

No of Drives are same in both Source Server & Target Server.

Drive Names should be same in both Source Server & Target Server.

Installation of Database & SAP should be same in both Source Server & Target Server.

1. STOP SAP & Oracle SERVICES AND EMPTY FOLLOWING DIRECTORIES :Go to Target Server & Stop all services (oracle & SAP both).

Now Delete the All files inside the following Directories.SAPDATA_HOME\sapdata1\sysauxSAPDATA_HOME\sapdata1\systemSAPDATA_HOME\sapdata1\temp

SAPDATA_HOME\sapdata1\undo

SAPDATA_HOME\sapdata1\cntrlSAPDATA_HOME\sapdata2\sr3_1 sr3_nSAPDATA_HOME\sapdata3\sr3702_1 sr3702_n

SAPDATA_HOME\sapdata4\sr3usr_1SAPDATA_HOME\origlogA\cntrlSAPDATA_HOME\origlogB\cntrl

SAPDATA_HOME\sapdata1\cntrl

1. PLACE BACKUP FILE IN SAPBACKUP DIRECTORYPlace the xxxxxxxx.andFile In Sap backup FolderSAPDATA_HOME \sapbackup

The File Name Will Be Like This belerzpm.and

1. Open Cmd Prompt And Run This CommandBRRESTOREm fullb xxxxxxxx.andd diskc

Now The Restoration Process Has Started1. Again Delete Oracle Control Files under these directories that comes after restoration

SAPDATA_HOME \origlogA\cntrlSAPDATA_HOME \origlogB\cntrl

SAPDATA_HOME \sapdata1\cntrl

1. Create trace file in source server using this command:SQL>Alter database add controlfile to trace;

Copy this trace file to target server and rename to control.sql.

Now modify this control.sqlDelete all before startup mount & after CHARACTER SET UTF8; in control.sql

Change

to REUSESET

NORESETLOGS - RESETLOGS

Now, Put this Control.sql to C drive on SYSTEM.

Start Oracle ServicesSQL> @C:\CONTROL.SQL;

1. Copy all archive logs to SAPDATA_HOME\oraarch & Run these commandsSQL>RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;SQL>ALTER DATABASE OPEN RESETLOGS;

1. Create Users as per note 50088.

1. Start SAP Services.

5/27/2018 New

2/19

Check using ps -ef | grep orasid and sidadm and see no DB or SAP services are running.

sapcpe pf=/usr/sap/SID/SYS/profile/ instance profile

What command do you run to check file systemconsistency under UNIX or Linux?A.You need to run fsck [file system consistency check]command to check file system consistency and repair a Linux/ UNIX file system. Microsoft Windows/DOS equivalent

programs are scandisk and chkdsk.You must unmout file system before running fsck command.fsck should always be run in a single user mode.

Following is general sequence for running fsck:Goto single user mode:

# init 1

Unmount file system (for example /dev/sdb1 under Linux)# umount /dev/sdb1

Now run fsck command:

# fsck /dev/sdb1

Now mount filesystem

# mount -a

dfdisplays the amount of disk space available on the file system

5/27/2018 New

3/19

Syntax

df [OPTION]... [FILE]...

-a, --all include dummy file systems.

-c, --total display a grand total.

-h, print sizes in human readable format (e.g., 1K 234M 2G)

-k like --block-size=1K.

-m like --block-size=1M.

-s, --summarize display only a total for each argument.

--help display a help message and exit.

dfh

Filesystem Size Used Avail Use% Mounted on /dev/loop0 18G 15G 2.5G 86% /

duestimates and displays thediskspace used byfiles.

Syntax

du [OPTION]... [FILE]...

du -shc *.txt

Display the same data, but in a "human-readable" size format, and display a grand total.8.0K file1.txt 8.0K file2.txt 10.0K file3.txt 2.0K file4.txt 8.0K file5.txt 8.0K file6.txt 44.0K totaldf = display filesystemsdu = disk usage

In my experience the du command is a more accurate indicator of space usedand space available

r3trans in a SAP System

This tool r3trans does the complete transport work for tp. TP controls thetransports and generates the r3trans control files, but does no database-connect itself. All the "real work" is done from r3trans.

A sample call to R3TRANS could be as follows:(edit the following e.g. in the file /tmp/control)

EXPORT
http://www.computerhope.com/jargon/d/disk.htmhttp://www.computerhope.com/jargon/d/disk.htmhttp://www.computerhope.com/jargon/d/disk.htmhttp://www.computerhope.com/jargon/f/file.htmhttp://www.computerhope.com/jargon/f/file.htmhttp://www.computerhope.com/jargon/f/file.htmhttp://www.computerhope.com/jargon/f/file.htmhttp://www.computerhope.com/jargon/d/disk.htm

5/27/2018 New

4/19

FILE='/tmp/export'CLIENT=SELECT * FROM (e.g. t000)

You can start r3trans as follows:r3trans /tmp/control

The output will be generated as follows:

/tmp/export: All exported rows of the table (in a compressed format) trans.log: Information Output console: Return Code of R3TRANS (should be lower than 8)

How to download the latest version ?

You can download the latest versionof all the SAP Executables in the SAP

Service Marketplace. As the binaries are different for each platform, youshould have a look at the following link:Download Executable Patches on the SAP Service Marketplace

R3TRANS online help with all supported command line options and further examplesThis is r3trans version x.xx (release yyy - 15.12.03 - 13:51:42).

usage: r3trans []

The control_file describes what R3trans has to do.

The following options are possible:

-c f1 f2 : Copy file f1 to f2 with character set conversion.-d : DB connect. Test if SAP database is available.-i file : Import from file without using a control file.-l file : List the contents of file to the log file.-m file : List the contents of file to allow tp to create a cofile.-t : Test. All database changes are rolled back.-u : Unconditional modes. See below.-v : Verbose. Write more details to the log file.-w file : Log file. The default log file is 'trans.log'.-x : DB connect without access on any SAP table.

R3trans -d is the command use to check connection between the SAP appilcation and Database

Following methods used to check whether DB is active or not :

1. ps -ef |grep ora

2. ps -ef |grep ora_

3. ps -ef |grep pmon
http://www.easymarketplace.de/KernelPatches.phphttp://www.easymarketplace.de/KernelPatches.phphttp://www.easymarketplace.de/KernelPatches.php

5/27/2018 New

5/19

4. R3trans -d ; give RC - 0000 means active other than 0000

is error

How to check the version of TP & R3TRANSLogin into ur 000 client go to SPAM then select utilities-->check transport tool

What is the Listener ?

The listener process executes on the database server and manages client connection

requests to that database server. There can be one or multiple listener processes

listening for a database server. Each listener can listen with one or multiple protocol

addresses for a single database service. Note that service information does not have to

be configured in the listener.orafile. However, if Oracle Enterprise Manager or pre-

Oracle8i is used then service information must be configured in the listener.orafile.

Please find the below questions......1.)What is a listener??ans:listener is the interface between sap & database..2.)what is the command to check the connectivity between sap & database??ans:r3trans -d3.)what is the command to check the file system consistency check??ans: bds8.)What is the tcode to do unicode conversion??

ans:SPUMGSPUMG - Unicode Preconversion UCCHECK - Unicode Syntax Check SUMG - Unicode

Postconversion

9.)NAME THE TOOLS USED FOR VERSION UPGRADATIO??ANS:SUM(IS THE LATEST TOOL),UPGRADE ASSISTANT1.work process goes to PRIV mode what you will do?2.In your system how much swap space?3.How to create OPS$ user? how to reset?4.How to adjust memory parameters?5.what is OSS notes ? how you will implement? when?6.When creating JCO rfc connections which user is used?7.waht is SCM system? why maintain 2 databasess?

Phase 1.)1.)Communicate with the endusers,functional team & get the requirements,2.)Identify the roles,jobs,positions & responsibilities,3.)Identify the critical areas ,sensitive transactions that needs to be protected,4.)Identify the organisation levels such as plants,storage locations,ware houses,sales areas,5.)Design & explain the concept of security to the users,6.)Define the role matrix(role matrix is the excel sheet which contains username,designation,role,assigned transactions etc)7.)Conduct training to the training to the user administrators
http://scn.sap.com/message/5430217#5430217http://scn.sap.com/message/5430217#5430217

5/27/2018 New

6/19

Phase 2.):-1.)Design the roles based on the transactions,prepare the role matrix& get sign of from the users,2.)Identify the single,composite,parent,parent roles as per the role matrix,3.)avoid preparing the the role matrix based on users,it should be based on jobs & responsibilities,Phase 3.):-1.)Develop the roles based on role matrix,

2.)Define user based menus,3.)These roles are developed i.e. developed only in Development system,4.)Roles can be uploaded,downloaded,transported,imported to other systems in the landscape,5.)Profile can be generated using pfcgPhase 4.):-1.)These roles are transported from Dev to consolidation system or a client for testing,2.)Use pfcg or stms to transport the roles,3.)Create users to perform enduser\user acceptance test4.)conduct enduser testing to create users & assign roles5.)Schedule go live datePhase 5.):-1.)The roles are transported from DEV to PRD systems,2.)The roles are assigned to the buisness users,3.)Client setting & system settings are defined,

4.)Go live is scheduled

Upgrading the Kernel

For Java only systems, check the following:

1) For release 700, there is a incompatibility with jmon, which is eliminated with SAP Java Technology S Offline

Component (SAPTECHF.SCA). For release 700, SAP TECH S 700 OFFLINE SP14 PL24 is required:

This is on Higher level.

2) For release 700, the tool JSPM must have at least SP 24:

Platform-Specific Checks:

1) Oracle Database: Oracle 10.1 is not supported with the SAP Kernel 7.20. Needs at least Oracle 10.2
http://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220518/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220517/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220510/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220518/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220517/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220510/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220518/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220517/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220510/1.JPG

5/27/2018 New

7/19

2) Oracle Client Library: Oracle Instant Client 11g is required by SAP Kernel 720_EXT.

This is not applicable for this case as Kernel is 720_REL

Download Required Components / Patches

Download the following from SAP Service Market Place:

Latest SAPCAR Tool

SAP Kernel 720_REL 64 BIT UNICODE Latest Patch (DB-INDEPENDENT & DB-SPECIFIC Kernel Files)

SAP IGS 7.20 (If you have IGS installed, and your target Kernel would be 720_REL)

SAP IGS Helper (SAP IGS Fonts and Textures, though an optional component, it is recommended to install if you are upgrading

to Kernel 720_REL or 720_EXT.

DBA Tools Package from the Kernel Download Path of DB Specific section

SAPHOSTAGENT (The SAP OS Collector, onward's Release 7.20)

SAPCAR Tool =>

SAP KERNEL 720_REL 64 BIT UNICODE Latest Patch =>

5/27/2018 New

8/19

SAP IGS 7.20 (Internet Graphics Server) =>

Check if IGS is installed (should be as a Software Component / Development Component)

DBA Tools Package for Oracle 10g and 11g =>
http://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220552/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220551/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220550/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220546/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220552/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220551/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220550/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220546/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220552/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220551/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220550/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220546/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220552/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220551/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220550/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220546/1.JPG

5/27/2018 New

9/19

SAPHOSTAGENT (The SAP OS Collector onward's release 7.20) =>

Preparations

Stop the SAP System (No need to stop the Database)

Stop SAPOSCOL, assuming that your SAP system release is 700, SAPOSCOL is installed under SAP Kernel.

If the SAP Kernel is added to your path, you can directly execute below command:

5/27/2018 New

10/19

Stop processes "SAPSTARTSRV"

Remove any IPC objects that may exist: cleanipc remove

5/27/2018 New

11/19

Install SAPHOSTAGENT

Now as the SAP OS Collector has been stopped, and IPC has been cleaned up, you can install SAPHOSTAGENT

720, which in turn will update SAPOSCOL and deploy under path /usr/sap/hostctrl/exe/

Extract SAPHOSTAGENT.SAR somewhere on a temporary directory (Note: You should use the latest download

SAPCAR tool for extracting all the packages)

You should do the extraction using root, or ensure that the extracted contents belong to root ownership.

The extracted archive will contain saphostexec program

Start the installation of SAPHOSTAGENT as per below:

Subsequent to this, you will see that SAP OS Collector saposcol is now installed under /usr/sap/hostctrl/exe/onward's

Kernel 720

Install SAP Kernel 720

Well, the most awaited precious step has arrived now

But, you wouldn't be rushing up, without taking a backup of the current working Kernel before upgrade! Would

You?
http://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220590/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220589/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220579/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220590/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220589/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220579/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220590/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220589/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220579/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220590/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220589/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220579/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220590/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220589/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220579/1.JPG

5/27/2018 New

12/19

Take a backup of the existing Kernel 700, from the Global Kernel directory ( /sapmnt//exe/)and also of Local

Instance Specific Kernel Directories (/usr/sap///exe/)
http://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220592/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220591/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220592/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220591/1.JPG

5/27/2018 New

13/19

Now, switch to directory /sapmnt//exe/ with user adm

Save the following Files & Directories to another path to be used later:

1. Directoryjvm or sapjvm* if it exists

2. File protect.lst if it exists

3. Files rfcexec, rfcexec.sec if it exists

4. ICU Libraries (*libicu*), if they exist.

Now, switch to user root and change the owner of all files/directories to adm as shown below:

Now, delete all the files from the kernel directory, including the sub-directories. This ensures that there are no

remaining files from the earlier release, which have different name in release 7.20 or are in a different place in a sub-

directory.

5/27/2018 New

14/19

Now extract the new Kernel (using the latest SAPCAR tool) in /sapmnt//exe/ as shown below:

Extract the DBA Tools Package now, as shown below:

Extract IGS Packages now, as shown below:

Now, you need to restore the files to the current directory, which you saved earlier:

1. Directoryjvm or sapjvm* if copied

2. File protect.lst if copied

3. Files rfcexec, rfcexec.sec if copied

4. ICU Libraries (*libicu*), if copied
http://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220614/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220613/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220612/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220611/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220606/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220614/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220613/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220612/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220611/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220606/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220614/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220613/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220612/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220611/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220606/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220614/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220613/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220612/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220611/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220606/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220614/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220613/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220612/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220611/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85583-220606/1.JPG

5/27/2018 New

15/19

To, deploy the optional IGSHELPER.SARfile, switch to the relevant local directory /usr/sap// on

every instance and execute the below command:

Deploy the IGSHELPER.SAR to the relevant local directory /usr/sap// on every instance

as shown below:

Now switch to user root and run shell script saproot.sh from the kernel directory

Delete all the local executable's on the individual instances. To do this switch to local relevant executabledirectory/usr/sap///exe/ and execute rm -rf *

5/27/2018 New

16/19

Since the executables from the local executable directory can be executed for the start before SAPCPE runs, start an initial copyof the executables.

For all application server instances (PAS, CI, AAS, DI, CI) & For Java Only Systems, perform the below:

If your system is running with the SAPJVM:

sapcpe pf=/usr/sap//SYS/profile/ source: list:/sapjvm_.lst

Checking if the SAP system is using SAP JVM or 3rd Party JDK?

5/27/2018 New

17/19

Execute SAPCPE now to sync the kernel directory:

Follow-up Activities

This step only applies to release 7.00 and 7.01 Dual-stack and Java only systems.

In all (Dxx, DVEBMGSxx, Jxx, JCxx etc) instance profiles, you must set the following parameter:

FN_JSTART= jcontrol$(FT_EXE)

5/27/2018 New

18/19

You can start your SAP System now with the new SAP Kernel 720 (Check R3trans -x, Oracle DB & Listener should be up andrunning)

Well, WHAT DID JUST HAPPENED ?

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.

.
http://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220662/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220661/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220662/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220661/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220662/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220661/1.JPG

5/27/2018 New

19/19

.

.

I just switched to Local Instance Kernel directories and observed that all the executables were not replicated from the GlobalKernel directory.SAPCPE only replicated the JVM and other executables.

So, I manually copy all the executables from the Global Kernel Directory to all the Local Instance Specific Executabledirectories, and started the SAP system.

Voila. the SAP system started up like a champ

And the SAP Kernel has been successfully upgraded to SAP KERNEL 720_REL Patch

Level 401.
http://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220668/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220667/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220668/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220667/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220668/1.JPGhttp://scn.sap.com/servlet/JiveServlet/showImage/38-85668-220667/1.JPG

new

Documents