Re: Upgrading from 10g to 11g on Windows
Date: Wed, 30 Sep 2009 06:53:38 -0600
Just a small point, but you should probably check to see if the 126.96.36.199 patch is available for your platform, instead of using 188.8.131.52, especially if you're databases are using the spatial features, specifically 3D geometry. As I remember it, you have to upgrade to 184.108.40.206 first, then apply yet another patch fix to fix the 3D problem.
Also, be forewarned that starting with 220.127.116.11, lots of people seem to be getting a lot of "informational errors" in their alert log. It doesn't affect the data, it is merely a warning type error about LDI_DATE_ARRAY (going from memory here). All of these errors can be safely ignored, but it was a bit worrisome at first seeing all of these error messages constantly. I think the explanation was that one of the internal views is accessing a timestamp column, and if the value is null, it throws the error. I believe this supposed to be fixed in 11.2.
-- -- Bill Ferguson On Tue, Sep 29, 2009 at 1:46 PM, Schauss, Peter (IT Solutions) <peter.schauss_at_ngc.com> wrote:Received on Wed Sep 30 2009 - 07:53:38 CDT
> I am getting ready to upgrade some small instances of 10.2.0.3.0 to
> 18.104.22.168.0 on a new server.