Init parameterProcesses & sessions

SESSIONS

What it controls

The most sessions the instance allows.

Know this before you change it

Usually best left to derive from PROCESSES. Raise it only if you use shared servers or recursive sessions heavily.

Default: 1.5 × PROCESSES + 22

Check and change it

1-- Current value on every instance2SELECT inst_id, name, value, isdefault, ismodified3FROM gv$parameter4WHERE name = 'sessions';5 6-- Value stored in the spfile7SELECT sid, value FROM v$spparameter WHERE name = 'sessions' AND isspecified = 'TRUE';8 9-- Static: saved in the spfile, takes effect after a restart10ALTER SYSTEM SET sessions = 2272 SCOPE = SPFILE SID = '*';11 12-- Remove it from the spfile to go back to the default at the next restart13ALTER SYSTEM RESET sessions SCOPE = SPFILE SID = '*';

Related scripts

• Processes and sessions against their limitsCurrent and peak usage of processes, sessions and transactions since startup. A PEAK % near 100 means the next connection storm will hit ORA-00020.

Open in the parameter referenceOracle's reference

More in Processes & sessions

• PROCESSESThe most operating system processes that can connect to the instance, including background processes.
• OPEN_CURSORSThe most cursors one session can have open at once.
• SESSION_CACHED_CURSORSHow many closed cursors each session keeps cached, which saves repeated soft parses.
• JOB_QUEUE_PROCESSESThe most job slave processes for Scheduler and DBMS_JOB jobs.
• RESOURCE_LIMITWhether profile resource limits such as idle time and CPU per call are enforced.
• DDL_LOCK_TIMEOUTSeconds a DDL statement waits for a lock before failing with ORA-00054.