Thursday, 1 February 2018

Performance issue ,

what do you check from performance wise.?

if you understand clearly OS watcher and TFA clearly , you find most of the performance details.



here is a link :

TFaa- https://support.oracle.com/epmos/faces/DocContentDisplay?_afrLoop=574621158717715&parent=OSwatcher&sourceId=download&id=1513912.1&_afrWindowMode=0&_adf.ctrl-state=9z0rzmbu9_173

oswatcer : https://support.oracle.com/epmos/faces/DocumentDisplay?_afrLoop=574953915811780&parent=DOCUMENT&sourceId=301137.1&id=1531223.1&_afrWindowMode=0&_adf.ctrl-state=9z0rzmbu9_202
-------------------


First check how many inactive session are present , check fragmentation details , blocking sessions. stale statistics , index usable or unsable.

check listeners logs if there is any client time out issues.

/var/adm/syslog/syslog.log - For RAC issue , need to check syslogs.

check  application cpu, memeory etc..
(Did you check the listener log at the time the client was having time out issues?)

check if any tables or indexes in stale status , static details in Last Analyesed and dba_tab_modifications



oradebug setmypid 
oradebug unlimit 
oradebug -g all hanganalyze 3 
wait 30 seconds 
oradebug -g all hanganalyze 3 
wait 30 seconds 
oradebug -g all dump systemstate 258 
wait 30 seconds 
oradebug -g all dump systemstate 258 
exit  

Can I have this details?
  1. How long does the job take to complete under normal run?
  2. How long it too now when performance is bad?
  3. From when job is experiencing slow performance?
  4. When was the last time job completed within excepted time?
  5. What is the frequency of the job(daily, weekly) run? For all the runs does the job run at same time of the day?
  6. Was there any code change ,change in data volume or any changes we should be aware off?

Mon Jan 08 15:21:21 2018
Errors in file /u01/app/oracle/admin/PIDSD/diag/rdbms/pidsd/PIDSD/trace/PIDSD_ctwr_7471.trc  (incident=128315):
ORA-04031: unable to allocate 13508456 bytes of shared memory ("large pool","unknown object","large pool","CTWR dba buffer")
Incident details in: /u01/app/oracle/admin/PIDSD/diag/rdbms/pidsd/PIDSD/incident/incdir_128315/PIDSD_ctwr_7471_i128315.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Mon Jan 08 15:22:44 2018
ORA-04031 heap dump being written to trace file /u01/app/oracle/admin/PIDSD/diag/rdbms/pidsd/PIDSD/incident/incdir_128315/PIDSD_ctwr_7471_i128315.trc
Mon Jan 08 15:27:18 2018
minact-scn: got error during useg scan e:12751 usn:5
minact-scn: useg scan erroring out with error e:12751
Mon Jan 08 15:32:35 2018
minact-scn: got error during useg scan e:12751 usn:5
minact-scn: useg scan erroring out with error e:12751
Mon Jan 08 15:35:52 2018
Thread 1 cannot allocate new log, sequence 54390
Private strand flush not complete
  Current log# 2 seq# 54389 mem# 0: /u02/origlog/PIDSD/PIDSDredo_t1_g2_m1.dbf
  Current log# 2 seq# 54389 mem# 1: /u02/mirrlog/PIDSD/PIDSDredo_t1_g2_m2.dbf

=================================================




lan0 is down, please bring it up.

g1u3750c:12102/bin $ oifcfg getif
lan0  15.69.32.0  global  public
lan1  15.69.132.0  global  cluster_interconnect
lan2  15.69.132.0  global  cluster_interconnect

ifconfig lan0

[‎08-‎01-‎2018 07:54 PM]
g1u3750c:12102/bin $ ifconfig lan0
lan0: flags=a000000000001842<BROADCAST,RUNNING,MULTICAST,CKO,TSO,PORT>
        inet 0.0.0.0 netmask 0




=====================================

Things to be check if there is any issue.

Node health check - CPU , Memmory ,  DISK, Network.,load average.

server up time ,logs



No comments:

Post a Comment