GES Processes

In RAC environments, GES process structures are used to record details about local and remote processes with an interest in global locks.

There must be one GES process for each process in each instance in the cluster. Therefore there will be more GES process structures in each instance than KSUPR (process) structures.

I think that the abbreviation for GES processes is kjp

In the SGA there are two main GES process structures:

• ges process array
• ges process hash table

In Oracle 10.2.0.1 (32-bit Linux) the ges process array occupies 256000 bytes

• Each element is 800 bytes in length.
• The number of elements is defined by the _LM_PROCS initialization parameter
• The default value for _LM_PROCS is 320 (where PROCESSES = 150)

In Oracle 10.2.01 (32-bit Linux) the ges process hash table occupies 8640 bytes

GES process structures are covered by three latches:

In Oracle 10.2.0.1 (32-bit Linux) :

• The ges process table freelist does not have any children
• The ges process parent latch has one child for each GES process
• The ges process hash list does not have any children

Static kjp structures are also allocated for

• kjplmon_
• kjppmon_

A list of addresses of kjp structures can be obtained using

SQL> ORADEBUG LKDEBUG -a proc

For example

You can dump detailed information for each GES process using

SQL> ORADEBUG LKDEBUG -A proc

This command produces output in the following format for each GES process.

Possible values for the process state are probably KJP_NORMAL, KJP_FREEZE and KJP_UNFREEZE

The GES process structures also appear in the SYSTEMSTATE (level 10) dump:

SQL> ALTER SESSION SET EVENTS 'IMMEDIATE TRACE NAME SYSTEMSTATE LEVEL 10';