Transact Codes

To list all transaction codes se16 and then type tstcfind /usr/sap/RS2 -name core fastest way to find core filesrspfpar to display profile parameterSMLG: maintain logon groupsSM51: SAP serversSM50 : click on processor from menu and click on trace file to reset files. This will empty up disk space… this will happen in OS collector stop or producing error…. Some time its good to run this command from UNIX command prompt “ > (trace file name like dev_rfc) to clean these files faster instead of using of going through sm50SICK: Check the system statusSM21: System logsSM13: Update requestSm12: Find locks entreesDB12: to check oracle BackupDB02: Database Performance: table and indexGRMG: generic request for monitoringSM35: batch jobsST11: error log filesSM37 – display background job (be sure you only put activity 03)SM36 to create jobsSM69 and SM49 External Operating system commandsSE01 (transaction code) click on log for informationST06 CPU load and IO-waitST03 performanceST02 BufferAl08 user infoRZ70 : SLD from ABAP sitesSMGW system gatewayST11 to check ICMP trace file for CRMCRM_ICI_Trace transaction command to check ICI trace in CRM serverRZ11 to find exact path like rdisp we can use *rdisp* and pressing F4 to find the exact command..RZ10 to read the profile to find exact Path like rdisp SM37 and ST22 job logSOST take it to the sap connect request for printing jobsSP01 printer spoolSPAD Spool AdministrationSCOT Sap connect administrationRspfpar it’s a transaction code to find printer parameters….use rspo* this to find printer spooler parameter. Look for rspo/store_location this parameter, see if shows db or os path to find spool request… RZ12 RFC server group maintenanceSM02 to post message for usersDB02 to show info about database To increase the size of the data base in solaris 10 use this command brspace -f tsextend -t PSAPUNDO

To increase the size of the data base in solaris 9 use sapdba command and follow the screenIn work directory: Use rm core if this file is not actively written then use this command “ ln –s /dev/null core” if its actively written then use “> core” to empty the file…

SARA: You can do archiving, component wise using tcode SARA. After archiving you will get free space on your disk.

SM04 and AL08:Tracking user logon. where do u schedule background job in sap : sm36Create new users :su01Rz10 : SAP Alert Monitor/Database alert monitor/ Operating system alert monitor/ Monitor call distribution/ Monitor current workload/ Local Alert Monitor for Operat.Syst/ Local File System MonitorSCAT: Creation of the CATT test casewhat are the standard user coming with sap in a new installation : sap* and DDICwhat are the standard clients in a fresh implementation : 000, Early watch Client : 066 For users to copy sap standard date from 011 what are users which get created at the operatiing system level when you install sap : Sid, Adm. SAPservice<sid>what do u use to deploy plugins, addons : SAINTfor updates : spamwht is the transaction to set operation modes : rz04what transaction is sql trace : ST05what tcode for system log : SM21what tcode for system trace : ST01what transaction for viewing tables (data browser) : SE16SE11 : you can see ABAP dictionarywhat transaction to run abap programs and reports or read abap code : SE38wht is db calender transaction : DB13what is the transaction where we can all the memory,cpu, db performance utilization : st03nNT operating system monitor..includes CPU and memory etc/ Remote File System Monitor: St06where can you configure TMS from : STMSwhts transport organizer : defines Queues , lets your distribute in the instances wht is a tcode where you can see all the active users : al08lets see you want to check how many users are in the system wht you will dothere is a table called usr02> go to se16 > put the table name usr02 > and run it > show all the users in the sap systemwht is the transaction SALE : define sending and receiving systems and for its for creating logical systemtcode for creating a new client : where do u create a rfc connection from : SM59To delete a client : SCC5to monitor the client copy : SCC3to do a remote client copy : SCC9to do a local client copy : SCClwht is ccms : computing central management systemswht is the tcode for ccms : RZ20

if you type srzl you should see the screen sap easy access COMPUTING center management system Call transaction SM51 and determine the name of the instancetransaction SM51, list the types of work processestransaction SM50 to determine the number of dialog work processesTo display all the users in the entire system, use transaction AL08.SM04 to determine how many sessions you are usingST03 for whole summarized total work perform by any userSA38 - run reports (unless you make all customize reports)Sm51- kernel releaseSEARCH_SAP_MENU - this will help user to find the right path using SAPstandard menuSMX - display own jobSM37 – display background job (be sure you only put activity 03)SQVI - create own querySP02 - display own spoolSPAD : create your own printerS00 - create document and send (just like SBWP)SO00 - SAP office short messageSo01/sbwp : SAP emailSU53 - very important to include this. this will show the authorizationMessage.SE10- I want to copy some table content between SAP system Production and DevelopersSM02 : You can send messages to users logged onSe37 : Function Builder- to write functionsSe93 : you can create your own transactionsSCC8 : Client exportSt22: Abap rumtime errorPFCG : To create rolesSCUA: Central user administratorSPRO : to customize dataSM66 : Global work process over-viewSM01: to lock transactionsSCIF to monitor XI We20 and we21 for XISMQR CRM middle ware QueSM52 to display available VMCSE03 to change client informationSMSY to generate key from solution managerSM37 and ST22 job logSMICM to check Http servicesSICF select virtual host click execute then click on default host-> sap-> BC->BSP. Right click on BSP to check if its activated or not…TCODE:CRMC_IC_ACTIONWZ to launch IC web ClientSMQ1 or SMQ2 to check if que are running slow before running index rebuild scheme/$otr is a transaction to reset buffer

To start IGS from Command Line: nohup /sapmnt/RD2/exe/igswd_mt -mode=profile pf=RD2_DVEBMGS31_miller-1(this Profile could be deferent or change the profile) &errors in the IGS logs at /usr/sap/<SID>/<INSTANCE>/igs/logcheck the logs in /usr/sap/<SID>/<INSTANCE>/work for errors related to IGSuse SE38 in program “GRAPHICS_IGS_ADMIN” and click execute and click Execute again to monitor acitivity…

to check the database instance is running.. Need to go to sql command line and type select database_status from V$instances

ps –ef | grep smon to see if oracle is running

The IGS server is down.Needs to be restarted.here are the commands to restart IGS if on UNIX.

1 cd /usr/sap/<i><SID>/</i>DVEBMGS<i><system number>/</i>igs

2 ./bin/stopigs3 ./bin/startigs -p /usr/sap/<i><SID>/</i>DVEBMGS<i><system number>/</i>igs

Oracle command to find time on the system:SELECT TO_CHAR(CURRENT_DATE, 'DD-MON-YYYY HH:MI:SS') FROM dual;

Unix commandPrstat –a like vmstat or iostatlpstat –o to clean /varusr/sap/(sid)/(int)/profile/work to check all log file like in ST11/etc/ services to check servicesdf –tk |grep (file name)df –tk will show mount file system with sizedf –k information on current file systemdf –tk | grep saparch or oraarchdu –sk Tells you how much space a file occupies use du -s *.txt - Would report the size of each txt file in the current directory. Below is an example of the output.du -ch *.txt - Display the size of the txt files in a friendly size format listing as well as the total capacity of all the files combined/var/log/syslog to check logs for printinggrep (entry name) (file Name)To find a information on file use /(word looking for)To make change in a file :%s/ (change from)/(change to)g(for global or many change). If its only one change take g outCopy file from one system to another scp (system 1):/path (system 2):/pathTo find out who is working in the system type finger and enterFirst tar the file by using tar command and then we can use Compress command to compress this tar file

1. Hidden files start with .(dot) command is to find ls –alrt. ls –lrt will not show hidden files

2. Log file of sap is in home/(sid)adm3. Instance file path /usr/sap/(sid)/dvebmgs00/work4. Log files path /usr/sap/(sid)/jc45/work5. /usr/sap to find out sap systems

This service allows every UNIX machine in a local area network to read the password file using the ypcat passwd command, including shadow password files.Example : ypcat –Host | grep (SID)DATAFILEdeactivate the Updates from SM14 and then follow the step belowFirst check is it system datafile or non system datafile.If this is non system down time is not required.sqlplus "/ as sysdba"SQL> alter tablespace <name> offline;SQL> !mv <sourcedir/*> <targetdir/>SQL> alter tablespace <name> rename datafile 'oldpathand name' to 'new path and name';SQL> alter tablespace <name> online;SQL> exitFor system datafile u need to down system.Let me know if u need any help reg this.think 1 of your tablespace is full. Then open telnet connection and logon to ora<sid> user and run brtools. Select space management and increase the size of the tablespace.conn /as sysdbabrtoolstablesapce maintanenceextend tablespaceBRTOOLSIf any object(table/index,Datafile will not reach maximum extents as u said) reaches maximum extents you can increase them using T-code SE14.Go to SE14 -->give the table name-->click on edit-->click on storage parameters-->and you can increase the max.extents here.If your table space is full you have to add Datafile or resize existing Datafile.To add datafile please do as specified below.1.If yours is unix login as ora<SID> and type brtools at command prompt.2.in the menu select 2,space management3.in the next menu select 1.extend table space3.In the next menu select 3,tablespace name and it prompts for the name and type PSAPUNDO.4.CONTINUE5.CONTINUE6.you will get the following screen.Options for extension of tablespace PSAPUNDO (1. file)

1 * Last added file name (lastfile) ....... [/oracle/CRD/sapdata2/undo_1/undo.data1]2 * Last added file size in MB (lastsize) . [6800]3 - New file to be added (file) ........... [/oracle/CRD/sapdata2/undo_2/undo.data2]4 ~ Raw disk / link target (rawlink) ...... []5 - Size of the new file in MB (size) ..... [6800]6 - File autoextend mode (autoextend) ..... [no]7 # Maximum file size in MB (maxsize) ..... [10000]8 # File increment size in MB (incrsize) .. [20]9 - SQL command (command) ................. [alter tablespace PSAPUNDO add datafile '/oracle/CRD/sapdata2/undo_2/undo.data2' size 6800M autoextend off]

Standard keys: c - cont, b - back, s - stop, r - refr, h - help-------------------------------------------------------------------------------

7.choose 5 if you want to specify size of Datafile.Also check whether enough space is available at OS level to add this datafile.(use df -k "path of directoy" to check space

8.click on continue and it will take few minutes to add the datafile and your tablespace is now extended!You can execute this when SAP is Up and running,no need to stop SAP or DB.

Print Spooler issueLook in SM50 for processes called 'SPO' these are SAP's spooler/printing processes. By default there will be just 1. You can increase the number of these by changing the instance profile parameter "rdisp/wp_no_spo" via RZ10. You will need to restart the instance for the change to take effect.

Setting Access Privileges for SAP System Directories and Files

SAP Directory or Files Access Privilege in Octal Form

Owner Group

/sapmnt/<SID>/exe 775 <sid>adm sapsys

/sapmnt/<SID>/exe/saposcol 4755 root sapsys

/sapmnt/<SID>/global 700 <sid>adm sapsys

/sapmnt/<SID>/profile 755    

/usr/sap/<SID> 751    

/usr/sap/<SID>/<Instance ID>

755    

/usr/sap/<SID>/<Instance ID>/*

750 <sid>adm sapsys

/usr/sap/<SID>/<Instance ID>/sec

700 <sid>adm sapsys

/usr/sap/<SID>/SYS 755 <sid>adm sapsys

/usr/sap/<SID>/SYS/* 755 <sid>adm sapsys

/usr/sap/trans 775 <sid>adm sapsys

/usr/sap/trans/* 770 <sid>adm sapsys

/usr/sap/trans/.sapconf 775 <sid>adm sapsys

<home directory of <sid>adm>

700 <sid>adm sapsys

<home directory of <sid>adm>/*

700 <sid>adm sapsys

UMASKNewly created files have rights determined by UMASK definitions. An UMASK is a four digit octal number that specifies those access rights that are not to be given to newly created files. You can define UMASKS in any of several files, to include:

        .login

        .cshrc

        .profile

        /etc/profile

As with UNIX access rights, the corresponding octal positions represent user, group, and world access, and the value of the digit represents which access privileges should be removed (remove none = 0, remove write = 2, remove all = 7). You can use the UMASK to automatically restrict permissions for newly created files. For example, by defining a UMASK of 0027, you specify that all newly created files have the access rights 750.

If there are several SAP systems on the server(s), it is possible to perform the administration tasks separately using different groups. Assign the access rights appropriately for the files in the directory \usr\sap (to include sub-directories). You can distinguish between the administrators and groups by using the system IDs of the SAP systems (for example, sapsys<SAPSID1>, and sapsys<SAPSID2>). All administrators should have access to the two directories at the \usr\sap top level.

If there are several SAP systems installed on a single server, then an additional area of shared memory exists. This memory is created by saposcol and is used jointly by the OS Collector and all SAP systems. Therefore, give full control access rights to the sapsys<SAPSIDx> groups for the executable file saposcol. To avoid access conflicts here, start saposcol before starting the first SAP system.

 Example: saposcol -k

Finding and Removing Old and Inactive FilesPart of the job of cleaning up heavily loaded file systems involves locating and removing files that have not been used recently. You can locate unused files using the ls or find commands. For more information, see ls(1) and find(1).

Other ways to conserve disk space include emptying temporary directories such as the ones located in /var/tmp or /var/spool, and deleting core and crash dump files. For more information about these files, refer to Chapter 39, Managing System Crash Information.

How to List the Newest FilesList files, displaying the most recently created or changed files first, by using the ls -t command.

$ ls -t [directory]

-t Sorts listings by latest time stamp first. 

directory Directory you want to search. 

Example--Listing the Newest FilesThe following example shows how to use ls -tl to locate the most recent files within the /var/adm directory. The sulog file was created or edited most recently.

$ ls -tl /var/adm

total 134-rw------- 1 root root 315 Sep 24 14:00 sulog-r--r--r-- 1 root other 350700 Sep 22 11:04 lastlog-rw-r--r-- 1 root bin 4464 Sep 22 11:04 utmpx-rw-r--r-- 1 adm adm 20088 Sep 22 11:04 wtmpx-rw-r--r-- 1 root other 0 Sep 19 03:10 messages-rw-r--r-- 1 root other 0 Sep 12 03:10 messages.0-rw-r--r-- 1 root root 11510 Sep 10 16:13 messages.1-rw-r--r-- 1 root root 0 Sep 10 16:12 vold.logdrwxr-xr-x 2 root sys 512 Sep 10 15:33 sm.bindrwxrwxr-x 5 adm adm 512 Sep 10 15:19 acctdrwxrwxr-x 2 adm sys 512 Sep 10 15:19 sa-rw------- 1 uucp bin 0 Sep 10 15:17 aculog-rw-rw-rw- 1 root bin 0 Sep 10 15:17 spellhist

drwxr-xr-x 2 adm adm 512 Sep 10 15:17 logdrwxr-xr-x 2 adm adm 512 Sep 10 15:17 passwd

How to Find and Remove Old or Inactive Files 1. Become superuser.2. Find files that have not been accessed for a specified number of days and list them

in a file.

# find directory -type f[-atime + nnn] [-mtime + nnn] -print > filename

directory Directory you want to check. Directories below this also will be checked. 

-atime +nnn Finds files that have not been accessed within the number of days you specify. 

-mtime

+nnn Finds files that have not been modified within the number of days you specify. 

filename File containing the list of inactive files.

4. Remove the inactive files that you listed in the previous step.

# rm `cat filename`

filename File created in previous step which contains the list of inactive files. 

Example--Finding and Removing Old or Inactive FilesThe following example locates regular files in /var/adm and its directories that have not been accessed in the last 60 days and saves the list of inactive files in /var/tmp/deadfiles. These files are then removed with the rm command.

# find /var/adm -type f -atime +60 -print > /var/tmp/deadfiles &

# more /var/tmp/deadfiles

/var/adm/log/asppp.log/var/adm/aculog/var/adm/spellhist/var/adm/wtmpx/var/adm/sa/sa13

/var/adm/sa/sa27/var/adm/sa/sa11/var/adm/sa/sa23/var/adm/sulog/var/adm/vold.log/var/adm/messages.1/var/adm/messages.2/var/adm/messages.3# rm `cat /var/tmp/deadfiles`

#

How to Clear Out Temporary DirectoriesBecome superuser. 1. Change to the /var/tmp directory.

# cd /var/tmp

2.

3. Caution -

4. Be sure you are in the right directory before completing the following step. The next step deletes all files in the current directory.

5.

6. Delete the files and subdirectories in the current directory.

# rm -r *

7. Change to other directories containing unnecessary temporary or obsolete subdirectories and files, and delete them by repeating Step 3 above.

Example--Clearing Out Temporary DirectoriesThe following example shows how to clear out the /var/tmp directory, and verifies that all files and subdirectories were removed.

# cd /var/tmp

# ls

deadfiles wxconAAAa0003r:0.0 wxconAAAa000NA:0.0test_dir wxconAAAa0003u:0.0 wxconAAAa000cc:0.0 wxconAAAa000zs:0.0# rm -r *

# ls

#

How to Find and Delete core Files1. Become superuser. 2. Change the directory to where you want to start the search.

3. Find and remove any core files in this directory and its subdirectories.

# find . -name core -exec rm {} \;

Example--Finding and Deleting core FilesThe following example shows how to find and remove core files from the user account belonging to jones using the find command.

# cd /home/jones

# find . -name core -exec rm {} \;

How to Delete Crash Dump FilesCrash dump files can be very large, so if you have enabled your system to store these files, do not retain them for longer than necessary.

1. Become superuser. 2. Change to the directory where crash dump files are stored.

# cd /var/crash/system

system System that created the crash dump files. 

4.

5. Caution -

6. Be sure you are in the right directory before completing the following step. The next step deletes all files in the current directory.

7.

8. Remove the crash dump files.

# rm *

9. Verify the crash dump files are removed.

# ls

Example--Deleting Crash Dump FilesThe following example shows how to remove crash dump files from the system venus, and how to verify that the crash dump files were removed.

# cd /var/crash/venus

# rm *

# ls

http://jesus.olea.org/personal/SAP.htmlhttp://www.sap-img.com/sap-bc.htmhttp://help.sap.com/saphelp_nw04/helpdata/en/70/b38937809c8f71e10000009b38f842/content.htm

stopsap d(directory)36 (Instance)Startsap d36stopsap all will stop all sap system except central instance --- startsap allsaposcol -k os collectorcleanipc (IPC) remover3trans -dIPCrm -musr/sap/(instance) to look for license file

saplicense -show show status saplicense -installsaplicense -get will show the status of license keyHow to install license

sap* can get into this system without licnese and client number to install license key....

You can refresh the buffer of an application server (if you mean so) by using the transaction "$SYNC". However, as Anand mentioned this is a critical operation which will have effect on the overall system.

If it is the HR buffer you mean, you can use the FM "*PSBUFFER*INIT*" .

/usr/sap/sid/dvebmps for central instance

under /sapmnt/<SID>/profile/ or /usr/sap/<SID>/SYS/profile/ same thing

The sequence is startup profile then DEFAULT.PFL and then instance profile

START_DVEBMGS##_<hostname> startup profile file<SID>_DVEBMGS##_<hostname> instance profiledefault.pfl

RD2K903263RD2 (sid)---- domain controllerse01 (transaction code) click on log for informationstms

SAP Administrator Daily Activities SAP DAILY ACTIVITIES

1] Check that all the application servers are up: sm51 SAP Servers sm04/al08 Logon Users

2] Check that daily backup are executed without errors db12 Backup logs: overview

3] SAP standard background jobs are running successfully. Review for cancelled and critical jobs. sm37 Background jobs--- Check for successful completion of jobs. Enter * in user-id field and verify that all critical successful jobs and review any cancelled jobs.

4] Operating system Monitoring st06

5] Extents monitoring db02 Database monitoring--Check for max-extents reached

6] Check work-processes(started from sm51) sm50 Process overview-- All work processes with a running or waiting status.

7] Check system log sm21 System log-- Set date and time to before the last log review. Check for errors ,warning, security, message-bends, database events.

8] Review workload statistics st03 Workload analysis of <sid> st02 tune summary instance

9] Look for any failed updates sm13 update records

10] check for old locks sm12 lock entry list

11] Check for spool problems sp01 spool request screen-- check for spool that are in request for over an hour.

12] Review and resolve dumps st22 ABAP Dump analysis

13] Checking .trc file in SAP trace directory for block corruption on daily basis. C:\ORacle\sid\saptrace

14] Archive backup

brarchive -f force -cds -c Insert the archive backup tape

----------------------------------In st22 look for the core dumps if any and report to the respective consultants and try to know why it happened.

In sm21 try to check for errors.

In sp01 try to see if any spool jobs have failed.

In st02 look if any swaps are happening, swaps are not good for performance.

In st04 look for Database alert logs and Performance.

In st03 look for ratio hits.

In sm59 look for connectivety tesing if there are other systems also connected to your SAP R/3 system

In db13 look if the jobs have run successfully.

In sm37 look for any cancelled scheduled job and take action appropriately.

In sm12 look for any pending locks from the previous days.

In sm13 look for any hanged updates, or updates pending for long or updates in PRIV mode. -----------------

Mass transport imports

I remember when all transports had to be done via the operating system command line, which is where this tip comes in. Occassionally, after an upgrade or the implementation of support packages, your developers will want you to import a lot of transports back into your QA (or even your production) system.

A quick way doing this is as follows:1) Import the list of transports into Excel, 1 transport per line.2) In the next column, enter the following Excel Formula in the first cell: ="echo 'Importing "&A1&"';"&"tp addtobuffer "&A1&" SID;"&"tp import "&A1&" SID;"3) Copy this cell down the second column as far as necessary, so you get an echo, addtobuffer and import command generated for each transport.4) Once the command lines are generated, copy the second column, and use PASTE SPECIAL, VALUES to paste it to a third column.

5) Now you have a command line string for each transport. Copy this column into a file in /usr/sap/trans/bin on the system you're importing into, and execute the file.

Notes:Obviously, you can add any extra parameters, just by changing the formula you use in column 2. For Windows environments, don't create the echo command - just make sure you have echo set on in the command window. For UNIX environments, do leave the echo statement in, just in case there are problems - you'll want to tell your developers which transport was broken.

It is very easy to obtain the patch level of some core R/3 executables such as: disp+work, tp and r3trans. Many people would like to know how to do this. Here, I will show you how to do it for R/3 systems running on Windows and SQL Server environments. 

1. Go to the command prompt.  2. Change to the "run" directory of your SAP instance (cd \usr\sap\<SID>\sys\exe\run).  3. Run the following three commands: 

         dsp+work -V | find "patch number"  

         tp -V | find "patch number"      

         r3trans -V | find "patch number" 

If you want to see all the release information, then do not filter for the patch number. 

Now that you know how to do this, you can get creative and write a little script that reads the names of all your SAP servers from a text file and then it runs the three commands listed above. This way, you can get the patch level of all your systems by just running a script. This becomes in handy when you're consulting or putting reports together. 

Transport Request (STMS) client import 1. Run tcode STMS2. Click the button with the truck (or F5)3. Doubleclick on the queue you want to schedule the import to4. Click on the button with the truck (or CTRL+F9)5. Selct "At Start Time" and specify a time for the first run6. In the same windows, you can choose "Period" (even if the field looksdeactivted)7. Click continueNow the import job is scheduled.To study : earlywatch, SAPCPIC concentrate more on performance and system support, tablespace, datafiles, performance

multiple user loggin in the system lets so like 50 users and they run catt scripts mass data load scripts and i check how is performance of the system like  cpu utilization, memory utilizationand  I/o utilization before going to production in every company they do stress  ing

tp import T11k904711 P11 U06

tp import all <sapsid>

tp export T11K904711 client123

The individual modes are:

0 Overtaker: Import from the buffer without deleting and set unconditional mode 1 in the buffer to trigger another import.

1 During export: Ignore the incorrect status of the command file.

  During import: Ignore the fact that the change request was already imported.

2 During export: Do not expand the selection with TADIR brackets.

  During import: Overwrite original objects.

3 During import: Overwrite system-dependent objects.

6 During import: Overwrite objects in unconfirmed repairs.

8 During import: Ignore restrictions based on table classification.

9 During import: Ignore the fact that the system is locked for this type of transport.

SAP Database Startup and Shutdown

Startup

- Login as '<sid>adm'

- To interrupt Open Windows 'Shift Control-C'

- Unix > startsap all (this will startup the SAP and database system)

To stop central sap stop all (dvembs00)

Note :- startsap R3 - will startup SAP only startsap DB - will startup database only

SAP Startup Profile resides in /sapmnt/<SID>/profile/<SID>_DVEBMGS00

Shutdown

- Check if there are any users or processes executing in the SAP System   (use transaction code SM50 and SM04 - delete their session before shutdown)

- Login as '<sid>adm'

- To interrupt Open Windows 'Shift Control-C'

- Unix > stopsap all (this will shutdown the SAP and database system)

Note :- stopsap R3 - will shutdown SAP only stopsap DB - will shutdown database only

Starting and Stopping SAP NetWeaver ABAP Under UNIX Proceed as follows to start and stop SAP NetWeaver ABAP under UNIX:

Starting...

       1.      Log on to the host of your central system as the SAP administrator <sid>adm.

       2.      Enter startsap ALL to start SAP NetWeaver ABAP.

The database, the ABAP instances, and all other processes for your system are started on this host.

In the case of an add-in installation (ABAP + Java), the Java instances are automatically started together with the corresponding ABAP instances.

Stopping       3.      Log on to the host of your central system as the SAP administrator <sid>adm.

       4.      Enter stopsap R3 to stop SAP NetWeaver ABAP.

In the case of an add-in installation (ABAP + Java), the Java instances are automatically stopped together with the corresponding ABAP instances.

The stopsap command with the R3 switch does not stop the database simultaneously. If you want to stop the database simultaneously, use the command stopsap or stopsap ALL.

Starting and Stopping SAP NetWeaver Java Under UNIX Proceed as follows to start and stop SAP NetWeaver Java under UNIX:Starting...

       1.      Log on to the host of your central system as the SAP administrator <sid>adm.

       2.      Enter startsap ALL to start SAP NetWeaver Java.

The database, all Java instances, and all other processes for your system are started on this host.

Stopping       3.      Log on to the host of your central system as the SAP administrator <sid>adm.

       4.      Enter stopsap J2EE to stop SAP NetWeaver Java.

The command Stopsap with the switch J2EE does not stop the database simultaneously. If you want to stop the database simultaneously, use the command stopsap or stopsap ALL.

Restarting the Java Stack of an SAP NetWeaver Add-In Installation With an add-in installation, a Java instance is assigned to an ABAP instance. The Internet Communication Manager (ICM) of the ABAP instance starts and stops the associated Java instance as required.Proceed as follows to restart the Java stack of your SAP NetWeaver add-in installation (ABAP + Java):...

       1.      Log on to the ABAP stack of SAP NetWeaver.

       2.      Open the list of SAP servers by calling transaction SM51.

       3.      Double-click the instance for which you want to restart the Java stack.

You are now connected to the selected instance.

       4.      Start the ICM Monitor (transaction SMICM) by entering /nSMICM in the command field.

       5.      In transaction SMICM, choose Administration ® J2EE Server ® Send Soft Shutdown ® With Restart.

       6.      The corresponding SAP NetWeaver Java stack for your instance is stopped and restarted

Starting or Stopping Application Services via Adaptive Computing  The procedure for starting and stopping the application services with Adaptive Computing is discussed in the corresponding section:

Adaptive Computing is only supported by using Adaptive Computing Controller 1.0 only running on SAP NetWeaver Release '04 (see SAP Note 725397) which of course can adaptively control all releases from SAP R/3 4.6C up to SAP NetWeaver 04s.

 Starting an Application Service: To access this information, go to: help.sap.com and choose Documentation ® SAP NetWeaver ®Adaptive Computing Controller 1.0, navigate to Adaptive Computing Controller Main Window ® Logical Landscape ® Application Service Detailed Information ® Application Service ® Starting an Application Service. .Stopping an Application Service: To access this information, go to: help.sap.com and choose Documentation ® SAP NetWeaver ®Adaptive Computing Controller 1.0, navigate to Adaptive Computing Controller Main Window ® Logical Landscape ® Application Service Detailed Information ® Application Service ® Stopping an Application Service. In the Visual Administrator:

   <Instance>         Server(n)             Services                 Security Provider                      Then, on the right side of the screen:                           Runtime                                Login Sessions Voila!  A list of users for that Server process. Now repeat for each Server(n) to see everyone.

The cron Command

An at job executes only once at a particular time. However, cron is much more flexible, because you can schedule system events to execute repetitively, at regular intervals, by using the crontab command. Each user on the system can have a crontab file, which allows them to schedule multiple events to occur at multiple times, on multiple dates. The jobs are specified by files in the /var/spool/cron/cronjobs directory, while configuration is managed by the files /etc/cron.d/cron.allow and /etc/cron.d/cron.deny.

To check your own crontab, you can use the crontab –l command: bash-2.05$ crontab -l root10 3 * * 0,4 /etc/cron.d/logchecker10 3 * * 0 /usr/lib/newsyslog15 3 * * 0 /usr/lib/fs/nfs/nfsfind1 2 * * * [ -x /usr/sbin/rtc ] && /usr/sbin/rtc -c > /dev/null 2>&130 3 * * * [ -x /usr/lib/gss/gsscred_clean ] && /usr/lib/gss/gsscred_clean

This is the standard crontab generated by Solaris for root, and it performs tasks like checking if the cron logfile is approaching the system ulimit at 3:10 A.M. on Sundays and Thursdays, creating a new system log at 3:10 A.M. only on Sundays, and reconciling time differences at 2:01 A.M. every day of the year.

The six fields in the crontab stand for the following: Minutes, in the range 0–59 Hours, in the range 0–23 Days of the month, in the range 1–31 Months of the year, in the range 1–12 Days of the week, in the range 0–6, starting with Sundays The command to execute

If you want to add or delete an entry from your crontab, you can use the crontab –e command. This starts up your default editor (vi on the command line, textedit in CDE), in which you can make changes interactively. After saving your job, you then need to run crontab by itself to make the changes.

System access can be monitored interactively using a number of measures. For example, syslog entries can be automatically viewed in real time using this command:

$ tail -f /var/adm/messages

Another way of obtaining disk space usage information with more directory-by- directory detail is to use the /usr/bin/du command. This command prints the sum of the sizes of every file in the current directory and performs the same task recursively for any subdirectories. The size is calculated by adding together all of the file sizes in the directory, where the size for each file is rounded up to the next 512-byte block. For example, taking a du of the /etc directory looks like this:

# du /etc

/bin. Symbolic link to the /usr/bin directory. /dev. Contains logical device names (defined in the next chapter) for the devices. /devices. Device-related files controlled by the file system: devfs. /lib. Contains shared libraries such as SMF executables. /etc. Administrative and configuration files. /export. You can define it according to your needs, but commonly used to hold user

home directories. /home. This is the default mount point for user home directories. /mnt. Default mount point used to temporarily mount file systems. /sbin. Contains system administration commands and utilities. Used during booting

when /usr//bin has not yet been mounted. /tmp. Contains temporary files that are deleted when the system is rebooted. /usr. UNIX System Resources. Holds OS commands and programs

Running RSANAORA ABAP Program against the job will test current program to show if its working or why its taking long…..

useradd -d /user/(username) -m -s /bin/csh (username)passwd -r files (username)passwd userid and set a temp password and force them to change it next login using passwd -f userid

Or use the wrapper script (unix only) which may be invoked after setting the correct $ORACLE_HOME environment variable opatch command  [options>] [-h[elp]]  where command is one of:    apply   lsinventory   rollback   version It also lists the patch log file directory:  $ORACLE_HOME/.patch_storage/patch_logfile

/usr/sap/(SID)/JC65/j2ee/admin that’s where the go file is to start j2ee engine

Logging and Trace FilesThe following files are available for logging important security events and helping administrators with troubleshooting:

Security Logging

Location in Log Viewer: ./log/system/security.<n>.log

Location in file system: <drive>:\usr\sap\<SID>\<instance_number>\j2ee\cluster\serverX\log\system\security.<n>.log

This file contains a log of important security events, such as successful and failed user logons, and creation or modification of users, groups and roles. For a complete list of events that are logged and the format in which they are logged, see What is Logged?.

1. Trace Files

Location in Log Viewer: ./log/defaultTrace.<n>.trc

Location in file system: <drive>:\usr\sap\<SID>\<instance_number>\j2ee\cluster\server0\log\defaultTrace.<n>.trc

This file contains all the trace information for the whole server and includes trace information for UME libraries and the UME Provider (com.sap.security.core.ume.service). The information in this file is on a very fine-granular level and includes exceptions, warnings, and debugging information. It is mainly required by the SAP support team.

1. Directory Server Logging

When you use an LDAP directory server as a data source for the User Management Engine (UME), you can configure log files to monitor and troubleshoot the connections. For more information, see the following:

Directory Server Access Log

Directory Server Connection Pool Log

Viewing Logging and Trace Files in the Log Viewer...

In the Visual Administrator, on the Cluster tab, choose <system_id> ® Server ® Services ® LogViewer.

Make sure the Runtime tab is displayed.

In the navigation tree, choose Cluster ® Server ® <J2EE_installation_directory> and navigate to the required file.

Configuring the Log ViewerYou can change the severity level of logging and tracing using the log configuration services in the Visual Administrator. ...

In the Visual Administrator, on the Cluster tab, choose <system_id> ® Server ® Services ® Log Configurator.

Choose the configuration you want to change.

11 For security logging, choose Categories ® Root Category ® System ® Security ® Audit.

11 For tracing, switch to advanced mode and choose Locations ® Root location ® com ® sap ® security.

Change the severity level as required.

1. Select the required package and choose Edit.2. Under Severity change the severity settings.

The new severity level will be activated immediately. You do not have to restart the server.

Configuring Security Logging

You can use UME properties to configure what is logged. The following options are available:

1. Log the object ID of an event.

2. Disable the logging of the actor of an event, only anonymous is recorded.

3. Disable the logging of the client host address.

4. Log the client hostname.

For more information about editing UME properties, see Editing UME Properties.For more information about UME properties relevant to UME properties, see Security Audit.

Admin Tool / Config Tool Shortcuts

Admin Tool: (/usr/sap/<SID>/JC<##>/j2ee/admin/go)

J2EE LicensesServer >> Services >> Licensing Adapter

J2EE ApplicationsServer >> Services >> Deploy >> Application

SLD (System Landscape Directory)Server >> Services >> SLD Data Supplier

LoggingServer >> Services >> Log ConfiguratorServer >> Services >> Log Viewer

ADS (Adobe Document Services)Server >> Services >> Document Services ConfigurationServer >> Services >> Destinations >> HTTPServer >> Services >> Destinations >> WebService >> sap.com/tc~wd~pdfobject/com.sap.tc.webdynpro.adsproxy.AdsProxy/ConfigPort_Document

SSL SetupServer >> Services >> Key StorageServer >> Services >> SSL Provider

J2EE Security ConfigurationServer >> Services >> Security Provider

Config Tool: (/usr/sap/<SID>/JC<##>/j2ee/configtool/configtool.sh)

Secure Store -Oracle Passwords for J2EE Startup

-J2EE Passwords for SDM

Memory ParametersCluster Data >> Instance<##> >> Server<##>

Security PolicyCluster Data >> Instance<##> >> Server<##> >> Services >> com.sap.security.core.ume.service

A) Create SAP SystemsSystem Administration >> System Configuration >> System Landscape

Right-click Portal Content >> New System from TemplateSelect the template "SAP system with Load Balancing"

Group=DefaultLogical System Name = ADBE<SID>003Message Server = <hostname>.corp.adobe.comSAP Client = 003SAP System ID = <SID>Server Port = 36##WAS Description = WebASWAS HostName = <hostname>.corp.adobe.com:<port> (use WebDispatcher Port)WAS Protocal = httpSAVE

Update the System Alias for your new System:BW System Aliases:BW

R3 System Aliases:R3 SAP_ECC_HumanResources SAP_ECC_Travel

B) Import BP Common Parts SP2

C) Migrate Favorites using ICE Protocol (offline steps)

1) Login to EP6 2) System Administration >> System Configuration >> Knowledge Mgmt >> Configuration >> Content Mgmt >> Utilities >> System Principals >> System User 3) Click NEWEnter your LoginID for both "User" and "User Name"Select ALL checkboxesClick OK

4) Restart J2EE

5) Export Favorites from EP66) Import Favorites into EP7

Command Dir Descriptionalias /usr/bin/ Check out aliases with SIDadm login. These provide shortcuts....cont'd.

brarchive /sapmnt/SID/exe/ -h option will give you all the parameters that can be used ....cont'd.

cdexe;saposcol -d /sapmnt/SID/exe/ This brings prompt Collector>. Type stat to see status of sa....cont'd.

chdbpass R/3 kernel CD

<CD-DIR>/UNIX/COMMON/INSTALL/CHDBPASS(CD-DIR is your CD mo....cont'd.

cleanipc /sapmnt/SID/exe/ Remove the SCSA(Shared memory of SAP): (either or) - SAP c....cont'd.

disp+work -V (capital V) /sapmnt/SID/exe/ Shows current patch level for SAP kernel, and other DB and O....cont'd.

dpmon pf=<inst.Profile> /sapmnt/SID/exe/ Shows at unix level all SAP processes running. Select p in t....cont'd. imp help=yes /oracle/SID/bin/imp/ Oracle tool. Run above command as oraSID to get help/info on....cont'd. infcfgcheck /sapmnt/SID/exe/ See note: 71776. Infcfgcheck -h shows all the options. This ....cont'd. ipclimits /sapmnt/SID/exe/ Shows kernel configurations for shared memory. Compare these....cont'd. lgtst /sapmnt/SID/exe/ This is used by OSS1 transaction to connect to OSS message s....cont'd. lsnrctl /oracle/SID/bin/ For Oracle listner process. lsnrctl start - to start lis....cont'd.

oerr ora <Err#> /oracle/SID/bin/ Run as oraSID to get SQL error information.Eg., oerr ora 7....cont'd. R3trans /sapmnt/SID/exe/ Use this to delete clients that are copied incompletely when....cont'd. R3trans -d -v -w r3trans.log /sapmnt/SID/exe/ checks for valid connection to database. R3trans -w <ControlFile> /sapmnt/SID/exe/ You can write a control file for client delete/copy/export a....cont'd. sapdba /sapmnt/SID/exe/ Will not let you reorg psaproll and psaptemp.If you want t....cont'd. sapdba -check /sapmnt/SID/exe/ Creates a status report list from the database. sapdba -cleanup /sapmnt/SID/exe/ Cleans up SAPREORG directory. sapevt EventID name=SID nr=SAP System# [-p event parameter] [-t ] pf=Instanceprofile of your R/3. /sapmnt/SID/exe/ Useful to trigger a previously defined event (thus an event ....cont'd. saplicense -install/check/show/get/temp/help /sapmnt/SID/exe/

For installing the R/3 runtime license and for checking the ....cont'd. sappfpar pf=ProfileName check nr=InstNumber name=InstName

/sapmnt/SID/exe/ This checks the consistency of profile parameters. Checks al....cont'd. saprouter /sapmnt/SID/exe/ An OSS connection can be made secure by means of the SAProut....cont'd. showipc <Inst#> /sapmnt/SID/exe/ Shows all message queue, semaphore set and shared memory ide....cont'd. sqldba lmode=y or svrmgrl /oracle/SID/bin/ This is Oracle Server Manager. Login as SIDadm or oraSID and....cont'd. startdb /sapmnt/SID/exe/ Starts DB. This is called when startsap command is issued. startsap This is an alias. startsap r3/db/all (Default is : all)Aliased to script sta....cont'd. stopdb /sapmnt/SID/exe/ You can use this to shutdown DB. This is also called when R/....cont'd.

stopsap r3/all Alias to a script in SIDadm home dir. Aliased to SIDAdmHome/stopsap_host_SID# which calls /usr/sap....cont'd. tp addtobuffer TO TARGET /sapmnt/SID/exe/ Add transport req to the buffer,you need the data & co files....cont'd. tp check all /sapmnt/SID/exe/ The result of the 'tp check all' is to make a list of all fi....cont'd. tp checkimpdp SID /sapmnt/SID/exe/ Checks to see if RDDIMPDP is running. For any tp command f....cont'd. tp cleanbuffer <SID> /sapmnt/SID/exe/

/funlets/sap101/FullRecord.asp?ID=35tp clearold <SID> /sapmnt/SID/exe/ Cleans up the transport area according to parameters set in ....cont'd. tp clearold all /sapmnt/SID/exe/ The age of the files that are listed in the file 'ALL_old.li....cont'd. tp connect SAPSID /sapmnt/SID/exe/ You should see a message that a connection could be made to ....cont'd. tp createcofiles /sapmnt/SID/exe/ Does this recreate co files ??? tp delfrombuffer TO TARGET /sapmnt/SID/exe/ Delete a transport req. from the buffer. tp gentb <SAPSID> /sapmnt/SID/exe/ Runs conversion requests wrtitten to TBATG in system SAPSID. tp get dbinfo <SID> /sapmnt/SID/exe/ Gives database information. tp go TARGET /sapmnt/SID/exe/ check the DB destination. Shows current env variables effect....cont'd. tp import <CR> client=QAS uX /sapmnt/SID/exe/ u0- unconditional mode 0 allows the change request to be imp....cont'd. tp import all clientcascade /sapmnt/SID/exe/ Note: using this all imported changes are made to ALL client....cont'd. tp import all QAS /sapmnt/SID/exe/ Import all transport requests in the QAS transport buffer, i....cont'd. tp locksys <SID> or tp unlocksys <SID> /sapmnt/SID/exe/

Prevents new user logins, except SAP*, DDIC !! tp RETURN CODES are /sapmnt/SID/exe/ 0- success4- Warnings occurred

8- Errors occurred12- Fa....cont'd. tp showbuffer TARGET /sapmnt/SID/exe/ Display buffer entries. tp showinfo <Transport Request #> /sapmnt/SID/exe/

Display information on a transport req. tp showparams SID /sapmnt/SID/exe/ Shows tp version information and a lot more paramters on - g....cont'd.

Stop and Start IPCDispatcher and Server

This document describes how to start and stop the IPCServer and IPCDispatcher

**********************************************************************Stopping the ICPServer and Dispatcher:

As the ipcadm account on the correct server:

CM1 – landroverCM2 – bnez-aCM3 – Ferrari-a

1. Stop the Server: /usr/sap/ipc/bin/ipcserver stop2. Stop the dispatcher: /usr/sap/ipc/bin/ipcdispatcher stop3. Ensure that the /usr/sap/ipc/bin/server.pid file has been removed.4. Ensure that the /usr/sap/ipc/bin/dispatcher.pid file has been removed.

Starting the ICPServer and Dispatcher:

As the ipcadm account on the correct server:

CM1 – landroverCM2 – bnez-aCM3 – Ferrari-a

1. Ensure the dispatcher and the server are not running:2. landrover% ps -ef |grep ipc

ipcadm 25845 25822 0 08:10:37 pts/8 0:00 -csh ipcadm 25644 1 0 07:19:33 ? 0:12 /usr/j2se/bin/../bin/sparc/native_threads/java -server -Xms32m -Xmx256m -cp ../ ipcadm 25693 1 0 07:19:57 ? 0:17 /usr/j2se/bin/../bin/sparc/native_threads/java -server -Xms64m -Xmx512m -cp .:. ipcadm 25854 25845 0 08:13:26 pts/8 0:00 grep ipclandrover%

3. If they are stop them.4. Start the dispatcher: /usr/sap/ipc/bin/ipcdispatcher start5. Start the server: /usr/ipc/bin/ipcserver start

Log files are located in:

/usr/sap/ipc/bin/ as-rw-r--r-- 1 ipcadm sapsys 6 Jan 12 07:19 dispatcher.pid-rw-r--r-- 1 ipcadm sapsys 0 Jan 12 07:19 IPCDispOut.log-rw-r--r-- 1 ipcadm sapsys 6 Jan 12 07:19 server.pid-rw-r--r-- 1 ipcadm sapsys 142 Jan 12 07:20 IPCServ1Out.log-rw-r--r-- 1 ipcadm sapsys 558369 Jan 12 08:14 IPCServ1Err.log-rw-r--r-- 1 ipcadm sapsys 81583 Jan 12 08:14 IPCDispErr.log

Start and Stop Webdispatcher

A) Standalone WebDispatcher

1) STARTING WEB DISPATCHERa) Cleanup old semaphores

sapwebdisp pf=sapwebdisp.pfl -cleanupb) Start Web Dispatcher

sapwebdisp pf=sapwebdisp.pfl -auto_restart -shm_attach_mode 6 &

2) STOPPING WEB DISPATCHERa) ps -ef|grep sapwebdisp

b) kill -2 <pid> <pid>

B) Integrated WebDispatcher

1) AUTOMATIC WEB DISPATCHER STARTUPa) Add the following lines to the SAP Startup Profile

(<SID>_DVEBMGS##_hostname)

#-----------------------------------------------------------------------# start WebDispatcher#-----------------------------------------------------------------------Start_Program_05 = local $(DIR_EXECUTABLE)/sapwebdisp pf=$(DIR_PROFILE)/sapwebdisp.pfl -auto_restart -shm_attach_mode 6

b) This will start and stop the WebDispatcher when you issue “startsap” or “stopsap”

2) MANUAL WEB DISPATCHER STARTUP

a) See commands for Standalone Webdispatcher

C) STARTING ADMIN PAGES

http://<WebDispatcher_Server>:<port>/sap/wdisp/admin/default.html

Note: This path is defined in the SAPWEBDISP.PFL file. You can reset the password with ./sapwebdisp –bootstrap(CAREFUL: this will overwrite your existing profile. Do this on a test system, then move the icmauth.txt file to the appropriate directory)

To monitor ear project files for portalYou can check the whole exception stack trace in the defaultTrace.trc file in /usr/sap/<SID>/<instance>/j2ee/cluster/server<N>/log

To remove application from portal One way to do it is from SDM and do undeploy Another way to remove the application is:Go to Visual Administrator->Server->Services->Deployright side Under the Deploy_Service->Server -> Webdynpro. You will see the applications deployed to webdynpro container. Select the application you want to remove from the system, stop the application and click the remove button to remove it.

Assign to the role com.sap.pct.pdk.JavaDeveloper to your user, if you don't find it install Java PDK (usefull and free tool) then once inside the portal go to:

Java Developer --> Portal Archive Deployer&Remover --> Remove Archive and select you app at the combo box.

Try to re-schedule the job in QA using the program RDDNEWPP on se38 in client000 and client 200. Clear the tables TRBAT and TRJOB in QA. Try to transportagain. Look if there are any file called something .lock in sap/trans/tmp, ifit is there remove it.