Note #*402742.1 *explains the issue pretty well. I didn't know that there
actually is a one-off patch available for some versions of Oracle on some
platforms. I'm undecided about whether or not I'm going to apply the
one-off patch. Looks like a very low-risk patch. I certainly cannot
consider moving to the 10.2.0.3 patchset. We're are on 10.1.0.5 ( Solaris 9
64-bit), do not use java inside the database, do not use TSTZ or TSLTZ
outside of the data dictionary and the TZ_OFFSET function is not used, BUT
we are in an affected time zone (U.S. Pacific). If the data dictionary
columns that use TSTZ or TSLTZ are only related to the Scheduler, then it
seems low risk to me to let the Scheduler be off by an hour for a few
weeks. We do not use the Scheduler for any application-related things.
It's just the automatic statistics gathering that's affected as far as I can
tell. I'll be interested in hearing more about what folks decide to do.
Regards,
Mark Strickland
Seattle, WA
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jan 22 2007 - 17:58:49 CST
