Active Session History (ASH) performed an emergency flush
1,問題描述:
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE 11.2.0.4.0 Production
TNS for Solaris: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production
alter日誌報下面內容:
Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of _ASH_SIZE to a sufficiently large value. Currently, ASH size is 266338304 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:
select total_size,awr_flush_emergency_count from v$ash_info;
SQL> select total_size/1024/1024,awr_flush_emergency_count from v$ash_info;
TOTAL_SIZE/1024/1024 AWR_FLUSH_EMERGENCY_COUNT
-------------------- -------------------------
250 2
2,問題解決:
Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.2 and later [Release: 11.2 and later ]
Information in this document applies to any platform.
Symptoms
Periodically see the following message in the alert log.
Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of _ASH_SIZE to a sufficiently large value. Currently, ASH size is bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query: select total_size,awr_flush_emergency_count from v$ash_info;
Cause
Typically some activity on system causes more active sessions, therefore filling the ASH buffers faster than usual causing this message to be displayed. It is not a problem per se, just indicates the buffers might need to be increased to support peak activity on the database.
Solution
The current ASH size is displayed in the message in the alert log, or can be found using the following SQL statement.
select total_size from v$ash_info;
Then increase the value for _ash_size by some value, like 50% more than what is currently allocated. For example if total_size = 250MB, then an increase of 50% more would be (250MB + (250MB * 50%)) = 375MB.
sqlplus / as sysdba
alter system set "_ash_size"=393216000 scope=spfile;
SQL> select * from v$version;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE 11.2.0.4.0 Production
TNS for Solaris: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production
alter日誌報下面內容:
Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of _ASH_SIZE to a sufficiently large value. Currently, ASH size is 266338304 bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query:
select total_size,awr_flush_emergency_count from v$ash_info;
SQL> select total_size/1024/1024,awr_flush_emergency_count from v$ash_info;
TOTAL_SIZE/1024/1024 AWR_FLUSH_EMERGENCY_COUNT
-------------------- -------------------------
250 2
2,問題解決:
Applies to:
Oracle Server - Enterprise Edition - Version: 11.2.0.2 and later [Release: 11.2 and later ]
Information in this document applies to any platform.
Symptoms
Periodically see the following message in the alert log.
Active Session History (ASH) performed an emergency flush. This may mean that ASH is undersized. If emergency flushes are a recurring issue, you may consider increasing ASH size by setting the value of _ASH_SIZE to a sufficiently large value. Currently, ASH size is bytes. Both ASH size and the total number of emergency flushes since instance startup can be monitored by running the following query: select total_size,awr_flush_emergency_count from v$ash_info;
Cause
Typically some activity on system causes more active sessions, therefore filling the ASH buffers faster than usual causing this message to be displayed. It is not a problem per se, just indicates the buffers might need to be increased to support peak activity on the database.
Solution
The current ASH size is displayed in the message in the alert log, or can be found using the following SQL statement.
select total_size from v$ash_info;
Then increase the value for _ash_size by some value, like 50% more than what is currently allocated. For example if total_size = 250MB, then an increase of 50% more would be (250MB + (250MB * 50%)) = 375MB.
sqlplus / as sysdba
alter system set "_ash_size"=393216000 scope=spfile;
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/25373498/viewspace-1976916/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- Active Session History (ASH)Session
- ASH(Active Session History)——概述(1)!Session
- ASH(Active Session History)——根據SID生產報告(3)!Session
- WRH$_ACTIVE_SESSION_HISTORYSession
- Active Session History ReportsSession
- Clean WRH$_ACTIVE_SESSION_HISTORY in SYSAUXSessionUX
- v$active_session_history檢視Session
- v$active_session_history檢視[轉]Session
- V$ACTIVE_SESSION_HISTORY檢視的使用Session
- 11g v$active_session_history的新增列Session
- 轉載--V$ACTIVE_SESSION_HISTORY檢視的使用Session
- V$ACTIVE_SESSION_HISTORY 檢視中包含的資訊Session
- 一次WRH$_ACTIVE_SESSION_HISTORY問題處理Session
- 通過active_session_history我們能得到什麼Session
- 【ASH】如何匯出檢視DBA_HIST_ACTIVE_SESS_HISTORY的查詢結果資料
- v$active_session_history的wait_time和time_waited 列SessionAI
- 從dba_hist_active_sess_history裡尋找session間的等待關係Session
- 11G 中的V$ACTIVE_SESSION_HISTORY 檢視沒有資料Session
- ORACLE 10g SYSAUX表空間快速增長之WRH$_ACTIVE_SESSION_HISTORY篇Oracle 10gUXSession
- v$action_session_historySession
- DBA_HIST_ACTIVE_SESS_HISTORY應用
- Oracle ASH和Session Tracing(ZT)OracleSession
- [Oracle Script] check active sessionOracleSession
- ASH記憶體強制Flush日誌解決一例記憶體
- [20211214]檢視檢視V$ACTIVE_SESSION_HISTORY遇到奇怪問題.txtSession
- 查詢DBA_HIST_ACTIVE_SESS_HISTORY緩慢
- session效能的影響,後臺 flush dirtySession
- active session的準確定義!Session
- 加快dba_hist_active_sess_history的查詢速度
- 11gr2 rac WRH$_ACTIVE_SESSION_HISTORY未自動清理導致SYSAUX空間過度增長SessionUX
- 10.27 V$SESSION_WAIT_HISTORYSessionAI
- [20130125]利用v$active_session_history檢視解決資料庫問題.txtSession資料庫
- ASH可以生成指定的session或sql_id的報告,ASH和AWR的區別SessionSQL
- 通過shell指令碼快速定位active session問題指令碼Session
- V$SESSION.STATUS='ACTIVE' AND WAIT_EVENT='Idle'SessionAI
- 巧用dba_hist_active_sess_history跟蹤某個時間段內SQLSQL
- Error: The action can not be performed because ...could not be locked?ErrorORM
- oracle ASHOracle