Anuroop Challa

  Doc ID 130866.1 REM Script is meant for Oracle version 9 and higher REM ----------------------------------------------- set serveroutput on exec dbms_output.enable(1000000); declare cursor c_dbfile is select f.tablespace_name,f.file_name,f.file_id,f.blocks,t.block_size ,decode(t.allocation_type,'UNIFORM',t.initial_extent/t.block_size,0) uni_extent ,decode(t.allocation_type,'UNIFORM',(128+(t.initial_extent/t.block_size)),128) file_min_size from dba_data_files f, dba_tablespaces t where f.tablespace_name = t.tablespace_name and t.status = 'ONLINE' order by f.tablespace_name,f.file_id; cursor c_freespace(v_file_id in number) is select block_id, block_id+blocks max_block from dba_free_space where file_id = v_file_id order by block_id desc; /* variables to check settings/values */ dummy number; checkval varchar2(10); block_correction1 number; block_correction2 number; /* running variable to show (possible) end-of-file */ file_min_block number; /* variables to ch

=================================== 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 83886080 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;  ==================================================== The ASH buffers may need to be increased if the message is logged frequently. Please review: Active Session History (ASH) Performed An Emergency Flush Messages In The Alert Log (  Doc ID 1385872.1  ) Thanks for the visit !  Any doubts or correction/suggestions, please comment below it helps me to improve in further posts.

===================REFRENCE ============== This is an informational error that you are getting this error because somebody is running a DDL (create table/index) that is specifying the maxtrans parameter.  Please refer the below note for more details:  DataPump Export/Import Generate Messages "The Value (30) Of Maxtrans Parameter Ignored" in Alert Log (  Doc ID 455021.1  )  ======================================

Cause: ====== This error is only affecting the session seeing the error. This error does not relate to any potential data corruption or any data loss. This error is only telling us that the client and server process communication was terminated due to some event. Most of the customers tried workaround of setting "_optim_peek_user_binds"=false to avoid this problem OR In Some cases Bug 18841764 Network related error like ORA-12592 or ORA-3137 or ORA-3106 may be signaled Network/TTC related error ORA-12592, ORA-3137, ORA-3106 may be signaled on SQL*Net TCP/IP transport. Usually this problem is seen with following circumstances. - Sending large size data to database server, for example, using sqlldr, expdp Solution: ========= workaround 1 ============ one time occurrences can be safely ignored as there wasn't any impact. OR If error is consistent, SQL> alter system set "_optim_peek_user_binds"=false; Restart the db instance and listener. I