Solution : https://service.sap.com/sap/support/notes/403004 (SAP Service marketplace login required)
Summary :
SAP Note describes an issue where the system startup via 'startsap' leads to erroneous reports of database startup failure, despite successful database activation. The root cause is the R3trans tool’s inability to connect to the Oracle database, resulting in return code 12. Various potential issues include incorrect OPS$ user configuration, shared library issues, or improper environment settings. To diagnose, users should execute 'R3trans -x' and review the trans.log. Solutions might involve adjusting shared libraries or environment settings, and consulting respective SAP Notes for error specifics detailed in the trans.log.
Key words :
customer component bc-db-ora oracle priority recommendations / additional info category, load library '/usr/sap/km3/sys/exe/run/dboraslib, load /usr/sap/<sid>/sys/exe/run/dboraslib, dir_library '/usr/sap/<sid>/sys/exe/run', /usr/sap/<sid>/sys/exe/run/startdb, attributes database system oracle header data released, shared libraries incorrectly set environment problems, database failed notify database administrator, error => oci-call 'olog' failed, incorrectly configured ops$ user problems
Related Notes :
| 400241 | Problems with ops$ or sapr3 connect to Oracle |
| 361641 | Creating OPS$ users on UNIX |
| 180430 | Installing the ORACLE client software for UNIX |
| 34479 | Collective note for problems with SQL-Net V2 ORACLE |