The size of the instance lock database is largely dependent on the lm_ress and lm_locks parameter settings. Changes in gc_files_to_locks do not affect the size of the instance lock database. If the instance lock database is too small it will be dynamically expanded using shared pool memory.
You're right, sorry about that. It works!
Area #4 `Lock Manager' containing Subareas 0-0
Total size 000000000054e000 Minimum Subarea size 00000000
Area Subarea Shmid Stable Addr Actual Addr
4 0 8014 00000000e48e5000 00000000e48e5000
Subarea size Segment size
000000000054e000 0000000000b37000
By the way, can I identify the "Subarea size" as the memory used by Lock Manager? And this number includes all IDLM strutures? Everytime I increase
the PCM locks over a datafile, does it affect directly this Subarea or
depend on PCM Locks dynamic utilization?
What's that ";" doing on the end of the command? You can get away with that sort of thing in SQL*Plus, but not in svrmgrl.
Many thanks for your reply. The problem is svrmgrl doesn't seem to understand the command. Please see bellow:
SVRMGR> connect internal Connected. SVRMGR> oradebug ipc; ORA-00070: command ipc SVRMGR>
Did you look in the trace file for the process in user_dump_dest? That's where the information goes.
I am running a OPS 8.0.6 environment on HP-UX N4000 machine(HP-UX 11 64bits). I would like to evaluate the amount of memory took to implent OPS locking instance strutures to do a better planning. I tried to issue from svrmgrl the command ORADEBUG IPC, it doesn't work at all, is there any other way to measure these strutures?