Upgrading to Oracle Database 11g

Oracle 11g: Helps reduce your IT costs

• Reduce Tangible Costs with 11g
  • Reduced Hardware and Storage Costs
  • Reduced Support Costs
• Reduce In-Tangible Costs with 11g
  • Increased Productivity
  • Reduced Upgrade Costs
  • Enhanced Security
  • Faster Performance
  • Greater Availability

Database 11g Reduces Tangible CostsCosts 70% Less to Operate

Reduce In-Tangible CostsExtreme Cost Savings

An OS Change means something like Solaris -> Linux, or Windows ->AIX. Something like Linux-32 to Linux-64, or Windows XP to Windows Vista does is not considered an OS Change.

Customers often claim they need to have zero downtime, but requirements really vary more than that.

Most customers like the manual ugprade because they think it gives them more control, but the truth is that the DBUA uses identical scripts and automates some of the manual busywork for you.

If the customer really cannot tolerate an hour of downtime, then the other options should be investigated. These are often more complicated to set up and get working, but we will talk about how to use these upgrade alternatives.

Database Upgrade Assistant (GUI)

Example:dbua -silent -sid dwh-oracleHome /opt/oracle/product/RDBMS10g-diagnosticDest /opt/oracle/diag -sysDBAUserName sys -sysDBAPassword manager-recompile_invalid_objects true -degree_of_parallelism 4-emConfiguration LOCAL -dbsnmpPassword manager -sysmanPassword manager

Command Line Upgrade

• Step-by-step:

1. Complete online backup of the database
2. Install 11g Oracle software and apply patch set 11.1.0.7
3. Analyze the DB using utlu111i.sql and follow all requirements given by the script
4. Create a new 11g listener with NETCA
5. Switch to the new environment, startup the DB (startup upgrade) and create the SYSAUX tablespace (if source db is an Oracle 9i db)
6. Run upgrade script catupgrd.sql and afterwards recompile with utlrp.sql – compare with utluiobj.sql
7. Check the post upgrade status: utlu111s.sql
8. Run catuppst.sql if you are upgrading from 10g

Anmerkung:
utlmrp.sql gibt es seit 10g nicht mehr, da der DEFAULT: PARALLEL ist :-)
Bei 9.2 gab es noch ein UTLMRP.SQL fuer MultiProc-Maschinen

Uses RMAN or export/import to build up a copy of the database
Copy will be synchronized with Streams and switchover can be happen anytime

1. Start with logical standby setup.
2. Use DBUA to upgrade the Logical Standby
3. Turn on log transport to synchronize (this could take some time to catch up)
(At this point the users have no idea of any changes)
4. Switchover primary to standby, upgrade the former primary. If systems are identical then we could stop right there. If the original standby is less powerful or otherwise shoudln‘t be the primary, we can switch back.

Keep in mind that this concept doesn‘t support all datatypes.

Create a guaranteed restore point for the production system using Flashback Database.
Build the logminer dictionary. This takes one statement, around 4-5 minutes.
Convert the physical standby to logical using the new KEEP IDENTITY clause introduced in ???. Normally a logical standby would change the database ID, but in this case we will keep it.
Startup the standby database in the new target environment (e.g. 11.1.0.7). Synchronize again.
Switch roles. The standby becomes production, and users are now on the upgraded database.
But, we don‘t want a logical standby, we want a physical standby. So, flashback to that guaranteed restored point.
Startup form that restore point in the new Oracle Home.
Convert to physical standby
Synchronize by turning on log shipping. This upgrades the physical standby database.
Switch back if desired.

Switchovers are very fast (e.g. <1 minute for the whole process). UPS used this for an upgrade scenario and talked about it at OpenWorld.

We recommend leaving COMPATIBLE at the original value (if 10.1 or higher) for a week before changing to 11.1.0. That way you can still downgrade if there is a problem. When we talk about fallback strategies this will be part of the discussion.

If you are running a 9i->11 upgrade and have not applied the DST patch, you will run into a problem. When the database is opened in upgrade mode, we have to increase COMPATIBLE to 10.1. But, at this point the upgrade cannot proceed without the timezone patch. However, you also cannot go back and install the timezone patch in 9i because COMPATIBLE has been raised to 10.1. Thus your database is lost and has to be restored.

Data file headers are changed when this command is issued. Redo log formats are changed on first access. If the redo logs are big, this can affect performance for a while after the upgrade, until all redo log changes are complete.

The CONNECT role was changed for security purposes in 10g Release 2. The possible issue that could be encountered here is that some users with the CONNECT role might find that there are some functions that they can no longer carry out after the restrictions on the CONNECT role are put in place.

Best practice is to create your own CONNECT role with the necessary privileges, and grant this role to the users who need those privileges.

The security issue was the famous “Oracle Worm” which tried to attack the database by exploiting users with default passwords and the CONNECT role to access the database. This caused customers and Oracle to be aware of how wide-ranging the CONNECT role is, and realize that it needed to be restricted by default.

General Notes:
For database links between different Oracle versions connections must be supported in BOTH directions in the matrix above.eg: As 9.2 -> 7.3.4 is not supported then database links between these version are not supported in either direction.
Unsupported combinations may appear to work but can encounter errors for particular operations. The fact that they appear to work should not be relied upon – issues on unsupported combinations will not be investigated.
Since new database servers are compatible with a limited set of older OCI clients, it may not be necessary to upgrade the client software when upgrading the database. However, some new features may not work without upgrading the client software. So, for example, an Oracle 7.3.4 client is able to connect to an Oracle8i database, but is not able to take advantage of newer features such as Transparent Application Failover (introduced in v8).
Oracle Applications , or other Oracle products, may have supported configurations not listed in the matrix above.
The matrix above also applies between different platforms and between 32/64 bit releases of Oracle client / server except where any Oracle platform desupport notice indicates otherwise .

© 2011, www.oracledatabase12g.com. 版权所有.文章允许转载,但必须以链接方式注明源地址,否则追究法律责任.

相关文章 | Related posts:

1. Upgrading to RAC 11g R2 What you should know
2. Upgrading to 11g–Why,How and Best Practices
3. Oracle Database 11g: New Features Overview eStudy Student Guide
4. Advanced Compression in Oracle Database 11g
5. Competing Against Microsoft SQL Server 2008 with Oracle Database 11g
6. Upgrade from Oracle Database 10g to 11g:What to Expect From the Optimizer
7. Oracle Database 11g: High Availability Student Guide
8. Oracle Database 11g: Change Management Overview eStudy
9. Protecting Applications Using Oracle 11g Database Vault
10. Upgrade to Oracle Database 11g:Single Instance to RAC & ASM