how much of a nuisance is hundreds of these trace files, when we're not yet using ASH? (haven't yet worked out the licensing issues).
metalink turns up empty. sounds like a little re-create of a view with a substr( ) would fix this right up. so would turning off active session history.
This is a bigger pain than the event log being filled with 2 lines per log file switch.
Paul
Mon Jan 31 15:00:32 2005 ORACLE V10.1.0.3.0 - Production vsnsta=0 vsnsql=13 vsnxtr=3 Oracle Database 10g Release 10.1.0.3.0 - Production Windows 2000 Version V5.0 Service Pack 4 CPU : 1 - type 586 Process Affinity: 0x00000000 Memory (A/P) : PH:664M/2047M, PG:2658M/3955M, VA:1164M/2047M Instance name: mysid
Redo thread mounted by this instance: 1
Oracle process number: 27
Windows thread id: 1504, image: ORACLE.EXE (m000)
*** ACTION NAME:(Auto-Flush Slave Action) 2005-01-31 15:00:32.378 *** MODULE NAME:(MMON_SLAVE) 2005-01-31 15:00:32.378 *** SERVICE NAME:(SYS$BACKGROUND) 2005-01-31 15:00:32.378 *** SESSION ID:(139.1657) 2005-01-31 15:00:32.378 *** KEWROCISTMTEXEC - encountered error: (ORA-12899 (See ORA-12899.ora-code.com): value too large for column "SYS"."WRH$_ACTIVE_SESSION_HISTORY"."PROGRAM" (actual: 52, maximum: 48) ) *** SQLSTR: total-len=1293, dump-len=240, STR={INSERT /*+ APPEND */ INTO WRH$_ACTIVE_SESSION_HISTORY ( snap_id, dbid, instance_number, sample_id, sample_time, session_id, session_serial#, user_id, sql_id, sql_child_number, sql_plan_hash_value, service_hash, session_type, sql} kewa_flusher: Exception handler 13509 - Will resignal! *** KEWRAFM1: Error=13509 encountered by kewrfteh -- http://www.freelists.org/webpage/oracle-l
