Check sessions and processes limits in Oracle

Oracle database has a gv$resource_limit view to check if any database resource reach his connection limit:
set linesize 190
set pages 200
select * from gv$resource_limit;

    INST_ID RESOURCE_NAME                  CURRENT_UTILIZATION MAX_UTILIZATION INITIAL_ALLOCAT LIMIT_VALUE
---------- ------------------------------ ------------------- --------------- --------------- ------------
         1 processes                                       44             300        300             300
         1 sessions                                        52             215        512             512
         1 enqueue_locks                                   30             295       6480            6480
         1 enqueue_resources                               24             165       2472       UNLIMITED
         1 ges_procs                                        0               0          0               0
         1 ges_ress                                         0               0          0       UNLIMITED
         1 ges_locks                                        0               0          0       UNLIMITED
         1 ges_cache_ress                                   0               0          0       UNLIMITED
         1 ges_reg_msgs                                     0               0          0       UNLIMITED
         1 ges_big_msgs                                     0               0          0       UNLIMITED
         1 ges_rsv_msgs                                     0               0          0               0
         1 gcs_resources                                    0               0  UNLIMITED       UNLIMITED
         1 gcs_shadows                                      0               0  UNLIMITED       UNLIMITED
         1 smartio_overhead_memory                          0           71704          0       UNLIMITED
         1 smartio_buffer_memory                            0               0          0       UNLIMITED
         1 smartio_metadata_memory                          0               0          0       UNLIMITED
         1 smartio_sessions                                 0               1          0       UNLIMITED
         1 dml_locks                                        1              29       2252       UNLIMITED
         1 temporary_table_locks                            0              28  UNLIMITED       UNLIMITED
         1 transactions                                     1               7        563       UNLIMITED
         1 branches                                         0               0        563       UNLIMITED
         1 cmtcallbk                                        0               3        563       UNLIMITED
         1 max_rollback_segments                           11              11        563           65535
         1 sort_segment_locks                               1              12  UNLIMITED       UNLIMITED
         1 k2q_locks                                        0               0       1024       UNLIMITED
         1 max_shared_servers                               1               1  UNLIMITED       UNLIMITED
         1 parallel_max_servers                             0               0        270            3600
This info is, as all v$ views, from instance startup to current time. So, in this example we can say that max processes limit was reached, and just now there are only 44 processes running. v$resource_limit is a very useful view for day-to-day work because you can glance in a moment if there is or were some process reaching his limit

If you check sessions, processes or another parameter and they are nearly or reaching their limits you can resize them by following this article: change parameters in Oracle
Please note that if you set processes value, oracle will automatically set sessions value to (1.1 * PROCESSES) + 5 for oracle 10g and (1.5 * PROCESSES) + 22 in oracle 11g and above...(for previous versions you should set both parameter accordingly)

And finally, you can obtain detailed and historical info with Oracle Historical Session Information

Comments

Post a Comment

Popular posts from this blog

Oracle Historical Session Information with ASH >10g

Purging and archiving Oracle alert.log and listener.log