Shulou(Shulou.com)05/31 Report--

This article mainly introduces how to patch ORACLE, the article introduces in great detail, has a certain reference value, interested friends must read it!

Opatch tool is used to patch. The specific operation method is readme.txt in the patch package.

1. A way to check whether a patch is installed (upgrade opatch if the following command fails)

$ORACLE_HOME/OPatch/opatch lsinventory

two。 Download the patch pack

View the current opatch version. The opatch version included with Oracle 11.2.0.1.0 is 11.1.0.6.6. The README.html of the patch pack contains the minimum version of opatch that describes the patch or PSU, and needs to be upgraded if the current opatch version is too low (the $ORACLE_HOME/OPatch/opatch version command can be seen).

3. Opatch version upgrade

Download the Patch 6880880 file (such as p6880880_112000_Linux-x86-64 represents the 64-bit version of linux), mv the original $ORACLE_HOME/OPatch directory, extract the Patch 6880880 file and automatically generate the $ORACLE_HOME/OPatch directory.

4. Verify that opatch has been upgraded successfully

$ORACLE_HOME/OPatch/opatch version

5. Turn off DB and snooping

6. Enter the directory of the patch pack

7. Patch (Oracle software section)

The command to patch is usually a simple opatch apply.

$ORACLE_HOME/OPatch/opatch apply

8. Patch (database part, PSU patch set upgrade needs to be performed, only a specific patch generally does not need to be performed)

SQL > STARTUP migrate

SQL > @ $ORACLE_HOME/rdbms/admin/catbundle.sql psu apply

Sql > shutdown immediate

Sql > startup

9. Recompile CPU dependent views (this step can be ignored)

This step always needs to be performed only once on a database to complete the follow-up work when the CPU patch was first released in January 2008. If you have performed this step when installing the previous PSU or CPU, then you do not have to perform this step again. In addition, even if you do not perform this step, the database is working properly, which just means that the installation of the CPU patch in January 2008 did not end normally.

Cd $ORACLE_HOME/cpu/view_recompile

Sqlplus / as sysdba

SQL > @ recompile_precheck_jan2008cpu.sql

SQL > SHUTDOWN IMMEDIATE

SQL > STARTUP UPGRADE

SQL > @ view_recompile_jan2008cpu.sql

SQL > SHUTDOWN

SQL > STARTUP

SQL > exit

10. Compile invalid object

SQL > @ $ORACLE_HOME/rdbms/admin/utlrp.sql

11. Check to see if there is a similar file under admin/*/bdump. Centdb_mmon_9603.trc has been writing, and if so, restart DB.

twelve。 Uninstall the patch

Opatch rollback-id patch number such as 9264253

If you hit a patch 1618213, but do not find a single patch pack, and find multiple PSU, such as finding two such packages on MOS, Database 11.2.0.1 PSU Patch 18139690 and Database 11.2.0.1.2 PSU Patch 18031668, we can only hit the last one, because PSU is a cumulative patch package that contains each other from small to large.

An experiment of personal upgrade: upgrade a specific patch 8574851PowerReadme.txt does not say to upgrade the data dictionary, only need opatch apply, the individual specially to execute SQL > @ catbundle.sql psu apply also reported an error

The difference between stand-alone and RAC with patch 8574851

(a) In a non-RAC environment:

Shut down all services that are running from this ORACLE_HOME.

Confirm the return status from each shutdown command to verify

The shutdown is successful and there are no errors.

(B) In a RAC environment:

For each node in the RAC system, shut down the services for

The specific machine that are running from the ORACLE_HOME.

OPatch will be used on each node in the RAC system one at

A time. If this patch is not rolling RAC installable treat

It as a non-RAC environment and shut down all services.

As an example, in the case of a two node RAC system:

1. Stop instances running on node 1.

2. Run 'opatch apply / 8574851' on node 1.

3. When the apply finishes, opatch asks for confirmation

Before going on to apply the patch to node 2.

4. Start instances on node 1.

5. Stop instances running on node 2.

6. Ask opatch to continue to applying the patch to node 2.

7. Start instances on node 2.

An experiment of patch 8574851 in RAC

The above is all the content of this article "how to patch ORACLE". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

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.