5
SAPOSCOL : how SAP R/3 instance communicate with OS SAPOSCOL a tiny program developed by SAP as daemon so that SAP R/3 instance can comunicate with its OS host. By using this SAPOSCOL program, SAP R/3 can communicate and can get a lot of information about OS including CPU usage, memory level usage, swap, disk activity, network information, monitored process, system configuration, client – server connectivity, etc. Hmm….we can get it without directly communicate with OS. Just use SAPGUI from your workstation. Usually, SAPOSCOL program had to be started before your SAP R/3 instance so that it can supply your R/3 instance with OS information. To start SAPOSCOL program, your just entered your OS console/terminal and use ora[SID] (if you’re using Oracle) or SAPservice[SID] if you’re using MS SQL. Just type : #saposcol If SAPOSCOL process had been running, it will show you the information and status. To stop SAPOSCOL, just type : #saposcol -k

SAPOSCOL How Sap R3 Communicates With OS

Embed Size (px)

Citation preview

Page 1: SAPOSCOL How Sap R3 Communicates With OS

SAPOSCOL : how SAP R/3 instance communicate with OS

SAPOSCOL a tiny program developed by SAP as daemon so that SAP R/3 instance can comunicate with its OS host. By using this SAPOSCOL program, SAP R/3 can communicate and can get a lot of information about OS including CPU usage, memory level usage, swap, disk activity, network information, monitored process, system configuration, client – server connectivity, etc. Hmm….we can get it without directly communicate with OS. Just use SAPGUI from your workstation.

Usually, SAPOSCOL program had to be started before your SAP R/3 instance so that it can supply your R/3 instance with OS information. To start SAPOSCOL program, your just entered your OS console/terminal and use ora[SID] (if you’re using Oracle) or SAPservice[SID] if you’re using MS SQL.

Just type : #saposcol

If SAPOSCOL process had been running, it will show you the information and status.

To stop SAPOSCOL, just type : #saposcol -k

To check SAPOSCOL information, just type : #saposcol -s

SAPOSCOL Status command on NED

bash-3.00$ saposcol -s

**************************************************************

Collector Versions :

Page 2: SAPOSCOL How Sap R3 Communicates With OS

running : COLL 21.03 711 - V3.80 64Bit

dialog : COLL 20.95 700 - V3.72 64Bit

Shared Memory : attached

Number of records : 4590

Active Flag : active (01)

Operating System : SunOS mhpa600c 5.10 Generic_144500-19 sun4us

Collector PID : 26406 (00006726)

Collector : running

Start time coll. : Sun Feb 26 05:02:30 2012

Current Time : Mon Feb 27 10:12:34 2012

Last write access : Mon Feb 27 10:12:29 2012

Last Read Access : Mon Feb 27 10:12:07 2012

Collection Interval : 60 sec (next delay).

Collection Interval : 60 sec (last ).

Status : free

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Page 3: SAPOSCOL How Sap R3 Communicates With OS

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 2

Collector in IDLE - mode ? : NO

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 60 sec

SAPOSCOL Status command on WID WDP

widadm> saposcol -s

**************************************************************

Collector Versions :

running : COLL 20.95 700 - V3.72 64Bit

dialog : COLL 20.95 700 - V3.72 64Bit

Shared Memory : attached

Number of records : 4795

Active Flag : active (01)

Operating System : SunOS muepsip002 5.10 Generic_144488-12 sun4v

Collector PID : 4718 (0000126E)

Collector : running

Start time coll. : Mon Feb 20 11:19:46 2012

Current Time : Mon Feb 27 10:13:41 2012

Page 4: SAPOSCOL How Sap R3 Communicates With OS

Last write access : Mon Feb 27 10:13:36 2012

Last Read Access : Thu Jan 1 01:00:00 1970

Collection Interval : 60 sec (next delay).

Collection Interval : 60 sec (last ).

Status : free

Collect Details : required

Refresh : required

Header Extention Structure

Number of x-header Records : 1

Number of Communication Records : 60

Number of free Com. Records : 60

Resulting offset to 1.data rec. : 61

Trace level : 2

Collector in IDLE - mode ? : YES

become idle after 300 sec without read access.

Length of Idle Interval : 60 sec

Length of norm.Interval : 10 sec

**************************************************************