SAP BASIS OS Level (UNIX) Commands?

Commands	Description
dpmon d	Dispatcher queue monitor
Sapdba (up to SAP R/3 -4.7)/ brtools	database administration
PS	Running work process
ps -eaf|grep dw	process overview
ps -eaf|grep ora	check oracle service is running
Ps –eaf | grep dw kill -9	Kill work process
msmon pf=profile path name=sid	to check the message server status
gwmon pf=profile path nr=num	to check the gateway status
Ps –eaf | grep lsnrctl	Listener status
Rslgview pf =-r –ft | pg	System logs
Disp + work –v	to check the version of r3 kernel
R3trans –d ,tnsping	Checking the connection with database
Df –k	File system monitor
Du –k	Display all directories and size of current directory
Sqlplus “/as sysdba” (new versions)	SQL prompt and database connection
Saplicence  -get	to get hardware key
saplicense -install	to install license
sappfpar all pf=profile path	display all profile parameters
sappfpar check path=profile path	checks the required space for memory
memlimits	to check the available space for heap and swap memory
telnet	Remote system login
telnet <ipaddress><dispatcherportnum>	to check the remote sap system is up and running
ftp	file transfer protocol
rcp	remote copy of files
Start/stop sap	Start / stop Sap instance
ping	check destination host reachable
niping	check connection between server and a client by transferring packets
systeminfo	check the configuration of system
Ps -eaf	Processes status
lsps -a	Swap space
topas	Memory

How to delete old batch session on SM35

Users have created a ton of batch input sessions and processed them with SM35. The users did 

not care about deleting unwanted sessions and there are a lot of old sessions, with almost any 

status (in processing/in background/processed/errors). All of them are junk (in your terms), and 

have to be removed from the system.

You can delete unwanted sessions with ABAP program RSBDCTL6 at once and then setup a 

background job that deletes the sessions for a specific session, user who created the session, 

date range, older than x days etc. that runs on a regular basis.

As an alternative, you can run program RSBDC_REORG. However, our tests showed that this 

program may not be suitable for sessions that have a status other than processed.

Note: This has been validated on a ECC 5.0 system. Please consult SAP Marketplace if your 

system doesn’t have these programs and/or if these are suitable for your release.

How to check how many users running on instance at os level?

1. How to check how many users running on instance at os level?

SM 04 we check instance vise, AL08 we check total instances only Dialog users. ST06 --LAN tab--> check there how many users are login the system wide here we check system names and ip address also.

2. How can we basis people change the database parameters?

OS level we set parameters

Linux, Oracle DB..

go to /oracle/SID/112_64/dbs/initora.sap

here we copy file initora.sap to offline_ora.sap or online_ora.sap

then inside we modify the parameters...

next we login db13 then we given profile parameter as per our backup set profile parameter.

How to configure Central User Administration (CUA)

Here is the procedure for Central user administration configuration in a landscape:

1. Create Logical systems to all clients for the landscape using BD54 or SALE as
   comfortable.

2. Attach Logical system to clients using same.

3. Create RFC connection to relevant systems with the same name as logical system name.

If you Logical system name is SIDCLNT100 for dev then create RFC connection to
DEV with same name SIDCLNT100.

4. Let us suppose you Central system: DEVCLNT100
Child system: QUACLNT200

5. Create user CUA_DEV_100 in devclnt100 system

4. Create user CUA_QUA_200 in quaclnt200 system.

Create RFC’s to child systems from central and central to child.

5. Now logon to central system and execute tcode SCUA to configure CUA.

Enter the name of the distribution model: CUA

Press create

Enter ALL Child system RFC’s

Save your entries now result screen will appear

If you expand the nodes for

the individual systems, you normally see the following messages for

each system: .ALE distribution model was saved,. .Central User

Administration activated and Text comparison was started.. 

If problem messages are displayed here, follow the procedure in SAP Note 333441:

6. Setting the Parameters for Field Distribution

Enter Tcode SCUM in central system following screen will appear

Now maintain your filed distribution and save it.

You can use transaction SUCOMP to administer company address data.

You can use transaction SCUG in the central system to perform the synchronization activities 

between the central system and the child systems by selecting your child system on the initial

screen of transaction SCUG and then choosing Synchronize Company Addresses in the 

CentralSystem

After you have synchronized the company addresses, you can transfer the users from the newly 

connected child systems to central administration.

This is done, as with the synchronization of the company addresses, using

transaction SCUG in the central system. To do this, on the initial screen of

transaction SCUG, select your child system and choose the Copy Users to

the Central System button.


Use:

You can use the report RSCCUSND from the central system of Central User Administration (CUA) to synchronize the master data of selected users with a child system of the CUA. The report sends the master data (including role and profile assignments) to a child system of the CUA.
If master data exists in the child system for the user sent, it is overwritten.

Procedure:

1. Start report RSCCUSND (for example, using transaction SA38).
2. In the Receiving System field, specify the child system to which you want
    to send the user data.
3. You can use the fields User and User Group to restrict the number of users.
4. Specify the data that you want to distribute under Distribution Options.
5. Choose Execute.

Difference between PFILE and SPFILE? What are their advantages?

Difference between PFILE and SPFILE? What are their advantages?

 PFILE

Until Oracle 8i, we were using a text file called the PFILE (parameter file) for setting the database initialization parameters. This PFILE is read at instance startup time to get specific instance characteristics. The PFILE is text based, and can be edited in an editor like vi on UNIX or Notepad on Windows. Any changes that were made in PFILE would only take effect when the database is restarted,

Since SAP/Oracle recommends using SPFILE over PFILE, I will provide some details on SPFILE to answer your question in more detail.

SPFILE

In Oracle9i, a new feature called SPFILE (server parameter file) was introduced. SPFILE is a binary file that contains the same information as the old PFILE. SPFILE permits dynamic changes without requiring you to restart that instance.

By default, if you do not specify PFILE in your STARTUP command, Oracle will use server parameter file (SPFILE). If you choose to use the traditional text initialization parameter file (PFILE), you must specify the PFILE clause when issuing the STARTUP command.

The SPFILE is different from the PFILE in that it cannot be directly edited. This is because it has a header and footer that contain binary values. Since you cannot change a SPFILE directly, Oracle allows you to manage the SPFILE via the ALTER SYSTEM command.

When you execute the ALTER SYSTEM command, the parameter change is validated immediately, which helps avoid errors associated with entering an incorrect parameter name or an invalid value. In addition, the ALTER SYSTEM allows you to specify whether you want to update the parameter immediately, update just the SPFILE, or both. All these features help avoid human error associated with manually updating a PFILE.

The following example shows how to change the current value of SESSIONS and store the value in the SPFILE.

SQL> ALTER SYSTEM SET SESSIONS=200 SCOPE=SPFILE;

The new part in this command is the parameter SCOPE. You have the following options for this.

SCOPE = SPFILE

(For both static and dynamic parameters, changes are recorded in the spfile, and will take effect in the next restart.)

SCOPE = MEMORY

(For dynamic parameters, changes are applied in memory only. No static parameter change is allowed.)

SCOPE = BOTH

For dynamic parameters, the change is applied in both the server parameter file (SPFILE) and memory. No static parameter change is allowed.)

For dynamic parameters, we can also specify the DEFERRED keyword. When specified, the change is effective only for future sessions.

Now for the first part of your question. Since you are using Oracle 10G, you have to use the ALTER SYSTEM command to change the Oracle parameters as recommended by the SAP Early Watch Alert.