Scribd
Upload
92 views

ACFS File System Is Not Configured.: Opatch Auto

- A database patch requires stopping the database and application for 2 hours of downtime. - There are two cases for applying the patch depending on how the database home is configured - if it is shared or not shared. - In the shared database home case, the patch must be applied to each node sequentially, unmounting and remounting any shared file systems, and restarting the database instance on each node.

Uploaded by

Cường Trịnh
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
92 views

ACFS File System Is Not Configured.: Opatch Auto

- A database patch requires stopping the database and application for 2 hours of downtime. - There are two cases for applying the patch depending on how the database home is configured - if it is shared or not shared. - In the shared database home case, the patch must be applied to each node sequentially, unmounting and remounting any shared file systems, and restarting the database instance on each node.

Uploaded by

Cường Trịnh
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

 Required:

- Stop applicatition
- Stop database
- Down time: 2 hours
 Case 1: GI home and the database homes that are not shared and Oracle
ACFS file system is not configured.

As root user, execute the following command on each node of the cluster:

# opatch auto <UNZIPPED_PATCH_LOCATION>/31537677

 Case 2: GI home is not shared, database home is shared, Oracle ACFS may
be used.

Patching instructions:

1. From the Oracle database home, make sure to stop the Oracle RAC
databases running on all nodes. As the database home owner execute:
2. $ <ORACLE_HOME>/bin/srvctl stop database –d <db-unique-
name>
3. On the 1st node, unmount the Oracle ACFS file systems. See My Oracle
Support Document 1494652.1 for unmounting Oracle ACFS file systems.
4. On the 1st node, apply the patch to the GI home using the opatch
auto command. As root user, execute the following command:
5. # opatch auto <UNZIPPED_PATCH_LOCATION>/31537677
6. If the message, "A system reboot is recommended before using ACFS" is
shown, then a reboot must be issued before continuing. Failure to do so
will result in running with an unpatched ACFS\ADVM\OKS driver.
7. On the 1st node, remount Oracle ACFS file systems. See My Oracle
Support Document 1494652.1 for mounting Oracle ACFS file systems.
8. On the 1st node, apply the patch to the database home using the opatch
auto command. Since the database home is shared, this operation will
patch the database home across the cluster. Note that a USM only patch
cannot be applied to a database home. As root user, execute the
following command:
9. # opatch auto <UNZIPPED_PATCH_LOCATION>/31537677 -oh
<DATABASE_HOME>
10. On the 1st node only, restart the Oracle instance, which you have
previously stopped in Step 1. As the database home owner execute:
11. $ <ORACLE_HOME>/bin/srvctl start instance –d <db-
unique-name> -n <nodename>
12. On the 2nd (next) node, unmount the Oracle ACFS file systems. See My
Oracle Support Document 1494652.1 for unmounting Oracle ACFS file
systems.
13. On the 2nd node, apply the patch to GI home using the opatch
auto command. As root user, execute the following command:
14. # opatch auto <UNZIPPED_PATCH_LOCATION>/31537677 -oh
<GI_HOME>
15. If the message, "A system reboot is recommended before using ACFS" is
shown, then a reboot must be issued before continuing. Failure to do so
will result in running with an unpatched ACFS\ADVM\OKS driver.
16. On the 2nd node, running the opatch auto command in Step 9 will
restart the stack.
17. On the 2nd node, remount Oracle ACFS file systems. See My Oracle
Support Document 1494652.1 for mounting Oracle ACFS file systems.
18. On the 2nd node only, restart the Oracle instance, which you have
previously stopped in Step 1. As the database home owner execute:
19. $ <ORACLE_HOME>/bin/srvctl start instance –d <db-
unique-name> -n <nodename>
20. Repeat Steps 8 through 13 for all remaining nodes of the cluster.

1.2.5 Patch Post-Installation Instructions

After installing the patch, perform the following actions:

1. Apply conflict resolution patches as explained in Applying Conflict Resolution


Patches.
2. If applying a PSU, load modified SQL files into the database, as explained
in Loading Modified SQL Files into the Database.
3. Upgrade Oracle Recovery Manager catalog, as explained in Upgrade Oracle
Recovery Manager Catalog.

This patch includes new stub modules for database applications. As a consequence you
must relink all database applications. This applies to Pro*COBOL, Pro*C and OCI
database applications. This is valid for standalone database applications and for
openUTM database applications.

1.2.5.1 Applying Conflict Resolution Patches

Apply the patch conflict resolution one-off patches that were determined to be needed
when you performed the steps in One-off Patch Conflict Detection and Resolution.

1.2.5.2 Loading Modified SQL Files into the Database

The following steps load modified SQL files into the database. For an Oracle RAC
environment, perform these steps on only one node.

1. For each database instance running on the Oracle home being patched, connect
to the database using SQL*Plus. Connect as SYSDBA and run
the catbundle.sql script as follows:
2. cd $ORACLE_HOME/rdbms/admin
3. sqlplus /nolog
4. SQL> CONNECT / AS SYSDBA
5. SQL> STARTUP
6. SQL> @catbundle.sql psu apply
7. SQL> QUIT

The catbundle.sql execution is reflected in
the dba_registry_history view by a row associated with bundle series PSU.

For information about the catbundle.sql script, see My Oracle Support


Document 605795.1 Introduction to Oracle Database catbundle.sql.

8. If the OJVM PSU was applied for a previous GI PSU patch, you may see invalid
Java classes after execution of the catbundle.sql script in the previous step.
If this is the case, run utlrp.sql to re-validate these Java classes.
9. cd $ORACLE_HOME/rdbms/admin
10. sqlplus /nolog
11. SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql

You might also like