Skip to Main Content

SQL Developer

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

SQL Developer - High usage of memory !

Intel_024Aug 5 2013 — edited Nov 8 2013

Hello All,

I have downloaded SQL Developer 4 today and when i started working on it, my computer memory started to IRK a lot. So when i checked in "Task Manager", i found something very strange.

The memory consumption was too high (almost 350 MB). Can someone tell me why is this version of SQL Developer is using such as huge amount of memory or is there some workaround for this issue.

I tried to attach the screenshot but that did not happen.

Any help is greatly appreciated.

Thanks in advance,

Aravind S

Comments

User_H3J7U

The queue triggered event job only when the enqueue occurs. Moreover, if a new enqueue occurs during the job execution, the scheduler will skip that event.
Simplest way is to start a single non-event job with a continuous dequeuing. Or enable multiple event job instances and dequeue all messages on startup. The third option is to register the pl/sql callback, but you still need to read messages on startup. Pl/sql callback is starting up to 20 processes on simultaneous enqueue.

murali rishna

i enable this one as well, still ,it is not working.
DBMS_SCHEDULER.SET_ATTRIBUTE('<<jobname>>','parallel_instances',TRUE);
As per your comment " enable multiple event job instances and dequeue all messages on startup. "
do you have sample,please share it?

User_H3J7U

Parallel_instances is needed to solve this problem_:_
Note:
The Scheduler runs the event-based job for each occurrence of an event that matches event_condition. However, by default, events that occur while the job is already running are ignored; the event gets consumed, but does not trigger another run of the job. Beginning in Oracle Database 11g Release 1 (11.1), you can change this default behavior by setting the job attribute PARALLEL_INSTANCES to TRUE. In this case, an instance of the job is started for every instance of the event, and all job instances are lightweight jobs. See the SET_ATTRIBUTE procedure in Oracle Database PL/SQL Packages and Types Reference for details.
How to dequeue messages from queue, you can find in the documentation Advanced Queuing User's Guide (pl/sql). See also Administrators Guide about event based jobs.

murali rishna

i tried with parallel instance,it is not working.still event are the in que table.

1 - 4
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Dec 6 2013
Added on Aug 5 2013
3 comments
768 views