Shulou(Shulou.com)06/01 Report--

Environment

Operating system windows 2008R2

Original library version: oracle 11.2.0.1

Upgrade version: oracle 11.2.0.4

Upgrade method: software package upgrade

Problem description

In recent days, when some colleagues responded to upgrading the original database through oracle 11.2.0.4 in the windows 2008R2 environment, they found that the dblink of the original database could not be used properly after the upgrade was completed, and they began to think that they were caused by the failure of the software upgrade. Even if the original dblink statement is recompiled, an error will still be reported.

No corresponding instructions were found on the official website. At first, it was speculated that the situation was caused by bug. After many tests, it was found that it was caused by the operation in the upgrade process. The correct operation steps are as follows.

Correct upgrade steps

(1) decompress the installation package

(2) run setup as an administrator under the database directory generated by the decompression

(3) check: do not want to be notified of serious security problems in the configuration

(4) check: skip software updates

(5) check: upgrade the existing database

(6) check: simplified Chinese and English

(7) check: enterprise version

(8) oracle base: default

(9) software location:

Original: d:\ app\ Administrator\ product\ 11.2.0\ dbhome_1

It is now changed to: d:\ app\ Administrator\ product\ 11.2.0.4\ dbhome_2

(10) prerequisite check

(11) Summary

(12) install to about 80%, and the oracle netca program appears. Check "perform typical configuration" → next step for configuration listening →.

(13) about 90% of the dbua program appears when it is installed:

Parallelism (default) → check "do not move data files during upgrade" → specifies the location of the database files to be created → recovery and diagnostic location default: e:\ app\ Administrator\ flash_recovery_area → profile → start upgrade

(14) to view the upgrade report, you can use the "configure Database password" to see if any upgrade users are locked.

(15) check the upgraded version of the database: select * from v$version

(16) check whether the components of the database have been successfully upgraded:

SELECT COMP_NAME, VERSION, STATUS FROM SYS.DBA_REGISTRY

Pay attention to the red section above, otherwise after the upgrade is completed, the original dblink may not work properly and can only be solved by rebuilding the dblink.

Note: if the operating system is linux, after the upgrade is completed, change $ORACLE_HOME and $PATH to a new one and make it effective.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.