What do the v$resource_limit numbers look like
on the other node ?
Is there any other way that the bad node could
have become the master for all the dictionary
cache information ? Does one node start up
a few minutes before the other ? Is there
anything that makes one node the preferred
not for
Jonathon,
Currently we do not pin anything in the shared pool. Still nothing from
Oracle on this yet.
Thank you,
Paul Sherman
DBAElcom, Inc.
voice - 781-501-4143 (direct #)
fax- 781-278-8341 (secure)
email - [EMAIL PROTECTED]
-Original Message-
Sent: Thursday, May 02, 2002 7
That certainly sounds like the solution to the immediate
problem. (Mind you, those initial numbers look like
generated values, not manual settings).
However, it doesn't answer the question of why
one of the machines has the problem.
Do you think it;s possible that lots of material
gets loaded
Bryan, There have been issues with this hanging
problem with OPS in some releases. I am not sure if
this is the problem, but applications that heavily use
the rowcache in an OPS environment can have
performance problems if the shared_pool is loaded and
cause sudden hangs when the row cache object
Check out the following two values:
Resource Current MaxInitial Limit
Name Utilization UtilizationAllocation Value
---- ----
lm_ress252143 256732 177599 UNLIMI
V$RESOURCE_LIMIT not V$RESOURCE...
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, May 02, 2002 3:37 PM
> Here is the results of looking at the v$resource table for the node with
the
> issue.
>
> select * from v$resource;
>
> ADDR
Hmmm,
Not v$resource but v$resource_limit ..
Anjo
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, May 02, 2002 11:37 PM
> Here is the results of looking at the v$resource table for the node with
the
> issue.
>
> select * from
Here is the results from v$resource limit on the node with the problem.
RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION
INITIAL_AL LIMIT_VALU
-- --- ---
-- --
processes
Here is the results of looking at the v$resource table for the node with the
issue.
select * from v$resource;
ADDR TYID1ID2
-- -- --
D4F7C2F8 TS 3 692077582
D4F7C340 TS 38 268439158
D4F7C388 RT 2 0
D4F7C3D0 PI
Trivial checks that you've probably gone through,
but are there messages for
Dynamic resource allocation
Dynamic lock allocation
in the alert log.
Are you using partitioned views
Do you see lots of waits for "DFS Lock handle"
on the instance that isn't having the memory
problem
Jonat
What does V$RESOURCE_LIMIT say? You can probably post that as a reply...
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, May 02, 2002 2:27 PM
> No messages in the alert log about dynamic lock allocation, the node that
is
> having the
No messages in the alert log about dynamic lock allocation, the node that is
having the issue has a small load on it right now and the memory is still
being used up.
Thanks
-Original Message-
Sent: Thursday, May 02, 2002 3:29 PM
To: Multiple recipients of list ORACLE-L
Any messages in
Any messages in the alert file, like dynamic lock allocation or resource
allocation ?
In Oracle8 locks and resources for OPS are dynamically allocated from the
shared pool after the initial values of _LM* are used.
You can monitor that in v$resource_limit.
Anjo.
- Original Message -
To:
13 matches
Mail list logo