HP-UX: Memory Corruption Using JAVA Database 8.1.6.2-8.1.7.2
(Doc ID 204292.1)
Last updated on DECEMBER 14, 2023
Applies to:
Oracle Database Cloud Service - Version N/A and laterOracle Database - Enterprise Edition - Version 8.1.6.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
HP-UX PA-RISC (64-bit)
HP-UX PA-RISC (32-bit)
HP 9000 HP-UX 11.0 (32 bit)
Purpose
This note describes some symptoms that may be encountered as a result of hitting HP-UX port specific <Bug 2042715>.
Versions of Oracle Affected
~~~~~~~~~~~~~~~~~~~~~~~~~~~
8.1.X 32 bit
8.1.X 64 bit
The bug is fixed in 9.0.1
Platforms Affected
~~~~~~~~~~~~~~~~~~
HP-UX 11.00 and 11i - 32 bit
HP-UX 11.00 and 11i - 64 bit
Heavy use of Java on the server can cause PGA memory corruption leading to a variety of problems like ORA-600 or ORA-7445 errors or spinning processes. Specifically, two or more JVM threads can end up sharing the same stack, which is illegal.
Unfortunately, due to the nature of the memory corruption, it is not possible to characterize the problem into a small set of easily identifiable symptoms.
Likelihood of Occurrence
~~~~~~~~~~~~~~~~~~~~~~~~
Whenever heavy use of JVM is made on the database.
Scope
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |