Skip to content

ORA-00020 Reported When GES_PROCS Used Up

SYMPTOMS

ORA-20 Occurred when current process number is still far from parameter processes setting, and ges_procs used up in v$resource_limit

select * from v$resource_limit;

RESOURCE_NAME CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_ALLOCATION LIMIT_VALUE
—————————— ——————- ————— ——————– ——————–
processes 19766 20472 30000 30000 <============= max utilization of processes is only 20472, which is far from the max limit of 30000
sessions 19795 20499 45072 45072 <===========
enqueue_locks 21128 21234 515026 515026
enqueue_resources 1652 2169 201336 UNLIMITED
ges_procs 19761 19761 19761 19761 <================= ges_procs is used up
ges_ress 370233 1000559 799194 UNLIMITED

CAUSE

The same issue is investigated in

Bug 20734725 – ORA-20 ERROR REPORTED DUE TO GES_PROCS USED UP.

Which is closed as “Not a bug” but a configuration issue – _ksmg_granule_size is set too low, in this case granule size should be 512M, however it is currently set to 32MB manually.

SOLUTION

Set a larger _ksmg_granule_size, eg 512MB when SGA_MAX_SIZE (or memory_max_target) is larger than 128GB.

SQL> alter system set “_ksmg_granule_size”=536870912 scope=spfile;

restart database is needed.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: