SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.

com/site/saparchives/SAP-basis-operation-3-unix--linux

Search this site

SAP BASIS
Administration and
Learning Tutorials
Welcome to BASIS World !!!
U can send BASIS content to
SAP BASIS Tutorial 3 Unix & Linux
justsap@yahoo.com and will
add it to SAPArchives.
SAP BASIS Material
SAP BASIS

BASIS FAQs

BASIS Transactions

SAP BASIS Scope

SAP Forum

Database Tasks
Creating Database Statistics, Index Rebuilds, and Log Backup
Jobs – MS SQL Server

Database statistics refresh jobs should be scheduled to run

twice daily on all the SAP systems. But occasionally a manual
refresh needs to be done due to table reorganization, index
rebuild, etc.

1. Log on to the server using the <sid>adm user ID.

2. Open the MS SQL Server Enterprise Manager.
3. Expand the navigator tree until you see the
Management entry. Expand it.
4. Right-click on Database Maintenance Plans and
click New Maintenance Plan.
5. Use the wizard to create the job you need.
6. You may now close the Enterprise Manager session
and log off the server.

Creating Database Statistics, Index Rebuilds, and Log Backup

Jobs – Oracle

1. Log on to the appropriate SAP instance any client.

2. Go to transaction DB13.
3. On the DBA Planning Calender for Oracle Database
<SID>: Maintain screen, double-click on a blank line on
any day in the future.
4. On the Schedule Action for <Day>. DD.MM.YYYY
popup, use the radio button to turn “on” the task you
want to do. For each action, you need to fill in the
Start Time in military time format, the Period (Weeks)
which is how many weeks between running of this job –
blank for one time only, 1 for weekly, 2 for bi-weekly,
etc. and Calender if you want to use any calendar except
the SAP supplied standard Factory calendar.

These are the details for each action:

Whole database offline + redo log or

Whole database offline backup or
Whole database online + redo log or
Whole database online backup
Generic tape names for database backup
Database backup profile – usually
init<SID>.sap
Options for ReDo log backup
Redo log backup
Generic tape names for database backup
Options for ReDo log backup
Partial database offline backup or
Partial database online backup
Tablespace names to be included in the back
up
Generic tape names for database backup
Database backup profile – usually
init<SID>.sap

1 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

Check and update optimizer status

Tablespace names to be included in the
statistics run
Adapt next extents
Tablespace names for next extents adaption
Check database
N/A
Verify database
Tablespace names to be verified
Database backup profile – usually
init<SID>.sap
Cleanup logs
N/A

5. You may now leave the DB13 transaction.

===================================================================
See also :-

http://sites.google.com/site/saparchives/Home-SAP-BASIS
http://sites.google.com/site/saparchives/sap-basis-transactions
http://sites.google.com/site/saparchives/Home-SAP-BASIS/SAP-BASIS--unknown-
sap-tricks
http://sites.google.com/site/saparchives/SAP-BASIS-everything-about-sap-clients
http://sites.google.com/site/saparchives/frequently-used-procedures
http://sites.google.com/site/saparchives/SAP-BASIS-BASICS
http://sites.google.com/site/saparchives/SAP-BASIS-what-is-asap
http://sites.google.com/site/saparchives/SAP-BASIS-configuration
http://sites.google.com/site/saparchives/SAP-basis-operation---unix--linux
http://sites.google.com/site/saparchives/SAP-basis-operation-2---unix--linux
http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux
http://sites.google.com/site/saparchives/SAP-basis-operation-1---windows
http://sites.google.com/site/saparchives/SAP-basis-operation-2---windows
http://sites.google.com/site/saparchives/SAP-basis-operation-3---windows
http://sites.google.com/site/saparchives/SAP-basis-interview-questions
http://sites.google.com/site/saparchives/sap-training-courses-ecc-60
http://sites.google.com/site/saparchives/sap-basis-refference-steps-1
http://sites.google.com/site/saparchives/SAP-basis-transactions

==============================================================================
Jobs, Job Logs, and the Job Queue

Scheduling a New Job

1. Log on to the appropriate SAP instance and client using BATCH_USER.

2. Go to transaction SM36.
3. On the Define Background Job screen, fill in the Job name field with the new job
name. Select a Job Class priority of A for High, B for Medium, and C for Low. It is
SAP’s recommendation that all client-owned jobs begin with a Z for identification
purposes. And most Basis people recommend the next two characters be the initials
for the SAP module for which the SAP instance runs. Like ZBC* for a Basis job, and
ZHR* for a Human Resources job. Click on the Specify start condition button or
press F5.
4. On the Start Time popup, click the Immediate button to start the job right away, or
click the Date/Time button to specify a date/time in the future for which the job run.
Click “on” the Periodic job radio button and then click the Period values button if you
want to schedule to job to run on a periodic basis. Provide the periodic values and
click Save back to the main Define Background Job screen.
5. On the main Define Background Job screen, click the Step button.
6. On the Create Step 1 popup, fill in the ABAP program Name and any Variant
needed to run the program – you had to have created the variant using
BATCH_USER before using it here. Then click Save once more.
7. Back on the Define Background Job screen, check that all the job information is
correct and then click the Save button one last time.

Modifying a Released or Scheduled Job

2 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

1. Log on to the appropriate SAP instance and client as either the user ID owning the
job or an administrator ID.
2. Go to transaction SM37.
3. On the Simple Job Selection screen, fill in the Job name field or use any of the
screens filtering options to produce a list from which you can see the job to be
changed. In order for a job to be changed, it has to have a status of Schedule or
Released so turn those statuses “on” and turn the rest “off”. Click on the Execute
button.
4. On the Job Overview screen, click “on” the line containing the job to be changed
and then click Job → Change.
5. On the Change Job screen, make your changes and then click Save. If you have
more than one occurance of the same job in your list, you must change each job
scheduled to run earlier than that job you just changed. Once the job you changed
runs, all occurences of the jobs running after that date will be changed as well.
Deleting a Released of Scheduled Job

1. Log on to the appropriate SAP instance and client as either the user ID owning the
job or an administrator ID.
2. Go to transaction SM37.
3. On the Simple Job Selection screen, fill in the Job name field or use any of the
screens filtering options to produce a list from which you can see the job to be
deleted. In order for all occurances of a job to be deleted, all statuses of the job
should be checked “on”. And enter an all-encompassing date like 01-01-1990 through
12-31-2010. Click on the Execute button.
4. On the Job Overview screen, click “on” all the perpetent line containing the job(s)
to be deleted and then click on the Delete job from database button.
5. On the Delete Scheduled Jobs? popup, confirm the deletion.

Viewing the Job Queue

1. Log on to the appropriate SAP instance and client as either the user ID owning the
job or an administrator ID.
2. Go to transaction SM37.
3. On the Simple Job Selection screen, fill in the Job name field or use any of the
screens filtering options to produce a list from which you can see the job you want to
view. In order for all occurances of a job to be viewed, all statuses of the job should
be checked “on”. Click on the Execute button.

Deleting an Active aka Runaway Job

Opinions on this topic vary so these are good guidelines to

use. These are
pretty much in the order they should be tried:
1. Kill the session via SM37 or SM04.
2. Try End session through SM50 or cancel program from SM66.
3. If the Work Process in SM50 is in stopped state then
killing it will not help much or quickly, you need to identify
why it is stopped (running a program on another server, runing
in parallel etc.) Try and end those.
4. Kill Work Process in SM50 without core.
5. Kill process or PID via program RSBDCOS0.
6. If all else fails, restart the SAP instance server.

The most important things to remember when killing a WP are:

1. Change to restart = no as otherwise the session can jump

back in sometimes as most of its memory is not actually living
in the WP.
2. Allow it a long time to stop, there is no need to do it twice or 50 times
as I have seen some people do, the poor old thing is just trying to recover rollback
and reinitialize itself.
Cleaning the Job Log

1. Log on to the appropriate SAP instance and client.

2. Go to transaction SE38 and type in Program name RSBTCDEL and click on the
Execute button.
3. On the Delete batch jobs screen, fill in the filtering information you need. It is
suggested that Delete with forced mode be “on”. Click on the Execute button.
4. A status message will appear in the bottom Status Bar as the list of job logs to be
deleted is built. Once all the specified job logs have been deleted, a final total of jobs
logs cleaned will appear in the bottom Status Bar.

Support Package and Binary Patch Tasks

3 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

In order to apply new support packages and kernel patches to a SAP system,
several preparation steps are required:

· Checking for new SPAM updates, support packages and kernel patches
· Downloading the new SPAM updates, support packages, and kernel
patches
· Preparing the new SPAM updates, support packages, and kernel patches
for application
· Applying the new SPAM updates, support packages, and kernel patches
· Mass recompiling all programs used in patched components

Be aware that SPAM/SAINT update and support package application occurs within
the SAP system using the SPAM transaction. These corrections are changes to
ABAP program code and must be handled in a special way by SAP. Kernel patches,
on the other hand, are fixes to SAP executables found on the SAP server. Kernel
patches must be applied when the SAP instance is down.

Please refer to the Check for New SPAM Updates, Support Packages and Kernel
Patches.
Checking for New SPAM Updates, Support Packages and Kernel
Patches

To check if SAP has released any new software fixes for your release of SAP, you
need to know your current support package and kernel release levels.

The patching process consists of:

- finding you current patch levels

- finding what patches you should be applying
- downloading the patches
- unCARing the patches
- loading the patches into the patching EPS queue
- applying the patches

Find your Current SPAM Update and Support Package Level

Method One:

1. Log on to your SAP instance, any client.

2. On any SAP screen, click System -> Status…
3. On the System: Status popup, click the Component Information button.
4. On the System: Component Information popup, you will see the support package
level for each component installed in your current SAP instance.

Method Two:

1. Log on your SAP instance, any client.

2. Go to transaction SPAM.
3. On the Support Package Manager screen, turn “on” the radion button beside
the Imported Support Packages in the Directory section of the screen, and
then click Display button.
4. On the OCS Package Directory: Imported Packages screen, you will see a list
of all SAP Support Packages imported into your current SAP instance.
Find your Current Kernel Patch Level

Method One:

1. Log on to your SAP instance, any client.

2. Go to transaction SM51.
3. On the SAP Servers screen, click on the server for which you need the
information and then click on the Release Notes button.
4. On the SAP Release Information from Server screen, look down the SAP R/3
Kernel information section until you find Kernel Patch number. To the right,
you will find the current patch level of your current SAP instance.

Method Two:

1. Log on to the SAP instance sever using a Telnet session as user <sid>adm.
2. Change the Telnet windows properties to use a Screen Buffer Size of 9999.
3. At the Linux prompt, type:

4 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

disp+work –v

and press ENTER.

4. Scroll back up the listing to where you entered the command in step c.
5. Scroll down the listing untill you find a line beginning patch number. To
the right is the patch number for the SAP instance hosted on this server.
Find the Most Current SAP Support Packages

It should be noted here that sometimes an older SAP may run on

a newer SAP Basis level. For example, CRM 4.0 has a Basis
level of a 6.20 instance but runs on a 6.40 kernel. So make
sure that the kernel patches you download match the SAP R/3
Kernel located via SM51.

1. Log on to the SAP Marketplace using an OSS ID with Administration

rights – http://service.sap.com/patches.
2. In the navigator tree on the right-hand side of the My Application
Components screen. For example, to find new patches for CRM Basis expand
as follows:

Support Packages and Patches

My Company’s Application Components
SAP CRM
SAP CRM 4.0
Entry by Component
CRM Server
SAP BASIS 6.20

3. Scroll down the Download screen until you find your current package
level. Any support packages after your current level will need to be applied to
your SAP System.
4. You may now leave the SAP Marketplace.

Find the Most Current SAP SPAM Update

1. Log on to the SAP Marketplace using an OSS ID with Administration

rights – http://service.sap.com/patches.
2. In the navigator tree on the right-hand side of the My Application
Components screen. For example, to find new patches for SPAM/SAINT for
CRM 6.20 expand as follows:

Support Packages and Patches

My Company’s Application Components
SAP SPAM/SAINT UPDATE
SPAM/SAINT UPDATE 6.20
SPAM/SAINT UPDATE 6.20

3. Click the Download tab of the SPAM/SAINT UPDATE screen. Find

the SPAM/SAINT Update – Version XXX value. If this SPAM version is higher
than you current SPAM version, you will need to download and apply the latest
SPAM update.
4. You may leave the SAP Marketplace.

Find the Most Current SAP Kernel Patches

1. Log on to the SAP Marketplace using an OSS ID with Administration

rights – http://service.sap.com/patches.
2. In the navigator tree on the right-hand side of the My Application
Components screen. For example, to find new patches for CRM 4.0 expand
as follows:

Support Packages and Patches

My Company’s Application Components
SAP KERNEL 32-BIT
SAP KERNEL 6.40 32-BIT
Linux on IA32 32bit
ORACLE & #Database independent

3. Scroll down the Download screen until under the File Name column
you find SAPEXEDB*.SAR files. Unless SAP has instructer you to use a
different kernel, the most recent SAPEXEDB*.SAR is the one you need to
download. You may leave the SAP Marketplace.
4. Now go to the @Database independent section in the same list as

5 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

ORACLE was displayed. Scroll down the page until you find the
SAPEXE*.SAR that matches the same number as the SAPEXEDB*.SAR you
found in the previous step. These two files will give you a complete kernel
replace.
5. You may leave the SAP Marketplace.
Download SPAM/SAINT Updates

1. Log on to the SAP Marketplace using an OSS ID with Administration

rights – http://service.sap.com/patches.
2. In the navigator tree on the right-hand side of the My Application
Components screen. For example, to find new patches for SPAM/SAINT for
CRM 6.20 expand as follows:

Support Packages and Patches

My Company’s Application Components
SAP SPAM/SAINT UPDATE
SPAM/SAINT UPDATE 6.20
SPAM/SAINT UPDATE 6.20

3. To download a SPAM/SAINT update, click on the SPAM/SAINT

Update Title hyperlink. Click the Download button. On the File Download
popup, click the Save button. On the Save As popup, select a location to
store the SPAM/SAINT update and click the Save button. Alternatively, you
may add the patch to your SAP Download Manager and download all patches
in one batch group.
4. Once you have downloaded your SPAM/SAINT updates, you may
leave the SAP Marketplace.
Download SAP Support Packages

1. Log on to the SAP Marketplace using an OSS ID with Administration

rights – http://service.sap.com/patches.
2. In the navigator tree on the right-hand side of the My Application
Components screen. For example, to find new patches for CRM Basis expand
as follows:

Support Packages and Patches

My Company’s Application Components
SAP CRM
SAP CRM 4.0
Entry by Component
CRM Server
SAP BASIS 6.20

3. To download a support package, click on the package Title

hyperlink. Click the Download button. On the File Download popup, click the
Save button. On the Save As popup, select a location to store the support
package and click the Save button. Alternatively, you may add the patch to
your SAP Download Manager and download all patches in one batch group.
4. Once you have downloaded as many support packages as you need
to apply, you may leave the SAP Marketplace.
Download SAP Kernel Patches

1. Log on to the SAP Marketplace using an OSS ID with Administration

rights – http://service.sap.com/patches.
2. In the navigator tree on the right-hand side of the My Application
Components screen. For example, to find new kernel patches for CRM 4.0
expand as follows:

Support Packages and Patches

My Company’s Application Components
SAP KERNEL 32-BIT
SAP KERNEL 6.40 32-BIT
Linux on IA32 32bit
ORACLE

3. To download a kernel patch, click on the

SAPEXEDB_<version>.SAR hyperlink. Click the Download button. On the
File Download popup, click the Save button. On the Save As popup, select a
location to store the kernel patch and click the Save button. Alternatively, you
may add the patch to your SAP Download Manager and download all patches
in one batch group.
4. Now backup a step and instead of clicking ORACLE, click

6 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

#Database independent. The full path would look like this:

Support Packages and Patches

My Company’s Application Components
SAP KERNEL 32-BIT
SAP KERNEL 6.40 32-BIT
Linux on IA32 32bit
#Database independent

5. This produces a list of database independent kernel patches. Scroll

down the Download screen until under the File Name column you find
SAPEXE_<version>.SAR. Use the same instructions in step 5 to download the
patch. Make sure that the version number of your database independent files
matches the version number of your MS SQL Server dependent file.
6. Once you have downloaded the kernel patch, you may leave the
SAP Marketplace.

Download Other SAP Binary Patches

Unlike SPAM/SAINT updates, support packages, and kernel

patches, the storage location for other SAP binary patches can
be either SAP Marketplace or sapserv1. SAP Marketplace is the
normal respository but if you can’t find your patch there, go
look on sapserv1.

***Due to the shutdown of the sapserv1x servers in April, this

section has been discontinued. Everything should now to
accessible via SAP Marketplace.***
Prepare a SPAM/SAINT Update or Support Package for Application

Once you have downloaded your SPAM/SAINT Update and/or support package(s),
they must be moved to the appropriate transport directory and uncompressed.

1. For a SAP instance, move the downloaded K*.?AR file to the

/usr/sap/trans/tmp directory on the SAP Transport Domain Server which is
normally the DEV server of a SAP “Flavor”.
2. Log on to the appropriate server as <sid>adm.
3. Type the following:

cd /usr/sap/trans ¬
SAPCAR.EXE -xvf “tmp\*.?AR” ¬

This will unCAR all CAR and SAR files in the \usr\sap\trans\tmp directory to the
/usr/sap/trans/EPS/in.
4. Log off the server.
5. Log on client 000 of the appropriate SAP system.
6. Go to transaction SPAM.
7. From the menu bar of the Support Package Manager screen, click
Support Package → Load Packages → From application server.
8. On the SPAM: Confirm upload popup, click the green √
picture-icon. The progress of the support package loads will show in the
status bar at the bottom of the screen.
9. Scroll down the SPAM: Uploading Packages from the file system
screen to make sure your SPAM/SAINT update is listed. Use the Go Back
icon to return to the previous screen.
10. You may now leave the SPAM transaction.

Prepare a Kernel Patch for Application

Kernel patches must be applied on the SAP server. The SAP instance must be down
before a kernel patch can be applied.

1. Logon the server to be patched as <sid>adm.

2. The downloaded SAPEXE*.SAR and SAPEXEDB.SAR files must be
uncompressed using SAPCAR.EXE. You can place the SAPEXE*.SAR files in
any directory and use the SAPCAR.EXE –xvf “*.?AR” to unCAR the files.
3. You may now leave the server.

Prepare other SAP Binary Patches for Application

Use the same procedure as Preparing a Kernel Patch for Application.

Application of SPAM/SAINT Updates

7 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

Before you apply the most current SPAM/SAINT, please pull the
OSS Note 484219 - Known problems with transaction SAINT in
Basis Release 6.20 or for whatever version you are using and
review any problems you may have adding the SPAM/SAINT patch.

Once you have loaded the latest SPAM/SAINT update into your support Package
manager buffer, you need to apply the update to your SAP system.

1. Log on client 000 of the appropriate SAP system.

2. Go to the SPAM transaction.
3. From the menu bar of the Support Package Manager screen, click
Support Package → Import SPAM/SAINT update. Click the green √
picture-icon to continue.
4. The progress of the SPAM/SAINT update application will be
displayed in the status bar at the bottom of the screen. These messages look
very similar to the messages generated during a change request transport.
5. When the Restart SPAM popup appears, click the green √
picture-icon to leave the SPAM transaction.
6. Go to the SPAM transaction. You may notice programs compiling in
the status bar at the bottom of the screen. This is normal.
7. Once you are again on the Support Package Manager screen, verify
that the SPAM status in the Status section of the screen contains a green light.
8. You may now leave the SPAM transaction.

Application of SAP Support Packages

Before applying any support packages to your SAP system,

release all “repair” change requests to prevent error messages
due to locked resources. Repairs are usually advanced
corrections obtained from SAP Notes that are eventually
accumulated into support packages. So the same objects
“repaired” in the advanced corrections will be “repaired”
during the application of the support package. Releasing the
repair change requests allows the support package to overlay
the temporary advanced correction “fix”.

Before you apply the most current SPAM/SAINT, please pull the
OSS Note 782140 - OCS: Known problems with Support Packages in
Basis Rel.6.20 or for whatever version you are using and
review any problems you may have adding the SPAM/SAINT patch.

Once you have loaded the latest support packages into your support
Package manager buffer, you need to apply the packages to your SAP
system.

1. Log on client 000 of the appropriate SAP system using a

adminitrator user ID that is not DDIC or SAP*.
2. Go to the SPAM transaction.
3. On the Support Package Manager screen, click the Display/Define
button to build your import queue. On the Component Selection popup, click
on the Comp. ID having support packages you want to install. The component
order support packages should be applied is SAP_BASIS, SAP_ABA,
SAP_APPL, and PI.
4. A list of all application support packages for the selected component
will appear in the Define Queue popup. Select the support packages you
want to apply. See SAP Note 782140 for information on restrictions to
grouping support packages into queues. The Package ID with the green √ to
the left is the highest support package to be placed in the queue. All lower
number support packages for this component will be applied as well. Click the
green √ picture-icon to confirm the queue.
5. From the menu bar of the Support Package Manager screen, click
Support Package → Import queue.
6. On the SPAM: Import Queue popup, read the displayed information
and then click the green √ picture-icon to continue.
7. The progress of the support package application will be displayed in
the status bar at the bottom of the screen. These messages look very similar
to the messages generated during a change request transport.
8. When the Imported successfully Information popup displays, click
the green √ picture-icon to continue.
9. On the Support Package Manager screen, verify that the SPAM
status in the Status section of the screen contains a yellow light and the Next
action value is Confirm queue. To confirm that your support packages applied

8 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

completely, click the green √ picture-icon. A Support Package queue was

confirmed message will appear in the status bar at the bottom of the screen.
10. You are ready to build another support package queue, or if you have
applied all the necessary support packages, you may now leave the SPAM
transaction.

Application of SAP Kernel Patches

*** It is recommended that the /usr/sap/<SID>/SYS/exe/run directory be copied to

/usr/sap/<SID>/SYS/exe/backup_run before replacing the kernel ***

1. Log on to the appropriate server as <sid>adm.

2. Double check that the SAP instance, SAPOSCOL, and
SAP<SID>_00 services are stopped.
3. To apply the new kernel patch to a R/3 instance, copy the new files
into usr\sap\<SID>\SYS\exe\run directory. If prompted for overwrites, say yes
to all.
4. After the new kernel has been copied make sure that the following
file ownerships are correct:

All files in /usr/sap/<SID>/SYS/exe/run <sid>adm

/usr/sap/<SID>/SYS/exe/run/saposcol root
/usr/sap/<SID>/SYS/exe/run/br* ora<sid>
/usr/sap/<SID>/SYS/exe/run/sapdba ora<sid>

5. After the successful completion of the kernel patch, you may bring
the instance back up and log off the server.

Application of other SAP Binary Patches

Use the same procedure as Application of SAP Kernel Patches.

Other SAP Issues

SAP System Response Troubleshooting

1. What has changed since the performance is poor?

System Parameter Changes (RZ10)?

Increase in the number of users?
Kernel patch?
Support Packages?
Linux and Oracle patches?
Hardware Changes?

2. Any signs of general problems in the System Log - SM21?

3. Places to look:

SM50: → Process → Trace → Components – is there a Trace level

set? Is it greater than 1? What is the utilization of the work
processes? Click the white clock picture-icon. Is the total CPU for the
last dialog process > 10 minutes?
ST04: Is the database monitor activated? If yes, it should deactivated it
in normal operation. ST02: Check the buffering quality. If paging occurs
in a buffer, the corresponding parameter should be increased. Also refer
to SAP Note 121625 in this context.
ST03: → Select a server → Today's Workload: What are the response
times? In the case of poor response times, where is most of the time
needed? Button 'Top Time': Are there a lot of different transactions with
poor response times or are there only a few? Is a certain transaction
always slow or only sometimes?
ST06: → Detail analysis menu → Hardware Info. To which extent are
the hardware resources utilized? Call ST06 at times with poor system
performance. What is the CPU utilization? → Goto → Current Data →
Snapshot → Top CPU processes and display the main CPU consumers.
What is the utilization of the disks? How high is the paging in the base
pool?

9 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

4. If only few transactions are affected by the performance problem,

you should additionally note the following points:

1. Check whether modifications were made in the

affected or related transactions.
2. ST03: Display the corresponding performance
records.
3. SE30: Carry out a runtime analysis for the affected
transactions.
4. ST05: If the database times are high, you should
generate an SQL trace of the affected transactions to find out
whether the database access is carried out in a useful way.

5. Look for tables that have experienced unusual monthly growth.

1. DB02 → Space Statistics button

2. Press Enter on the Tables and Indexes popup
3. History → All objects off/on
4. Click the Months button
5. Click on the first number under the Rows –
Chg/Month header and click the Sort button.
6. The sorted results shows the top tables when it
comes to rows changes per month. These tables are your
“database hogs”.

6. What is considered “normal” response time?

Performance Standards:

Response time -- 1 second (dialog), < 1 second (update)

CPU time -- approx 40% of average response time
Wait time -- < 1% of average response time
Load time -- < 10% of average response time
DB request time -- approx 40% of average response time

Database Standards:

Direct reads -- < 10 ms

Sequential reads-- < 40 ms
Changes -- < 25 ms

High Value Indications:

DB request time –- Database or index problems

Load time -- Buffer problems
Wait time -- Not enough work processes
Locked tasks
Long running transactions
SAP System Start Up Troubleshooting

Whether you are trying to start a brand new SAP instance, or an old one, there are
some very specific places to look for information.

If this is a brand new SAP instance, and the installation completed 100% successfully,
you know that the instance itself must be viable. If your installaion was never able to
complete due to the instance not being able to start up, the issue is probably due to
lack of resources. Use the sapinst directory to search the installation logs and find
your problem. Sort them with “ls – ltr” is see the list sorted in descending order for
the ease of viewing.
If you have a test searching tool, look for “error” in all files with the suffix “.log”.

If your SAP instance has been up and running fine for a good while, then something
has probably changed that makes it not come up.

· have you changed any instance paramters?

· did you do a kernel replacement for some reason?
· have there been SAP Support Packages applied that
might
necessitate a kernel replacement?
· have there been OS patches?
· is the database archiver stuck or hosed?
· has a crucial directory run out of space?

10 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

· has a semaphore or ipc segment gotten stuck from a

previous run?
· is your memory so fragmented that it can’t get enough
primary space to start the instance?
· has someone changes the directory privileges?

To investigate an unsuccessful start up, look at the logs in the /home/<sid>adm

directory. Sort them with “ls – ltr” is see the list sorted in descending order for the
ease of viewing.

If nothing obvious is found, go to the /usr/sap/<SID>/DVEBMGS00/work directory

and do the same thing in this directory. The most useful information can be found in
the dev_wx, dev_ms, dev_disp, dev_rfcx, and stderrx files.

If all else fails, zip the contains of the /usr/sap/<SID>/DVEBMGS00/work directory,

open a problem with SAP, and attach the zipped file to it. Also provide them with the
answers to the above questions as well as your current hardware and database
platforms, patch level for SAP support packages, kernel, and the OS, and anything
else you might think useful.
The Delicate Art of SAP Note Search

How often have you seen a posted message saying "I have searched through SAP
Notes and can find nothing related to this matter."? And how often have you gone to
SAP Marketplace and done a search yourself and found a hit? If we only had a had a
nickle...

Searching SAP Notes (formerly known as OSS notes) is a science as well as an art.
Lets use this error message as an example:

"BR051I BRBACKUP 6.10 (80)

BR055I Start of database backup: bdmsqjbi.anf 2004-02-27 00.05.42
BR602W No valid SAP license found - please contact SAP"

First, you should search the specific error message "BR602W No valid SAP license
found". If you get at least one hit, you should read the SAP Note even if it didn't look
as if it pertained 100%. Why? Because it might contain information leading to other
notes that did pertain, or give you new ideas for more search terms to help narrow
the scope of my query.

If you didn't find a note that matched the problem, you could make your next search a
little less specifc, like "brbackup No valid SAP license found". First you could search
for the phrase, and if you had no luck, you could search for all words. And if that
produced nothing tangible, you could make it even less specific as in "brbackup SAP
license error" or "SAP license error".

Normally a very specific query will get you the results you need. But sometimes things
get lost in translation. For example, you are applying support packages and get an
import error with the following message "Panic! Panic! Panic! there's no object
header". Since we speak English and we realize that the SAP product was designed
and implemented in Germany, we have to guess that the English word "Panic!"
somehow was translated from the German word "Warning!" and that we can
temporarily delay a panick attack until we can research the error. Moral of the story?
Realize that some things just don't translate correctly from language to language,
and search accordingly. If you searched for "Panic! Panic! Panic!" and got no hits,
you could try "warning message no object header".

Last, and not least, read and become familiar with your SAP Notes. There are certain
notes that you pull over and over again due to some task that needs fresh, current
and precise information. These are mostly lists of supported printer devices, known
problems with applying patches, etc.

SAPGui Troubleshooting

If a user seems to be experiencing SAPGui errors, several things need to be

checked:

· Is the operating system on the user’s workstation patched to the

level recommended by SAP?
· Is the user using a version of SAPGui that is too old for his
workstation?
· Is the user using a version of SAPGui that is not certified for his
operating system?
· Is the user’s workstation having resource problems?

11 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

· Is the user’s workstation connected to the LAN?

· Can a different user reproduce the same error on the same
workstation?
· Are there any SAPGui patches that have not been applied?

Most SAPGui problems can be solved by either a) deleting and reinstalling SAPGui
on the workstation, or b) deleting and installing a newer version of SAPGui.

Make sure that these lines were added to the services file on the user’s workstation:

After you have successfully configured your SAPGui, add these three lines to the
bottom of your \Windows\system32\drivers\etc\services file:

sapdp00 3200/tcp
sapmsR3I 3600/tcp
#

If you have SAP Instances using System Numbers other than 00, you will have to add
their equivalents to the services file as well. Also, check if you are having connection
problems due to firewall restrictions. And, be sure that your Insert Key is set so that
you can type your password in properly – you can delete whatever is in the password
field in order to enter your password.

If you have never tested connectivity to a SAP instance on the workstation having the
connection problem, first you need to make sure that the workstation can connect to
the SAP server in some non-SAPGui way. Let’s say your user us trying to connect to
System ID (SID) DEV, System Number 00, and IP address 10.1.10.11. Open a
DOS-Windows and type this:

telnet 10.1.10.11 3200¬

If the screen rolls and goes totally blank then your dispatcher is reachable. You can
close the DOS session. If your window never goes completely blank and you set a
"Connecting To 10.1.10.11... Could not open connection to the host, on port 3200:
Connect failed" error message right under the command you entered, the dispatcher
is not reachable. Also, make sure the \Windows\system32\drivers\etc\hosts file on
the workstation is correct.

For information regarding operating system, resource, and hardware requirements for
running SAPGui, see SAP Note 26417 - SAP GUI Resources: Hardware and
software.
Central User Administration is Not Transferring Change from
the CUA Parent Client

If CUA stops sending changes from DEV to QAS or PRD, something in the RFC
setup has changed. Either the password or the user type for RFC_USER was
changed, or the SM59 RFC connection to was changed and is no longer working.

Use SCUL in DEV in your DEV CUA parent to list the errors that are occurring. Look
for the user you tried to transport but could not. You might see “You are not
authorized to change users in group” or “No authorization for group users in role”.
This does not mean that YOU are not authorized, it means that the RFC_USER doing
the ALE communication between the SAP systems is not authorized.

First, reset the RFC_USER password in DEV, QAS, and PRD. And make sure that
the user type is Communication and not dialog. Now go to sm59 and do remote
logins using the QAS RFC connections. If they work (ie nothing seems to happen
after you click the remote logon button) everything should now be fixed. If you get a
logon screen for QAS, change the password in the sm59 screen to the same
password you changed RFC_USER to in DEV and QAS.

Retry your user change. If it still doesn’t go to QAS, maybe the QAS system is
hosed and down.

Important SAP Marketplace Links

Inbox http://service.sap.com/inbox Read

messages from SAP to you
Installation Guides http://service.sap.com/instguides Download SAP
product installation
guides
License Keys http://service.sap.com/licensekey Request New
Permanent License Key
Messages to SAP http://service.sap.com/message Open problems

12 of 13 04/15/11 10:14 AM
SAP BASIS Tutorial 3 Unix & Linux - SAP BASIS Administration and ... http://sites.google.com/site/saparchives/SAP-basis-operation-3-unix--linux

with SAP
QuickLinks Page http://service.sap.com/quicklinks An index of
SAP links
Oracle DBA Page http://service.sap.com/dbaora Page
for Oracle DBA Material
OSS Notes http://service.sap.com/notes Search
the SAP Notes Database
Patches http://service.sap.com/patches
Download SAP software patches
Remote Connection http://service.sap.com/remoteconnection Learn about
the OSS connection and
order it from
SAP
Service Connection http://service.sap.com/serviceconnection Open a
Service Connection for SAP
to access
your SAP landscape
Software Distribution http://service.sap.com/swdc
Download new images of
Installation
CDs & DVDs
SSCR http://service.sap.com/sscr Register
Developers and Changes
made against
SAP objects
User Administration http://service.sap.com/user-admin Add/Change
OSS ID user information

SAP BASIS - INDIA

Sign in Recent Site Activity Terms Report Abuse Print page | Powered by Google Sites

13 of 13 04/15/11 10:14 AM