Skip to main content

Metrics Process Limit Usage percentage (%) is critical or warning in OEM or Cloud Control 12c or Cloud Control 13c

Please run the below queries to trace details during Metric alert "Process Limit % is >= 75" in OEM or Cloud Control 12c or Cloud Control 13c
To check the Metrics Process Limit Usage (%):
*****************************************************

 set lines 300
col INITIAL_ALLOCATION for a17
col LIMIT_VALUE for a12
select resource_name,current_utilization,max_utilization,
INITIAL_ALLOCATION,LIMIT_VALUE,((current_utilization*100)/(INITIAL_ALLOCATION)) as "Process limit %"
from v$resource_limit
where resource_name in ('processes');
The below query will give you all connected sessions (ACTIVE and INACTIVE) to instance:
*******************************************************************************************************
set pages 100
set lines 1000
col SPID heading 'PID' for a06
col SID for 99999
col SERIAL# heading 'serial' for 999999
col SQL_ID for a14
col USERNAME for a10
col PROGRAM for a20
col MODULE for a18
col OSUSER for a07
col MACHINE for a20
select p.spid,s.sid,s.serial#,s.sql_id,s.username,s.status,s.program,s.module,s.osuser,s.machine,s.event
from v$session s, v$process p where s.paddr=p.addr;
The below query will give you the sessions connected from particular machine :
******************************************************************************************
set pages 100
set lines 1000
col SPID heading 'PID' for a06
col SID for 9999
col SERIAL# heading 'serial' for 999999
col SQL_ID for a14
col USERNAME for a13
col PROGRAM for a16
col MODULE for a16
col OSUSER for a08
col MACHINE for a24
col EVENT for a27
select p.spid,s.sid,s.serial#,s.sql_id,s.username,s.status,s.program,s.module,s.osuser,s.machine,s.event
from v$session s, v$process p where s.paddr=p.addr and s.machine like '&MACHINE'
and s.status in('&status');
The above query will ask you to enter the status (type INACTIVE and press ENTER);
*************************************************************************************************

 Enter value for status: INACTIVE

 To run the previous query again for Active sessions, type the below
****************************************************************************

 SYS@OPRP1 > /

 Then it will ask you to enter the status (type ACTIVE and press ENTER):
**********************************************************************************

 Enter value for status: ACTIVE
The below query will give you count of sessions connected from each machine:
******************************************************************************************
set lines 500
set pages 1000
col MACHINE for a35
col OSUSER for a15
col USERNAME for a19
break on report
compute sum of count(*) on report
select s.machine,s.status,s.osuser,s.username,s.SQL_ID,count(*)
from v$session s, v$process p where s.paddr=p.addr
group by s.machine,s.status,s.osuser,s.username,s.SQL_ID
order by 6 desc;

Comments

Post a Comment

Popular posts from this blog

Export and import multiple schema using expdp/impdp (Data Pump utility)

Use the below sql query to export and import multiple schema: expdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp exclude=statistics logfile=expdpschemas120514.log impdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp logfile=impdpschemas120514.log sql query to export and import a schema: expdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp exclude=statistics logfile=expdpschema120514.log impdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp logfile=expdpschema120514.log Parameter STATISTICS=NONE can either be used in export or import. No need to use the parameter in both. To export meta data only to get ddl of the schemas: expdp schemas=schema1,schema2,schema3 directory=TEST_DIR dumpfile=content.dat content=METADATA_ONLY exclude=statistics To get the DDL in a text file: impdp directory=TEST_DIR sqlfile=sql.dat logfile=sql.log dumpfil...
3 comments
Read more

Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan

Deal all, Below post content is not my own. It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Hence we had implemented the same mentioned in the title "Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan". Introduction The "cost-based optimizer (CBO or just optimizer) is the part of database software that determines the most efficient means of accessing the specified data (or at least what it "calculates" as the most efficient). The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints. Some changes in those conditions may affect the calculations of the plan...
9 comments
Read more

SQL query to find the cause or reason for more archive log generation

Finding reason or cause for heavy or more archive log generation in a particular time period As i said in the previous post we are going to see SQL queries to find the cause or reason for more archive log generation in a problematic window... Sometimes customer would ask the sql query which generated more archive logs sometimes before or days before (not for current archive logs generation which is described in the previous post). In such scenarios, follow the steps below. Step 1: ====== First you must know the timing when more number of archive logs generated in the databases. for that you can use the below query. Below sql query gives how many number of archive logs generated for each and every hour... col day for a12 set lines 1000 set pages 999 col "00" for a3 col "01" for a3 col "02" for a3 col "03" for a3 col "04" for a3 col "05" for a3 col "06" for a3 col "07" for...
1 comment
Read more