I have 400 concurrent users killing JD Edwards with batch and interactive jobs, but I’m chewing through the processes on oracle, so much so that I need to augment the count again and again.
select 'processes utilization from v$resource_limit', current_utilization, 'max' || max_utilization
from v$resource_limit where resource_name = 'processes';
select 'sessions utilization from v$resource_limit', current_utilization, 'max' || max_utilization
from v$resource_limit where resource_name = 'sessions';
Above I put sessions and processes, as they go hand in hand.
The above SQL will show you your maximum processes and also sessions, which is great.
I thought that I’d also show you the lifecycle of the change that you need to make. Who say’s CNC’s don’t make great DBAs!
alter system set processes=950 scope=spfile;
System altered.
SQL> shutdown abort
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 16702308352 bytes
Fixed Size 2238128 bytes
Variable Size 3489663312 bytes
Database Buffers 13186891776 bytes
Redo Buffers 23515136 bytes
Database mounted.
Database opened.
SQL> show parameter process
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
aq_tm_processes integer 1
cell_offload_processing boolean TRUE
db_writer_processes integer 1
gcs_server_processes integer 0
global_txn_processes integer 1
job_queue_processes integer 20
log_archive_max_processes integer 4
processes integer 850
processor_group_name string ****
SQL> quit
Disconnected
</PRE>
No comments:
Post a Comment