| Clarification of ASH trace file issue: Oracle Database 10g Manageability Features [message #109788] |
Mon, 28 February 2005 22:06 |
pgongloo
Messages: 8
Registered: February 2005
|
Junior Member |
|
|
An issue posted a month or two back that needed clarification.
Issue:
"win32 - w2k server sp4
Oracle 10g - 10.1.0.3.
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. "
Solution:
Actually, this happened, since on Windows, the "program" column in V$SQL was more than the usual 48 characters. This issue is discussed in Bug: 3697285: ORA-12899: VALUE TOO LARGE FOR COLUMN.
There's a fix available for the above. Also, there's a workaround available if you're unwilling to apply the patch..
alter table WRH$_ACTIVE_SESSION_HISTORY modify (program VARCHAR2(64));
alter table WRH$_ACTIVE_SESSION_HISTORY_BL modify (program VARCHAR2(64));
Please refer to bug 3697285 for further information.... There is no need to turn of any of the features either through _ init.ora parameters or setting statistics_level to basic for this to work..
-gp
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
