Solution : https://service.sap.com/sap/support/notes/12715 (SAP Service marketplace login required)
Summary :
The SAP Note describes issues related to the SCSA (Shared Common System Area), a small shared memory segment accessed by all SAP programs. Issues include SysLog messages appearing in stderr files instead of the SysLog in Transaction SM21, inability to activate traces in Transactions ST01/ST05 due to a missing "SCSA.SWB", various stderr messages indicating invalid arguments or no space on devices, discrepancies in the settings and versions of the SCSA, and error messages during R/3 shutdown. The note also discusses root causes such as insufficient system resources, poor R/3 installation/configuration, ownership conflicts, and incorrect application settings.
Key words :
scsa/shm/file scsa/shm/key scsa/shm/size scsa/shm/start scsa/autocreate, cd /usr/sap/c11/sys/exe/run ls -, shared memorym 22 0x0382be84 --rw-rw-rw h21adm sapsys, manche kommandos untersuchen auch die environmentvariable 'sapsystem', called '/usr/sap/c11/sys/exe/run/', semaphores 21 0x0382bee4 --ra-ra-ra h21adm sapsys, disp+work dwora rslgsend rslgcoll sapmscsa, /usr/sap/c11/dbvmsg00/work/, - sap command cleanipc <instance number> remove, sap command cleanipc <instance number> remove
Related Notes :
173743 | |
45580 | How are syslog files deleted? |
25099 | Activate SQL trace |