RE: Oracle and DST changes
- From: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>
- To: <strickland.mark@xxxxxxxxx>, "Barbara Baker" <barb.baker@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 31 Jan 2007 10:37:06 -0700
I think you're missing a very important point here. Just becuase you
are going to patch regardless of the utlzuv2.sql output does NOT mean
that you don't need to run utltzuv2.sql. The utltzuv2.sql script is to
tell you if you have any affected data and if you do, then you have to
backup (copy) that data into varchar2 columns BEFORE patching and then
restore (copy back) the data AFTER the patch. You can backup/restore
the data into varchar2 columns manually, or use the provided scripts
from Metalink.
Regards,
Brandon
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Mark Strickland
That looks right to me. If you're going to patch everything no matter
what, then I don't see a reason to run utltzuv2.sql unless you're just
curious.
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
- References:
- RE: Oracle and DST changes
- From: Mercadante, Thomas F \(LABOR\)
- RE: Oracle and DST changes
- From: Sam Bootsma
- Re: Oracle and DST changes
- From: Mark Strickland
- Re: Oracle and DST changes
- From: Mark Strickland
- Re: Oracle and DST changes
- From: Barbara Baker
- Re: Oracle and DST changes
- From: Mark Strickland
Other related posts:
- » Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- » RE: Oracle and DST changes
- » RE: Oracle and DST changes
- » Re: Oracle and DST changes
- » Re: Oracle and DST changes
- RE: Oracle and DST changes
- From: Mercadante, Thomas F \(LABOR\)
- RE: Oracle and DST changes
- From: Sam Bootsma
- Re: Oracle and DST changes
- From: Mark Strickland
- Re: Oracle and DST changes
- From: Mark Strickland
- Re: Oracle and DST changes
- From: Barbara Baker
- Re: Oracle and DST changes
- From: Mark Strickland