ORA 700 [kskvmstatact: excessive swapping observed]

By
ORA 700 [kskvmstatact: excessive swapping observed]
========================================
One of my database down suddenly.
Reason:  ORA-700 SWAP error, as the dump it's taking more that 10 minutes pmon killed the process and the database was down.

this database running with less memory .

Solution
alter system set "_kse_die_timeout"=XX or 0 if we want to disable the pmon killer during dumping .


note:
The error is documented in: 
- Note:1919850.1 - 12c: Warning Message About Heavy Swapping Observation and ORA-700 [kskvmstatact: excessive swapping observed] 

Because your swap memory has low values of swap in / swap out, this warning message can be safely ignored. 

Given both the alert log message and ORA-700 are expected behavior for 12c, no action is required. 

An enhancement request (ER) was created to change the threshold in future releases in 
Bug 19495842 - CHANGE THRESHOLD IN THE SWAP WARNING IN THE ALERT_<SID>.LOG 


=================
1 - Increase the timeout value to _kse_die_timeout to 360000 to increase the timeout to 1 hour or 180000 if you desired 30 minutes . That will stop PMON killing the process and db shutdown.

2 - Set "_kse_die_timeout"=0 (it is a dynamic parameter so can be set with alter system) but in this case If a process does get stuck spending ages dumping diagnostic data it would not be automatically killed after XX mins, this means that all the resources for the process still allocated and could cause other issues related to locking or hanging issue.
==================================

Comments

Post a Comment

Popular posts from this blog

SQL Tuning Task Creation ORA-13780: SQL statement does not exist.

By
SQL Tuning Task Creation ORA-13780: SQL statement does not exist. ================================================= example:- declare  l_sql_tune_task_id  varchar2(100); begin  l_sql_tune_task_id := dbms_sqltune.create_tuning_task (         sql_id      => 'your sql_id',         scope       => dbms_sqltune.scope_comprehensive,         time_limit  => 10800,         task_name   => 'tuning task name',         description => 'tuning task description');  dbms_output.put_line('l_sql_tune_task_id: ' || l_sql_tune_task_id); end; / declare * ERROR at line 1: ORA-13780: SQL statement does not exist. ORA-06512: at "SYS.DBMS_SYS_ERROR", line 79 ORA-06512: at "SYS.PRVT_SQLADV_INFRA", line 125 ORA-06512: at "SYS.DBMS_SQLTUNE", line 655 solution :----  SELECT SNAP_ID FROM DBA_HIST_...
Read more

Shareplex some commands

By
Shareplex some commands i will post here and update in this post with more commands later, if i provide with example so post become lengthy so please to understand. =====================================================================   sp_ctrl  :- Shareplex provides a command line utility called    'sp_ctrl'   this  sp_ctl located in  <product_directory>/bin  ($SP_HOME/bin)  , if you set profile in os level you easy redirect location. Below i will give commands run under  sp_ctrl  sp_ctrl (xxx)>   show config   ==> To check the active configuration (source side). sp_ctrl (xxx)>   show log reverse  ==> To check the log file sp_ctrl (xxx)>  show  ==>   command to displays status of the replication processes (Capture, Read, Export, Import and Post) . sp_ctrl (xxx)>  status  ==> command from sp_ctrl utility...
Read more

ORA-1092 : opitsk aborting process

By
sharing This error shown when load high from database and unix server(as we have unix type veritas cluster ) detect hang and db failover to another node. even in alertlog show only one errror and no other info(no trace file generation) trace cause so  in this case below is help to trace(generate trace file immediate when impact time by using below mentod) and raise case to vedor and upload trace file(even if you can able to trace cause from file as you can) Hanganalyze need to be collected when the situation occurs, below are the steps to perform such task.  Hanganalyze  sqlplus '/ as sysdba'  oradebug setmypid  oradebug unlimit  oradebug hanganalyze 3  -- Wait one minute before getting the second hanganalyze  oradebug hanganalyze 3  oradebug tracefile_name  exit  Thanks for the visit !  Any doubts or correction/suggestions, please comment below it helps me to improve in further posts.
Read more