Oracle 10.2.0.4: OEM bug 8350262

Source: Internet
Author: User

Oracle 10.2.0.4: OEM bug 8350262

1. Discover Problems

Today, in the OEL 4 environment, we upgraded from 10.2.0.1 to 10.2.0.4, and then created the database in dbca. The database didn't move during the 91% period and waited for a long time. Finally, we reported the following error ~ Let's take a look!



















I searched through google for bugs in Oracle 10.2.0.4 and 10.2.0.5. I was lucky enough to get caught ~

Open the emConfig. log file as prompted.

Vi/u01/app/oracle/product/10.2/db/export toollogs/dbca/prod/emConfig. log

 

Aug 17,2011 10:12:30 AM oracle. sysman. emcp. util. OUIInventoryUtil setOUILoc

CONFIG: Setting oracle. installer. oui_loc to/u01/app/oracle/product/10.2/db/oui

Aug 17,2011 10:12:30 AM oracle. sysman. emcp. util. OUIInventoryUtil setOUILoc

CONFIG: Setting oracle. installer. oui_loc to/u01/app/oracle/product/10.2/db/oui

Aug 17,2011 10:12:33 AM oracle. sysman. emcp. util. CentralAgentUtilgetCentralAgentHomeAndURL

CONFIG: Central Agent home and URL :{}

Aug 17,2011 10:12:33 AM oracle. sysman. emcp. EMConfig restoreOuiLoc

CONFIG: Restoring oracle. installer. oui_loc to/u01/app/oracle/product/10.2/db/oui

Aug 17,2011 11:45:57 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: LOG_FILE value:/u01/app/oracle/product/10.2/db/export toollogs/dbca/prod/emConfig. log

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: HOST value: oel1

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: PORT value: 1521

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: SID value: prod

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: LISTENER value: LISTENER

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: LISTENER_OH value:/u01/app/oracle/product/10.2/db

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setFlag

CONFIG: Flag '-config' set to true

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setFlag

CONFIG: Flag 'db' set to true

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: EM_HOME value:/u01/app/oracle/product/10.2/db

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: DB_UNIQUE_NAME value: prod

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: SERVICE_NAME value: prod

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

<Product/10.2/db/export toollogs/dbca/prod/emConfig. log "1500L, 138732C Top

Aug 17,2011 10:12:30 AM oracle. sysman. emcp. util. OUIInventoryUtil setOUILoc

CONFIG: Setting oracle. installer. oui_loc to/u01/app/oracle/product/10.2/db/oui

Aug 17,2011 10:12:30 AM oracle. sysman. emcp. util. OUIInventoryUtil setOUILoc

CONFIG: Setting oracle. installer. oui_loc to/u01/app/oracle/product/10.2/db/oui

Aug 17,2011 10:12:33 AM oracle. sysman. emcp. util. CentralAgentUtilgetCentralAgentHomeAndURL

CONFIG: Central Agent home and URL :{}

Aug 17,2011 10:12:33 AM oracle. sysman. emcp. EMConfig restoreOuiLoc

CONFIG: Restoring oracle. installer. oui_loc to/u01/app/oracle/product/10.2/db/oui

Aug 17,2011 11:45:57 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: LOG_FILE value:/u01/app/oracle/product/10.2/db/export toollogs/dbca/prod/emConfig. log

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: HOST value: oel1

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: PORT value: 1521

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: SID value: prod

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: LISTENER value: LISTENER

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: LISTENER_OH value:/u01/app/oracle/product/10.2/db

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setFlag

CONFIG: Flag '-config' set to true

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setFlag

CONFIG: Flag 'db' set to true

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: EM_HOME value:/u01/app/oracle/product/10.2/db

Aug 17,201 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: DB_UNIQUE_NAME value: prod

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: SERVICE_NAME value: prod

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setParam

CONFIG: Setting param: ORACLE_HOME value:/u01/app/oracle/product/10.2/db

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. ParamsManager setFlag

CONFIG: Flag '-cluster' set to true

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. util. ClusterUtil areNodesAlive

CONFIG: Alive node cache contents: []

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. util. ClusterUtil areNodesAlive

CONFIG: oel1 not found in alive node cache

Aug 17,2011 11:46:27 AM oracle. sysman. emcp. util. ClusterUtil areNodesAlive

CONFIG: oel2 not found in alive node cache

Aug 17,2011 11:46:29 AM oracle. sysman. emcp. util. ClusterUtil areNodesAlive

CONFIG: Node: oel1 is accessible.

Aug 17,2011 11:46:29 AM oracle. sysman. emcp. util. ClusterUtil areNodesAlive

CONFIG: Node: oel2 is accessible.

Aug 17,2011 11:46:29 AM oracle. sysman. emcp. ParamsManager getInaccessibleNodeList

CONFIG: All nodes are up. Nodes: [oel1, oel2]

Aug 17,2011 11:46:29 AM oracle. sysman. emcp. ParamsManager getInaccessibleSidList

CONFIG: All nodes are up. Nodes: [oel1, oel2] Sids: [prod1, prod2]

 

2. Oracle's explanation of the cause of this bug:

In Enterprise Manager DatabaseControl with Oracle Database 10.2.0.4 and 10.2.0.5, the root certificate used to securecommunications via the Secure Socket Layer (SSL) protocol will expire on31-Dec-2010 00:00:00. thecertificate expiration will cause errors if you attempt to configure DatabaseControl on or after 31-Dec-2010. existing Database Controlconfigurations are not impacted by this issue.

If you plan to configure Database Control with either of theseOracle Database releases, oraclestrongrong recommends that you apply Patch 8350262 to your Oracle Homeinstallations before you configure Database Control. configuration of Database Control istypically done when you create or upgrade Oracle Database, or if you runEnterprise Manager Configuration Assistant (EMCA) in standalone mode.

Note the following:

(1) The issue impacts configuration ofDatabase Control with Oracle Database 10.2.0.4 and 10.2.0.5 only. It does notimpact database creation or upgrade.

(2) The issue does not impact existingDatabase Control tolerations.

(3) Application of Patch 8350262 does not require any databasedowntime

 

3. Solve the Problem

The recommended steps for ORACLE are as follows:

Recovering from Configuration Errors on a Single InstanceDatabase

Single Instance

Recovering from Configuration Errors on a Single InstanceDatabase
1. Ignore any errors and continue with the installation or upgrade. Thedatabase will be created without errors.

2. Apply Patch 8350262 to your Oracle Home installation usingOPatch.

Opatch apply

Invoking OPatch 10.2.0.4.2

Oracle Interim Patch Installer version 10.2.0.4.2
Copyright (c) 2007, Oracle Corporation. All rights reserved.

Oracle Home:/myhost
Central Inventory:/scratch/pchebrol/oraInventory
From:/etc/oraInst. loc
OPatch version: 10.2.0.4.2
OUI version: 10.2.0.4.0
OUI location:/myhost/oui
Log file location:/myhost/export toollogs/opatch/opatch2011-01-02_11-00-00AM.log

ApplySession applying interim patch '000000' to oh'/myhost'

Running prerequisite checks...

OPatch detected non-cluster Oracle Home from the inventory andwill patch the local system only.

Backing up files and inventory (not for auto-rollback) for theOracle Home
Backing up files affected by the patch '000000' for restore. This might take awhile...
Backing up files affected by the patch '000000' for rollback. This might takea while...

Patching component oracle. sysman. agent. core, 10.2.0.4.0a...
Updating jar file "/myhost/sysman/jlib/emCORE. jar"
"/Sysman/jlib/emCORE. jar/oracle/sysman/eml/sec/fsc/FSWalletUtil. class"
Updating jar file "/myhost/sysman/jlib/emCORE. jar"
"/Sysman/jlib/emCORE. jar/oracle/sysman/eml/sec/rep/RepWalletUtil. class"
Updating jar file "/myhost/sysman/jlib/emCORE. jar"
"/Sysman/jlib/emCORE. jar/oracle/sysman/eml/sec/util/RootCert. class"
Updating jar file "/myhost/sysman/jlib/emCORE. jar"
"/Sysman/jlib/emCORE. jar/oracle/sysman/eml/sec/util/SecConstants. class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd _
Java. jar/oracle/sysman/eml/sec/fsc/FSWalletUtil. class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd _
Java. jar/oracle/sysman/eml/sec/rep/RepWalletUtil. class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd _
Java. jar/oracle/sysman/eml/sec/util/RootCert. class"
Updating jar file "/myhost/sysman/jlib/emd_java.jar" with "/sysman/jlib/emd _
Java. jar/oracle/sysman/eml/sec/util/SecConstants. class"
ApplySession adding interim patch '000000' to inventory

Verifying the update...
Inventory check OK: Patch ID 8350262 is registered in Oracle Home inventorywith proper meta-data.
Files check OK: Files from Patch ID 8350262 are present in Oracle Home.

OPatch succeeded.

  • 1
  • 2
  • Next Page

Related Article

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.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.