askMLabs

• Oracle Virtualization Plug-in
• Oracle ZFS Storage Appliance Plug-in
• Fusion Middleware Plug-in

• Need to import the Oracle Enterprise Manager Ops Center Certificate to the agent keystore

[root@elxxxx-vm ~]# JAVA_HOME=/u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.4.0/jdk
[root@elxxxx-vm ~]# export PATH=$JAVA_HOME/bin:$PATH
[root@elxxxx-vm ~]# which java
/u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.4.0/jdk/bin/java
[root@elxxxx-vm ~]# cd /etc/opt/sun/cacao2/instances/oem-ec/security/jsse
[root@elxxxx-vm jsse]# ls -lrt
total 16
-rw-r--r-- 1 root root 2064 Jun 23  2015 keystore
-rw-r--r-- 1 root root 1014 Jun 23  2015 agent.cert
-rw-r--r-- 1 root root 1658 Jun 23  2015 truststore
-rw-r--r-- 1 root root 1658 Jun 23  2015 truststore_gf
[root@elxxxx-vm jsse]# $JAVA_HOME/jre/bin/keytool -list -keystore /u01/app/oracle/product/12.1.0/agent12c/agent_inst/sysman/config/montrust/AgentTrust.jks
Enter keystore password:
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 9 entries
..
...

[root@elxxxx-vm jsse]# pwd
/etc/opt/sun/cacao2/instances/oem-ec/security/jsse
[root@elxxxx-vm jsse]# $JAVA_HOME/jre/bin/keytool -export -alias cacao_agent -file oc.crt -keystore truststore -storepass trustpass
Certificate stored in file <oc.crt>
[root@elxxxx-vm jsse]# ls -lrt
total 20
-rw-r--r-- 1 root root 2064 Jun 23  2015 keystore
-rw-r--r-- 1 root root 1014 Jun 23  2015 agent.cert
-rw-r--r-- 1 root root 1658 Jun 23  2015 truststore
-rw-r--r-- 1 root root 1658 Jun 23  2015 truststore_gf
-rw-r--r-- 1 root root  706 Feb 18 10:51 oc.crt

[root@elxxxx-vm jsse]# cd /u01/app/oracle/ovm-manager-3/
[root@elxxxx-vm ovm-manager-3]# ls -lrt
total 32
drwxr-xr-x 5 oracle dba  4096 Feb 17  2014 ovm_shell
drwxr-xr-x 3 oracle dba  4096 Jun 22  2015 machine1
-rw-r----- 1 oracle dba    92 Jun 22  2015 ovm_console_configuration.properties
drwxr-xr-x 2 root   root 4096 Jun 22  2015 bin
-rw-r--r-- 1 root   root 1369 Jun 22  2015 ovmmCoreTcps.ks
drwxr-xr-x 7 oracle dba  4096 Jun 23  2015 ovm_upgrade
drwxr-xr-x 4 oracle dba  4096 Jun 23  2015 weblogic
drwxr-xr-x 9 oracle dba  4096 Jun 24  2015 ovm_cli
[root@elxxxx-vm ovm-manager-3]# ls -lrt /u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.3.0/jdk/bin/keytool
[root@elxxxx-vm ovm-manager-3]# ls -lrt /u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.4.0/jdk/bin/keytool
-rwxr-xr-x 1 oracle dba 51979 Mar 12  2013 /u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.4.0/jdk/bin/keytool
[root@elxxxx-vm ovm-manager-3]# /u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.4.0/jdk/bin/keytool -keystore ./ovmmCoreTcps.ks -exportcert -alias ovmm -file ovmm.cr
Enter keystore password:
*****************  WARNING WARNING WARNING  *****************
* The integrity of the information stored in your keystore  *
* has NOT been verified!  In order to verify its integrity, *
* you must provide your keystore password.                  *
*****************  WARNING WARNING WARNING  *****************
Certificate stored in file <ovmm.cr>
[root@elxxxx-vm ovm-manager-3]# ls -lrt
total 36
drwxr-xr-x 5 oracle dba  4096 Feb 17  2014 ovm_shell
drwxr-xr-x 3 oracle dba  4096 Jun 22  2015 machine1
-rw-r----- 1 oracle dba    92 Jun 22  2015 ovm_console_configuration.properties
drwxr-xr-x 2 root   root 4096 Jun 22  2015 bin
-rw-r--r-- 1 root   root 1369 Jun 22  2015 ovmmCoreTcps.ks
drwxr-xr-x 7 oracle dba  4096 Jun 23  2015 ovm_upgrade
drwxr-xr-x 4 oracle dba  4096 Jun 23  2015 weblogic
drwxr-xr-x 9 oracle dba  4096 Jun 24  2015 ovm_cli
-rw-r--r-- 1 root   root  601 Feb 18 10:55 ovmm.cr
[root@elxxxx-vm ovm-manager-3]# echo $JAVA_HOME
/u01/app/oracle/product/12.1.0/agent12c/core/12.1.0.4.0/jdk
[root@elxxxx-vm ovm-manager-3]# $JAVA_HOME/jre/bin/keytool -list -keystore /u01/app/oracle/ovm-manager-3/ovmmCoreTcps.ks
Enter keystore password:
*****************  WARNING WARNING WARNING  *****************
* The integrity of the information stored in your keystore  *
* has NOT been verified!  In order to verify its integrity, *
* you must provide your keystore password.                  *
*****************  WARNING WARNING WARNING  *****************
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 1 entry
ovmm, Jun 22, 2015, PrivateKeyEntry,
Certificate fingerprint (MD5): XXXXXXXXXXXXXXXXXXXXXXX
[root@elxxxx-vm ovm-manager-3]#

[oracle@elxxxx-vm ~]$ $AGENT_HOME/bin/emctl secure add_trust_cert_to_jks -trust_certs_loc /u01/app/oracle/ovm-manager-3/ovmm.cr -alias ovmm
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Password:
Message   :   Certificate was added to keystore
ExitStatus: SUCCESS
[oracle@elxxxx-vm ~]$
[oracle@elxxxx-vm ~]$ $JAVA_HOME/jre/bin/keytool -list -keystore /u01/app/oracle/product/12.1.0/agent12c/agent_inst/sysman/config/montrust/AgentTrust.jks
Enter keystore password:
Keystore type: JKS
Keystore provider: SUN
Your keystore contains 11 entries
...
..

[root@elxxxx-vm ovm-manager-3]# cat /var/exalogic/info/em-context.info
ExalogicID=Oracle Exalogic X2-2 AK00000000
[root@elxxxx-vm ovm-manager-3]# cd /u01/app/oracle/ovm-manager-3/ovm_shell
[root@elxxxx-vm ovm_shell]# /opt/sun/cacao2/bin/cacaoadm get-param jmxmp-connector-port -i oem-ec
jmxmp-connector-port=11172
[root@elxxxx-vm ovm_shell]#

[oracle@elxxxx-vm ~]$ $AGENT_HOME/bin/emctl stop agent
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Stopping agent ..... stopped.
[oracle@elxxxx-vm ~]$ $AGENT_HOME/bin/emctl start agent
Oracle Enterprise Manager Cloud Control 12c Release 4
Copyright (c) 1996, 2014 Oracle Corporation.  All rights reserved.
Starting agent ......... started.
[oracle@elxxxx-vm ~]$ cd /u01/app/oracle/ovm-manager-3/ovm_shell
[oracle@elxxxx-vm ovm_shell]$ sh ovm_shell.sh  --url=tcp://localhost:54321 --username=admin --password=**********
OVM Shell: 3.2.8.733 Interactive Mode
>>> from com.oracle.ovm.mgr.api import *
>>> from com.oracle.ovm.mgr.api.event import *
>>> from com.oracle.ovm.mgr.api.virtual import *
>>> from com.oracle.ovm.mgr.api.physical import *
>>> from com.oracle.ovm.mgr.api.physical.network import *
>>> from com.oracle.ovm.mgr.api.physical.storage import *
---
>>> ovm = OvmClient.getOvmManager ()
>>> f = ovm.getFoundryContext ()
>>> j = ovm.createJob ( 'Setting AK000000000' );
>>> j.begin ();
>>> f.setAsset ( "EXALOGIC_ID", "AK000000000");
'AK000000000'
>>> j.commit ();
>>>
[oracle@elxxxx-vm ovm_shell]$

• You need to deploy the necessary plug-ins required for the monitoring capabilities of the softwares that you will be installing on vServers like Weblogic Servers, Webcenter , OTDs , Peoplesoft etc ...
• You can install "Oracle Engineered System Healthchecks" plug-in and configure the targets to perform the exalogic health checks.

• Two primary ODAs with 12.1.0.4 OEM 12c installed - At PDC
• Two secondary ODAs with 12.1.0.4 OEM 12c (Standby with ASM replication from primary for OMS binaries) - At SDC
• Database and Grid are on 11.2.0.3
• Oracle Database is two instance RAC both on primary and secondary
• ODAs are with old control version (oakcli)

• The secondary datacenter SDC will be replaced with a third datacenter TDC. So we got new ODAs and they are stacked and installed at new datacenter. These ODAs are called toda01 and toda02. The next step is to create a new standby database at TDC with primary database at PDC.
• Grid software will be 12.1.0.2.
• Database software will be 11.2.0.3 and 12.1.0.2 ( Need to install both the binaries, so that the latest version can be used for database upgrade)

• In this step, we are going to create a new standby database TOEMDB for the primary database POEMDB. At this point of time, we have  two standby databases up and running. We need to make sure that the archive logs are shipped to both the standby locations. Once the second standby database is created, we need to prepare the toda's for the OMS creation.

• Now the standby setup for database at SDC can be disabled. Need to remove all the configurations for SDC standby database at primary database running at PDC.
• Now primary database is at PDC and One Standby Database is at TDC. Primary OMS is at PDC and Standby OMS is at TDC.
• DNS ( loadbalancer ) updates need to be done to reflect the new ODAs at TDC. All the references for ODAs at SDC should be removed from DNS and loadbalancer.

• The OEM setup looks as shown above after completely replacing the SDC datacenter ODAs with TDC ODAs.

• Rack and stack the ODAs at FDC.
• Database with version 11.2.0.3 and 12.1.0.2
• Grid wit h12.1.0.2 version.

• Swith the roles of the OEMs at PDC and TDC.
• Once the OEM at PDC is standby, we can repeat the same steps from 1-7.

• When the ODAs at PDC are replaced completely with new ODAs, we can switch back the roles. So that, ODAs at PDC will run the primary OEM and PDAs at TDC will run the standby OEM.