After Login Incremented Allocated Memory

[MarioHeredia]

Hi, I have a question.

The following occurs. After the logging tool to. Without ever opening SQL Window. The memory of that user grows and grows and grows ... I make a Log Off and nothing, continue growing.
Only closed of tool, the memory is freed.
Is a parameter? Is a option? Please Help Me. Thanks. Mario.

 

[Marco Kalter]

I tested this. Each SQL Window adds about 100KB. When it is closed the 100KB are released again. What values do you measure, and how do you measure them?

 

[MarioHeredia]

Hi, Marco.
Thanks for your answer and your time.

The pga_alloc_mem field is increasing. In 5 minutes, I can have 20Mbytes or more.
Only the login, not opening any windows, it happens.
when you look at the v$sessions view, there are two sessions: one active and other inactive. The inactive not grow but the active is permanently growing .. the event handling is "db sequential read".
Then, without a window is running a query in the background. As the query does not end resources continues to take ... the point is that it does not end.
It's very, very strange.
The user only has permissions to CREATE SESSION.

Do you think?
BR,
Mario.

 

[MarioHeredia]

Marco,
One thing more ....

I thought about the event, "db sequential read" event ... I try SELECT ANY DICTIONARY giving permission to the user.

And ... stop growing.
Then, because the tool need this information?
I cant grant this privilege at users.

BR,
Mario.

 

[MarioHeredia]

Hi Guys,

I can't solution this problem yet.
I really need any comment about this problem.

The end user may not have this privilege "SELECT ANY DICTIONARY" for solution of "PLSQL Developer Problem".

Thanks.
BR,
Mario.

 

[IvanZ]

PLD selects across sys.dba_* views if it can (and setting Use DBA Views is set), otherwise it uses - sys.all_* views.

If you are a DBA the question you should ask - whats wrong with the query and its execution using sys.all_* against query with sys.dba_* views.

 

[Hilarion]

The amount of connected sessions of PL/SQL Developer in Oracle depends on the "Session Mode" preference of PL/SQL Developer (one session in "Single session" mode, two sessions in "Dual session" mode and separate sessions for most of PL/SQL Developer windows and for object browser in "Multi session" mode).
If you are looking at v$sessions using PL/SQL Developer, then you'll always see at least one session active - it will be the session that PL/SQL Developer is using to retrieve the v$session data.
In "Multi session" mode, if you are querying the v$sessions using "SQL Window" of PL/SQL Developer (and not the "Sessions..." tool), then the memory use for that session will depend almost only on what queries you executed in that specific "SQL Window" before querying the v$sessions (and including that particular query too). As far as I know, in this mode, even triggering Code Assistant in that specific "SQL Window" will not use that window's session, so should not affect it's memory use.

Regardless of what I wrote above, you are referring to memory usage of Oracle server, not the PL/SQL Developer application, so if there's something wrong, then you should probably ask your Oracle DB server administrator for help in diagnosing if this level of memory use is something you should worry about or not, and if yes, then what may be causing that (including showing you what specific actions/queries cause that effect).