Thanks. We applied the Oct 2020 RU, so I guess it should have got included,
but checking...
On Sat, 5 Dec 2020 at 00:37, Laurentiu Oprea <laurentiu.oprea06@xxxxxxxxx>
wrote:
Did you check if you hit Bug 17871069?
În vin., 4 dec. 2020 la 19:36, Stefan Koehler <contact@xxxxxxxx> a scris:
Hello Purav,
„kxs-heap-p“ is just the (sub-)heap. What are the allocated chunks about
inside this (sub-)heap?
As you mentioned you are running on Solaris, you can use a DTrace script
of mine to identify the code path that allocates these memory chunks:
http://soocs.de/public/scripts/dtrace_kghal_pga_code
Hope this helps.
Best Regards
Stefan Koehler
Independent Oracle performance consultant and researcher
Website: http://www.soocs.de
Twitter: @OracleSK
Purav Chovatia <puravc@xxxxxxxxx> hat am 04.12.2020 17:01 geschrieben:from a Standalone Java App which uses the Thin driver.
Hello Experts,
Need some help desperately.
We have an application that is doing a StoredProc call and a SQL call
Primary Key.
The StoredProc does an UPDATE with a WHERE clause on the single column
If the SQL%ROWCOUNT=0 then it will do an INSERT.Key.
The SQL does a select on the table with a WHERE clause on the Primary
thing that stands out is that the table has 100+ columns.
No joins. No CLOB/BLOB/LOB. No XML. Prepared Statements used. Only
decreasing.
PGA goes on increasing and hence free memory on DB server goes on
server on Linux as well on Solaris.
Problem originally started with ojdbc7.jar from 12.1.0.1.
We tried the ojdbc7.jar from 12.1.0.2 and the problem worsens.
Problem persists with ojdbc6.jar from 11.2.
With ojdbc6.jar problem does not reproduce.
Problem persists with DB 11.2.0.4, 12.1.0.2. Problem persists on DB
or on DB side except ORA-04036 in case of 12c because it will cap PGA with
On DB server, we dont see any open cursor problem. No error on App side
pga_aggregate_limit.
We dug on PGA front and identified that subheap kxs-heap-pis where thememory is used. But cannot understand what does that mean?
subheap! Developers are ready to fix the issue but they have been
Would appreciate any ideas.
It was a shock to realize that there is no way beyond identifying the
requesting to tell what is to be fixed. Is there no way to identify what is
eating up the PGA?
--
Thank you.
//www.freelists.org/webpage/oracle-l