SAPOSCOL - Operating System Collector

Ø  What is SAPOSCOL ?

SAPOSCOL is a stand-alone program that runs in the operating system background. It runs independently of SAP instances exactly once per monitored host. collects data about operating system resources like,

• Usage of virtual

• Usage physical memory

• CPU Utilization

• Utilization of physical disks 

• Utilization of file systems

• Resource usage of running processes

Ø  How it works ?

• SAPOSCOL runs exactly once on each host.

• SAPOSCOL runs independently of the SAP system.

By default, SAPOSCOL collects the current data every ten seconds and records it, and records the hourly averages for the last 24 hours, The data is stored in shared memory.  This data will be fetched by background job “SAP_COLLECTOR_FOR_PERFORMANCE” and writes it to the MONI performance database table.

Ø  How to check the SAPOSCOL data ?

At SAP level you can view the information collected by SAPOSCOL using tcodes/transactions ST06, OS06 & OS07.

Ø  SAPOSCOL Administration from OS Level

Login to Server as SIDADM user

SAPOSCOL Stop
saposcol -k

SAPOSCOL Start
saposcol -l

Check SAPOSCOL status
saposcol -s

Ø  SAPOSCOL administration from GUI

• Execute transaction OS07N
• Select from the left panel (Marked as 1)
• Expand 'Additional functions' and choose 'Administrator SAPOSCOL'       (Marked as 2)
• Select the command "Start, Stop or Status" from top menu (Marked as 3)

Also Read,

SAP Kernel Topics

Thanks for reading, Please share your valuable feedback

How to take database backup in Sybase ASE

Database Backup commands :-

Login to Sybase Database as SYBSID user

> isql  -Usapsa -PXXX -SSID   -X
> go
> use master
> go
> dump database <SID> to "<directory> "
> go

Database backup with compress option:-

Login to Sybase Database as SYBSID user

> isql -Usapsa -PXXX -SSID -X
> go
> use master
> go
> dump database <SID> to "<directory>" with compress = 101
> go

Also Read :-

Backup automation for Sybase Database in SAP

Sybase DB Restore with Full Backup

SM02: SAP System Messages

SM02 T-code is a very useful for communicating system changes or alerts to the active SAP users. It can be used to broadcast messages regarding various information's like system down time,  maintenance time, etc

Execute T-code SM02

Click on 'Create' option for broadcast new message,

• System message text – The 3 lines are the space for your message
• Server - Select the application server from the list
• Client - Client number to display the message
• Lang -  Language ( Only be received based on sender specific language )
• Display To - The time till the message display
• Delete on – when to delete time

Confirm your message has activated & shows on the SM02 screen

Once the message has saved, that will display to the all active users in system & new login users while hey are login 

Also you can edit, delete the existing message in SM02 screen by selecting your message

Thanks for reading, Please share your valuable feedback

Also Read:-

SAP Basis Topics

Commoncryptolib update in SAP System

What is Cryptographic Library in SAP

The SAP Cryptographic Library is the default security provider for the secure store and forward (SSF) mechanisms. The SAP Cryptographic Library provides the functions for creating and verifying digital signatures within SAP NetWeaver Application Server (SAP NetWeaver AS).

To Upgrade / Install crytolib follow the stets,

Download the Comoncryptolib Files form SP download center

• https://launchpad.support.sap.com/#/softwarecenter
• INSTALLATIONS & UPGRADES
• By Alphabetical Index (A-Z)
• C
• SAP CRYPTOGRAPHIC SOFTWARE
• SAPCRYPTOLIB
• COMMONCRYPTOLIB 8
• Download the Latest File

Download the correct version by selecting your Server OS.

Check the Current version of SAP Commoncryptolib in your system

T-code - STRUST

Environment ----> Display SSF Version

Find out the current cryptolib location of your system using below parameter values in RZ11. 

- ssl/ssl_lib
- snc/gssapi_lib
- spnego/krbspnego_lib
- ssf/ssfapi_lib
- sec/libsapsecu

Check the Commoncryptolib files under Directory which you found from above parametes, Depends on OS the crytolib files are different. 

Directory example :- /sapmnt/SID/exe/uc/linuxx86_64

For Upgrade follow the below steps,

• Stop all SAP Application Server

If you have multiple Application Servers, stop all application servers.

• Login to Primary Application server

Copy the downloaded Commoncryptolib SAR files to the Primary Application Server 

Uncar the SAR file to a temporary location using below command,

                      

sapcar -xvf Filename.SAR

• Copy the extracted files (using sapcar) to the the crytolib directory (Primary Application Server) 

• Start the SAP Application Servers

Make sure system is up &r running without any fails

• Check the Commoncryptolib version after upgrade

T-code - STRUST

Environment ----> Display SSF Version

Thanks for reading, Please share your valuable feedback

Also Read:-

SAP Basis Topics

Disable SAP HANA System Replication with hdbnsutil

We can disable SAP HANA system replication in an SAP HANA system using hdbnsutil.

Remember before disable Replication :-

• Login as SIDADM user
• Secondary system must be offline

Disable Procedure :-  

1. Unregister Secondary System

• Stop Secondary System
• Unregister Secondary System  using below command

           hdbnsutil –sr_unregister

2. Disable system replication 

Use Below command on Primary System 

          hdbnsutil –sr_disable

Check the status using command /hdbnsutil -sr_state

After Disable the replication we can replicate the systems again ,

On Primary System :-

            hdbnsutil –sr_enable

If it not working the use below command to forcefully disable the replication,

    

            hdbnsutil –sr_disable --force

the start replication again,

            hdbnsutil –sr_enable

On Secondary System :-

Stop Secondary system

Use below command to start again the replication,

            hdbnsutil -sr_register

Full Command :- 

hdbnsutil -sr_register --replicationMode=<sync> --operationMode=<logreplay> --name=<SiteB>     --remoteInstance=<instId> --remoteHost=<hostname_of_SiteA>

Start Secondary System

If the above steps not worked the use below option to configure the replication again,

Stop Secondary system then,

            hdbnsutil -sr_cleanup --force

            hdbnsutil -sr_register   (Full command mentioned above)

Start the secondary system

Also Read,

SAP HANA System Replication setup with hdbnsutil

Prerequisites for Configuring SAP HANA System Replication

Replication Modes of SAP HANA System Replication

Thanks for reading, Please share your valuable feedback

SAP HANA System Replication setup with hdbnsutil

The following steps show how to configure such a system. In this scenario there are two SAP HANA systems: A, B named SiteA & SiteB. This scenario supports a tier 2 secondary with sync replication mode.

Check the Replication prerequisites using below link,
Prerequisites for Configuring SAP HANA System Replication

1. Enable system replication in Primary System.
    Primary System Loggical Name - SiteA

     Login as SIDDM

    cd /usr/sap/<sid>/HDB<instancenr>/exe
    /hdbnsutil -sr_enable --name=SiteA

   To check if the site has been successfully enabled for system replication with hdbnsutil run:
   

    /hdbnsutil -sr_state

2. Stop the tier 2 secondary System
     sapcontrol -nr <instance_number> –function StopSystem HDB or HDB stop

3. Register Secondary System on Primary

hdbnsutil -sr_register --replicationMode=sync --operationMode=logreplay --name=SiteB     --remoteInstance=<instId> --remoteHost=<hostname_of_SiteA>

4. Start the secondary system
sapcontrol -nr <instance_number> –function StopSystem HDB  or  HDB start

To check if the site has been successfully enabled for system replication with hdbnsutil run

/hdbnsutil -sr_state

Also Read,

Disable SAP HANA System Replication with hdbnsutil

Replication Modes of SAP HANA System Replication

Thanks for reading, Please share your valuable feedback.  

Replication Modes of SAP HANA System Replication

Check the Prerequisites for Configuring SAP HANA System Replication using below link,

Prerequisites for Configuring SAP HANA System Replication

While registering the secondary system for replication, we may specify the replication mode to use otherwise the default replication mode will use.

Following are the different SAP HANA replication modes for the redo logs,

Synchronous in-memory (SYNCMEM) :- 
The secondary system sends an acknowledgment back to the primary system as soon as the data is received in memory.  When the connection to the secondary system is lost, the primary system continues the transaction processing and writes the changes only to the local disk. Data loss can occur when primary and secondary fail at the same time as long as the secondary system is connected or when a takeover is executed, while the secondary system is disconnected.

This option provides better performance because it is not necessary to wait for disk I/O on the secondary system, but it is more vulnerable to data loss. The disk I/O speed on the secondary system doesn't influence the primary's performance.

Synchronous (SYNC) :-

The primary system waits with committing the transaction until it gets a reply that the log is persisted in the secondary system. This option guarantees immediate consistency between both systems.

When the connection to the secondary system is lost, the primary system continues the transaction processing and writes the changes only to the local disk. No data loss occurs in this scenario as long as the secondary system is connected. Data loss can occur, when a takeover is executed while the secondary system is disconnected.

Additionally, this replication mode can run with a full sync option. This means that log write is successful when the log buffer has been written to the log file of the primary and the secondary system. When the secondary system is disconnected, the primary system suspends the transaction processing until the connection to the secondary system is reestablished. No data loss occurs in this scenario. 

 Prerequisites for Configuring Full Sync option,

• Configure your system replication with the SYNC replication mode. 
• Check that the system replication status is active and in sync for all services. 
• Enable the full sync option with hdbnsutil -sr_fullsync --enable

The full sync option can be switched on and off using the command:

hdbnsutil -sr_fullsync --enable|--disable

Asynchronous (ASYNC) :
The primary system commits the transaction after sending the log without waiting for a response. Here we have no delay because the data transmission is asynchronous to the transaction in the primary system.

This option provides better performance because it is not necessary to wait for log I/O on the secondary system. Database consistency across all services on the secondary system is guaranteed. However, it is more vulnerable to data loss. Data changes may be lost during takeover.

Replication Mode Change Command :-
hdbnsutil -sr_changemode --mode=sync|syncmem|async

Replication Mode Status check Command :-
hdbnsutil -sr_state --sapcontrol=1

Thanks for reading, Please share your valuable feedback.  

Prerequisites for Configuring SAP HANA System Replication

 SAP Hana 2.0 System Replication Structure 

Hana System Replication Pre-requisite

• Primary & Secondary database must be Installed and configured

• Confirm both systems are up & running independently

• PKI SSFS key and data should be copy from Primary to secondary system

• Both Systems are in same size & configuration

• Both Systems are in same Hana Version

• Both Systems are in same SID & Instance Number

• Both Systems should be installed on different hosts

• Both Systems should be one same network segment

• Initial database backup must be performed on Primary System before replication start (System DB & All Tenant DB)

For DR Configuration, Instead of the above below points also required,

• Both Servers are in different location / Data Centers

• DB System can be with same structure or minimum compared with PRD 

Tools using configure Hana Replication

• hdbnsutil 
• SAP Hana Cockpit
• SAP Hana Studio

Hana 1.0 also having same Replication structure, but Hana Cockpit will not support  till Hana 1.0 SPS 11.

Also Read,

Prerequisites for Configuring SAP HANA System Replication

SAP HANA System Replication setup with hdbnsutil

Thanks for reading, Please share your valuable feedback.  

User Types in SAP

Five Type of users in SAP,  they are

1. Dialog User
2. System User
3. Communication User
4. Service User
5. Reference User

1. Dialog users:

Dialog users are interactive users, this is used to logon SAP System using the SAP GUI. While logon system checks user password has expired or initial, so user can update his password. 

2. System Users: 

It is used to communicate within the system. The system user can not login to SAP GUI and it wont check password details, so only admin can change the password. For example internal RFC Users.

3.Communication Users:

These are non-interactive users. This users used for background processing & communicate between systems. GUI logon not permitted for this type of users. Their passwords are valid for a certain period & it will expire. The users have the option to change their passwords.

4. Service Users: 

This type of users are available to a group of users access. The system doesn’t check the details of password and only admin can change the password. Normally highly restricted authorizations are given to this type of user.

5. Reference users: 

This type of users used for authorization of administration. You are not allowed for login to SAP System with the reference user type.

SAP Kernel executable files with description

 Here is List of SAP executable on SAP systems.

SAPCAR
To uncar compression files

R3ldctl
The tool for exporting all table structures to the file system during an OS/DB-Migration.

R3check
The tool will check Cluster-Tables for errors

R3ta
Split large tables for export and import

R3load
The table import & export tool of SAP during Installation, Upgrade, and Migration.

R3szchk
The tool for determining the sizes of the different tables in the target database during the import in an OS/DB-Migration.

R3trans
his is the tool, that does the real work for tp. tp controls the import and export of changes and r3trans does them using scripts, that were generated from tp.

R3tran_XXX.SAR
It is a compressed archive with the latest version of R3trans from the SAP Service Marketplace, used when we patched the kernel.

SAPEXEDB_XX.SAR
Compressed file containing DB Dependent executables (Kernel Files)

SAPEXE_XX.SAR
Compressed file containing the Database Independent executables (Kernel Files)

sapexec
Call SAP Function Modules

startdb
Program to start the database

startj2eedb
Program to start the database (Java)

startrfc
The tool is a very easy SAP command line interface to start all of the implemented function modules of SAP systems.

startsap
Program to start SAP

stopdb
Program to stop the database

stopj2eedb
Program to stop the database (Java)

stopsap
Program to stop SAP

tp
The Transport Tool. This program coordinates the complete import and export of program and table changes made within the SAP system in order to transport them through the complete System Landscape.

sapmscsa
SCSA Administration

saplicense
The Tool for the installation of a new SAP License. This is needed when the license expires e.g. because of a hardware change.

saposcol
The SAP Interface to the Operating System for Performance Data. The Operating System Collector collects CPU Usage, Disk Performance, Paging etc.

sapparar
Reads the SAP Profile

sappfpar
This tool can be used for checking the profiles after changes and before restarting the SAP system.

saproot.sh
Script to set Root permissions necessary for some kernel programs

saprouter
The program for the Router Connection from customers to SAP and vice versa.

sapsecin
Generation of the PSE (Personal Security Environment)

sapstart
Starts SAP processes

sapstartsrv
Starts SAP processes

cfw
GUI Control Framework for ABAP Objects

cleanipc
Cleans Inter-Process Communications Memory

disp+work
Dispatcher & Workprocess – “The complete Kernel” – Here the complete ABAP is processed

Dpj2ee
Dispatcher for Java

msclients
Shows running instances registered in the Message Server

msg_server
Main Message Server executable

msmon
Message Server Monitor Utility

msprot
Monitor Message Server at the OS level

db2jcllib.o
Rsdb/db2jcl_library parameter

db2radm
Used to configure DB2Connect

dbadaslib.o
Part of lib_dbsl – database-dependent SQL handler

dbdb2pwd
Create an encrypted DB2 Password File

dbdb2slib.o
Part of lib_dbsl – database-dependent SQL handler – DB2

dbsdbslib.o
Part of lib_dbsl – database-dependent SQL handler

dev_sapstart
Log file for starting sap

dipgntab
Activation and adjustment of the nametabs with the ABAP Dictionary.

dpmon
Used to get the process overview of an instance in text mode.

dsrlib.o
Distributed Statistics Records

Dw_gui.o
Dependent module for Disp+work

Dw_mdm.o
Dependent module for Disp+work

Dw_stl.o
Dependent module for Disp+work

Dw_xml.o
Dependent module for Disp+work

Dw_xtc.o
Dependent module for Disp+work

Eg2mon
Monitor program for Extended Global Memory Segments 

Em2mon
Monitor program for Extended Memory management 

emmon
Test program for Extended Memory

enqt
Check and Monitor the Enqueue Lock Table

enrepserver

SAP Enqueue Replication Server

enserver
SAP Enqueue Server

ensmon
Enqueue Server Monitor Programs to monitor the enqueue server and the enqueue replication servers.

Es2mon
Programs to monitor the enqueue server and the enqueue replication servers.

esmon
Program to monitor the enqueue server and the enqueue replication servers.

estst
Test program for the Extended Memory Segments 

evtd
This program is able to trigger events within the SAP system. The tp tool uses this feature. It can be used as the trigger for self-written interfaces as well.

exe_db2.lst

The ‘*.lst’ files are text files used by sapcpe to determine which files to compare/copy on instance startup.

gateway.lst
The ‘*.lst’ files are text files used by sapcpe to determine which files to compare/copy on instance startup.

gw.properties
Gateway processes

gwmon  
Program gwmon (at the operating system level) or SAP transaction SMGW monitors the SAP Gateway.

gwrd
Program gwmon (at the operating system level) or SAP transaction SMGW monitors the SAP Gateway.

icm.properties
Tool to monitor and manage the Internet Communication Manager (ICM) from the SAP System (transaction SMICM).

icmadmin.SAR
Tool to monitor and manage the Internet Communication Manager (ICM) from the SAP System (transaction SMICM).

icman
Tool to monitor and manage the Internet Communication Manager (ICM) from the SAP System (transaction SMICM).

icmbnd
Program to bind ports with numbers from 0 to 1023

icmon
Internet Communication Manager (ICM) used for HTTP(S), SMTP based communication used to monitor and manage the Internet Communication Manager (ICM) from the SAP System (transaction SMICM).

instance.lst
List of database-independent executables. These executables are valid for all database systems used by the SAP system.

instancedb.lst

List of database-dependent executables. These executables can only be used with a particular database system.

ipclimits
Reports IPC memory available to SAP at the OS level

j2eeinst.lst
The ‘*.lst’ files are text files used by sapcpe to determine which files to compare/copy on instance startup.

jcmon
Program to monitor and manage Java processes

jcontrol
Program to control Java processes

jenqulib.jar
Java Enqueue Library

jlaunch
Program starts the Java processes

jlogunzip.jar
Java Classes used to unzip archives (used from the sapstartsrv)

jperflib.jar
J2EE client Jar file

jstartup.jar
Java Startup FrameWork jar file

jstartupapi.jar
J2EE Engine Monitoring API

jstartupimpl.jar
J2EE Monitoring

ldap_rfc
LDAP Connector

ldappasswd
Store LDAP directory user and password

ldapreg
LDAP Registration Service

lgtst
Program to test the message server

libicudata30.a
ICU Common Library – Part of the RFC SDK and are used for RFC connections.

libicui18n30.a
ICU Common Library – Part of the RFC SDK and are used for RFC connections.

libicuuc30.a
ICU Common Library – Part of the RFC SDK and are used for RFC connections.

libjenqulib.o
Part of the RFC SDK and are used for RFC connections.

libjmon.so
JMON Shared Library – Part of the RFC SDK and are used for RFC connections.

libjperflib.so
Part of the RFC SDK and are used for RFC connections.

libregex.o
Part of the RFC SDK and are used for RFC connections

librfcum.o
Dynamic Load Library – Part of the RFC SDK and are used for RFC connections.

libsapcsa.o
CSA Shared Library – Part of the RFC SDK and are used for RFC connections

libsapsecu.o
SECU Shared Library – SAP seculib library used for default encryption. It’s referenced in the j2ee startup logs in the working directory.

libsapu16.so
Part of the RFC SDK and are used for RFC connections

libsapu16_mt.so
Part of the RFC SDK and are used for RFC connections.

mdxsvr

MDX Parser for RFC

memlimits
he program memlimits lets you determine how much swap space is currently available in the host system.

niping
Program to test the SAP network layer and the SAProuter

rfcexec
The tool to start other programs from within SAP (ABAP) on the OS level via the gateway on any other (or the same) server.

rfcexec.sec
The tool to start other programs from within SAP (ABAP) on the OS level via the gateway on any other (or the same) server.

rfcping
Ping the RFC layer

rscparulib.o
 Dynamic shared library with code page converter

rscpf2f
Check installed locales for given list of languages.  

rscpf3f
Find possible system code pages for given list of languages.      

          
rscpf_ars
Test program for code page conversion, language handling, and locales in combination with ‘rscparulib.o’.  (only for support)

rscpf_db
est program for code page conversion, language handling, and locales. This program will connect to the database and also attached to the shared memory of an instance if possible.  (only for support)

rslgcoll
Central System Logging Collector

rslglscs
Show the Syslog specific parts of the shared memory segment ‘SCSA’. 

rslgsend
Central System Logging Sender

rslgview
View SAP Log at the OS level

rstrcscs
Program creates a common memory segment for the SCSA, locates the trace switches block within it and initializes the trace switches block.

rstrfile
R/3 system trace file tool

rstrlscs
The command “rstrcscs r” removes that common memory segment again.

rstrsscs
The command “rstrsscs” allows change to the switch settings in the trace switches block within the SCSA.

rsyn.bin
For each kernel version of the R/3 System, there exists an appropriate file rsyn.bin which contains the ABAP/4 syntax description.  It describes what to do when compiling an ABAP statement 

sapccm4x

CCMS Agent for Abap

sapccmsr
CCMS Agent for Java

sapcontrol
sapcontrol’ is used to stop/start/monitor the sap instances (for example, from the sapmc).

sapcpe
This checks that the local executable are up to date each time an SAP instance that uses local executable is started.

sapcpeft
Parameter file used by sapcpe

sapcpp46.o
Virus Scan Adapter files (Note 964305)

sapdbmrfc
RFC for SAPDB connections

sapevt

This program is able to trigger events within the SAP system. The tp tool uses this feature. It can be used as trigger for self-written interfaces as well.

sapftp
FTP Client, that can be used from within the SAP system (from ABAP) to communicate with other FTP servers.

saphttp
HTTP Client, that can be used from within the SAP system (from ABAP) to communicate with other HTTP servers – e.g. for interfaces.

sapiconv
Program for the conversion of text files

sapkprotp
Relocate a Content Server Repository

sapmanifest.mf
Text file that contains the kernel patch level and is read by the JSPM (Java Support Package Manager).

sapmanifestdb.mf
Text file that contains the database kernel patch level and is read by the JSPM (Java Support Package Manager).

sapuxuserchk
The program xuser is a tool from maxdb which stores the logon information to the DB.  This utility program called by sapcontrol which is a program that uses the web service APIs of the ABAP and Java startup framework to control an instance from the command line.

sapwebdisp
The SAP Web dispatcher is used for load balancing for a setting up an SAP Internet scenario. It is the only application that needs to be located in the DMZ. Everything “behind” this can (and should) be located in your intranet. So, only one port on one IP address needs to be opened to internet and the SAP Web dispatcher can handle the traffic with the different SAP instances.

sapxpg
Program that starts programs on an external host. The tool for starting OS commands from within SAP Systems.

scs.lst
The ‘*.lst’ files are text files used by sapcpe to determine which files to compare/copy on instance startup.

scsclient.lst
The ‘*.lst’ files are text files used by sapcpe to determine which files to compare/copy on instance startup.

semd
A Test Tool used to verify semaphore operations.

servicehttp

The port number where the server should listen for HTTP requests.

shmd

Related to Shared Memory

showipc
Checks shared memory segments

sldreg
SLD registration program

sldreglib.o
SLD registration program

ssfrfc
Secure Store and Forward (SSF)

wdispadmin.SAR
Web Dispatcher Administration Interface archive program

wdispmon
Web Dispatcher Monitor program

webdispinst.lst
Web Dispatcher Administration Interface list

xml63d.o
Virus Scan Adapter files

vscan_rfc
Virus Scan Adapter files 

If i miss any executable's in the list, please leave a comment.

Related Posts :-

Ø SAP Kernel Upgrade

Ø How to find SAP Kernel Version

Thanks for reading, Please share your valuable feedback.