4 Replies Latest reply: Apr 18, 2013 9:53 AM by user571263 RSS

    Moving to new server and from 11.2.0.1 to 11.2.0.3 at the same time

    user571263
      I have 2 11.2.0.1 databases running on windows server 2008, and am moving them to a VMware server running the same OS.

      While I am doing this, I figure I may as well apply the 11.2.0.3 patch by installing it on the new server and upgrading the databases.

      I've yet to do an "out of place" patch, so I'm assuming I can do the following:

      Install 11.2.0.3 on the new server running the setup.exe -downloadUpdates command, copy backed up datafiles (from online or offiline backups) over from current prod databases, restore them with rebuild controlfile & open database, then shut down and do startup upgrade?

      Or would it be a better practice to create the databases on the new server and just do full imports?



      thanks in advance.
        • 1. Re: Moving to new server and from 11.2.0.1 to 11.2.0.3 at the same time
          Srini Chavali-Oracle
          Either approach will work - how big are theses databases and how much down downtime can you afford ?

          http://docs.oracle.com/cd/E11882_01/server.112/e23633/toc.htm

          Starting with 11.2.0.2, "out-of-place" upgrades are recommended

          Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2 [ID 1189783.1]

          HTH
          Srini
          • 2. Re: Moving to new server and from 11.2.0.1 to 11.2.0.3 at the same time
            user571263
            Thanks - since the first one I am moving over is a test database, I just created the instance on the new server, shutdown the source test database then copied sp & control files & datafile directory structure over with data files, and decided to try DBUA rather than startup upgrade. Right now it's about 1/2 way through the upgrade so we'll see how it goes.

            For the production database I am going to first try my cloning technique then do a startup upgrade or use DBUA. What I'm thinking about doing is copying my last (user managed) online backup over (after creating the instance & directories), doing a startup no mount, rebuild the controlfile to reflect any changes, recover with backup controlfile & apply latest redo, open with resetlogs then shutdown and startup upgrade (or DBUA).

            If that works well that's probably the way I'll do the actual production roll over this way, but leave it in recover mode until I shutdown the old database and apply the last redolog, then upgrade it.

            I suppose that given these databases are relatively small I could also do the upgrade first then just drop the schemas with tables in them and do a schema level impdp.
            • 3. Re: Moving to new server and from 11.2.0.1 to 11.2.0.3 at the same time
              Srini Chavali-Oracle
              If you need to open your copied over database on the new server, then you will need to copy/clone the 11.2.0.1 software also (since you cannot open a 11.2.0.1 database using 11.2.0.3 binaries, unless you upgrade first). Also DBUA is highly recommended approach.

              http://docs.oracle.com/cd/E11882_01/em.112/e12255/oui6_cloning.htm#BCGEJGAJ

              http://docs.oracle.com/cd/E11882_01/server.112/e23633/preup.htm#i694345

              HTH
              Srini
              • 4. Re: Moving to new server and from 11.2.0.1 to 11.2.0.3 at the same time
                user571263
                I think I ran into this situation awhile ago when I inadvertently cloned a 11.2.0.1 database to my 11.2.0.3 install (from an online backup) on my workstation as a test without thinking I was going to a different version.

                I think I remember it allowing me to startup mount, create control file and apply redo, but when I tried to open with resetlogs I was getting errors, so I shut it down and if I recall I had to to a startup upgrade and eventually got it opened up.

                Pretty sure this would not be an Oracle recommended approach though..