Why Does Oracle Rac opatch auto fail to hit Rac database home?

Source: Internet
Author: User

Why Does Oracle Rac opatch auto fail to hit Rac database home?
First explain the environment: OS: AIX 7.1Oracle version: Oracle Rac 11.2.0.3 before the release of the 11.2.0.3.9 Patch Set, Rac is not officially used, so simply hit the latest 11.2.0.3.11 patch set.
Today, two sets of Rac were newly installed some time ago to form the latest psu, And the opatch auto method is also used to create psu, but one of the Rac is patch together with Rac and Grid, the other is the patch Set of patch Grid only. Very depressing. The crsconfig_params of the two rac sets are basically the same. I installed the configurations of the two Rac sets in one hand. Why are there so many deviations?
The Rac: root @ HDB01 of the Rac and Grid patch is as follows: /oraapp/oracle/backup>/oraapp/grid/gridhome/OPatch/opatch auto/install/psu-ocmrf/home/grid. rspExecuting/oraapp/grid/gridhome/perl/bin/perl/oraapp/grid/gridhome/OPatch/crs/patch11203.pl-patchdir/install-patchn psu-ocmrf/home/grid. rsp-paramfile/oraapp/grid/gridhome/crs/install/crsconfig_params
This is the main log file:/oraapp/grid/gridhome/export toollogs/opatchauto2014-09-28_15-07-56.log
This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:/oraapp/grid/gridhome/export toollogs/opatchauto2014-09-28_15-07-56.report.log
2014-09-28 15: 07: 56: Starting Clusterware Patch SetupUsing configuration parameter file:/oraapp/grid/gridhome/crs/install/crsconfig_params
Stopping RAC/oraapp/oracle/product/11.2.0/dbhome_1... Stopped RAC/oraapp/oracle/product/11.2.0/dbhome_1 successfully
Patch/install/psu/17592127/custom/server/17592127 apply successful for home/oraapp/oracle/product/11.2.0/dbhome_1 patch/install/psu/18522512 apply successful for home/oraapp /oracle/product/11.2.0/dbhome_1
Stopping CRS... Stopped CRS successfully
Patch/install/psu/17592127 apply successful for home/oraapp/grid/gridhome patch/install/psu/18522512 apply successful for home/oraapp/grid/gridhome
Starting CRS...CRS-4123: Oracle High Availability Services has been started.
Starting RAC/oraapp/oracle/product/11.2.0/dbhome_1... Started RAC/oraapp/oracle/product/11.2.0/dbhome_1 successfully
Opatch auto succeeded. root @ DB01:/oraapp/oracle/backup> su-grid

The Rac: root @ ODB01, which only patches the Grid, is as follows: /install/psu>/oraapp/grid/gridhome/OPatch/opatch auto/install/psu-ocmrf/home/grid. rspExecuting/oraapp/grid/gridhome/perl/bin/perl/oraapp/grid/gridhome/OPatch/crs/patch11203.pl-patchdir/install-patchn psu-ocmrf/home/grid. rsp-paramfile/oraapp/grid/gridhome/crs/install/crsconfig_params
This is the main log file:/oraapp/grid/gridhome/export toollogs/opatchauto2014-09-28_15-08-19.log
This file will show your detected configuration and all the steps that opatchauto attempted to do on your system:/oraapp/grid/gridhome/export toollogs/opatchauto2014-09-28_15-08-19.report.log
2014-09-28 15: 08: 19: Starting Clusterware Patch SetupUsing configuration parameter file:/oraapp/grid/gridhome/crs/install/crsconfig_params
Stopping CRS... Stopped CRS successfully
Patch/install/psu/17592127 apply successful for home/oraapp/grid/gridhome patch/install/psu/18522512 apply successful for home/oraapp/grid/gridhome
Starting CRS...CRS-4123: Oracle High Availability Services has been started.
Opatch auto succeeded. root @ ODB01:/install/psu>
View the Mos document: (Doc ID 1479651.1) It is found that there is a database in HDB (that is, the database is created in the form of dbca), and there is no database DB in ODB. Ps: Now I suddenly remembered that I did set up a database on HDB some time ago and did some data migration for testing... (Dull) in opatch, oracle found that no database was registered to OCR, so it only patched the Grid.
The commands provided by Mos show that there is indeed ora in CRS on HDB. hdb. db: grid @ HDB01:/home/grid> crsctl stat res-p-w "TYPE = ora. database. type "| egrep '^ NAME | ^ ORACLE_HOME' NAME = ora. hdb. dbORACLE_HOME =/oraapp/oracle/product/11.2.0/dbhome_1ORACLE_HOME_OLD = NAME = ora. hdb. dbORACLE_HOME =/oraapp/oracle/product/11.2.0/dbhome_1ORACLE_HOME_OLD = grid @ HDB01:/home/grid>
In ODB, there is no output after the command is run. Check the/etc/oratab file and no database except ASM is found: grid @ ODB01: /home/grid> crsctl stat res-p-w "TYPE = ora. database. type "| egrep '^ NAME | ^ ORACLE_HOME' grid @ SRMBODB01:/home/grid>
You can use the following command to patch the Rac patch: As root user, execute the following command: opatch auto <UNZIPPED_PATCH_LOCATION>-oh <DATABASE_HOME>-ocmrf <ocm response file>
2-node oracle rac database. When rac1 goes down, rac2 cannot respond in time because of its large business volume.

1. manually check the session to find the transaction with the longest processing time, and then check the specific transaction. Locate the problem based on the SQL statement executed by the transaction;
2. Execute ADDM and view the report. analyze the cause of suspension based on the report.

This is largely due to the fact that RAC does not matter.

San names cannot be resolved when oracle installs rac

Scan name must be declared in the/etc/hosts file.
If you use a dns server, you also need to configure forward/reverse resolution.

Related Article

E-Commerce Solutions

Leverage the same tools powering the Alibaba Ecosystem

Learn more >

Apsara Conference 2019

The Rise of Data Intelligence, September 25th - 27th, Hangzhou, China

Learn more >

Alibaba Cloud Free Trial

Learn and experience the power of Alibaba Cloud with a free trial worth $300-1200 USD

Learn more >

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.