Solution : https://service.sap.com/sap/support/notes/809477 (SAP Service marketplace login required)
Summary :
SAP note addresses issues with the startsap and stopsap scripts failing due to various configuration and environment-related errors. Key problems include incorrect DBNAME parameter settings, command path access errors, and unresponsive scripts after system updates. The solution provides comprehensive steps for obtaining updated script versions from the SAP service marketplace, emphasizing the importance of backing up old scripts, ensuring proper file permissions, and adhering to platform-specific configurations. Since SAP release 701, the functionality of the start and stop processes has been merged into a single script, streamlining operations and reducing manual handling.
Key words :
output starting sap-collector demon ---- start, cd <exe-dir>cp startsap stopsap, cd <exe-dir>cp startsap stopsap 6, /server0/bin/ext/antlr/antlr, cat /proc/sys/kernel/shmmax, startsap command starts sap instances, chtag -tvc iso8859-1 <file, transaction - check transport tool, startsap/stopsap function get_jdb_sid, check java database connect
Related Notes :
| 1446465 | Instance started with the incorrect instance profile |
| 1304480 | CCMS agent and kernel: patches 2009 |
| 1273591 | Installation Enhancement Package 2 for NetWeaver 700 |
| 1257757 | startsap: "start of saposcol failed" after kernel patch |