If you get the ORA-04030: ... (kxs-heap-w,KGL Iterator information) error in alert log
and if you see obsoleted parent cursors lying around.
Then you are hitting Bug 12791981 - ORA-4030 due to "KGL Iterator information" .
Look more from MOS (My Oracle Support) document 12791981.8 .
If you are trying to check those obsolete cursors you are probably hitting the same error ORA-04030 and then you know that there are also those obsoleted cursors in the database.
With this SQL you can check those obsoleted cursors:
select sql_id, address, IS_OBSOLETE, count(*) from v$sql where IS_OBSOLETE='Y' group by sql_id, address, IS_OBSOLETE having count(*)>=10;
Or just:
select count(*) from v$sql where IS_OBSOLETE='Y';
You can fix this bug with patch 12791981 .
NOTE! This bug can also be fixed with patch 14799269 (this is more complete fix according to MOS) but it is only available for 11.2.0.3.1 version and newer ones.
The most effective method to Solve Oracle ORA-04030 Error Message through Remote DBA Services
ReplyDeleteThe Oracle Error ORA-04030 underwear that "Out of process memory" The ORA-04030 is a mix-up caused by an inadequacy of RAM on a committed (non-shared server) condition. Generally, the screw up is an "out of process memory" botch, where Oracle can't acquire the RAM anticipated that would complete the undertakings. It can in like manner be caused by too little of a Program Global Area (PGA) and by not setting parameters adequately considerable to allow enough RAM for taking care of. It is a run of the mill botch when running an import as well. The oversight can happen when trying to execute an outside movement or when running a data pump import.
Contact to Online Oracle DB Support and Database Administration for Oracle to fathom this blunder.
For More Info: https://cognegicsystems.com/
Contact Number: 1-800-450-8670
Email Address- info@cognegicsystems.com
Company’s Address- 507 Copper Square Drive Bethel Connecticut (USA) 06801