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/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- V$ACTIVE_SESSION_HISTORY檢視的使用Session
- [20211214]檢視檢視V$ACTIVE_SESSION_HISTORY遇到奇怪問題.txtSession
- 10.27 V$SESSION_WAIT_HISTORYSessionAI
- 【DBA】DBA_HIST_ACTIVE_SESS_HISTORY檢視用途
- session效能的影響,後臺 flush dirtySession
- ASH可以生成指定的session或sql_id的報告,ASH和AWR的區別SessionSQL
- 1003 Emergency (25分)
- [20211223]tpt ash ash_index_helperx指令碼.txtIndex指令碼
- ORA-15032: not all alterations performedORM
- [20220129]完善tpt ash ash_index_helperx指令碼.txtIndex指令碼
- [20220422]完善tpt ash ash_index_helperx指令碼2.txtIndex指令碼
- [Active Learning] Multi-Criteria-based Active Learning
- mysql關於FLUSH TABLES和FLUSH TABLES WITH READ LOCK的理解MySql
- Ubuntu強制重啟後提示emergency modeUbuntu
- Javascript history物件的 history.pushState() 和 history.replaceState() 方法JavaScript物件
- statspack、awr、addm,ash影片分享
- mac提交svn提示CHECKOUT can only be performed on a version resourceMacORM
- OPATCHAUTO-72141: Grid patching cannot be performed in rolling mode on single noORM
- spring.profiles.active=@profiles.active@的含義Spring
- Active Record Associations
- history物件物件
- AP History
- ALTER SYSTEM FLUSH BUFFER_POOL
- MySQL:unblock with 'mysqladmin flush-hosts'MySqlBloC
- MySQL5.7 Waiting FOR TABLE FLUSHMySqlAI
- innodb_flush_log_at_trx_commitMIT
- InnoDB引擎之flush髒頁
- history.go()Go
- history.forward()Forward
- history.back()
- JavaScript history 物件JavaScript物件
- history.length
- history.back(-1)和history.go(-1)區別Go
- History- Linux下定製個性化history記錄Linux
- [20220311]完善ash_wait_chains指令碼.txtAI指令碼
- mysqldump: Error: Binlogging on server not activeMySqlErrorServer
- HMAC: Introduction, History, and ApplicationsMacAPP
- linux-history命令Linux
- 常見命令-history