I am currently testing the patchset for Oracle 126.96.36.199 to 188.8.131.52. Why is this Oracle patchset an upgrade/migration? It isn't being sold or advertised as an upgrade.
This patchset is not really an upgrade or a migration, in the truest senses of the words. An upgrade would be going from Oracle 9.2.0 to 9.2.1. A migration would be going from Oracle 7 to Oracle 8. Beginning in Oracle 9i, the official documentation now refers to all of this as a migration. But many Oracle DBAs still make the distinction between an upgrade and a migration.
There is a difference in this patchset which blurs the lines. Previous patchsets, like going from Oracle 8.0.4 to 8.0.5, just required shutting down the database and installing software. Then the databases were restarted. With this patchset, from 184.108.40.206 to 220.127.116.11, you shut down the database and install the software. Then, things get blurred towards the upgrade/migrate steps. You have to STARTUP MIGRATE the database and run the $ORACLE_HOME/rdbms/admin/catpatch.sql script.
In the end, for old school DBAs, this is still a patchset. But the lines are getting blurred to make it look more and more like an upgrade.
For More Information
- Dozens more answers to tough Oracle questions from Brian Peasland are available.
- The Best Oracle Web Links: tips, tutorials, scripts, and more.
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your technical Oracle and SQL questions -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.
Dig deeper on Oracle database design and architecture
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.