Solution : https://service.sap.com/sap/support/notes/123366 (Connexion à SAP Service Marketplace requise)
Mots Clés :
oracle release hardware hardware release max, incorrect operating system settings, oracle shared global area, internal operating system parameters, current dec kernel parameterization, entire allocated shared memory, oracle allocates shared memory, oracle allocates 2 segments, operating system maximum, allocated shared memory
Notes associées :
| 606395 | FAQ: Oracle Limitations |
| 217543 | Oracle does not start with an SGA larger than 8GB |
| 217505 | Tru64 kernel parameters for R/3 for Tru64 4.x |
| 159989 | Oracle SGA for Reliant (32-bit) larger than 1.3 GB |
| 146528 | Configuration of R/3 on hosts with much RAM |
| 142019 | 3GB Memory and Oracle 8 on Windows (NT or 2000) |
| 130140 | ORA-4030 on NT, out of process memory |
| 106525 | Oracle processes terminates with memory problems |
| 105429 | EXTSHM on IBM AIX |
| 103747 | Performance: Parameter recommendations as of Release 4.0 |
| 103374 | ORA-00600 [SKGMINVALID]/ORA-00600 [SKGMBUSY] |
| 99834 | Additions to upgrade from Rel. 2.2x to 4.0B |
| 92052 | Current Oracle patch set for version 7.3.3 |
| 84937 | ORA-7310 on HP-UX and Oracle 7.3.3 for SGA > 1 GB |
| 66575 | Increasing SGA limits in UNIX -special info for SUN |
| 50434 | SGABEG on SUN Solaris with Oracle 7.x and 8.0.x |