How 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 ASHSIZE TO A SUFFICIENTLY LARGE VALUE. CURRENTLY, ASH SIZE IS 67108864 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;
MOS: Active Session History (ASH) Performed An Emergency Flush Messages In The Alert Log (Doc ID 1385872.1)
bash-3.2$ sqlplus "/ as sysdba";
SQL*Plus: Release 11.2.0.3.0 Production on Thu Sep 11 14:03:36 2014
Copyright (c) 1982, 2011, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
--------- --------------------
ORCL READ WRITE
SQL>
SQL> alter system set "_ash_size" =16777216 scope=spfile;
System altered.
SQL> shut immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup;
ORACLE instance started.
Total System Global Area 1.2831E+10 bytes
Fixed Size 2171296 bytes
Variable Size 2080382560 bytes
Database Buffers 1.0704E+10 bytes
Redo Buffers 44785664 bytes
Database mounted.
Database opened.
SQL>
SQL>
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
--------- --------------------
ORCL READ WRITE
SQL>
SQL>
SQL> alter system switch logfile;
System altered.
SQL> /
System altered.
SQL> /
System altered.
SQL> exit
Thanks and Comments Please...........!
