Asset ID: |
1-72-1550243.1 |
Update Date: | 2016-06-21 |
Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1550243.1
:
ODA DBconsole aka DBControl fails during attempts to install on the Oracle Database Appliance : Using Configurator, manually or commandline emctl
Related Items |
- Enterprise Manager for Oracle Database
- Oracle Database Appliance Software
- Enterprise Manager for Oracle Database
- Oracle Database Appliance
|
Related Categories |
- PLA-Support>Eng Systems>Exadata/ODA/SSC>Oracle Database Appliance>DB: ODA_EST
- _Old GCS Categories>ST>EM>Managing Oracle Database>DBControl>EMCA
|
Several problems have been encountered when attempting to install DBConsole / DBControl on ODA : this note describe diagnostic suggestions, places to look and fixes
In this Document
Applies to:
Oracle Database Appliance - Version All Versions and later
Enterprise Manager for Oracle Database - Version 12.1.0.2.0 to 12.1.0.3.0 [Release 12.1]
Enterprise Manager for Oracle Database - Version 11.1.0.7 to 11.2.0.4 [Release 11.1 to 11.2]
Oracle Database Appliance Software - Version 2.1.0.1 to 2.10.0.0
Information in this document applies to any platform.
ODA Install GridInst.pl , emctl , enterprise manager, dbconsole , dbcontrol, Configurator, Step 20l
Symptoms
While attempting to install DBConsole aka DBControl on ODA:
- you have multiple failures
- unable to install manually **
- unable to install running steps
- unable to install using a deployment
EM DBConsole (also know as DBControl) has been replaced in database 12.x versions with EM Express
** COMMENT: This note is regarding a niche problem on the ODA which we have seen more than a few times:
There are excellent notes on Manual installation and deinstallation for DBControl aka DBConsole you should be aware of:
NOTE:278100.1 - How To Drop, Create And Recreate the Database Control (DB Control) Release 10g and 11g
Note 578011.1 - How to manage DB Control 11.x for RAC Database with emca
Note 1377211.1 - When to Use the Create/Drop Dbconsole Commands which are Given in Note:278100.1.
Changes
New or relatively new usage:
- The failure to create DBConsole can occur during the very first deployment
- This problem can also occur after a deployment which skipped the installation of DBConsole option
- The problem can actually be seen after a successful deployment (not recommended)
Cause
ODA Dbconsole steps can fail many ways and places:
- Can be associated with the first attempt to install EM / DBconsole
- Can be associated with the removal of an instance after the installation of DBConsole
- Can be associated with RACone**
this _might_ be a variation of the removal of one instance problem: i.e. the failure is not due to RACone, but how RACone and DBConsole was installed
- MISMATCHED or Mixed Case for Node Names between various locations required for a normal installation
Solution
One possible Solution
Re-configure the ODA with the bare metal image, and use lower case letters in the hostname.
The installation is completed without problems, and the EM-console for the database runs correct.
For Support
Track bugs similar to the following for current workarounds, fixes or basic problem diagnosis steps
- e.g. bug 16450280
Did the customer ever remove an instance on either node?
Did they attempt to install EM while one instance or node was down
Have they manually made any changes to various files associated with Node names
Here are some places and diagnostic steps you might find useful
from our env:
@ # grep DBCONTROL_HTTP_PORT test.log
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT.
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT_<node1>.
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT.
@ CONFIG:
@ /u01/app/oracle/product/11.2.0.3/dbhome_1:<node1>.us.oracle.com:<node1>:rac1te
@ st:{}:null:{DBCONTROL_HTTP_PORT=1158, RMI_PORT=5520, JMS_PORT=5540,
@ AGENT_PORT=3938}
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT_<node1>.
@ CONFIG: Setting param: DBCONTROL_HTTP_PORT_<node1> value: 1158
@ CONFIG: Ports assigned for Node: <node1> : {DBCONTROL_HTTP_PORT=1158,
@ RMI_PORT=5520, JMS_PORT=5540, AGENT_PORT=3938}
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT_<node2>.
@ CONFIG: Setting param: DBCONTROL_HTTP_PORT_<node12> value: 1158
@ .
@ from bug:
@ .
@ $ grep DBCONTROL_HTTP_PORT test.log
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT.
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT_DC1ODA01P1.
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT.
@ CONFIG:
@ /u01/app/oracle/product/11.2.0.3/dbhome_1:DC1ODA01P1.corp.firstrepublic.com:DC
@ 1ODA01P1:wingspan:{}:null:{DBCONTROL_HTTP_PORT=1158, RMI_PORT=5520,
@ JMS_PORT=5540, AGENT_PORT=3938}
@ CONFIG: No value was set for the parameter DBCONTROL_HTTP_PORT_DC1ODA01P1.
@ CONFIG: Setting param: DBCONTROL_HTTP_PORT_DC1ODA01P1 value: 1158 <<< UPPER case hostname
^^^^^^^^^^
"...We re-configure the ODA with the bare metal V2.6.0.0.0 image, and use lower case letters in the hostname.
The installation is completed without problems, and de EM-console for the database runs correct.
Thank you for the solution !
This SR can be closed, and please update bug 16450280 with this solution.
Possible references of interest include
References
<NOTE:278100.1> - How To Drop, Create And Recreate the Database Control (DB Control) Release 10g and 11g
<NOTE:578011.1> - How to manage DB Control 11.x for RAC Database with emca
<NOTE:1377211.1> - When to Use the Create/Drop Dbconsole Commands which are Given in Note:278100.1
<BUG:16450280> - ODA RACONE CONFIGURATION FAILS AT STEP 21 (DBCONSOLE)
<NOTE:1496134.1> - ODA (Oracle Database Appliance): HowTo Configure EM Database Control (DB Console) After Installation
Attachments
This solution has no attachment