Skip to main content

Oracle share memory usage by RDBMS on linux

My server is configured with HugePage, it's swapping, this is the shell script to find out how much shared memory used by each database, how much memory is using normal page or HugePage, this script only list memory bigger than 100,000kB.

for line in `ps -ef|grep ckpt|grep -v "+ASM"|grep -v "grep"|awk '{print $2"_"$8}'`;
do
#echo $line
PID=$(echo $line|cut  -d "_" -f 1)
DBNAME=$(echo $line|cut  -d "_" -f 4)
SMAPS=$"/proc/"$PID"/smaps"
echo "#########"$DBNAME"########"$SMAPS"########"
awk '/^Size:/ {if ($2>100000) i=1};i && i++ <= 12' $SMAPS
done

Sample output: This example shows that 268MB on 4kB (normal page), 10GB on 2048kB page (HugePage)

#########FFDE2########/proc/64294/smaps########
Size:             268332 kB
Rss:               12300 kB
Pss:                 135 kB
Shared_Clean:      12300 kB
Shared_Dirty:          0 kB
Private_Clean:         0 kB
Private_Dirty:         0 kB
Referenced:        12300 kB
Anonymous:             0 kB
AnonHugePages:         0 kB
Swap:                  0 kB
KernelPageSize:        4 kB
Size:           10452992 kB
Rss:                   0 kB
Pss:                   0 kB
Shared_Clean:          0 kB
Shared_Dirty:          0 kB
Private_Clean:         0 kB
Private_Dirty:         0 kB
Referenced:            0 kB
Anonymous:             0 kB
AnonHugePages:         0 kB
Swap:                  0 kB
KernelPageSize:     2048 kB

How much shared memory used totally on this server:
ipcs -m | awk 'NR > 3 { sum += $5 } END { print sum }'

To sum up memory size of the process PID=59376 (ckpt process)
grep '^Size:' /proc/59376/smaps|cut -d: -f2|cut -d"k" -f1|xargs  | sed -e 's/\ /+/g' | bc

To see the hugepage usage info:
[root@vdclracdev02 ~]# grep Huge /proc/meminfo
AnonHugePages:         0 kB
HugePages_Total:   70000
HugePages_Free:    50517
HugePages_Rsvd:       73
HugePages_Surp:        0
Hugepagesize:       2048 kB

To check the configuration of hugepage:
[root@vdclracdev02 ~]# grep -i hugepage /etc/sysctl.conf
vm.nr_hugepages = 70000


Comments

Popular posts from this blog

Opatch apply/lsinventory error: oneoff is corrupted or does not exist

I am applying the quarterly patch for 19c RDBMS, I tried using napply but failed, but somehow it corrupted the inventory though nothing applied. further apply and lsinventory command ran into error like this: $ ./OPatch/opatch lsinventory Oracle Interim Patch Installer version 12.2.0.1.21 Copyright (c) 2020, Oracle Corporation.  All rights reserved. Oracle Home       : /u02/app/oracle/19.0.0 Central Inventory : /u01/app/oraInventory    from           : /u02/app/oracle/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.21 OUI version       : 12.2.0.7.0 Log file location : /u02/app/oracle/19.0.0/cfgtoollogs/opatch/opatch2020-09-08_13-35-59PM_1.log Lsinventory Output file location : /u02/app/oracle/19.0.0/cfgtoollogs/opatch/lsinv/lsinventory2020-09-08_13-35-59PM.txt -------------------------------------------------------------------------------- Inventory load failed... OPatch cannot load inventory ...

oracle dba_hist_sysmetric_summary

found this blog is helpful to get CPU and IO statistics on oracle database. http://shob-dbadmin.blogspot.ca/2012/12/how-to-find-total-io-of-database.html courtesy to  Shomil Bansal , below are hist writing, not mine. How to find total IO of the database instance Total IO of database instance is sum of the physical reads, physical writes and redo writes. There are several views to find these values. v$sysmetric  - Reports metric values for only the most current time sample 60 secs. v$sysmetric_summary  - Reports metric values for time sample of 1 hour. v$sysmetric_history  - Reports metric values every 60 sec from the time instance is up. Better way to analyse IO using this view to take deltas between two time periods. dba_hist_sysmetric_history  - All the above views are refreshed when the instance is restarted. This view, part of AWR, stores the historical stats. I have used this view for my report. Query: ====== set lines 350...

Oracle ASM DISK IO performance

Oracle OEM show a chart of disk performance, as shown in the chart below. when the OEM target database is 10gr2, the number of average disk response time (ms) is 0.01 ms, which unreasonable low. when the target database is 11gr2, the number is about 10ms, which I think is reasonable. it's time to find out where the discrepency comes from. The backend query is this one: set linesize 200 col name format a9 col path format a19 --col MB_per_sec format select t3.name,t2.name,t2.path,t2.reads,t2.read_time,round(t2.read_time/t2.reads*1000,3) rd_rspd_ms,t2.writes,round(t2.write_time/t2.writes*1000,3) wr_rspd_ms, round((t2.read_time+t2.write_time)/(t2.reads+t2.writes)*1000,3) dsk_rspd_ms,round((t2.bytes_read+t2.bytes_written)/1024/1024/(t2.read_time+t2.write_time))  MB_per_sec from V$asm_disk t2, v$asm_diskgroup t3 where t3.group_number=t2.group_number order by 1,2 / NAME      NAME      PATH               ...