Solution : https://service.sap.com/sap/support/notes/131561 (SAP Service marketplace login required)
Summary :
When initiating multiple R/3 instances, some work processes fail due to various Oracle-related connection errors such as ORA-01034 and ORA-12500. These issues primarily occur because the listener handling database connections becomes overburdened when a significant number of work processes simultaneously request connections, exceeding the configured queue size. The recommended solutions involve adjusting the queue size in the listener configuration, proactive shadow process creation on UNIX systems, deactivating Oracle tracing, modifying OS parameters, and staggering the startup of SAP instances. Adjustments to the `listener.ora` file and possible OS level tweaks are detailed to curb these connection errors effectively.
Key words :
sql error '12203' fatal ni connect error 12203 datenbankfehler 12203 beim con aufgetreten sql error 12203 performing conthe abended work processes, terms tns-12203 tns-12547 tns-12540 tns-12500 tns-12535 tns-12541 otrace reason, sql-net v2, internal limit restriction exceededora-12541, error messages mentioned, operating system side restrictions, dedicated server processyou receive, false operating system parameterization, small time offset solution 1, error messages
Related Notes :
| 609332 | Composite note: ORA-12541/ORA-12224 |
| 513524 | Composite ORA-12540 SAP note |
| 505630 | Composite SAP Note ORA-12547 |
| 445029 | ORA-12203 composite SAP note |
| 437362 | Composite note ORA-12500 |
| 381105 | ORA-12203 / ORA-12535 when starting the R/3 work processes |
| 356370 | Kernel parameters for HP Tru64 UNIX 5.x |
| 92537 | Oracle trace is automatically active |
| 34479 | Collective note for problems with SQL-Net V2 ORACLE |