SQL Developer hits Java GC limit while exporting

Hello everybody, I do live!  I may have taken a week off post wedding and honeymoon, but I am back now and tonight I ease into things with a rather simple issue from My Oracle Support article "GC Overhead Limit Exceeded Message In SQL Developer When Running A Query" via note ID 1634930.1 which has a deceiving title because this happens when exporting instead, but is still worth a read anyways.

Configuring notifications in OEM Grid Control

Hot on the heels of my article the other day, about opatch not applying to a RAC instance correctly, is another DBA focused document but there is a reason for that!  How do we get better at Support?  Learning about the system, and what tools are available to help us be more proactive are some great ways to advance your skills!  The document "How To Configure Notification Rules in Enterprise Manager Grid Control" located in My Oracle Support via note ID 429422.1 fits in both of those buckets!  Not only do we learn about OEM, but we learn what is important from Oracle's perspective to monitor about our systems!

Learn more about JVMs by tuning with JVM Diagnostics

I think we have all been there.  Garbage Collection (GC) for Java Virtual Machines are chewing up your server processing power and once they are done with the server they need to be rebooted.  Instead of a perpetual "throw memory at it" type of solution, take a gander at this post from Oracle.  Were you aware that the JVMD (Java Virtual Machine Diagnostics) tool was part of Oracle Enterprise Manager which is licensed with several other Management Packs?  Is this already in your environment, licensed, and just sitting there gathering dust?  What if you cannot use the tool?  Read the post anyways, and learn about things like "Eden space" or different algorithms to use for your GC!