[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | Oracle |
Notice: | For product status see topics: UNIX 1008, OpenVMS 1009, NT 1010 |
Moderator: | EPS::VANDENHEUVEL |
|
Created: | Fri Aug 10 1990 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1574 |
Total number of notes: | 4428 |
1511.0. "Distributed Lock Manager (DLM) limits & usage (VMS" by ALCALA::BURGOS (Luis Burgos. NSC Spain.) Mon Feb 10 1997 13:15
There is a customer with a single maxed-out 8400 with 10 CPU's running an
Oracle-based application, which keeps 100% CPU usage most of the day.
They are planning to move the aplication to a dual system using Oracle
Paralel Server software. And I have been requested to look into the
"Distributed Lock Manager", which apparently the OPS software uses,
limits and usage, and weather to use dinamic locks or not.
Apparently they have run previously into some sort of "Max. Number of
Process/Working Set Size" VMS limit,so that only half of their 6 GB
memory it's actually been used. And they want to make sure they don't
find any surprises in the planned migration.
At this moment they are using VMS 6.2, but they are about to move to 7.1
as soon as they can make Oracle run properly on it (apparently they are
hitting some sort of 450 MB max SAG area Oracle limit),
I have been looking into the VMS documentation but I don't seem to be
able to find any "Distributed Lock Manager" limits or guidelines
documentation. Could you please provide me or point me to where find such
information.
Thanks in advance.
Luis Burgos.
PD.- Cross-posted in Oracle notesfile.
T.R | Title | User | Personal Name | Date | Lines
|
---|