Didn't remember that detail of ORDER BY, that caused me lots of headaches on the first db we migrated. David Ramírez Reyes MES DBA Technical Leader On 4 July 2014 01:06, Chitale, Hemant K <Hemant-K.Chitale@xxxxxx> wrote: > > > There's a 32MB file of a presentation "Upgrade and Migrate to Oracle > Database 11g" by "Roy Swonger & Mike Dietrich". > > Search for it on oracle's site (or a google search). > > > > Also remember that behaviour of Group By changes (results are NOT ordered > as you might have expected / seen them in 9i - so an ORDER BY is necessary > if you expected sorted results), many optimizer changes as well. Changes > to dbms_stats are also significant. > > > > Hemant K Chitale > > > > > > *From:* Chitale, Hemant K > *Sent:* Friday, July 04, 2014 2:02 PM > *To:* 'RStorey@xxxxxxxxxxxxxxxxxx' > *Cc:* ORACLE-L > *Subject:* RE: Manual UPgrade question > > > > Specifically responding to : > > > > ------------------------------------------------ > > According to documentation, the datafiles are not changed. The upgrade > involves recompilation of binaries and such. > > > > Or does the upgrade alter the contents of the sys tablespace? > > ------------------------------------------------- > > > > The Upgrade **DOES** update the system tablespace (lots and lots of > changes !). It would update the UNDO Tablespace. It also needs a new > SYSAUX tablespace. Datafile headers need to be updated when the database is > OPENed. > > > > The word size conversion requires additional scripts --- utlirp.sql and > utlrp.sql and a separate script for Java objects. > > There are a number of support notes on word size conversion --- 62290.1, > 548978.1, 341880.1 are three that I have saved. > > > > Hemant K Chitale > > > > > > *From:* oracle-l-bounce@xxxxxxxxxxxxx [ > mailto:oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx>] *On > Behalf Of *Storey, Robert (DCSO) > *Sent:* Thursday, July 03, 2014 10:08 PM > *To:* Oracle L > *Subject:* Manual UPgrade question > > > > > > So working on a manual upgrade of 9iR2 to 11gR2. Changing hardware and > word size. Import/Export is not an option, DBUA is not an option, nor is > transportable tablespaces. Manual is all I have left short of buying > migration software such as Shareplex or Goldengate. > > > > The manual upgrade appears straight forward. My question is for after the > upgrade. > > > > So I have a new server that will be my production server. I'll do my > testing on it. So, assuming the manual upgrade is successfully wrung out > and tested and I'm ready to do the live upgrade. > > > > I'm curious if , now that I have the upgraded DB on the production server > could I just recopy over new versions of the datafiles, controlfiles, redo > Logs(?) and restart the upgraded database without having to run through the > upgrade again. > > > > According to documentation, the datafiles are not changed. The upgrade > involves recompilation of binaries and such. > > > > Or does the upgrade alter the contents of the sys tablespace? > > > > Thanks > > This email and any attachments are confidential and may also be > privileged. If you are not the intended recipient, please delete all copies > and notify the sender immediately. You may wish to refer to the > incorporation details of Standard Chartered PLC, Standard Chartered Bank > and their subsidiaries at https://www.sc.com/en/incorporation-details.html > . >