Showing posts with label Tunning. Show all posts
Showing posts with label Tunning. Show all posts

Tuesday, 4 October 2011

How to detect what is the Oracle memory hunger process

How to detect what is the Oracle memory hunger process? Previously I did share a script on how to check the top 10 memory consumption process in Unix.
It is recommended to check the growth memory usage of your Oracle Application Server from time to time.
Top Memory Usage Checking
$ UNIX95= ps -eo vsz,ruser,pid,args | sort -rn | head -10
  85796 applprod 21020 f60webmx webfile=5,1425,apps_oracle
  80228 applprod  5803 f60webmx webfile=5,2443,apps_oracle
  68388 applprod 27304 f60webmx webfile=5,1619,apps_oracle
  65828 applprod 15211 f60webmx webfile=5,1741,apps_oracle
  65444 applprod 11075 f60webmx webfile=5,264,apps_oracle
  64676 applprod 20696 f60webmx webfile=5,2163,apps_oracle
  62948 applprod   885 f60webmx webfile=5,2303,apps_oracle
  56996 applprod 24789 f60webmx webfile=5,2458,apps_oracle
  54884 applprod 18172 f60webmx webfile=5,2405,apps_oracle
  54756 applprod 18077 f60webmx webfile=5,61,apps_oracle
From the output above, it seems that the Oracle form process f60webmx utilize a high amount of server memory.
Quite abnormal because the f60webmx form process should be terminated after certain time of inactivity.
Use the script as below to check on the status of f60webmx session by using the Unix PID.
Oracle Forms Session Checking
SELECT s.STATUS "Status",
s.TYPE "Type",
s.username "DB_User",
s.osuser "Client_User",
s.server "Server",
s.machine "Machine",
s.module "Module",
s.logon_time "Connect Time",
s.process "Process",
p.spid,
p.pid,
s.SID,
s.audsid,
SYSDATE - (s.last_call_et / 86400) "Last_Call"
FROM v$session s,
v$process p
WHERE s.paddr = p.addr(+)
AND s.process = <replace WITH Unix PID>;

Monday, 16 May 2011

Health Check on the Database


How to Perform a Health Check on the Database [ID 122669.1] Applicable from Oracle v7 to v11.
about 7 hours ago from web

Wednesday, 27 April 2011

Oracle Management Pack

Kerry Osborne’s Oracle Blog » Blog Archive » Oracle Management Packs – Kerry Osborne’s Oracle Blog

Disabling ADDM in 10g and 11g

You may not be licensed to use ADDM and want to stop automatic statistics collection, which is enabled by default.

The method alters from 10g to 11g

10g

Use the package to modify the snapshot interval to 0

Execute dbms_workload_repository.modify_snapshot_settings
(retention=>20160, interval=> 0);

11g

The initialization parameter should be set to DIAGNOSTIC+TUNING (default) or DIAGNOSTIC to enable automatic database diagnostic monitoring. Setting CONTROL_MANAGEMENT_PACK_ACCESS to NONE disables many Oracle Database features, including ADDM, and is strongly discouraged, but seems to be the only way to disable the automatic monitoring.

Tuning relies on having a diagnostic license which explains why the options are NONE, DIAGNOSTIC or DIAGNOSTIC+TUNING