Basis SAP

GRMG configuration for TREX system

2011-06-24T22:10:00.000-07:00

1.Log on to the TREX host as root

2. Go to the directory . : /usr/sap/TPZ/TRX10

Set the environment variables required by TREX by executing the following scripts.

. TREXSettings.sh

3. Go to the directory /exe/CCMS, in which the script for installing the TREX monitoring functions is located

4.Execute the following command to configure monitoring of availability (heartbeat/GRMG):

python ccms_config.py --grmg

Created GRMG upload file at location : /usr/sap/TPZ/TRX10/hostname/trace/grmg/GRMG_config.TPZ_10.hostname.xml

Uploading XML Customizing File by Transaction GRMG

1. Start transaction GRMGin the SAP system.

2. Choose Upload/Download.

There are two ways to upload the TREX scenario:

○ Choose Upload/Download ® Upload Scenario.

Choose the XML customizing file for the corresponding TREX instance and choose Open.

The window GRMG customizing file uploaded successfully appears.

Choose Upload/Download ® Poll agents for new scenarios.

This upload of the TREX scenario will only work if the SAPCCMSR agent is running and has been registered previously.

In the list GRMG Scenarios for Availability Monitoring, choose the corresponding TREX scenario.

Choose Start/Stop ® Start Scenarios.

The window GRMG scenarios have started appears.

Oracle Bundle Patch

2010-04-08T21:59:00.000-07:00

How to Apply Oracle Bundle Patch

Download the dump from SAP service market place to your system.
1.PRE INSTALLATION INSTRUCTIONS
 Copy the dumps of patch at below mentioned path.
Drive/oracle/"SID"/"oracle version"/OPatch

 Stop SAP & DB along with all services of SAP & DB.
 Back up the current database that is installed, the %ORACLE_HOME% directory and Oracle inventory under c:\Program files\oracle directory. (This will help if there are problems applying the patch, and to restore the Inventory in case of an issue with the patch.)
 Now apply bundle patch.
OPatch>opatch apply patch no
 Installation may be interrupted coz. of error in overwriting an existing .dll file giving following error file already in use.
In case of above error don’t rename the file and RETRY(It doesn’t work) instead cancel the installation then and there rename the .dll file and start patch application again.
3. POST INSTALLATION INSTRUCTIONS
 Start all services of DB & DB
 Run script catcpu.sql
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @%ORACLE_HOME%\Bundle\Patch17\catcpu.sql
SQL> QUIT
 If above script reports any error then
Inspect the logfile %ORACLE_HOME%\Bundle\Patch17\Apply__.log for any errors.
 If catcpu.sql reports any Invalid Objects, compile the invalid objects as follows.
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @%ORACLE_HOME%\rdbms\admin\utlprp.sql 0
Above script will compile the invalid objects.
 To check for any invalid objects still there or not, execute the following statement:
SQL> SELECT OBJECT_NAME FROM DBA_OBJECTS WHERE STATUS = 'INVALID';
 Recompiling Views in the Database
To recompile the views for each database instance running out of the ORACLE_HOME being patched , follow these steps:
 Run the pre-check script, which reports the maximum number of views and objects that may be recompiled:
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @%ORACLE_HOME%\Bundle\view_recompile\ recompile_precheck_jan2009cpu.sql
SQL> QUIT
 Run the view recompilation script. Note that this script is run with the database in upgrade mode, which restricts connections as SYSDBA.
sqlplus /nolog
SQL> SHUTDOWN
SQL> CONNECT / AS SYSDBA
SQL> STARTUP UPGRADE
SQL>@%ORACLE_HOME%\Bundle\view_recompile\
view_recompile_jan2008cpu.sql
SQL> SHUTDOWN;
SQL> STARTUP;

 Check the log file for any errors. The log file is in the current directory and is named: vcomp__.log
 If any invalid objects were reported, run the utlrp.sql script as follows:
sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @%ORACLE_HOME%\rdbms\admin\utlrp.sql
 If still any invalid objects are there then recompile those manually.
SQL> alter schemaname. compile;
 Verify that the view recompilation has been performed for the database, by executing the following statement:
SELECT * FROM registry$history where ID = '6452863';
TO VIEW ALL PATCHES APPLIED ISSUE BELOW COMMAND:-
\ORACLE\"SID"\"oracle version"\OPATCH>OPATCH LSINVENTORY

SAP Test system refresh activity

2009-10-07T10:41:00.000-07:00

SAP Test system refresh activity.

Follow the below steps for SAP test system refresh activity from Production server backup.

1. Take the relevant screenshot of system

STMS,SCC4,SM59,SAP standard jobs,DB13,SLICENSE,CCMS settings,SPAD

2. Import the SPAD settings

3. Take the offline backup of production system

4. Take the backup of backSID.log,*.aft and initSID.ora of production and test server

5. Lock users in Test system

6. Take offline backup of test system

7. Open client in test server : SCC4

8. Export the client for profile SAP_USER in test server. Keep test system as target server

SCC8

9. Take the trace of control file on both the Test and production server

10. Stop the SAP instance and sap services

11. Note down the Schema users existing presently in the system.

SQL> select user name from dba_users;

12. Shutdown the database

13. Copy last offline backup log file(*.aft) from production system to test server

14. edit the *.aft log file as per test server

change SID from prdoduction to test server SID, check ORA-HOME directory

15. Now restore the backup

brrestore –c –m full –b XXX.aft

16. Connect to oracle as sqlplus /nolog, connect /as sysdba and type startup Nomount.

17. Edit the controlfile of Prod. Change all production SID to test SID and NORESETLOGS TO RESETLOGS.

17. Use the edited controlfile of Prod to recreate the control file of Test

SQL> @Cntrl.sql

SQL>shutdown immediate;

18. SQL> Alter database open RESETLOGS.

19. Create new OPS$ADM using the below command.

I:\scripts>sqlplus /nolog @ORADBUSER.sql SAPSID NT DOMAIN SID (IF SIDADM is local user then give the host name in the place of Domain Name)

20. After this run the script sapdba_role to set proper right for OPS$ user IDs.

>sqlplus /nolog @sapdba_role.sql

21. Check whether SAPSR3P (schema owner) account has been locked or not:

select username,account_status from dba_users where username=”SAPPCE”;

22. If it is locked use this command to unlock it:

alter user SAPPCE account unlock;

23. Start the SAP application.

POST Processing Steps:

24. Update the license

Logon to SAP with DDIC-client 000; update the license key through the transaction SLICENSE.

25. check the consistency

Go to transaction SICK for checking the consistency of the system.

26. check the local host entry

Go to transaction SE37 and execute BPT_LOCAL_HOSTNAME_CHECK to check for the hostname entry.

27. Change the STMS configuration and perform post installation activity

Now go to transaction SE06 to perform post installation activities

28. Reconfiguring STMS

29. Login into DCE client 000 with DDIC , goto transaction STMS.

30. Schedule the standard jobs

Go to transaction SM36 and click on the button “Standard jobs” to schedule the standard jobs defined for the system.

31. Import the user master of test server

Goto the STMS and import the user master request

32. Close the client

33. Changing the client description.

34. Import profiles of active Server using RZ10.

35. Delete incorrect instances defined in RZ04, create correct instances and assign Operation modes for the same

36. Change the logical system name

37. Take an OFFLINE backup of the Test system and release the system to the users.

The entire procedure for DRS switchover

2009-06-21T06:51:00.000-07:00

PRODUCTION TO DRS SWITCHOVER

1. Take Offline backup of the PRD Database.

2. In SM02, Put message on the PRD system.

3. On PRD,

cmd>SVRMGR30

Connect Internal;

Alter system switch logfile;

Do switch log file 3-4 times.

4. In DRS, apply up to the last Archive Log created in PRD.

5. On PRD, Stop R/3, Shutdown Database And Stop SAP & Oracle Services.

6. On PRD, Backup Mirrlog A, Mirrlog B, Origlog A, Origlog B & Control file of PRD.

7. Shutdown DRS Database & Stop Oracle Services.

8. On DRS, Backup Mirrlog A, Mirrlog B, Origlog A, Origlog B & Control file of DRS.

9. Copy the redo log files & control files from PRD (production DB System) to DRS (DRS DB System). Copy the control file to all the locations on DRS (OriglogA, Saparch & Sapdata1 sub-folders).

10. Start the Oracle Services on DRS.

11. In DRS

Start SVRMGR30

Connect Internal;

Startup Mount;

Recover Database; (Ensure the message ‘Media Recovery Complete’ appears).

Alter databases Open; (This opens in NORESETLOGS mode).

Exit;

12. Start SAPOSCOL, SAP_00 services on DRS.

13. Start SAP R/3 application on DRS.

14. Logon to the DRS System through SAP Logon Pad.

15. Check the System Status & transactions like SM51, ST22, and SM21 Etc.

DRS TO PRODUCTION SWITCHOVER

16. On DRS, Stop R/3, Shutdown Database and Stop SAP & Oracle Services.

17. Copy the redo log files & control files from DRS (DRS DB System) to PRD (production DB System). Copy the control file to all the locations on PRD (OriglogA, Saparch & Sapdata1 sub-folders).

18. Start the Oracle services on the DRS.

19. Start the Oracle Services on PRD.

20. In PRD

Start SVRMGR30

Connect Internal;

Startup Mount;

Recover Database; (Ensure the message ‘Media Recovery Complete’ appears).

Alter databases Open; (This opens in NORESETLOGS mode).

Exit;

21. Start SAPOSCOL, SAP_00 services on PRD.

22. Start SAP R/3 application on PRD.

23. Logon to the PRD System through SAP Logon Pad.

24. Check the System Status & transactions like SM51, ST22, and SM21 Etc.

Note: - DRS: DRS database server

PRD: Production database server

Explain the client create, delete and copy?

2009-04-10T22:50:00.000-07:00

We can create a client using the transaction SCC4. Mention the client name with the appropriate selection.

Note that SAP delivers the software with standard clients 000 and 001. You may not work in client 000, but may use client 001. However, SAP recommends that you begin SAP System implementation by creating a new client as a copy of client 000.

To Copy a client

A local client copy copies between clients within the same SAP System.
A remote client copy allows you to copy between clients in different SAP Systems.You can use a remote client copy to, for example, transport client-dependent as well client-independent Customizing data between SAP Systems.
A remote client copy proceeds in the same way as a local copy, but sends the data through a remote function call (RFC) connection to the target client.
A remote client copy is easy to use, and does not require file system space on operating system level.
The limitations of a remote client copy are as follows:

ü A remote client copy does not create a file at operating system level, so there is no "hard copy" of the client to be copied. Therefore, the same, identical client copy cannot be duplicated at a later date.

To delete a client from within SAP System:

Log on to the client to be deleted.
Use the menu option use Transaction code SCC5 or from the SAP System initial screen choose Tools _ Administration _ Administration _ Client admin _ Special functions _ Delete client.
Start the deletion of the client, preferably using background processing.
When you delete a client entry from table T000 with client maintenance (Transaction SCC4), you can no longer log on to the client or update it using change requests. The deletion process, however, does not eliminate the data belong to the client. This means the client-dependent data remains in your SAP System, occupying space in the database. Therefore, to eliminate an SAP client entirely, that is, to delete both the client and the client-dependent data, use the client delete functionality (Transaction SCC5).
Deleting a client entry with client maintenance (Transaction SCC4) allows you to temporarily lock the client. The deletion procedure preserves the data for the client but prevents users from logging on to the client or accessing the data belonging to the client. To restore the client and allow logon, recreate the client entry using client maintenance.
The amount of time required for the deletion of a client can be reduced by performing the deletion using parallel processes.

SAP Basis critical object : S_BTCH_JOB

2009-04-07T22:47:00.000-07:00

Definition

You use this object to assign users authorizations for all operations except scheduling. For example, you could assign users authorization to delete their own jobs.

This object is used to check all critical administration operations for background processing (Tools -> Administration -> Jobs -> Job overview.

Users do not need an authorization for this object to schedule background jobs; an authorization is normally not required for end users.

Exception: If background jobs are to be automatically released after scheduling, your users should have the authorization for value RELE so that the scheduled jobs are automatically released.

An authorization for this object means users have authorization for their own jobs in their current client. To assign a user administration authorization for all users and all clients, use authorization Background Processing: Background Administrator.

Defined fields

Operations on one job consists of the following fields:

o Functions: Operations the user is allowed to perform. Possible values are:

- DELE: Delete background jobs

- LIST: Display spool requests created by jobs

- PLAN: Copy or repeat jobs

- PROT: Display job processing logs

- RELE: Release jobs (automatic release after scheduling possible)

- SHOW: Display job queue

- Job group: Names of permitted job groups. Reserved: Set to *.

Example

With this authorization, users can release and delete their own background jobs in job administration. The users' jobs are also automatically released after scheduling.

Field Value Operations on a job DELE RELE Job group *

SAP Basis critical object : S_USER_PRO

2009-04-07T02:42:00.000-07:00

S_USER_PRO

Definition

Authorization object, which is checked during authorization maintenance.

The check is made in the following profile maintenance transactions
(Tools -> Administration -> User maintenance).

o SU02 (Maintain profiles)

o SU01 (Assign profile to user)

o SU10 (Assign profile to all users or remove assignment to all users)

Defined fields

The object is defined with the following fields:

o Authorization profile: In this field, you must enter the
authorization profiles that an authorization administrator may
maintain or that a user administrator may assign to his users.

o Activity: In this field, you can limit what the administrator is
allowed to do with the profile.
Possible values:

- 01: Create

- 02: Change

- 03: Display

- 06: Delete

- 07: Activate

- 08: Display change documents

- 22: Assign profile to users / remove assignment

- 24: Archive

Example
Field Values
Profile name *
Activity 01 - 06

This authorization allows the authorization administrator to create,
maintain, delete and display profiles at will. However, he may not
activate profiles or display change documents.

SAP Basis critical object : S_SPO_ACT

2009-04-02T07:50:00.000-07:00

Definition Authorization to perform actions on spool requests protected with authorization character strings. Use in the system: Only checked if the explicit or implicit value in the authorization attribute field of a spool request is not the same as the user ID of the user accessing it. The authorization is not checked if users access their own unprotected spool requests. Examples: Authorization is checked when users attempt to access the spool request of another user. Authorization is not checked if users attempt to delete their own spool request, and the authorization field in the spool request is either initial or contains the user's ID. The authorization is, therefore, mainly of interest for users who administer spool requests in the output controller. These users must access the spool requests of other users. This requires a S_SPO_ACT (spool: actions) authorization, in addition to the spool administration authorization (S_ADMI_FCD, system functions).

Defined fields

This object consists of the following fields: o Authorization field for spool actions: Operations permitted on protected spool requests. Possible values: o BASE: Check protected spool request in the output controller (determine whether the spool request exists); display request attributes o DISP: Display contents of a protected spool request o ATTR: Change attributes of protected spool request o AUTH: Change authorization value of a protected spool request o PRNT: Output protected request for the first time o REPR: Output protected spool request more than once o REDI: Redirect to another printer (of the same type). The printer should be the same device type. If used with ATTR, redirection to a different type of printer is permitted. o DELE: Manually delete request o USER: Change the owner o SEND: Send a request using SAPoffice o DOWN: Download a request o Value for the authorization check: Authorization value,for which the user is authorized. The authorization value is set in the attributes of the spool request. A user is permitted to perform a spool action if the value stored for this action in the user master matches the value in the authorization field in the spool request. If no value is specified in the authorization field of the spool request, all actions are permitted. An authorization key can be entered at the time a spool request is created, for example when a user selects Print. If no value is specified, the spool system automatically uses the ID of the user A user is always authorized for his or her own user ID and no authorization check takes place in this case. This means that a user can access his or her own spool requests without restriction unless an authorization key is entered that does not match the user ID. Users with the authorization value __USER__ can access all unprotected requests for all users in the client according to the authorized action. This authorization value is pre-defined and has the special meaning described. It can no longer be used for other purposes. Examples With this authorization, a user can reprint all requests with an authorization value beginning with FI. Field Value Authorization field for REPR spool actions Value for FI* authorization check

Dependencies

An additional authorization for S_SPO_DEV (spool: device authorizations) for at least one printer is always required for the physical output of a spool request.

SAP Basis Critical Object : S_SPO_DEV Definition Authorization to use a specific printer or other output device. Defined fields The object consists of the field Spool: Output device. In this field, enter the SAP names of the output devices for which a user is to be authorized. Example The value "LT*" authorizes a user to use all printers with beginning with "LT" in spool administration.

SAP Basis critical object : S_TMS_ACT

2009-04-01T07:25:00.000-07:00

Definition
TemSe manages objects with temporary, sequential data. The authorization S_TMS_ACT controls who is allowed to perform which operations on which TemSe objects. Caution: The authorizations only control direct access. For example, the spooler or background request management in the R/3 software system use TemSe for storing data. In such cases the TemSe objects are normally well protected against direct accesses because they perform their own software system access checks and want to maintain control.

Defined fields

Each authorization object consists of three fields: STMSOBJECT - Generic object name TemSe objects have names. Here the name is specified partly generically (i.e. with an asterisk ("*") at the end if necessary). TemSe objects can have any names. However, naming conventions are used, which are also defined in table "TST07". The spooler, for example, currently uses "SPOOLnnnnn", where nnnnn is the spool request number. STMSOWNER - Owner group OWN Own TemSe objects GRP External TemSe objects in own clients OCL TemSe objects in external clients STMSACTION - Abbreviation for action CRE Create TemSe object REA Read TemSe object DEL Delete TemSe object APP Append TemSe object MOD Modify TemSe object. This currently only applies to attributes, as the data of the TemSe objects cannot be changed in the current version.

Critical Basis Object : S_ADMI_FCD

2009-03-28T08:46:00.000-07:00

Definition

This authorization object checks access to several Basis functions, for
example, spool administration and monitoring.

Defined fields

The object defines one authorization field, System administration
functions. The possible values for this field are:

System administration

o NADM: Network administration (SM54, SM55, SM58, SM59, SMT1, SMT2,
SMQ1, SMQ2, SMQ3, SMQA, SMQR)

o PADM: Process administration (SM50, SM51, SM04); intercept
background job (debugging function in background job administration,
Transaction SM37)

o SM02: Authorization to create, change, and delete system messages

o UADM: Update administration (SM13)

o T000: Create new client

o TLCK: Lock/unlock transaction

o MEMO: Set SAP memory management quota using report RSMEMORY

o COLA: Administration of OLE automation servers and controls

o F4MX: Activate/deactivate ActiveX search help support
throughout the system

o TOUC: Execute report TOUCHALL

o QDEL: Execute report RSTRFCQDS or RSTRFCIDS to delete a queue in
SMQ1 or in SMQ2 in accordance with selection criteria

Spool Administration

Authorization for spool administration is controlled in two groups of
authorization values. You need authorizations from both groups to
execute spool administration.

These groups are:

o Client authorizations

- SPAD: Authorization for spool administration in all clients

- SPAR: Authorization for client-dependent spool administration
The functions of these values are the same, as the spool
administration objects are client-independent. We recommend you only
enter the value SPAD.
Without a functional authorization, the SPAD user cannot execute any
spool administration functions.

o Functional authorization:

- SPAA: Authorization to define output devices

- SPAB: Authorization to define physical or logical Output
Management Systems (OMS) in spool administration

- SPAC: Authorization to maintain device types and associated
objects (formatting, character sets, and so on)

- SPAM: Authorization to administer spool requests in external
clients (request client is not the administrator's client).
Authorization values SPAD and SP01 are also required (see below,
Administration of Spool Requests in the Spool Output
Controller).

SAPscript Font Maintenance

o FONT: Authorization to maintain SAPscript font data

TemSe Administration

The TemSe database stores spool request data, background processing job
logs and other data that only needs to be kept in the system for a short
period of time. These authorizations grant access to the TemSe
administration functions, such as consistency checks and reorganization.

- SPTD: Authorization for TemSe administration in all clients

- SPTR: Authorization for client-specific TemSe administration

Administration of Spool Requests in the Spool Output Controller

Authorization to administer spool requests is controlled using two
groups of authorization objects or authorization values. The
authorizations required depend on whether the administrator needs to
access spool requests from external clients (request client is not the
administrator's client).

These authorizations are:

- SP01: Authorization for administration of spool requests in the
spool output controller (all users and clients)

- SP0R: Authorization for administration of spool requests (all
users) in the spool output controller. Access is limited to
spool requests in the current client of the user.

For SP01:

- To access spool requests in your own client (apart from your own
unprotected requests), you need an additional authorization for
object S_SPO_ACT (Spool: Activity).

- To access spool requests in external clients, users with the
authorization for SP01 are automatically authorized to list
spool requests and to display their attributes.
Administrators with values SPAD and SPAM (see above), have
unlimited authorization for external client spool requests.

For SP0R: To access spool requests (apart from your own unprotected
requests), you need an additional authorization for object S_SPO_ACT
(Spool: Actions).

Monitoring:

o ST0M: Authorization to change trace switches

o ST0R: Authorization to analyze traces

o SM21: Authorization to analyze system logs

liveCache Administration:

o LC01: liveCache Administration authorization (display functions)

o LC02: liveCache Administration authorization (start, stop)

o LC03: liveCache Administration authorization (integration,
configuration)

o LC04: liveCache Administration authorization (initialization)

Other:

o AUDA: Basis audit administration

o AUDD: Basis audit display authorization

o BTCH: Test environment, batch

o UNIX: Execute UNIX commands from the SAP System using program
SAPMSOS0

o RSET: Reset/delete data without archiving

o SYNC: Reset buffers (buffer synch. with $sync, $tab...)

o UBUF: Execute report RSUSR405 - Reset all user buffers

o X25 : Open X.25 connection to SAP System(using report SAPSERVER)

o TRNL: Translation administration (Transaction SLW2)

o TCTR: Table control settings throughout the system

o CONV: Conversion according to release

o SCP1: Set character sets, languages, character conversions

o SCP2: Database character conversion

Example

You can use the following values to assign to a user the authorizations
for administration of the spool output controller. The user can execute
all operations of the spool output controller.

Field Value
System administration SPAD, SPAM, SP01
functions

Additional authorization for S_SPO_ACT (Spool: Actions):

Field Value
Authorization field *
for spool activity

Value for *
Authorization check

Additional authorization for S_SPO_DEV (Spool: Device authorization)

Field Value
Spool: Output device *

Basis Critical object : S_RZL_ADM

2009-03-25T02:41:00.000-07:00

Definition

Authorization object for R/3 System administration using the Computing
Center Management System (Tools -> Administration -> Computing Center ->
Management System).

Defined fields

The object consists of the field Activity. This field specifies which
operations may be executed.

Possible values:

o 01: All Management System functions including starting and stopping
instances, setting up and changing operation modes, checking system
status, etc.

o 03: Display authorization. None of the maintenance functions can be
executed.

Basis Critical Object: S_USER_AUT

2009-03-20T23:11:00.000-07:00

Basis Critical object : S_USER_AUT

Definition
Authorization object, which is checked during authorization maintenance.
The check is made in the following authorization maintenance
transactions (Tools -> Administration -> User maintenance).
o SU03 - maintenance of authorizations
o SU02 - allocate authorization to a profile
Defined fields
This object is defined with the following three fields:
o Authorization object: The authorization objects, for which the
authorization administrator may maintain, delete, etc.,
authorizations, must be entered here.
o Authorization name: With this field, the authorization administrator
can be given a limited name space for the assignment of
authorization names.
It makes sense to do this when there are several adminstrators, so
that the authorizations are not maintained reciprocally or possible
internal naming conventions are adhered to.
o Activity: This field can be used to limit what the administrator may
do with the authorization.
Possible values:
- 01 = create
- 02 = change
- 03 = display
- 06 = delete
- 07 = activate
- 08 = display change documents
- 22 = assign authorization profiles
- 24 = archive
Example
Field Values
Authorization object S*
Authorization name *
Activity 01 - 06
With this authorization, the authorization administrator can create,
change, delete, and display authorizations of any name for all objects
beginning with S (Basis authorization objects). The administrator can
not, however, activate the authorizations or display the change
documents.

SAP Basis critical object

2009-03-19T02:45:00.000-07:00

1. S_BTCH_ADM

Definition:

S_BTCH_ADM authorizes a super user to manage background processing (menu
path Tools -> Administration -> Jobs -> Job overview).
An administrator with this authorization can:
o Access background jobs in all clients of an SAP system. In the
overview, the system displays all background jobs throughout the
system.
Without this authorization, users can only work on background jobs
in the clients in which they are logged on.
o Perform all functions on background jobs.
o Execute programs in job steps.

Defined fields:

ID for background administrator: Enter Y to grant the above
authorizations to an administrator.
Value N or missing authorization: The user is not authorized as a
background processing administrator.

SAP_ABAP Patch Application

2008-06-30T10:29:00.000-07:00

Procedure:
Following Steps Can be done Online(before the downtime)
BEFORE ACTIVITY IS STARTED – ONLINE

· Check the space in the drive containing folder eps\in.- Approx - 2-3GB space required

· Copy the car files from \\sapmnt\trans\(KA62051.CAR) to \\\sapmnt\trans on the “saptranshost” (server on which transport requests are imported).

· Open the command prompt on the server. Use the following command to unpack the files.
:\usr\sap\trans>car –xvf *.CAR ( Application & CRT patches)
The corresponding files ( .ATT and .PAT ) will be generated in

\\\sapmnt\trans\eps\in

· First take the offline backup of the MRL DCE system.

· Lock all users except for SAP*,DDIC and Copy of DDIC id, then in SA38 run Btctrns1

ONE DAY BEFORE ACTIVITY IS STARTED – ONLINE

INFORM THE USERS THROUGH MAIL / SM02 the SAP Downtime required

Pre – requisites:
Please Note: Following steps to be done Offline
FOR PRODUCTION SERVER ONLY- ( Approx – 1 hr )

Bring the DRS in sync with Production server.-& -shutdown the Database & copy the online logs in DRS -in another folder (emergency )

Ensure you have a complete backup before this & backup of archive logs until database is shutdown.

Do not apply the offline redo logs on the DRS until this support package activity is completed in production server successfully. With no errors after application of TP req. Until clearance given by functional/ABAP Team

Lock all the users except the user used by the Basis Admin. (or using trx SU10).in prodn client

CHECK ARCHIVE LOG DIRECTORY SPACE, CHECK DB02 -TABLES SPACE GROWTH, SPACE CRITICAL OBJECTS ETC BEFORE APPLYING SUPP. PACKS.

Upgrade of SPAM/SAINT (if required):

Existing version is 6.20/0022.We have to upgrade it to latest release 6.20/0026 available at marketplace.

grep Command

2008-06-26T14:53:00.000-07:00

Syntax

grep [ -E -F ] [ -i ] [ -h ] [ -H ] [ -L ] [ -r -R ] [ -s ] [ -v ] [ -w ] [ -x ] [ -y ] [ [ [ -b ] [ -n ] ] [
-c -l -q ] ] [ -p [ Separator ] ] { [ -e PatternList ... ] [ -f PatternFile ... ] PatternList ... } [ File ...
]

Description

The grep command searches for the pattern specified by the Pattern parameter and writes each matching line to
standard output. The patterns are limited regular expressions in the style of the ed or egrep command. The grep
command uses a compact non-deterministic algorithm.

The grep command displays the name of the file containing the matched line if you specify more than one name in the
File parameter. Characters with special meaning to the shell ($, *, [, , ^, (, ), \ ) must be in quotation marks
when they appear in the Pattern parameter. When the Pattern parameter is not a simple string, you usually must
enclose the entire pattern in single quotation marks. In an expression such as [a-z], the - (minus sign) cml
specifies a range, according to the current collating sequence. A collating sequence may define equivalence classes
for use in character ranges. If no files are specified, grep assumes standard input.

Notes:
1 Paragraphs (under the -p flag) are currently limited to a length of 5000 characters.
2 Do not run the grep command on a special file because it produces unpredictable results.
3 Input lines should not contain the NULL character.
4 Input files should end with the newline character.
5 The newline character will not be matched by the regular expressions.
6 Although some flags can be specified simultaneously, some flags override others. For example, the -l option
takes precedence over all other flags. And if you specify both the -E and -F flags, the last one specified
takes priority.

Flags

-b
Precedes each line by the block number on which it was found. Use this flag to help find disk block numbers by
context. The -b flag cannot be used with input from stdin or pipes.

-c
Displays only a count of matching lines.

-E
Treats each pattern specified as an extended regular expression (ERE). A NULL value for the ERE matches every
line.

Note: The grep command with the -E flag is the same as the egrep command, except that error and usage messages
are different and the -s flag functions differently.

-e PatternList
Specifies one or more search patterns. This works like a simple pattern but is useful when the pattern begins with a - (minus). Patterns should be separated by a new-line character. A NULL pattern can be specified by two adjacent new-line characters or a quotation mark followed by a new-line character ("\n). Each pattern is treated like a basic regular expression (BRE) unless the -E or -F flag is also specified. Multiple -e and -f flags are accepted by grep. All of the specified patterns are used when matching lines, but the order of evaluation is unspecified.

-F
Treats each specified pattern as a string instead of a regular expression. A NULL string matches every line.

Note: The grep command with the -F flag is the same as the fgrep command, except that error and usage messages are different and the -s flag functions differently.

-f PatternFile
Specifies a file containing search patterns. Each pattern should be separated by a new-line character, and an empty line is considered a NULL pattern. Each pattern is treated like a basic regular expression (BRE), unless the -E or -F flag is also specified.

-h
Prevents the name of the file containing the matching line from being appended to that line. Suppresses file names when multiple files are specified.

-H
If the -r or -R option is specified and a symbolic link referencing a file of type directory is specified on the command line, grep will search the files of the directory referenced by the symbolic link and all the files in the file hierarchy below it.

-i
Ignores the case (uppercase or lowercase) of letters when making comparisons.

-l
Lists just the names of files (once) which contain matching lines. Each file name is separated by a new-line character. If standard input is searched, a path name of (StandardInput) is returned. The -l flag with any combination of the -c and -n flags behaves like the -l flag only.

-L
If the -r or -R option is specified and a symbolic link referencing a file of type directory is specified on the command line or encountered during the traversal of a file hierarchy, grep shall search the files of the directory referenced by the symbolic link and all the files in the file hierarchy below it. If both -H and -L are specified, the last option specified on the command line takes effect.

-n
Precedes each line with the relative line number in the file. Each file starts at line 1, and the line counter is reset for each file processed.

-p[Separator]
Displays the entire paragraph containing matched lines. Paragraphs are delimited by paragraph separators, as specified by the Separator parameter, which are patterns in the same form as the search pattern. Lines containing the paragraph separators are used only as separators; they are never included in the output. The default paragraph separator is a blank line.

-q
Suppresses all writing to standard output, regardless of matching lines. Exits with a zero status if an input line is selected. The -q flag with any combination of the -c, -l and -n flags behaves like the -q flag only.

-r
Searches directories recursively. By default, links to directories are followed.

-R
Searches directories recursively. By default, links to directories are not followed.

-s
Suppresses error messages ordinarily written for nonexistent or unreadable files. Other error messages are not suppressed.

-v
Displays all lines not matching the specified pattern.

-w
Does a word search.

-x
Displays lines that match the specified pattern exactly with no additional characters.

-y
Ignores the case of letters when making comparisons. PatternList Specifies one or more patterns to be used during the search. The patterns are treated as if they were specified using the -e flag.
File Specifies a name of a file to be searched for patterns. If no File variable is given, the standard input is used.

Examples
1 To use a pattern that contains some of the pattern-matching characters *, ^, ?, [, ], $, $, \{, and \},
enter:

grep "^[a-zA-Z]" pgm.s

This displays every line in pgm.s whose first character is a letter.
2 To display all lines that do not match a pattern, enter: grep -v "^#" pgm.s

This displays every line in pgm.s whose first character is not a # (pound sign).

3 To display all lines in the file1 file that match either the abc or xyz string, enter: grep -E "abcxyz" file1

4 To search for a $ (dollar sign) in the file named test2, enter:

grep \\$ test2

The \\ (double backslash) characters are necessary in order to force the shell to pass a \$ (single backslash, dollar sign) to the grep command. The \ (single backslash) character tells the grep command to treat the following character (in this example the $) as a literal character rather than an expression character. Use the fgrep command to avoid the necessity of using escape characters such as the backslash.

5 To search recursively through /tmp to find files which have the word IBM without recursing through links pointing to directories, type:

grep -R IBM /tmp
OR

grep -r -H IBM /tmp
6 To search recursively through /tmp to find files which have the word IBM and recurse through links as well,
type:

grep -r IBM /tmp
OR

grep -R -L IBM /tmp

Files

/usr/bin/grep
Contains the grep command.

What is authorization, authorization object, authorization profile, role?

2008-06-16T22:22:00.000-07:00

Actions and the access to data are protected by authorization objects in
the SAP system. Authorization objects allow complex checks that involve multiple
conditions that allow a user to perform an action. The conditions are
specified in authorization fields for the authorization objects and are AND
linked for the check. Authorization objects and their fields have descriptive
and technical names.

An authorization is always associated with exactly one authorization
object and contains the value for the fields for the authorization object.
An authorization is a permission to perform a certain action in the SAP
system. The action is defined on the basis of the values for the individual
fields of an authorization object.

A role is primarily a functional description
The technical realization of the role, in the form of concrete authorizations is achieved through the authorization profile associated with the role.

What is a composite profile?

A set of profiles which are included under a single profile name is called as a composite profile (SU02)

How can you find missing authorizations? How can you solve?

By running the SU53 transaction.
Identify the authorization object where the required filed value is to be given and the do the same thru SU01 or PFCG.

Importanat database command : BRTOOL and BRBACKUP

2008-06-10T06:15:00.000-07:00

Querying tape Required :
brbackup -q
brarchive -q

Initialising tape:
brbackup -c -i force -v / SCRATCH

brarchive -c -i force -v / SCRATCH

Backup:
Database Backup
brbackup -c -m all -t online -a -c -cds For Online Database

brbackup -c -m all -t online_cons -a -c -cds For Online consistent backup (Database + Archive Logs)

brbackup -c -m all -t offline -a -c -cds For Offline backup

Archive Log Backup
brarchive -c -cds Archive Log Backup with Copy ,delete & Save
brarchive -c -sd Archive Log backup with Save & Delete

Queryng Tape No. present inside Tape Drive
brbackup -i show
Restoring Offline Backup from Tape brrestore –c –m all –b <.aft file>

*.aft file for that particular backup will be at path : oracle\SID\sapbackup\<.aft>
Forcefully Ending the backup
1 Execute DB02 TCode
2 Go to Current Sizes
3 Read the Tablespace name whose backup status is 'ACTIVE'
4 Telnet of the Server / Take Dameware of server & goto command prompt
5 sqlplus /nolog
6 conn /as sysdba
7 Fire following command
alter tablespace end backup;

How can you configure the printer? Explain the spool admin?

2008-06-05T10:38:00.000-07:00

· The configuration of the spool system is a system administration task. The central tool for this is transaction SPAD.

· To create an output device, choose Output Devices on the Devices / Servers tab page. If there is already a large number of devices in your system, you can restrict the output list in the field next to the button (for example .PR*.).
Important information for a device:
ü Output device
Name, maximum of 30 characters long (case-sensitive).

ü Short name
For internal system purposes (can be automatically generated).

ü Device type
Printer model/family (more information about this below). The device type SWIN transfers the SAP system format to the Microsoft Windows printer driver. This is useful, for example, if various printers are used for front end printing in a Microsoft Windows environment.

ü Spool server
SAP application server with spool work processes or logical server.

ü Location
For example, building and room number (so that users can find their output).

ü Message
Used to temporarily override the location (such as .Is currently in maintenance.)

ü Lock printer in SAP system
Output requests for printers for which this indicator is selected are created but not transferred to the printer. The user receives the message ...no immediate printing.

ü Host spool access method
How does a spool work process contact the operating system spooler?

ü Host printer
Name of the printer at operating system level. Note that this name is case-sensitive. Under Microsoft Windows, there must not be a space in the printer name, and network printers are addressed using their UNC names (in the format \\R12345\P42). The specification __DEFAULT calls the defaultMicrosoftWindows printer (for example, for front end printing in a Microsoft Windows environment).

ü Host
Only for local printing, is calculated automatically from the spool server.

ü Destination hosts
Only for remote printing. Name of the host on which the operating system spooler (such as lpd or saplpd) is running.

What's the use of a domain controller and how to configure the same?

2008-05-30T23:29:00.000-07:00

The transport domain contains all SAP systems whose transports are to be administrated jointly. One of these SAP systems is chosen as the transport domain controller.
Since all activities relevant to the entire transport domain, such as configuring transport routes or RFC connections, can only be carried out on the domain controller, the SAP system selected to be the domain controller should have:
High availability
A high level of security
A high level of maintenance

The domain controller is normally configured on a production system or a quality assurance system. Out of several reason you may choose to set up an SAP System dedicated to tasks that may be carried out CENTRALLY. This includes the task of the TMS domain controller.
The system load on the SAP system that is chosen as the domain controller is low, and only increases for a short period when the TMS configuration is changed.
Configuration:

To activate the TMS on an SAP system, run transaction STMS in client 000 with user authorization S_CTS_ADMIN.
If the SAP system is already assigned to a transport domain, the TMS initial screen shows the system’s status, either as a domain controller, or as a SAP system within a domain.
If the SAP system is not yet assigned to a transport domain, the system tries to locate an existing transport domain within the current transport group by reading the file DOMAIN.CFG in the directory bin of the common transport directory. If no transport domain exists, a new transport domain is created, and the current SAP system is assigned as the transport domain controller.
When a transport domain controller is first created, the TMS generates:
ü A transport domain and a transport group
ü User TMSADM
ü The RFC destinations required for the TMS
ü File DOMAIN.CFG in directory bin of the common transport directory, for storing the TMS configuration
o The name of the transport domain may not contain blanks and may not be changed afterwards without reconfiguring the domain controller. By default, a transport domain will have the name DOMAIN_, where is the system ID of the domain controller. The name of the transport domain cannot be changed afterwards.

How will you configure a STMS, 3 system configuration?

2008-05-30T23:26:00.000-07:00

To configure the TMS:

Configure the transport domain
Assign SAP systems to the transport domain, and specify one SAP system as the transport domain controller.
Configure transport routes
The transport routes are used to define both the target system in which you want to consolidate change requests, and the SAP systems to which change requests are delivered after verification and testing.

Configure Quality Assurance (QA) Procedure
Define a QA system, where the decision is made whether objects may be further transported to the production system.
After setting up the TMS, use the TMS tools to check and monitor TMS configuration.

How many types of transport requests? Explain?

2008-05-27T22:21:00.000-07:00

There are 3 types of requests:
K type:
The transport K type implements transports of DE objects from the integration system into the consolidation system. When you create a transport request using the workbench organizer, it always uses this transport type by default meaning that all the transportable change requests stored in the workbench organizer are allocate this transport type. For this transport type, the objects are transported to the consolidated systems without changing the object’s system owner which means that the transported objects in the consolidated system become repair objects and no corrections are allowed for the imported objects.
C type:
With this transport type the objects change the system owner after they are transported which means that the source system of the object loses its ownership after the object is transported. So the target system in which the objects are transported becomes the original system. In other words objects are transported as original objects. So they can be corrected or modified in the target system too. That means that change authorization is also transported. In SAP terms, objects that are transported with C types are checked out of a system and checked into another system.
T type:
This transport type is useful when you have to copy object between two systems in a group ie when a system(other than consolidation system) receives a copy of objects, the corresponding transport takes place with transport type T. Object including the object of transport type T do not change their system owner. So the original system remains same.

Components of R/3 Architecture

2008-05-25T11:57:00.000-07:00

Database Server
The database server is the most powerful server in an R/3 system. R/3 uses the database management system as central storage for all R/3 data and R/3 metadata information. This central storage, the basis for the tight integration of all R/3 application modules, guarantees consistent data storage.
Three important factors govern the decision-making process for selecting data storage options.
· Adequate protection from data loss
· Appropriate speed of access
· Sufficient storage capacity to accommodate growth
The application server
While SAP uses the generic term application server to define a computer that receives connections from SAP clients, the actual connections are managed by SAP dialog servers.
A dialog instance is a software program that is running the SAP kernel (similar to an Oracle instance), and it is the job of the dialog instance to execute the ABAP programs and manage the requests for data and services. While there is generally a one-to-one mapping between an application server and a dialog instance, it is possible to have more than one dialog instance on an application server.

Instance
An instance is a group of R/3 services that are started and stopped together
The central instance
The central instance is a concept that is unique to SAP. The central instance is a combination of hardware and software. It contains a physical server (the application server) and numerous software components, including a message server, a database gateway (a pre-established connection between SAP and Oracle--or another database), and various update, enqueue, dialog, and spool facility software. In most generic SAP architectures, there are numerous application servers but only a single central instance. However, in addition to managing the SAP interfaces, the central instance can also serve as an application server.
Work Process
A work process is where individual dialog steps are actually processed and the work is done. Each work process handles one type of request.
The work process types are:
Dialog, for executing dialog programs(processes only one request at a time)
Update, for changing database entries( primary or secondary )
Background, for executing background jobs( started at a specified time )
Spool, for print formatting (generated online or during back ground processing For printing ) and
Enqueue, for executing lock operations

Dispatcher
Central process on an instance. It is responsible for starting work processes and distributing transaction load across work processes.
Message Server

Independent program that maintains a list of all instances in a SAP system. The message server determines which instance a user logs on to and organizes communication between instances

Gateway
Interface that converts one communication protocol into another.

Explain work processes
A work process is where individual dialog steps are actually processed and the work is done. Each work process handles one type of request.
The work process types are:
Dialog, for executing dialog programs(processes only one request at a time)
Update, for changing database entries( primary or secondary )
Background, for executing background jobs( started at a specified time )
Spool, for print formatting (generated online or during back ground processing For printing ) and
Enqueue, for executing lock operations
.

What is STMS? How do u configure it?

2008-05-25T11:54:00.000-07:00

STMS is used for configuring routes / importing into relevent server after release of a request.
STMS is being used to transport all your customization and workbench work from Development to QA and then to production.There are several steps need to follow for STMS configuration.1. Create Common mount point /usr/sap/trans. (Normally Development server file system need to be mount with Production system with nfs.)2. In all servers, to configure STMS follow the steps as mentioned below.i. Create Systemii. Select same domain for both the systems.iii. Again in Development server create Transport Route. (One Transport Layer for Standard objects and one layer for Customer Objects)iv. Activate the router in all the systems.3. Check the Status of all system of STMS after activation.

Type of Users in SAP system

2008-05-24T06:34:00.001-07:00

1. Dialogue:-
For this kind of users:-
GUI login is possible.
Initial password and expiration of passowrd are checked.
Multi GUI logins are checked.
Usage:- These are used for GUI logins.

2. System
For this kind of users:-
GUI login is not possible.
Initial password and expiration of passowrd are not checked.
Usage:- These are used for internal use in system like background jobs.

3. Communication
For this kind of users:-
GUI login is not possible.
Users are allowed to change password through some software in middle tier.
Usage:- These are used for login to system through external systems like web application

4. Service
For this kind of users:-
GUI login is possible.
Initial password and expiration of passowrd are not checked.
Multiple logins are allowed.
Users are not allowed to change the password. Only admin can change the password
Usage:- These are used for anonymous users. This type of users should be given minimum authorization.

5. Reference
For this kind of users:-
GUI login is not ible.
Initial password and expiration of passowrd are not checked.
Usage:- These are special kind of users which are used to give authorization to other users.

What is a client copy?

2008-05-21T21:52:00.000-07:00

A client copy does not "generate a new system". It is used to transferinformation between clients within the same system or to another system atthe same release and db level.

Procedure to create:
If it is a fresh installation, do this --

1. SCC4 --> Create client no. and fill other details.

2. Logon to the newly created client with SAP* and PASS as password.

3. SCCL --> choose any profile (preferably SAP_ALL), source client 000 and target client .

4. Preferably do a test run initially to check if it can go well.

5. As a care check space in databases.

You can do Client copies remotely or do an export/import of data. Please study the dependancies of client dependant/independant data rel.notes.
Export: If you need to do a full client copy and database is more than 50 or 60gb, the import may tae little long time. Export of the full data can be done with SAP_ALLprofile in Source system. SCC4 >> Export the data with required profiles. It will create data and cofiles under os level. (usr/sap/trans/data, cofiles).The export may take of 8 to 20 hrs dependts on data.The import may take several days based on the size of the data. You need to set some parameters before you start the import. After the succefull import you need to do post processing for client copy with request in scc8.

It depends upon what method you want to do client copy.
If you say remote client copy, i will suggest you against it because it takes hell lot of time to do client copy and any break for a moment in network connection will cause failure in client copy.If you are exporting the client then as such there is no problem, just remember the sequence in which you import the three (or two) transport requests.AND, keep enough free space in Tablespaces of Target server
Procedure :
1.Check Sufficeint space at OS level to keep extracted data from source client

2.Export the client using following path or scc8Tools (r) Administration (r) Administration (r) Client Admin. (r) Client Transport (r) Client Export. Select the data to be copied using a profile. (if u wnat client specific and cross client data use profile sap_expc). before importing ensure that all table spaces have enough sapce for this check source system table spaces and allocate table space accordingly)

3.Now create new client in target system

4.now import those requests in target client using stms or scc6

5.Now perform post processingTools (r) Administration (r) Administration (r) Client administration (r) Client transport(r) Import editing

SAP Transaction

2008-05-18T23:26:00.000-07:00

Some of the trasaction which are use by Basis Admins regularly. List of T-Code are given below
Daily maintenance
SM21 : Systemlog
SM37 : Check the batchjobs
SM50/51 : Show all processes on one server / all servers
SM66 : Show all active process on the system
ST11 : Display developer-traces
ST22 : ABAP-dumps

Background job-related
RZ04 : Operation modes
SM36 : Create background job
SM37 : Show background jobs
SM63 : Operation mode calendar
SM65 : Check background job-settings

Generally useful
AL11 : SAP directories
DB02 : Database performance: Tables and Indexes
PFCG : Profile generator
RZ10 : Profile maintenance
SARA : Archiving
SCC4 : Client change options
SE01 : Transport organizer, use SE09 for ABAP-transports, SE10 for customizing transports : SE06 (4.x up)
System change options, see SCC4 for Client change options.
SE71 : Maintain Layout-sets also known as sapscripts
SM02 : System message
SMGW : Gateway administration
SMLG : Define logon-groups
SMLT : Language administration
SPAM : Support Package Manager
SPAU : ABAP-dictionary assistant during support package-import
SPDD : Data-dictionary assistant during support package-import
STFK : Search the customer system that have an open connection to Walldorf

AIX command for Basis administrator

2008-05-15T20:20:00.000-07:00

Simple commands
chgrp grp filelist : Change the group that the file(s) belong to.
chmod 777 filelist : Change the rights of the file(s). 777: owner-world-user. 7: read-write-delete (=111)
chown user filelist : Change the owner of the file(s)
cp file1 file2 : Copy file1 to file2
cp /dev/null file : Clear all contents of file
errpt : Hardware error-report (IBM-unix)
ls –ltr : Show filelist, –parameters: l: show fileattributes , t: sort by time, r: reverse sortorder
more

mv file1 file2 : Move command
ps –ef : Show all running processes, -e, -f
vi : The famous vi-editor

2 A little more complex commands
kill : Kill a process as if it is cancelled. Child processes are killed as well.
kill –1 : Kill a process as if the user is logging out. Child processes are killed as well.
kill –9 : Kill a process as brutal as possible. Child-processes are not touched.
kill –USR2 : Increases TRACE by 1
kill –USR1 : ecreases TRACE by 1. When TRACE = 0 all open trace files are closed and can be cleared using ‘cp /dev/null filename’.
lslv : Show the logical volumes
lsvg : Show the volumegroups
sappfpar check pf= : Checks the profileparameter. Do they exist and do they have correct values.
set VAR VAL : set environment variable VAR to value VAL
printenv : prints the environementvariables
ps –ef grep xxx : Monitor processes with name containing xxx
ps –u : Monitor processes run by user