Skip to main content

OEM 13C Installation fails pre-requisites are getting failed in REDHAT 6.8

We are installing OEM13C in REDHAT 6.8 and pre-requisites are getting failed due to the non-certified version.

The certification information on My Oracle Support lists Red Hat Enterprise Linux 6 as a certified platform for "Enterprise Manager Base Platform - OMS 13.1.0.0.0". The certification information does not list any specific version of Red Hat Enterprise Linux 6, such as 6.1, 6,2, 6,3, 6,4, 6.5, 6.6, 6.7, etc., it only says "Red Hat Enterprise Linux 6".

However the EM 13.1 installation process doesn't recognize 6.8 as a certified version of RHEL 6. The error from the installer is shown below. The installer will not allow this to be skipped so the install can continue.

 



13.1 EM install does not support on RHEL6.8. This is taken care in next release of 13c OEM.

For 13.1 EM the following documentation bug is logged to get the OTN document updated with this information:
Bug 23328216 - 13c EM install on RHEL6.8 Fails

Workaround:

Once the GUI starts, check the /tmp directory where you will find something like /tmp/OraInstall<timestamp>/stage/prereq
Duplicate one of the sections under the OPERATING_SYSTEM tags and change the version to 6.8. Save it and then continue the install.


Good News is OEM 13.2 Released but Documentation not yet released.

-Anil12cdba
Labels:

Comments

Post a Comment

Popular posts from this blog

ORA-65139: Mismatch between XML metadata file and data file

Error: CDB$ROOT@EBTUPRDC> CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse; CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse * ERROR at line 1: ORA-65139: Mismatch between XML metadata file and data file /u05/odb/ORADATA_1/EBTUSPRDC/datafile/system.1531.807800993 for value of fcpsb (2230502002 in the plug XML file, 2230505492 in the data file) Fix: Don't open Non-CDB database until we complete pdb creation other wise we will get above error. Shutdown immediate; startup mount; alter database open read only; create xml file. shutdown immediate; Connect to CDB and Create Pluggable database .
2 comments
Read more

Useful OEM Queries to get Target details from OEM Repository

List Targets with TNS Listener ports configured : SELECT mgmt$target.host_name , mgmt$target.target_name , mgmt$target.target_type , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$target.target_name = mgmt$target_properties.target_name ) AND ( mgmt$target.target_type = mgmt$target_properties.target_type ) and ( mgmt$target.target_type = 'oracle_listener' ) and ( mgmt$target_properties.property_name = 'Port' ); Devora02       LISTENER_ora02                       oracle_listener Port 1529 Devora01       LISTENER_ora01                       oracle_listener Port 1529 Devora04       LISTENE...
1 comment
Read more

TFA-00002 : Oracle Trace File Analyzer (TFA) is not running

TFA Failed to start listening for commands on one of the Rac Node : As a root user /etc/init.d/init.tfa  start Starting TFA.. start: Job is already running: oracle-tfa Waiting up to 100 seconds for TFA to be started.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Successfully started TFA Process.. . . . . . TFA-00002 : Oracle Trace File Analyzer (TFA) is not running TFA Failed to start listening for commands Solution : run synctfanodes.sh  if you have root password . if no root password copy below files to TFA Failed node and try to restart TFA .. Please check whether these 4 files exist on all nodes are similar. TFA_HOME/server.jks TFA_HOME/client.jks TFA_HOME/internal/ssl.properties   TFA_HOME/internal/ portmapping.txt If not similar just copy these files to TFA Failing node and try TFA Restart ..It Worked for me .   [root@host01]# ./tfactl  -v "debug" start Starting TFA...
Post a Comment
Read more